Matrix Games Forums

I bought the Steam version of the game a couple weeks ago, having owned the Battlefront version earlier, and it's mostly been working fine, but now I ran into the same problem as apparently some others have had years ago. With me it came playing as the Axis, and trying to deploy a new Japan garrison unit.

The problem persist in different saved games (atleast the ones where that unit has already been purchased in the earlier turn), so even if I run the end turn again from the previous turn, it gives the same error on the next turn with the same purchased unit: Error: FAILED(draw_unit_layer_to_buffer), and then crashes to desktop. Game version in main menu is v1.10.00 (Steam version).

I didn't originally have any mods installed when this happened, and after I've tried changing in-game graphic resolution, enabling and disabling a few in-game graphic mods (Iron_Cross_Mod_v4-4, SIPRES NATO Counter Mod), verifying integrity of game files in Steam's game properties, turning off Steam cloud saves, deleting the whole game settings directory (C:\users\<user>\documents\My Games\Strategic Command WWII - World At War), rebooting, disabling 3D models, uninstalling and reinstalling etc, but nothing I can think of helps.

Is there a fix for this I haven't found, should I send my savegame files and dxdiag info (+something else?) to some support email address, or what's the procedure on this?

Hi KptnKaaos,

Thanks for the report and this is indeed a strange one as I haven't been able to repeat it on my end. It also only seems to happen on very few systems which makes it harder to track down and correct as it is not a consistent error.

However I believe I may have found the issue which is the good news. Unfortunately it can only be tested/verified on a system where this is repeatable like yours.

Could you send me an email at support@furysoftware.com?

Hubert

I've run into this intermittently and a work round I found on these forums (which I can't find now of course) was/is to press CANCEL rather than OK at the beginning of the turn when the units are first presented. Having made a few moves one can hit the New Unit tab and deploy without the crash.

Fluidwill Matrix,

Thanks for the reply. I noticed the same when I tried a test version provided to me. First I thought it was the test version doing it's magic, but after I doublechecked with the original game version, it worked with that too. Thing is, I could almost swear it didn't work when I first had this problem. I mean, it's almost the first thing to try in troubleshooting. Nevertheless, at the moment that work around does the job.

Hi Kptn/Hubert, see if the error happens in both the zoomed-in view and the zoomed-out view. I had this problem just yesterday with WiE. On turn 2, I'd get that error/crash when I tried to activate any German HQ. I tried most of the same troubleshooting KK described above with no luck, but I somehow thought to try switching the view from zoomed-in to zoomed-out, I was able to move the HQs. After that turn, I haven't had the problem again in either view.

FWIW I had just downloaded the most recent WiE update and was playing the version for the first time. 1939 Naval War 3.3 campaign. Was on PC app, not Steam.

Hope that provides some kind of clue for you. -GB1

Also Hubert I just noticed the thread on WiE discussing the same issue I had -- I should add that I was using the Iron Cross/Historical Flags Combined Mod.

Hi Georgiabulldog1,

Thanks for the info and there was an issue that required an update to the Iron Cross mod as we had changed some graphics and this issue would specifically occur when clicking on HQ units.

If you try this same action without the Iron Cross mod and it doesn't crash then this would confirm it.

The best thing to do is to update the Iron Cross mod to the latest and it should resolve the issue for you.

Hope this helps,
Hubert

Hi again Hubert, FWIW I figured out that the problem is with "historical flags/knights cross" combined mod. I suppose that mod doesn't have the most recent version of Iron Cross mod in its combination, thus the error. As you said, the updated IronX mod by itself resolves the issue. Thanks! -gb1