


The mentioned MaxShaderModelVS Wine fix makes the game work almost perfectly, without it 3D objects don't render at all
Faraway objects have Z-buffer glitches
Mouse movement was somewhat innacurate, still playable but bothersome

Followed method put forth by nanofoxie, albeit modified. The only modification made was to run the appropriate version of wine regedit
in Proton 8.0/:
# Set environment variable for use by wine regedit:
export WINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/331970/pfx"
# Modify registry of wine prefix(substitute Proton 8.0 with the directory/folder most closely matching the Proton version in use, or matching the major software version):
proton_dir="Proton 8.0"; "$HOME/.local/share/Steam/steamapps/common/$proton_dir/dist/bin/wine" regedit
HKEY_CURRENT_USER/Software/Wine/Direct3D/MaxShaderModelVS
Navigate to and create any missing keys in the path above. To create keys, right click an existing path to add the key. In my case, Direct3D
was missing so I simply right clicked Wine
and hit New
-> Key
, setting the name to Direct3D
. I then right clicked Direct3D
, hitting New
-> DWORD Value
, naming it MaxShaderModelVS
and leaving the value set to 0.
Strange issues when attempting to change resolution, in which the menu was chopped up and uncentered, but this may be an issue with game itself. Simply change resolution, close the game, and re-open. The campaign opening cutscene, at my chosen resolution of 1280x720, was no longer centered.

Not rendering correctly
Solid materials (ships, islands, ...) are rendered as cutouts (basically black)
Game issue, not a Proton issue
Mouse with too high polling rate behaves wrong (Game issue, not a Proton issue). Decrease polling rate/use older mouse to fix.
nanofoxie suggested a fix. While it did not work for me, it's worth a try.
Run wine regedit
on game's Wine prefix, set HKEY_CURRENT_USER/Software/Wine/Direct3D
MaxShaderModelVS
(DWord) to 0
.
Game's AppID is 331970
.
The Registry key has to be added to make models visible in game (otherwise you can only see effects and background). See original report at WineHQ: Treasure Planet: Battle at Procyon 1.00 | WineHQ.
To avoid updating prefix running a different Wine version, do:
$ export WINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/331970/pfx"
$ $HOME/.local/share/Steam/steamapps/common/Proton\ 6.3/dist/bin/wine regedit
Then navigate to HKEY_CURRENT_USER/Software/Wine/Direct3D
, creating any missing keys along the way. Create MaxShaderModelVS
DWord value and set to 0
.
I was able to finish a Skirmish mission without a single issue.
If game crashes after intro cinematic, consider disabling Steam overlay.
I was able to finish a Skirmish mission without a single issue.

Crashes on launch
doesn't work on windows for me either

Menus work perfectly fine, all settings seem to be respected.
The gameplay is also functioning correctly without any crashes.
However, the game does not render any models. At all. Only visual effects (explosions, ships wakes, etc etc).


Only shows particles and background, no ships or islands visible. Winedb says to disable vertex shaders
