Hubert Cater

Can you tell me what sound card and driver version you have running on your system?

Can you find the ERROR folder in your Global Conflict installation directory and send me the Error.sav file at support@furysoftware.com? This or the autosave.sav with instructions on how to repeat it will help me track it down. Thanks, Hubert

Thanks for posting this xwormwood and thanks to Mr. Langer for such a detailed review Hubert

Thanks richmi and not to worry in that SC Global Conflict is pretty much the end result of an almost additional 4 years of development. Long story short the game will provide much more of a challenge than the global campaign that was released with SC2 Blitzkrieg

csh1160, welcome to the SC series and for the Nupremal Mod, it can be found in the Battlefront Repository found here: http://www.battlefront.com/index.php?option=com_remository&Itemid=314&func=select&id=33&orderby=2&page=2

Glad to hear it gentlemen

Just a quick update that I believe this one is now resolved and should be a part of the next patch. Hubert

I think we've done this now a few times!

1. I'd have to see the turn in question to know for sure if it is a glitch or not, do you happen to have it so I cold take a look? 2. This would indeed be the normal behaviour 3. If the US and the UK do not share a common enemy this would be an error which would have been corrected with the first patch, but if they do share a common enemy then this is possible. If not then it may be another possible bug but I would have to see the turn in question to know for sure. 4. It would be helpful to know if this was before or after the US became fully mobilized. If it is prior to full mobilization then when the US Navy leaves this area it does reduce its readiness which can be very important during Multiplayer games as it would delay US entry. If however the Axis player declares war against the Philippines or the US itself then this is moot but at that point it is more the choice of the Axis player etc. Does this not apply in your game? 5. I'd argue that this would not be too ahistorical or unrealistic

Very odd, you don't happen to have the saved turn from when this occurred so I could repeat it and take a look? If so send to support@furysoftware.com Hubert

Hi Mabus77, Sounds like you are probably running Vista/Windows 7. If this is the case these operating systems are a bit picky with how they treat files created within the Program Files folder. What you will have to look for is a button in your installation directory in the top right corner called 'Compatibility Files'. If you click on this it will take you to the virtual folder where these files are stored. Here is a link with more info on what Windows is doing and why: http://www.hanselman.com/blog/VistasShowCompatibilityFilesAndTheScrumptiousWonderThatIsFileVirtualization.aspx Hope this helps, Hubert

Thanks Fred, I will take a look and see if I can track this down.

Looks like an error regarding the #VARIABLE_CONDITION where it was implemented in the Editor but not in the game EXE. The date field should be working as it is treated as a FAILSAFE, i.e. if the #CONDITION_POSITION does not satisfy the event, the event will still fire on or after the #DATE specified. For the #VARIABLE_CONDITION error, the game simply does not read this condition, i.e. it will always fire regardless of the value set, and I will correct this for the next patch. Sorry about that, Hubert

Can you try now?

Crispy if you ever encounter this type of error please send me the saved game file that causes the crash as I will be happy to correct the issue. If you still have it send it to support@furysoftware.com Thanks! Hubert

Sorry about this as I found the issue. Not sure how this slipped through the cracks but it looks like the updated Editor was not included with the latest patch. For now once you've applied the patch and if you want the latest Editor you can download it from here and I'll send it to Battlefront as well so we can have it available as an official hotfix as soon as possible: http://www.furysoftware.com/download/Editor-WWII_Global_Conflict.zip Once you download it simply decompress it and place it in your Global Conflict installation directory and it should work as expected.

I suspect that since I had submitted several single EXE updates to the Beta group it did not show up as a problem from the test installers.

Sorry about this as I found the issue. Not sure how this slipped through the cracks but it looks like the updated Editor was not included with the latest patch. For now once you've applied the patch and if you want the latest Editor you can download it from here and I'll send it to Battlefront as well so we can have it available as an official hotfix as soon as possible: http://www.furysoftware.com/download/Editor-WWII_Global_Conflict.zip Once you download it simply decompress it and place it in your Global Conflict installation directory and it should work as expected.

Very odd, can you tell me what the error might be and or more details on the issue in general?

Attila, Please send a support ticket to the helpdesk link found below and they should be able to sort it out for you: http://www.battlefront.com/helpdesk Hubert

Ah yes I think the wording was edited a bit for the first patch as it was a bit confusing, here is the wording as found in the latest version for the campaigns: "British War Office David Margesson The French cruiser "Emile Bertain" and the aircraft carrier "Béarn" arrived safely in Fort de France with 480 MPP in gold from the Banque de France. This gold belongs by right to the Free French Government in exile. We could try to seize this gold by invading Fort de France, but doing so will probably lead to war with Vichy France, and possibly with some other French colonies. On the positive side, our agents believe that doing so may swing the French garrison in Polynesia to switch its allegiance to the Free French. On the other hand, if we don't agree to invade Fort de France then we will lose out on an opportunity to capture not only the gold but also the French ships. However, the good news is that under the terms of the "Greenslade-Robert Agreement", if we don't invade Fort de France then the USA will provide us with immediate credit worth 125 MPPs, though the US may later intern the gold and seize ships for themselves. Shall we leave the gold for the US Government to intern (YES) or shall we invade Fort de France (NO)?" Essentially the answer is yes, you would have to invade it as the Allies by Declaring War.

Great to hear and definitely don't be shy about spreading the word either

And thank you for your help on this patch as well

I think this was mostly a legacy to the older UNIT script system where we simply had a failsafe date but now it can be used as a way of reminding the scripter that we are simply relying on the failsafe date and not the condition positions etc.

Hi Akiva, No problem at all and I just re-read that section of the review and you are right, it does make it sound much worse that it actually was when the only correction, based on the review, was to page 89 and a slight reorganization of 2 paragraphs. Either way glad to hear you purchased the game Hubert