benu

Need more input... Which version do you have? Goty patched to v1.94? Maybe the server was locked? Did you select a server without password which is running a compatible version? 1.92-1.94 can play together, 1.85-1.91 can play together, but they can't mix.

I did exactly that the last time i played. My helicopter was hit, engine went dead, i crash-landed it and got out. I then asked my teammates to bring a repair truck and took off again.

Afaik you can't force vet mode with server settings, but you can set cadet mode to the same settings, ie turn everything off. And afaik you can change maps to only run in vet mode, so they will not work in cadet mode. But the first solution is the better one imho. What else may be of interest: In flashpoint.cfg you can set the max allowed size of sound and face files that players can upload: MaxCustomFileSize="61440"; In the server.cfg you can set stuff like this: checkfiles[]= { "res\dta\hwtl\merged.pbo", "res\dta\data.pbo" }; kickDuplicate="true"; to check for modifed merged.pbo and data.pbo and to kick players using duplicate serials on your server. There is also the possibility to set up mod folders for servers and to force players to use exactly the same modfolder setup as the server with the equalModRequired command.

OFP Watch ASE

My version (ofp 1.00/eu and resistance) can select english, french, italian, spanish and german as language.

Did you change anything, like putting them into modfolders?!? WHERE?! lol Actually, i said OFP Watch is a serverbrowser that automatically downloads and installs the addons you need to play on a server, if the server supports that tool (auto-addon server). Our server does this. So you start ofp watch, select GDT server in the server browser and click on the "[GDT] RTS3 v1.1 fix" package (5.5mb). @CannonFodder: the server was up all the time, but i did some changes to dns, so maybe it was not reachable while the changes propagated through the net

It will work, it will not cause fade or any other problems in mp (as the resistance key is not even used there) and the legal consequences (if any) vary from country to country (ie it would be perfectly legal here).

To answer the original question: So you could install 3 times from the goty cds, using your goty key and your two cwc keys. Or you could goty once, and both cwc and install resistance on both of those two installations.

Afaik red hammer patches the game to version 1.30. And i never needed to play cwc again (at least with the cwc executable) after i bought resistance.... I just tried to install my goty version with my cwc key and it worked. As i guessed. CWC and GOTY keys are interchangable, resistance keys only matter if you install resistance...

You should check if you have the camel more than once, iirc it was in the bac addon too. Also you should try running ofp with the -nomap parameter. And you should mv 2s19.pbo, 88.pbo and rt3vehicleaddon.pbo to the normal addons folder as they have broken dependencies. This should help with the error messages. The green screen is more graphics card/driver related i think.

I could be wrong but i think only the cwc/goty key is checked for mp playing.

Hi CannonFodder, nice to see you here. As i told you on mapfact our new [GDT] server is online now. We have all RTS3 modern and ww2 addons in the ofp watch, and you can get the fixed addons (2s19.pbo, 88.pbo and rts3vehicleaddon.pbo) from there. I also fixed the the v1.1 missions to not contain the wrong addon dependency on 88.pbo anymore... If you'd like to have those let me know. Everything is organized into modfolders too by the ofp watch addon installer, rts3 modern goes to our gdt modfolder and ww2 goes to the rts3ww2 modfolder.

Although Goldmember really is the one who should fix this (although i could take a look at the addon too), this has not necessarily have anything to do with people using different config.bins. That is correct. As a player you have to press enter, on a dedicated the mission will stop working in most cases. Actually, that's not quite what is happening afaik. In most cases anyway (where totally correct missions stop working due to a corrupt addon). The addon dependencies in ofp work kind of "backwards". So if you build a crater addon that depends on addon "bla" but you do not mark bla as a dependency in your crater addon, then missions using addon bla will get the error message (and not missions using the crater addon). In addition the crater addon is very likely to put itself into any mission you make, making the mission unplayable for people without the crater addon. Incidentally they will get the same error message, although the error comes from a totally different source in this scenario. To give you an example: in the ww2 pack of rt3 the 88.pbo was missing a dependency (on vulcan iirc). This was causing errors in missions that had nothing to with ww2 or rts3, but that were using the vulcan. In ADDITION this caused the 88 to include itself into any mission made while you had the addon activated and so the dependency for WW2 88.pbo ended up in all rts3 v1.1 MODERN missions, which do not even use the 88.pbo. 2 different errors, but the error message is the same. And although both come from the 88.pbo, the first error causes people who DO HAVE the addon to get errors on totally correct missions, and the second causes people who DO NOT have the addon to get the error on missions made by someone with the addon.

