So ive tried to play FOC online with an friend who has the non steam version of the game, but i dont really know that this is the main reason this isnt working, for the last 2 days, the normal EaW without addon does work perfectly fine with both gameranger and tunngle. But in FoC we just cant see each other or join the game of the other in gameranger.I already tried a few Methods i found online:1. Tried this Fix with the RAM-Patch for FoC2. Tried to synchronize via this program3.
This Fix from the stargate eaw team:' You are using the Multiplayer 'Fix'. Due to a recent server change by LucasArts the 'fix' is currently the reason for the freeze - without it, it works just fine. To delete the fix, simply open.LucasArtsStar Wars Empire at War Forces of CorruptionDataXML and delete the file 'GameConstants.xml'. 'from here:Just dont know what to do anymore:(. Originally posted by Cabcoke:So ive tried to play FOC online with an friend who has the non steam version of the game, but i dont really know that this is the main reason this isnt working, for the last 2 days, the normal EaW without addon does work perfectly fine with both gameranger and tunngle. But in FoC we just cant see each other or join the game of the other in gameranger.I already tried a few Methods i found online:1. Tried this Fix with the RAM-Patch for FoC2.
Tried to synchronize via this program3. This Fix from the stargate eaw team:' You are using the Multiplayer 'Fix'. Due to a recent server change by LucasArts the 'fix' is currently the reason for the freeze - without it, it works just fine. To delete the fix, simply open.LucasArtsStar Wars Empire at War Forces of CorruptionDataXML and delete the file 'GameConstants.xml'. 'from here:Just dont know what to do anymore:(I know how to fix this, it is because Retail FoC is by default uncompatible with Steam Foc.
Here is a link to the fix that your friend needs to perform. Originally posted by:I already wrote that we did this step, and it did not help, but the solution i found did:)I think that the patch that is linked in the forum just is the wrong patchIt is NOT the wrong patch. Did your friend follow my instructions? The RAM patch WILL NOT induce compatibility if there are ANY fsaves prior to applying the patch. The method works. AND it can only be applied to a retail game. Since it is already included in the Steam release.The forum post on retakeeaw is written by me, JSYK, as well as the 3rd solution you tried - however solution 3 was for a different problem - not for Retail to Steam connectivity.
Originally posted by:Yes he follewed it, but what we saw was that the patch in the post didnt patch both eaw and foc (like written there), while the disneyforum one did, well its running now, despite we had a 'Synchronization Error' after 15 min in our first match:)Hmm, well I should test that. No reason why it shouldn't, since the RAM fix itself was INCLUDED with the lobby freeze update (the one that includes those 2 xml files that are installed). Perhaps for whatever reason the filefront download does not include both, however I had that link in there because the previous one from Lucasarts was not working when they shut down. Guess disney finally got that part of the site up again, so I shall change the link once more. Thanks for pointing that out.