@kisak-valve
Just tried new drivers (396.51) and still the same issue. I've also checked out the new Proton 3.7-4 Beta.

same when i try to save the game

Bump? :(
Vanilla game works well , but autosaves and mods still makes the game crash on that error...

Still the same, nothing new.

Tried with GE 5.0, still no change

I am so much looking forward to one of the awesome developers can help fix this - I do not have that type of skills but hope it can get some attention!

I will add that I actually got past the error by deleting the images that cause this error. I don't know what effect it has on the game actual but it is worth noting. I got Star Wars Galaxy at War Mod to play (Mainly in the Editor); but again, I don't know what side effects were introduced if any.

Given that these are images being loaded, there might not be much beyond artifacting or missing textures... I might play around with resolving this error (In Wine since I don't think Proton accepts community submissions??) given I do have programming experience.

I am curious how you got past it - I am all ears :-)
Both on Proton (Steam) and via Lutris (Wine Steam) i tried.
After crash there these 2 files in the save folder:

• preview.jpg (0 kb)
• screenshot.jpg (0 kb)
• status (169 kb)

In the "normal" Windows save folder there are also these:

• preview.jpg
• mission.scn
• map.scn
• game.scn

So for me, deleting the 2 .jpg does not work.
If I at least could delete the .jpgs and launch+continue until next autosave would be an ok workaround (I mean, better than not being able to play :-))

Thanks for your input!
-are two .jpg files (0 kb) in the save folder and a "status"-file. So in my case the files

