Update/correction
One workshop mod will not show in the list. I subscribed to other mods and they show up and load correctly. I have no idea why this one mod doesn't show.

I have the same issue. About half of my subscribed mods are not showing up on the Steam Play version of this title, but all are present when run on POL Wine.

@kisak-valve any update on this issue? Anything that can be done to help?

@graywolf-theheathen @Iiari - there is a workaround. If you create a Mods/ directory in <steam_path>/steamapps/common/Star Wars Empire At War/corruption and then copy the workshop folder there, then you the game will pick it up as a local mod.

You could also try a symlink

Update. Not sure which update did it but something changed with one of the last few Proton updates. My mods that were not showing in the list are now showing. So as of now I do not have this issue any longer.

Our QA retested this and verified that mods appear to be working in 3.16-5. Should we add the whitelist request label to this game?

I have re-tested the game with 3.16-5 on Ubuntu Mate 18.04.1
Game runs as expected and all my Steam Mods show in the list.
From what I see: Please whitelist this game.

@kisak-valve I just re-tested the game and I see all my Steam mods in the menu now.

From my perspective, this is ready for Whitelist

I don't think it's ready to be whitelisted. I was just playing with proton 4.11 and the game crashed while loading a mission.

It didn't crash yet now that I switched 5.0-3, but the planets flicker in the galactic view. They also flickered in 4.11. It's easy to reproduce by just going through the tutorial.
System Info
steam-32470.log

I've been playing it daily since 4.2-9 was the new version of proton. That's the one I still have it set to. I never have a single issue and it plays mods great. Even big mods. I use Absolute Chaos mod with 245 planets in the beta version. Smooth and never crashes.

Thank you for spotting that. So all I should have to do is input that in the launch options for the game properties and it should (sort of) work?

Oh my gosh! It works! Anticipating your caution in lowered performance, I minimized the game detailers so it is operating at its lowest graphics but it runs smoothly! Thank you!

Compatibility Report

• Name of the game with compatibility issues: Star Wars Empire at War: Gold Pack
• Steam AppID of the game: 32470

System Information

• GPU: Nvidia GeForce GTX 960
• Driver/LLVM version: NVIDIA 455.45.01
• Kernel version: 5.10.2-2-MANJARO
• Link to full system information report as Gist:
• Proton version: 5.13-5

I confirm:

• [ ] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-32470.log
Save File

Symptoms

In the Forces of Corruption expansion, during the heart of the maw campaign, it crashes to desktop with no error during a "Piracy" mission when playing the Zann Consortium. Reloading the above save results in the same crash.

Reproduction

Load the save game, and attempt to "Spread Corruption" on the nearby Empire planet with the red "corruption unit" in orbit, which triggers the "Piracy" mission. During this mission, you fight a space battle, and during this battle the game crashes every time.

@kisak-valve I tried this, but the crash persisted. Log file below:
steam-32470.log

I have also noticed that between the two log files, they both crash at read 1097 referring to I_BUTTON_RB_BUNKER.TGA1134.390:00d4:00d8:trace:seh:NtSetInformationThread (0x214,3,0x31eefc,4)

Is this the first time you've ran it in awhile? Have you ran it since late
2023 when they patched it up to 64 bit?

On Fri, Mar 29, 2024, 8:31 AM kisak-valve @.***> wrote:

STAR WARS™ Empire at War: Gold Pack (32470) no longer launches

Issue transferred from #7613
https://github.com/ValveSoftware/Proton/issues/7613.
@CounterPillow https://github.com/CounterPillow posted on
2024-03-29T13:13:24:
Compatibility Report

• Name of the game with compatibility issues: STAR WARS™ Empire at
  War: Gold Pack
• Steam AppID of the game: 32470

System Information

• GPU: AMD Radeon RX 7900 XT
• Video driver version: mesa 24.0.3
• Kernel version: Linux 6.8.2-arch2-1
• Link to full system information report as Gist
  https://gist.github.com/:
  https://gist.github.com/CounterPillow/974cb8b8ddce6ba6710f8d1302a1626c
• Proton version: 1710947987 experimental-9.0-20240320

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system
  available.

Proton Log:
https://overviewer.org/~pillow/up/d33d1afc8d/steam-32470 submitthis.log
Symptoms

Game flashes a white window briefly, then immediately closes. Used to run
fine literally earlier today but then I had to restart the game because it
froze and while I did that it seems Steam downloaded some runtime updates
that borked it.
Reproduction

1. Launch the game with Proton Experimental on Arch btw, KDE Plasma6
   Wayland
2. Observe a white window briefly appearing and then disappearing

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/584#issuecomment-2027248685,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2YGULHOL4LDC7U4VEWH2LY2VULLAVCNFSM4FRSCDS2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBSG4ZDIOBWHA2Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

