ERROR FAILED(draw_working_text_to_screen)

[CaesarAug]

I'm still getting occasional map-sync issues again but have only just realised this ERROR folder which contains the following code:

[2024-01-31 14:01:33 PM; 6.2.9200; 1920x1080x32(0); SC3: WWII World at War] FAILED(draw_working_text_to_screen):

I can tell right away something is wrong when the 1939 "World World II begins" notification screen does not appear on the game map. Or if it does (as expected) pressing Enter or Space bar does not close that notification (as it normally does) but opens the War Maps instead. In such cases, only left-clicking the mouse will make the "World War II begins" notification close. Same thing occasionally happens with other notification screens when the other side's turn begins. Really odd stuff...

I don't understand what it means and have no idea what's causing this. Never happened on Parallels Desktop for Mac gaming, but is coming up on a new Windows 11 Pro Intel i9 computer. Could this be a new bug with the latest updates? And/or something related to the editor? Thanks for any help!

[Illiniwek80]

I get the segmentation error a lot. Used to get it on an allied paradrop in Europe occasionally; yesterday I got it after monkeying around with Peru to see what I could do with it.

[CaesarAug]

Segmentation error? Interesting. Does this happen with the latest WaW 1.19.00 patch or has it occurred to you with previous patches?

EDIT! I wanted to reply here but inadvertently ended up "reporting" your post! Oops, sorry about that! Thanks for posting!
Moderators, please disregard my accidental "reporting" since I wanted to make a reply and hit the wrong button!

[Illiniwek80]

Ha ha... ok! I have been getting the segmentation error since first launch. It seems to happen when allied paratroops drop next to a river in France. Yesterday it seemed to happen when moving troops around fruitlessly in Peru.

It used to keep recurring, and the only way I could resolve it was to temporarily switch sides to Allied and move that paratroop unit in England once so it could no longer drop onto the problematic hex in France. Used to happen to me every other game or so, a regular occurrence.

[CaesarAug]

What does "segmentation error" mean? Did you get what I call "map-sync" issues, like attacks and explosions out of sync, for example? Or certain notification screens that do not close properly with the enter or space bar being pressed?

[Illiniwek80]

No, I don't get your issue. I only mention my issue because it has something to do with the map, generally speaking.

What does it mean? I dunno, I just come here to kill things.

[Hubert Cater]

Hi guys, can you try updating your video and sound card drivers to see if this helps?

Is it repeatable on a different PC, e.g. if you happen to have access to one. This just helps to narrow down if it is your particular PC or a general issue.

If there is ever a repeatable error, e.g. one that can happen in a repeatable way with instructions on how to repeat it, please don't hesitate to send me an error save file to support@furysoftware.com as it is the best way for me to track down and correct the issue.

For segmentation errors, that is just a general message that an error has occurred, but typically there can be a variety of reasons for that type of error.

Hubert

[CaesarAug]

Thank you, Hubert. I did consider video and sound driver updates. I even rolled-back to the original manufacturer video drivers to see if the newer Intel drivers by chance were the issue. But no, the same map-sync problem persisted. So I did a clean video driver reinstallation with Intel’s latest so in that sense I am up-to-date again. My sound drivers are likewise up-to-date. I am using FXSound to boost audio performance on the desk speakers, and it’s working just fine in general, so I don’t think this app has anything to do with this.

The thing that puzzles me is that the problem is not consistent. That is, sometimes it happens, and then it mysteriously resolves itself, usually after a system restart. But at some time, the problem just as mysteriously reappears, though my impression is that it comes back after using the editor. I notice too sometimes that when I open the editor, I get an occasional “not responding” message, though it always opens anyway and is usable. I also get the impression that when the editor opens normally, the game plays normally as well. And vice-versa.

It finally occurred to me to try making the editor, main game and launcher .exe files compatible with Windows 7 and to run as Administrator. Surprisingly, the problem seems to have disappeared. But of course I will continue to test as I have been testing until now, to see if the problem reappears again. I’ll report back here. Here’s hoping…

[CaesarAug]

Well, well, in my preliminary play-testing with the new adjustments to run the SC games in Windows 11 Pro with compatibility for Windows 7, the strange, intermittent map-sync issues I had been seeing do seem to have disappeared altogether! And they have not reappeared so far.

I’m also noticing that the game editors open as expected, they’re just as usable as they should be, and also when making changes to the scripts, these are updating without the hiccups I was also experiencing before, along with the map-sync issues.

So it is looking good! A very simple and quick fix: making the SC editor .exe, main game .exe and launcher .exe files run as Administrator and with compatibility with Windows 7. How about that!

[Hubert Cater]

Great to hear that workaround worked for you