@CeeWeee I looked up what I did and just realized that the fix I was talking about worked for MoW: AS1. (I haven't tried on 2 =/) I at the time, I had this error with loading the Star Wars mod I mentioned. I can play around my end for MoW: AS2 and see if I have any luck. I vaguely remember maybe editing "scn" files but that could be my mind playing tricks on me. It's been a while since I faced this error. XD

I noticed you mentioned that these are zero byte files. That's interesting... A fix might be to check the size of the file and ignore loading if empty.

I tried to add other .jpg's from Windows save...so that at least these were good. But the problem seems to be that the *.scn files are not saved before the crash...otherwise one could just load from there...

No solution - but I just used PlayOnLinux to download/install the MOWAS (not 2) from GOG.
This works very well including the savegames and previews...
...I wonder if it is either possible to copy that wine setup or install MOWAS 2 in that same repository?
Do you know?

@CeeWeee You could use the terminal and try running MOWAS2 like this:

WINEPREFIX="<MOWAS1 Wine Path>" wine <Path to MOWAS2 Launcher Exe>

:: EXAMPLE FOR ANOTHER GAME / EXE ::

WINEPREFIX="/home/abaddon/.wine" wine "C:\Program Files (x86)\Steam\Steam.exe"

Take note that in my example we are referencing an internal wine path when doing "C:\..." after "wine". In your case, you would change it to a Linux path since MOWAS2 isn't in the "working" wine setup....

I did some tests and there are some findings:

• MoW:AS2 crashes while reading a jpeg or bmp file. This can be worked around by deleting files from game directory or from resource pak files which are simply zip files. It leaves white and gray checker boxes in some menus.
• MoW:AS2 crashes while creating a jpeg. It creates an empty file, but crashes on creating jpeg data. It can be seen while saving a game. It tries to create a screenshot and errors.

It creates a screenshot and preview jpeg files. I copied both from Windows saves and set them to nonwritable. It worked with preview.jpg, it still crashed on screenshot because it couldn't access the file (so different bug, but still means it always tries to create new screenshot).

Interestingly, I deleted a screenshot file from existing Windows save an it was correctly rebuilt while launching a game. Maybe it was from steam cache (although offline steam said it failed to synchronize my game data and the file appeared after game launched), but maybe this jpeg creation works while game is launching, but fails later? Can someone find out what's different in those cases?

Here are log outputs... I generated these quickly by trying to use the editor mode for MoW: AS2.

PROTON_LOG=1 %command%
OUTPUT: steam-244450.log

WINEDEBUG="+timestamp,+pid,+tid,+seh,+debugstr,+module" %command%
OUTPUT: steam-244450-log-type-2.log

RIGHT

I used this script https://gist.github.com/orfibus/dfacf026886b5d27c5c2c2f52df23995
On robs realism
It allows to not crash on bmp / jpeg !
However when i arrive on a map, and then i move the camera, the games HANGS with this (proton_log=1)

7131.701:00c4:00cc:warn:seh:OutputDebugStringA "[18:30:18.919] [0x00CC] failed to join group chat 103582791434422218\n"
7131.701:00c4:00cc:trace:seh:dispatch_exception code=40010006 flags=0 addr=7B00FC38 ip=7b00fc38 tid=00cc
7131.701:00c4:00cc:trace:seh:dispatch_exception info[0]=00000046
7131.701:00c4:00cc:trace:seh:dispatch_exception info[1]=238009c8
7131.701:00c4:00cc:trace:seh:dispatch_exception eax=02b2f7bc ebx=23800a0c ecx=00000000 edx=02b2f7d0 esi=02b2f854 edi=02b2f7d4
7131.701:00c4:00cc:trace:seh:dispatch_exception ebp=02b2f814 esp=02b2f7b0 cs=0023 ds=20002b es=2b2002b fs=0063 gs=006b flags=00000213
7131.701:00c4:00cc:trace:seh:call_vectored_handlers calling handler at 692614D0 code=40010006 flags=0
7131.701:00c4:00cc:trace:seh:call_vectored_handlers handler at 692614D0 returned 0
7131.701:00c4:00cc:trace:seh:call_vectored_handlers calling handler at 01546A80 code=40010006 flags=0
7131.701:00c4:00cc:trace:seh:call_vectored_handlers handler at 01546A80 returned 0
7131.701:00c4:00cc:trace:seh:call_vectored_handlers calling handler at 7B637B70 code=40010006 flags=0
7131.701:00c4:00cc:trace:seh:call_vectored_handlers handler at 7B637B70 returned 0
7131.701:00c4:00cc:trace:seh:call_stack_handlers calling handler at 7B073170 code=40010006 flags=0
7131.701:00c4:00cc:trace:seh:__regs_RtlUnwind code=40010006 flags=2
7131.701:00c4:00cc:trace:seh:__regs_RtlUnwind eax=00000000 ebx=00000000 ecx=40010006 edx=02b2f858 esi=02b2f7bc edi=02b2f858
7131.701:00c4:00cc:trace:seh:__regs_RtlUnwind ebp=02b2f310 esp=02b2f308 eip=7b0730fe cs=0023 ds=002b fs=0063 gs=006b flags=00000212
7131.701:00c4:00cc:trace:seh:__regs_RtlUnwind calling handler at 7BC5B020 code=40010006 flags=2
7131.701:00c4:00cc:trace:seh:__regs_RtlUnwind handler at 7BC5B020 returned 1
err: DxvkMemoryAllocator: Mapping memory failed with VK_ERROR_MEMORY_MAP_FAILED
err: DxvkMemoryAllocator: Mapping memory failed with VK_ERROR_MEMORY_MAP_FAILED
err: DxvkMemoryAllocator: Mapping memory failed with VK_ERROR_MEMORY_MAP_FAILED
err: DxvkMemoryAllocator: Mapping memory failed with VK_ERROR_MEMORY_MAP_FAILED
err: DxvkMemoryAllocator: Mapping memory failed with VK_ERROR_MEMORY_MAP_FAILED
err: DxvkMemoryAllocator: Mapping memory failed with VK_ERROR_MEMORY_MAP_FAILED
err: DxvkMemoryAllocator: Memory allocation failed
err: Size: 33554432
err: Alignment: 4
err: Mem flags: 0x6
err: Mem types: 0xff
err: Heap 0: 64 MB allocated, 64 MB used, 119 MB allocated (driver), 15549 MB budget (driver), 16368 MB total
err: Heap 1: 2080 MB allocated, 1881 MB used, 2085 MB allocated (driver), 15549 MB budget (driver), 16368 MB total
err: Exception on CS thread!
err: DxvkMemoryAllocator: Memory allocation failed
7135.376:00c4:011c:trace:seh:NtQueryInformationThread (0xfffffffe,12,0x130cfec4,4,(nil))

sometimes it just crashs, but most of the time it hangs. Memory allocation is weird as a bug, as i have 16gb of vram and 32gb of ram.
Versions on proton tested : from 4.11 to 6.1-ge

I wish I could claim this thread again after deleting but creating the same account. Oh well.

@baptisterajaut If you don't move, does it crash after a while? Or does it only crash when moving?

Is there any chance that the reason the file is not getting saved is due to some kind of permission/path issue?

@blaine12100 I doubt it as the game should be launching with the user's uid/gid or whatever Steam itself uses if not that.

I made a script that enable play singleplayer mode in men of war assault squad 2, read the instructions.

https://github.com/kanroot/men_of_war_assault_squad_2_linux

The game devs could probably fix this by making a fallback for the function img.std.get_surface(...) in eBitmapImageStd at line 95. Someone should reach out to them.

after about 20-30 min in COOP skirmish the game hangs, music plays, cursor works, but I cannot interact - after a while I get dropped from coop game

steam-244450_mowas2_softlock.log

Mouse cursor keeps leaving the screen on dual-monitor setups.
According to the dev, Windows doesn't have that issue:

Workaround: --force-grab-cursor argument in gamescope

Hi any proper (non workaround) solution for the - save wanting to do a screenshot but gets a 0byte file instead and crashes out - error?

proton log: steam-244450.log
steam runtime: https://gist.github.com/vajdao/752a55179c51d56b1578e045c2b5de86
steam system info: https://gist.github.com/vajdao/77b81935684ac8e00a4a00aa144e1eaa

@kisak-valve

edit 2024.mar.04:
by heavy heart, i used kanroot's script i was like, ok, I'll sacrifice the saves for the sake that i could progress the game... And okay, it worked .... for a rough 5-6 mins, because at that point the game just crashed on me again out of nowhere (without any error message or popup windows), but this time not the screenshot error, but some "sound volume thickness error" lol!

proton log: steam-244450.log - you'll notice that im using kernel 6.5 while yesterday it was 5.15, yes im experimenting between swapping everything, comboing different kernel versions with different proton versions, same results

Game's log: game.log

@kisak-valve do you have any info about this please?

Any fix?

I tried deleting the .bmp but still getting another and another...

Replying to https://github.com/ValveSoftware/Proton/issues/626#issuecomment-776111483

Could u share the script again please?

having the same issue with robz realism mod

Hey! Come on! Fix this bug already and make some love for linuxers too...

@kisak-valve

+1 with the various issues involving image crashes.
Not being able to save in a campaign is bad enough but not being able to use mods normally is also annoying.

+2 with the issues described. The game is unplayable due to the instability, even in Proton Experimental.

NVIDIA drivers 535.216.03

The image format issue should be fixed now with Proton 10, I'm currently using Proton Experimental for Mowas2 and save file image preview works fine. Saving and loading work flawlessly.

Loading mods also seem to work fine, here's the 40K mod in a single player scenario.

Can confirm, game is now fully playable with Proton 10 🎉

I can confirm this too. It works finally.

Too bad I lost my interest in this game since then 😅 well... It is what it is.

I tested with the Proton 10 Beta version and it too seems to work for me too. I was able to load mods and play around in the editor. (My primary goal ~7 some odd years ago...)

mean while im on windows, get the exact error, but cant used proton.

mean while im on windows, get the exact error, but cant used proton.

It was fixed long ago on proton..

mean while im on windows, get the exact error, but cant used proton.

It was fixed long ago on proton..

you can used proton on windows?

mean while im on windows, get the exact error, but cant used proton.

It was fixed long ago on proton..

you can used proton on windows?

No, valve made proton for Linux, this is a linux thread. On windows you just run the game, no need for proton...🙄

Sorry for necro, but I want to document this.
I recently migrated from Windows 10 to Linux Mint and moved my games to an EXT4 drive. Most stuff works on Proton, but launching Men of War: Assault Squad 2 (on any Proton/settings) would crash with a Error 3:0000076432 or silently crash before even starting a window.
I tried the different boot up options (including safe with no mods) but none of them would work. Curiously, I was able to open the editor.
The editor still had a Vietnam mod applied. So, I suspected it had to do with the fact that I ran mods on Windows.
I backed up my old copy and re-installed Men of War. Works great in vanilla now, no issues, fast start up.
I haven't had the time to investigate this future, but perhaps if someone can replicate this issue, it can be added to Proton's ToDo list.
As for the above comments: Before any Windows user writes again, please note that that kind of crash (with EAX) can happen when playing modded and the mod maker forgot to add something. Proton is unrelated to it.