I can concur that the game itself plays fine once you get ingame. However, there are a few caveats that prevent this title from being perfectly stable in my experience:
If the game loses focus at any point during gameplay(alt+tab), it'll stop rendering and become unresponsive, forcing you to kill the game. Similarly, if you enter the game menu during gameplay (hitting Escape), there's no guarantee you can get back into the game again every single time in my experience. This could be limited to my own system, but requires testing.

debian/testing, mesa 18.3.0-devel (git-1281608849)
Ryzen 1700 / Vega64

For me gameplay works, but the game often freezes in the options menu.
Specs: https://gist.github.com/kwahoo2/033eedf8e8462e0957cf17039c84aa27

For me game runs perfect out of the box but when i try to change the resolution in game settings i get black screen with audio still playing in the background.

Os: Kubuntu 18.04.1
Cpu: Intel Core i7 4700MQ
Gpu: GTX 860m
Driver: 396.54

Edit: Same problem with the Old Blood.

Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-5 Beta:

Steam System Information

^ Default VSync setting is Enabled

[1] If I go directly into the game it seems to run ok. However the game often freezes in the settings menu and the pause menu. I experience a similar problem in 32-bit Rage as per #166, which may be related since the underlying game engine is the same.

I have played this game a few months ago in wine and didn't experience any hangs.

Update: The hang/freeze has been fixed in mesa-git

[2] Having played until you get into the first bunker, experience really sharp dips in frame rate to 14fps and some areas seem unable to do above 27/28 fps, up until this point it had been solid 60fps.
Update: So far the performance drop seems specific to that one bunker, the rest of the game has been perfect 60fps (played several hours). I tested it on the Pro drivers and there is no performance drop in the same spot, so I'm not sure if it's a problem with a specific shader or feature something else going on. I plan to finish the game to make sure there are no other issues before submitting an apitrace I made of that level to the mesa bug tracker.

Wolfenstein TNO performance bug

I think the game should still be whitelisted even with this one niggling issue for us AMD/mesa users.

UPDATE: I finished the game and apart from that one single area of the game, performance was perfect.

Steam Log
My system specs

I can confirm that the game runs perfectly in my rig, ultra settings with 60 fps stable in most parts (can't compare to Windows performance, but I assume it's the same). I've been able to alt+tab multiple times as well as changing the resolution without any black screen or freezes.
Arch Linux with i5 4670 + GTX 1060 6GB - 396.54 drivers

as of commits 5 days ago to mesa git, both the new order and the old blood run fine and have no menu freezups.
system: arch linux, vega 64, threadripper 1950x, mesa-git, llvm-svn

Since upgrading to 3.16-5, I've found that audio loops have been fixed. However, I still experience random freezes that are fixed by alt-tabbing out of the app and back in. Also, I've found that when I play the opening part of the game aboard the airplane, that although mouse+kb works, my steam controller will work until you get to the part where you man the turret to shoot down the jet bombers, then after a short time the right touchpad control freezes.

Been able to play this on Xubuntu. You wouldn't be able to tell its not a native linux game. Its been 23 days since the last comment. WORKS AMAZING FOR ME!

Ryzen 1500X
GTX 1050 Ti
MSI B350 PCMATE
8 GB RAM
XUbuntu

@jonbitzen If the right pad is emulated as mouse input, this may be a mouse warping issue in Wine. I didn't see this problem with a standard Xbox controller.

yes, the right touchpad is emulating mouse input. I have a similar issue on Subnautica - I can play for a while, then the mouse sticks to the center. I can clear it by alt tabbing in and out, but then the directional control is highly exaggerated and the only thing you can do is exit and restart.

is there any type of workaround?

It seems I am the ulucky oe here, then - but I can't play this game properly (eventhough performance is great).
The game starts properly and I can start a New game that plays quite far, all details at maximum, full screen and proper performance - no rendering error, everything works fine.
When I try to load a checkpoint (after "dying", loading a previous chekpoint, or simply when resuming a game), the game crashes and sends me back to desktop.
My PC has a Ryzen 7 2700X, 16 Gb of RAM, a 1Tb SSD and a Radeon RX480 8Gb.
I run Ubuntu 18.04.2, with default GNOME 3 / Unity all up to date; I tried the latest HWE / Mesa stack available in official repositories, the Padoka PPA Stable (Mesa 18.3.3), the Unstable one (19.1git), with Steam overlay on and off, with the latest official Linux kernel and the most recent Mainline kernel build, reducing details to minimum, switching to Windowed mode, using different Proton builds... Nothing works, the game crashes on each and every checkpoint load.

