

You'll need to tinker a bit to fix some problems but once this is done, it works fine from start to finish.
WINEDLLOVERRIDES="d3d8=n" %command%
Edited vars.cfg in game directory to set fpsLimit=60. It enables 60 FPS in game. Sound effects in cutscenes end up lagging behind but it was no big deal (voices were still synced)
Sound effects lag behind in cutscenes if you enable 60fps mode. Voices are fine.
Some random grey lines appear through the screen. To make them disappear, I had to use dgVoodoo2 2.79.1 (hence the WINEDLLOVERRIDES launch option) that I found on pcgamingwiki. The game wouldn't start with latest version (v2.83.2) and I couldn't find v2.78 mentionned in trolleybollocks report (dead links on official website).
I switched to community layout "Ina's Indiana Jones And The Emperor's Gamepad" to have sane controller mapping. Even though I reduced sensitivity to the lowest possible in the game settings, aiming was still way too sensitive in the 2-3 first person shooting segments.

do not work well out the box, but you can enjoy the game if using dgVoodoo2 + Gamescope + controller profile
WINEDLLOVERRIDES="d3d8=n" gamescope -w 1280 -h 960 -f %command%
videos are not scaled, white lines during playing
crash when alt+tab
crash when alt+tab
use dgVoodoo2 to obtain scaled cinematics and to avoid white lines, use Gamescope to fix alt+tab crash, use a Steam community controller profile

WINEDLLOVERRIDES="d3d8=n" %command%
Made custom layout "Indiana Jones and the Emperor's Steam Deck"
Fix for the white line problem on Steam Deck:
- Enter Desktop Mode on Steam Deck, download dgVoodoo 2.78 (Jan 11, 2022) from dege-diosg's GitHub via web browser, and extract the zip file
- In the extracted folder, double click the file dgVoodoo.conf to open in Kate editor
- Go to Edit > Find, type "dgVoodooWatermark" without quotes, change the value from true to false, and then click Save to overwrite the file
- Close the editor and return to the extracted folder. Copy the modified dgVoodoo.conf to the game directory .local/share/Steam/steamapps/common/Indiana Jones and the Emperors Tomb/GameData/bin (browse installed files via Steam to navigate there faster)
- Return to the extracted folder. Copy the file D3D8.dll from [extracted folder]/MS/x86 to the game directory .local/share/Steam/steamapps/common/Indiana Jones and the Emperors Tomb/GameData/bin
- Return to Gaming Mode, click on the game and go to Settings > Properties > General, and type WINEDLLOVERRIDES="d3d8=n" %command% exactly as is under "launch options"
- Exit back to the main menu and launch the game
On Proton 8.0-5, I was able to enjoy the entire game from start to finish without white lines using this method and it ran flawlessly on Steam Deck OLED. Don't forget to bump up the resolution via in-game settings for the best experience. I have no idea if this works with mods or not. Later versions of dgVoodoo crash the game on start-up on my Deck. I shared my controller config "Indiana Jones and the Emperor's Steam Deck" under community layouts for convenience for anyone who wants to use it.