I've run it successfully just earlier today, this morning, which was the 64-bit version. The game then froze after several hours of play, and I killed the task and went to make coffee. Upon returning it would no longer run, and I noticed that Steam downloaded an update of Steam runtime (sniper), though I'm not sure if that's related.

I tried restarting the computer to rule out any weird stray wine processes that were hung, no luck so far.

While verifying integrity of game files did nothing, uninstalling the game and then reinstalling it fixed it. Maybe Vulkan shader cache got shredded up or something? I can't prove it was the shader cache, but adding an option to clear it without redownloading the game could be neat.

Either way, works fine now with Proton Experimental. Thanks for the prompt replies!

I would like to add my experience to the last report at the Reproduction part. Longer loading times and the stuttering or "hiccup" happens with all big mods I have tried (All the EAWX mods[Thrawn's Revenge, Fall of the Republic, Revan's Revenge], Awakening of the Rebellion, Republic at War)

The main thing to understand about the the stuttering or "hiccups", is that they happen when inside a battle the game needs to load for the first time any unit, and any projectiles (lasers, missiles, etc), which is specially jarring when units start firing, once all of this happens though the game is smooth again (except when something new have to be loaded obviously)

However the way the game seems to handle loading/unloading between battles means that each battle the player has to suffer the same stuttering again.

A big difference between base game and most mods, is that modders for the sake to facilitate development and submodding, do not place their files in .megs if they can avoid it. (However placing everything in .megs could still lead to some very big files that the game may struggle to read anyway)

10/05/25 Edit: (In summary is not a "just mods" issue) Upon closer inspection playing just base game, I do notice that the hiccup is present, but is a micro hiccup and only shows up when loading the biggest vanilla models (Heroe capital ships, specially Dath Vader´s Executor) and usually when you call them as individual reinforcements, not when they come in full force at the start of the battle. The severity of the hiccup seems to have a correlation to the complexity of the units and file size. With mods usually having better quality with both their models and textures and quantity, the issue becomes more noticeable, but it is present in base game too.

28/05/25 Edit: Ignore last paragraph, behavior is also present on windows and is normal

@kisak-valve For the last month I have researched the problem of the heavy stuttering and the loading times. In order to confirm the issue I used debug tools from the game, Proton and some extra tools to keep track of what the game was doing, and I have pin down the problem and the solution, both being mod related and fixable from the modders end (I have shared my findings with the Eaw Modding comunity).

Unless there are plan/expectations for Proton to become capable of handling heavy syscall operations for files (due to how the game engine uses files, specially to allow mod support) I'm tempted to make a Whitelist Request

The source of the stuttering was indeed the huge number of loose files that mods have for the sake of facilitating mod development and submodding, creating a lot of I/O overhead (I am talking thousands of files that the game load/reads on demand). Once I confirmed the issue I packed into .megs (the same file format the base game uses) most of the files of one of the biggest mods out there, Thrawn's Revenge, which has up to 22k files (vast majority being Audio, Models and Textures). Doing that have solved the sttutering issue and aliviated loading times somewhat (though long loading times are also nature of mods, which is not any different compared to windows in my experience).

From my end now both base game and mods behave the same as they do in my Windows partition. (this includes some observations I wrote in my last comment, can be ignored). Well, besides the game's font not showing up

I've been trying to make the game's font work, I tried installing the game's font on the system, wine, proton(installing the font in the proton folder, compdata of the game, editing registry) but no luck.

steam-32470.log

Got the font working, Proton Experimental.

Checking the game's log I found this warning several times.
WARNING: Asked for font EmpireAtWar-Medium, windows gave us font Empire At War Medium

After asking a game dev and checking the font with FontForge I arrived to the problem: Proton is returning the correct font, but is giving the game the family font name instead(and the game seems to be coded expecting the normal font name instead). After editing the family font name with Font Forge and placing the edited version in files/share/fonts on the proton folder, the game was able to load the correct font.

The June 1 update of Proton Experimental make the game crash on launch, with a white window showing up and then disappearing. Going back to Proton 10 fixes the issue.

steam-32470.log

I can repro the same crash on Fedora 44 + Proton Experimental, likewise works on Proton 10.

steam-32470.log

Can confirm the same on my oled steam deck with proton Experimental

@Alexeyov @mszabo-wikia @waspennator Can you check with the latest Proton Experimental release 20260609 and see if that is still the case for you? It is working well for me with that release but failing with the Experimental release 20260529.

@Alexeyov @mszabo-wikia @waspennator Can you check with the latest Proton Experimental release 20260609 and see if that is still the case for you? It is working well for me with that release but failing with the Experimental release 20260529.

Updated proton Experimental and it seems to boot up now