Linux support

[asday9]

For me on Mint, so far I couldnt get it running. I know there will probably never be a linux version of this, but if someone has advice on what to tinker with so it might work, Id greatly appreciate it. So far it either crashes without image after the launcher or, when I enable dgvoodoo 2 in lutris, it launches into a black screen and stays there. by experimenting with the fix launcher option, I did get to see the main menu for like 2 seconds before it crashed again. What could be the issue?

[pauls2271]

Yeah, I didn't buy as I dumped Windows and run Linux now (CachyOS).

Supposedly it is a brand new, from scratch program (not just WITP-AE with new data tables). If so, there is no excuse for it not to run under Linux - especially if they want to get it to Steam and run under Steam-deck.

Requirements say Direct X 8a (which is like 25 years old) and recommend Direct X9 - also quite old. So I would look at if there are parms for DirectX8 or 9 emulation in Lutris (I dont run Lutris myself),

Have you tried it under Steam yet (you can add non steam programs to Steam and it will grab the emulation files). I've had some success doing this (this is how I run Cyberpunk 2077 even though I bought it from GOG not Steam).

[asday9]

Yeah, I didn't buy as I dumped Windows and run Linux now (CachyOS).

Supposedly it is a brand new, from scratch program (not just WITP-AE with new data tables). If so, there is no excuse for it not to run under Linux - especially if they want to get it to Steam and run under Steam-deck.

Requirements say Direct X 8a (which is like 25 years old) and recommend Direct X9 - also quite old. So I would look at if there are parms for DirectX8 or 9 emulation in Lutris (I dont run Lutris myself),

Have you tried it under Steam yet (you can add non steam programs to Steam and it will grab the emulation files). I've had some success doing this (this is how I run Cyberpunk 2077 even though I bought it from GOG not Steam).

yes, I did try steam with various proton versions. enabling dgvoodoo on lutris gave me some progress, as now I get a simple blackscreen but yeah. apparently the game is in 32 bit or something? apparently thats the issue because i dont have the right driver. Iam currently on that. Its weird because war in the east 2 and even war in the west do run perfectly fine on my system with simply proton experimental. I dont get whats going wrong here.

Ill look into that directx9 thin in lutris, but I am not that experienced with linux and lutris, Ill see what I can do

[HappyHedonist]

Try gamescope with either fullscreen or borderless and set a resolution. I would try GE-Proton, which you can download, and try that. I'm debating a purchase. If I do, I'll report back.

[Codechopper]

I also run Cachy, I tried setting up a custom wine prefix and it complains about..

Code: Select all

Unhandled exception: unimplemented function magnification.dll.MagInitialize called in wow64 32-bit code (0x7b5c98f7).

I tried to do a Library Override in winecfg, and a few other things like copying the native dll, etc. but the game continues to crash with the exception for magnification.dll. I also loaded into steam and tried Hotfix, Experimental and GE Proton 10-10 with no luck.

I ended up spinning up a Windows VM, but the dialogs, display and menus were all disproportionately HUGE.

So, I'll wait a bit to see if there is a graphics fix (it has been reported in a few places on the forums) for the VM, or maybe wine12 which may fix the issue with the .dll.

[asday9]

I also run Cachy, I tried setting up a custom wine prefix and it complains about..

Code: Select all

Unhandled exception: unimplemented function magnification.dll.MagInitialize called in wow64 32-bit code (0x7b5c98f7).

I tried to do a Library Override in winecfg, and a few other things like copying the native dll, etc. but the game continues to crash with the exception for magnification.dll. I also loaded into steam and tried Hotfix, Experimental and GE Proton 10-10 with no luck.

I ended up spinning up a Windows VM, but the dialogs, display and menus were all disproportionately HUGE.

So, I'll wait a bit to see if there is a graphics fix (it has been reported in a few places on the forums) for the VM, or maybe wine12 which may fix the issue with the .dll.

same for me. I did pretty much the same as you. I do have a VM where I pass a GPU through and it works fine in there.

[asday9]

I got this info from ChatGPT but I honestly don't know any better:
apparently this magnification.dll is the issue because wine is unable to emulate it, same with proton. This game is simply unrunnable under Linux. Though correct me if I am wrong.

[Codechopper]

same for me. I did pretty much the same as you. I do have a VM where I pass a GPU through and it works fine in there. its really weird considering its apparently brand new. Im getting a feeling they more or less reverse engineered war in the pacific with all of the ancient things it does almost 1 to 1. war in the pacific also didnt work for me though it gave me even less of an explanation for it.

That's the funny thing, Cachy runs WitP just fine. I did the same steps creating a wine prefix and a few other adjustments that I can't remember lol. I launch it from a script...

Code: Select all

#!/bin/bash
export WINEPREFIX=$HOME/.wine-witpae
cd "$WINEPREFIX/drive_c/Matrix Games/War in the Pacific Admiral's Edition"
taskset -c 0 wine "War in the Pacific Admiral Edition.exe" \
  -w -skipVideo -fd -px1920 -py1080 -altFont -deepColor -dd_sw

I set that all up a while ago, runs like a champ. I tried the same (as I said) with WiS and it's that darn magnification.dll that has it stumped.

I bought the game hoping it would work...at least I'm supporting the devs and hopefully the UI will be fixed for Windows (and VM!) soon(ish).

[Codechopper]

I got this info from ChatGPT but I honestly don't know any better:
apparently this magnification.dll is the issue because wine is unable to emulate it, same with proton. This game is simply unrunnable under Linux. Though correct me if I am wrong.

This is exactly the problem. It is identified and hopefully will be fixed in the next version of wine? We hope?