The only thing is that framerate capped at 30FPS, which can be rised to 60FPS, but beyond that it breaks game
Works out of the box with default Proton
There's a minor artifact on the screen, just two lines that show up on the screen all the time. It's easy to ingore them though.
Had to change the directional pad overlap between directions, otherwise I would have trouble going perfectly straight.
Horizontal and vertical lines showing up, very common during the gameplay. Positions of the lines depend on the camera position, and it's not game breaking.
Prerendered cutscenes were not stretched to the normal game resolution.
Couldn't name the save file, virtual steam deck keyboard didn't work properly.
Pops up an error message saying that an "Invalid floating point matrix was sent to the renderer" or something like that. Tried GE proton, tried experimental, tried adding the msvcrt override I saw in some other reports. Just the same error every time.
Using proton-5.9-GE-5-ST from GloriousEggroll you will not need vcrun6 and vcrun6sp6 and you dont have to add "msvcrt" to the overrides, the game will work out of box, there are some graphics bug white lines during gaming, but that can be solved with dgvoodoo2, i downloaded dgVoodoo v2.78 and copy D3D8, D3D9, D3DImm.dll, DDraw.dll, and GCore.dll into .local/share/Steam/steamapps/common/Indiana Jones and the Emperors Tomb/GameData/bin i launched the game with WINEDLLOVERRIDES="D3D8,D3D9,D3DImm,DDraw=n,b" %command% and there game work perfect without any graphic glitches.
To get past the start menu vcrun6 and vcrub6sp must be isntalled via protontricks. Then overide msvcrt.dll via winecfg or command.
It is required to install vcrun6 and vcrun6sp via protontricks. Then add msvcrt.dll override in wineconfig or as a launch command 'WINEDLLOVERRIDES="msvcrt"=n,b" %command%'. Then the game will run but similary like Max Payne, another DirectX8 game, there is a color depth issue in the newest proton versions, so unbearable color banding is present everywhere. To fix that a D8toD9 wrapper is required, older proton or just use Proton-GE.
Color banding on the newest proton, another D3D8 game with this issue
To fix color depth issue just use Proton GE or older protons.

crashes on game main menu
on main menu it displays error message saying abort render an invalid floating point camera was passed to the direct3d driver then exits game.
"protontricks 560430 --gui --force". install "vcrun6" and "vcrun6sp6". in winecfg add "msvcrt" to the overrides in library tab.

Still borked
Crashes before the main menu. It happens with Proton (up to 5.13-5), and Proton-GE (up to 6.0-GE-1).
Game shows white lines during during. Fixed with dgVoodoo. I think, it happens on Windows as well.
The game works out of the box with the Glorious Eggroll proton "Proton-5.9-GE-5-ST". Used widescreen and xinput mods, then used WINEDLLOVERRIDES="R_D3D,Dinput,Dinput8,GCore,XInput1_3,D3D8,D3D9,D3DImm,DDraw=n,b" %command%, so the proper dlls get loaded for the mods to work, otherwise the game will crash.

Still getting D3D driver error, even following the tweaks suggested by the last user
Still getting "(Render) An invalid floating point camera matrix was passed to the D3D driver!" error, even after disabling Esync, forcing D9VK, and using winetricks for suggested tweaks (vcrun6, vcrun6sp6 and msvcrt). Also, Proton-5.8-GE-2-MF didn't help at all with this game, with or without the tweaks.

The game itself is playable and still 'fun' from the 15 minutes or so I spent in the first level.
Was necessary to run up winetricks for the pfx eg navigate to location of pfx eg xxx/SteamLibrary/steamapps/compatdata/560430 then run WINEPREFIX=$PWD/pfx WINEARCH=win64 winetricks you have to "select the default wineprefix" then "select a Windows DLL or component" now locate the two packages vcrun6 and vcrun6sp6 in the list and check the boxes. Hit Ok and wait for the install to complete. Now select "Run winecfg" from the previous menu. When the WIne Configuration dialog appears, select the Libraries tab. Now in the "New override for library" dropdown select msvcrt and add it to the existing overrides. Now Ok that change. Exit out of Winetricks and run the game. The d3d camera error will now no longer occur and you can get into the game menu. After creating a save and try to start the game it might bomb out. On restarting the game select your previous save then start the game. You will start playing the first level
The game has some tearing as it does not support higher resolutions.
Wireless XBone controller was detected but prompts in game were for Keyboard/mouse. Not sure if is just how the game is but the controller does work in game.
The game is so old that it has a 30fps cap so it's smooth but slow.
The splash screens don't appear. I'm assuming the game has them! I started the first level multiple times to see if the game was consistent. The game might possibly also have an issue with cutscenes. Second time starting the first level I saw the classic Indy red dot on a map. Third time didn't see it. Might try a GE custom with media platform stuff in to see if it makes a difference.


(Render) An invalid floating point camera matrix was passed to the D3D driver!
This shows up immediately after the intro videos play, and the game freezes/crashes after


Does not work. The intro videos play, but as soon as the main menu shows up, the following error pops up and the game crashes: "(Render) An invalid floating point camera matrix was passed to the D3D driver!"