Proton: Men of War: Assault Squad 2 (244450)

[maximstewart]

I'm not sure if "eBitmapImageStd" is in Proton/Wine but I get the following error for Men of War: Assault Squad 2:

It allows the main game to load to menu but only without mods. Trying to use the editor throws the same error with or without mods loaded.

My system is (OLD):

Ubuntu 18.04
AMD Phenom II x6
GTX 750ti with NVIDIA 390.48 Drivers
Proton 3.7-3

My system is (CURRENT):

Ubuntu 20.04
AMD Phenom II x6
GTX 750ti with NVIDIA 440.100 Drivers
Proton 5.0-9
Linux Kernel: 4.15.0-109-generic

:: LOG OUTPUTS (From current system setup as mentioned above.) ::
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

[kisak-valve]

Hello @maximstewart, you may have better luck with nvidia 396.51 or newer.

[maximstewart]

@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.

[offboot]

same when i try to save the game

[baptisterajaut]

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

[SOlsson91]

Still the same, nothing new.

Tried with GE 5.0, still no change

[CeeWeee]

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!

[maximstewart]

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.

[CeeWeee]

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

[maximstewart]

@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.

[CeeWeee]

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...

[CeeWeee]

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?

[maximstewart]

@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)SteamSteam.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....

[K4rBie]

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?

[maximstewart]

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