Nevermind, I've found the problem in my .drirc file. I simply added the following section:
<application name="Wolfenstein: The New Order" executable="WolfNewOrder_x64.exe">
<option name="mesa_glthread" value="true" />
</application>
to prevent default settings to apply, as it was "mesa_no_error" in default which caused problems. Since then, game works properly (apart from the already-mentioned stuttering in the first mission's bunker)

Game doesn't sync to cloud. Runs great.

I've done some playing with the Steam Controller touchpad issue I mentioned above. I find that the controller is set up to click the touchpad to emulate the middle mouse button. If I click it the track pad becomes unresponsive (i.e., you can no longer change the look direction). It always works until you click it. It only stops working when you click it.

What's really neat is it ONLY does that if you're in a steamos-session (graphical session used by SteamOS). A regular desktop session (such as cinnamon) does not have this issue.

FWIW, the issue is probably completely unrelated to the one in Subnautica (as I erroneously suggested before).

@kisak-valve

I think there may be an issue with the steamcompmgr in the steamos-session.

I found this issue here:

https://github.com/ValveSoftware/Proton/issues/204

and if you scroll through to the middle, you'll find another guy with an issue in a game, and his workaround on SteamOS is to fiddle with the system and restart in a desktop session.

Likewise, with Wolfenstein, if I run in a regular desktop session on the same machine, the issue goes away.

I looked at the source for the steamcompmgr, and it looks like it handles XEvents, and may have a role in focus as well, any of which could be issues that interact with the game in a way such that you have to press a mouse button to ensure mouse tracking (?). I suspect there is some interaction between Proton and the steampcompmgr going on. Maybe that would help your developers look more closely at this potential source of the issue?

In addition to Wine, other applications like Dolphin and even Chrome have issues with the steamcompmgr mouse - that's being tracked over here:

https://github.com/ValveSoftware/SteamOS/issues/475

So to confirm, it's probably steamcompmgr but nobody's tried to fix it yet.

@dukesilver28 Can you run this for me:

cd ~/.local/share/Steam/steamapps/common/Proton\ 4.2/dist/lib64
curl -O flibitijibibo.com/opexit.tar.bz2
tar xvfj opexit.tar.bz2

Then try running the game again. This should at least fix sound, not sure about performance.

@flibitijibibo Can confirm, that fixes the audio.
Performance is exactly the same for me to previous versions of proton: Mostly perfect 60fps except for the fps slow down in first bunker. I'm using an RX Vega 56 + mesa 19.2-git.

This looks like it might be a nvidia specific issue?

@LeJimster
I had the same significant drop in performance with a Radeon RX 590.
Same scene, 4.2-5 > good performance, 4.2-6 > almost slideshow.

FAudio 19.06.07 is now available, for those willing to self-build until 4.2-7 is out:

https://github.com/FNA-XNA/FAudio/releases/tag/19.06.07

FAudio 19.06.07 is now available, for those willing to self-build until 4.2-7 is out:

https://github.com/FNA-XNA/FAudio/releases/tag/19.06.07

Seems to fix issues with Warframe.

steam-201810.log.gz
@kisak-valve, here's the log compressed into a gz file. Not sure why I didn't think of that.

@dukesilver28 Can you run this for me:

cd ~/.local/share/Steam/steamapps/common/Proton\ 4.2/dist/lib64
curl -O flibitijibibo.com/opexit.tar.bz2
tar xvfj opexit.tar.bz2

Then try running the game again. This should at least fix sound, not sure about performance.

@flibitijibibo That definitely fixed the sound. Thanks!

From just a few minutes playing again, I haven't had any more fps drops, even in that same level, so maybe it was a fluke, though @dubigrasu reported something similar. I'll post an update if any more performance issues arise.

EDIT: fwiw on my computer, the lib64 folder is at
~/.steam/steam/steamapps/common/Proton 4.2/dist/lib64
instead of
~/.local/share/Steam/steamapps/common/Proton\ 4.2/dist/lib64

It was pretty easy to figure that out, but I'm posting that just in case anyone else finds their way here and has the same issue.

@flibitijibibo @dukesilver28 I had the same issue, 15fps and no sound on a GTX 1080 with Nvidia 4.18, Proton 4.2.6. Running those commands fixed both sound and performance issues. Solid 60FPS now.

My guess is it’s issuing hundreds of commands per second and never executing them, so as time goes on the operation mutex lock time gets longer and longer as it iterates through the increasingly large linked list, causing the rapid slowdown. Once the executions were fixed the list size went down to being reasonably small again.

Compatibility Report

• Name of the game with compatibility issues: Wolfenstein: The New Order
• Steam AppID of the game: https://steamdb.info/app/201810/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.64
• Kernel version: 5.5.7-zen
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 5.0-3

LOG:
steam-201810.zip

Symptoms

Crash on launch

Still working for me.

System Info

• GPU: Radeon Vega 56
• Driver: Mesa 19.3.3/LLVM 9.0.1
• Kernel: 5.4.11-fsync
• Proton version: 5.0-3

@kisak-valve
Its working now. It seems if I have Chrome open when testing, I can have odd audio bugs, which you've seen before.

When restarting my computer and leaving Chrome closed, the launched and ran great.

LOG:
steam-201810.zip