PlayableShow Details
Unknown
Didn't change controller but had to change from keyboard to controller in the in game menu
With default proton settings the graphics were stuttering badly, forcing proton experimental no issues at all.
Setting Up Oddworld: New 'n' Tasty on Steam Using Heroic Games Launcher for controller issues
Open Steam in Desktop Mode:
Right-click on Oddworld: New 'n' Tasty in your Steam library. Select "Properties". Go to "Installed Files" and click "Browse". Right-click "NNT.exe" and select "Copy Location". If the Game is Not Installed:
Install the Heroic Games Launcher. Open Heroic Games Launcher:
Change "Game/App Title" to Oddworld: New 'n' Tasty. Click the folder icon next to "Select Executable". Navigate to the game folder you copied earlier and select "NNT.exe". Click "Next" on the remaining steps. Add the game to Steam through the Heroic Games Launcher. By following these steps, you should be able to run Oddworld: New 'n' Tasty smoothly on your Steam Deck without controller issues
Noticed some glitchy textures at the beginning of the game
I had to switch Proton to experimental version because otherwise game controls don't work. You should also configure control settings in-game (switch from mouse+keyboard scheme to gamepad). In case you are not aware how to do that: hold Steam button and use the right trackpad to emulate mouse movements; press the right trigger to emulate mouse click.
Neede some in-game change to use the controller instead of keyboard
Missing textures in practically all the signs where the button layout would be. Possibly also an issue on Windows.
There are a handful of rooms in the middle of the game where the framerate drops below 30 fps, despite average 200+ fps elsewhere.
The native version was so unstable I couldn't get past the first section, the game would crash at least once after nearly every checkpoint. The tutorial signs were also not being rendered. There may have been other issues but I didn't stick to find out. On Proton 7.0-4 I was able to finish the entire game without a single crash.
Native build has no audio during cutscenes. Too many problems getting controls to work properly on Proton to be worth the trouble.
Have to revert to default recommended control layout after selecting "controller" in game's options
Set screen refresh rate to 40 Hz
Disabling fullscreen in game options causes an immediate crash, and the game will not launch again until cloud support is disabled and local config data is deleted.
I use the 40 fps limiter in SteamOS settings
It would crash often at load up, using Proton Experimental for me. I could use the newest Proton without using Compatibility, but the movies would stutter and have no audio. Controls have always worked, no problems there.
Forcing 'Steam Linux Runtime' works perfectly for me, no issues with the game after setting it to that, I recommend trying it.
I use OS Beta, and Stable Steam on the Deck.
Switched dpad to output left stick
Some signs are glitched and don't display any text. This happens both via proton and native.
The Windows version via proton performs better than the native Linux version. Proton hits 60 fps easily, while the Linux client averages around 40 fps on the Deck.
Additionally, an earlier Steam Deck report said that the game doesn't respond to gamepad inputs, but the controls work fine for me, so that issue seems to be resolved now. Also, install the 720p videos DLC to get better performance during FMV cutscenes.
it's an almost passable experience. it is playable, but the problems are up to the surface
PROTON_USE_WINED3D=1 %command%
In windowed mode cutscenes show a black screen
lags even at lowest graphics, sometimes it freezes
Always crashes on vulkan, sometimes it freezes when using WINED3D
Neither the native nor the proton versions recognize controller inputs correctly, which makes it pretty much unplayable on Steam Deck
In cutscenes, it would occasionally display a static image before crashing
Crashes after a few minutes of playing. And all the time in the cutscene
All in all worse performance than the proton build
Runs but with occasional crashes
Crashes instantly in Window Mode
Due to Failed to get Thread Context crashes at loading Maps or checkpoints (Does not always happen)
The Linux native Version does not detect Gamepads correctly and you need either provide your own Button Mapping or to play it with Proton.
The Linux Native Version does not start if not installed in your Home Directory at ~/.local/share/Steam/steamapps/common/
The Linux Native version has worse performance than with Proton but is more stable.
Loaded existing save from native client which constantly crashed and ran smoothly as for 2 hours. Slight screen tearing was fixed by vsync.
This game was unplayable on native, constant glitches and crashes to the point that it was impossible to continue without a crash preventing progress. The game plays MUCH better with proton.
Unless you only intend to play the first half of the game, this is a no-go
There is a certain spot in the game where it crashes within a couple minutes consistently whether I use Proton or the Linux native version of the game.
Please ignore my previous report for this game.