I repeat: You get this error from broken addons. You normally get those messages ONLY in missions NOT using the broken addon(s). ADDITIONALLY these addons put themselves in most missions you make yourself, so that everyone NOT using the broken addon will get that error message with any mission you make. Broken addons cause 2 errors: one for ppl having the addon, in missions that do not use that addon, and one for ppl not having the addon in missions made by someone with the broken addon. Believe me, i have fixed enough of that kind of errors on my server to know what i am talking about. Open the crater pbo and look for a line addonsrequired in the cfgpatches section. Compare that to all classes referenced in the addon and look which of those are from "additional" addons (the official ones in res\addons count too, except those which bis preloads in their config.bin). It's exactly the same error, bas_repair depends on the ah64 without declaring that dependendy. All missions using the ah64 (and NOT the bas_repair) will stop working, complaining about a "missing addon bas_repairh". It can be fixed by putting <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">requiredVersion=1.85; requiredaddons[] = {ah64}; into the config.cpp of bas_repair.pbo. Putting the addon into the normal addon folder helps too (but it does not really correct the error).

You get those messages from "broken" addons which have wrong addon dependencies. As written before those addons have the tendency to include themselves automatically in any mission you make, even when you do not even use them in that mission. Also, some of those addons will not work on dedicated servers, except in the addons folder, eg not in a modfolder. The fix is really simply: make the addon at least v1.85 and put all addons it builds upon into requiredAddons[] section of the config.cpp. You would not believe how many addons have this kind of bugs...

All those bin2cpp tools are very unreliable, the results are almost always broken in some case (floats or scientific notation, punctuation). Use a forum search about this. Afaik the only use for tools like this is to look at specific parts, not for changing configs. You could use unpbo 1.3 for this, it made the best results for me. You can get that at ofpec too.

Yeah, but this one is different somehow. The error is definitively somewhere in the modern addons, as it appears even when i am not using ww2 addons. So the 88.pbo seems to get referenced there somewhere. I will do a search through all the files in the next days. And i will check if the error goes away if i take the dependency on bis_resistance out of the rts3vehicleaddon again. Update: i am do dumb I forgot that broken addons (like the 88.pbo) have the habit of including themselves into every mission, even those not containing them... There is no problem with the addons, the problem is that all v1.1 missions have 88.pbo as a dependency in their addons section in the mission.sqm. If you remove it there the mission works again...

I tried it and it causes errors with other missions (missing addon mfcti11) when put into a modfolder. This (put into the CfgPatches section of the config.cpp) seems to fix it: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">requiredVersion = 1.85; requiredAddons[] = {bmp2,su25,ah64,bradley,ch47d};

Try OFPEC.

Which files exactly were changed in 1043? I assume it was either config.bin, ecp.effects.pbo or both but i can't find anything in the readme. Do those fixes affect players who use the dr config.bin? Or does that still have those errors? Is there an updated dr config.bin then? Or did it never have them in the first place? A little more infos would be great... Edit: Whoops, nevermind, i just saw in the readme that the fixes were to the ecp_effects addon...

Fixing that seems to cause another problem: you get "missing addon 88" in modern rts3 missions It seems there are some more dependencies missing, i am looking into it...

I don't think this affects you. Or put another way: if you don't know about the problem it does not affect you Addons with missing dependencies cause problems in some missions where they are NOT used (this makes them so hard to find in many cases). In my case it was the crimson frost mission on winter nogojev which did not start anymore and displayed a "missing addon rts3vehicles" error message. After putting "bis_resistance" into the addon dependencies section the mission worked again.

Lol, i just found out the same, it's the jawa from bis_resistance. I put it into the config.cpp and the error message is gone.

Today i got an error message about "missing addon rts3vehicles" from an old mission on winter nogojev. I am trying to find out exactly where that incompatibility is coming from and will report back if i know more...

Isn't there an even newer version of the spectator script inside the fdf mod?!? How about using that?