i've tested the demo and its working wonderful. 80+ fps on mein leiben (whatever the highest profile).
On second restart i've got warning that gpu is out of memory. probably i have to set it lower for 4gb video memory. But the thing is that even with that warning i still have 80+ fps on max graphics with 8x anti aliasing.
The game will crash with 1 alt+tab

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen 7 1700X Eight-Core Processor         
    CPU Family:  0x17
    CPU Model:  0x1
    CPU Stepping:  0x1
    CPU Type:  0x0
    Speed:  3400 Mhz
    16 logical processors
    8 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Linux Mint 19 Tara (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.15.0-33-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11906000
    X Window Manager:  Mutter (Muffin)
    Steam Runtime Version:  steam-runtime-beta-release_2018-06-14

Video Card:
    Driver:  NVIDIA Corporation GeForce GTX 970/PCIe/SSE2
    Driver Version:  4.6.0 NVIDIA 396.54
    OpenGL Version: 4.6
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 144 Hz
    VendorID:  0x10de
    DeviceID:  0x13c2
    Revision Not Detected
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 1920 x 1080
    Primary Display Size: 20.91" x 11.77" (23.98" diag)
                                            53.1cm x 29.9cm (60.9cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 4096 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: 20K2

Memory:
    RAM:  32159 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Total Hard Disk Space Available:  841268 Mb
    Largest Free Hard Disk Block:  264354 Mb
    VR Headset: None detected

Recent Failure Reports:

just fyi there is a long standing bug on amd mesa drivers regarding faces not rendering correctly. I don't think the game should be white listed until thats resolved.

https://bugs.freedesktop.org/show_bug.cgi?id=104302

all the other bugs apart from the facial animation bug have been resolved. just need a fix for that

Whitelist Request

• Name of the game to be whitelisted: Wolfenstein II: The New Colossus
• Steam AppID of the game: 612880

System Information

• GPU: GTX 970
• Driver/LLVM version: NVIDIA 415.25
• Distro version: Ubuntu 16.04.5 LTS
• Link to full system information report as Gist
• Proton version: 3.16-6 Beta

I confirm:

• [x] that pressing the Play button in the Steam client is sufficient.
• [ ] that runtime config options are necessary to run the game.
• [ ] that no workarounds other than PROTON_* env variables are necessary.

Issues

• [x] I haven't experienced any issues.
• [ ] There are no issues left open for this game.
• [ ] Although I consider the gaming experience equal to Windows there are remaining issues.

I must test the facial animations myself, but does anyone know how far along is the fix for the water rendering bug ?

Hello @mmeyran, what water rendering bug? Was it being tracked on another issue tracker?

I've seen it mentioned in another comment, but I couldn't find it being tracked. Water in-game isn't rendered - using latest Padoka PPA Stable (Mesa 18.3.3) on Ubuntu 18.04.2 and a RX480 8Gb. I'll try with Padoka PPA git to see if by any chance the problem isn't the same as faces. I think I remember seeing water rendered once, but then it was rapidly "un-drawn" with an expanding circle of non-rendered water.

Is this still working for you? I've seen one recent report on Proton DB stating that it stopped working, and for me the game hangs after the logo videos. I can shortly hear a sound playing before the game hangs with a black screen and I have to kill it.

When adding +com_skipBootSequence 1 as launch option to skip the videos, I can see the screen where I should select the brightness though. But the game is frozen then. After killing and starting it again I quickly pressed enter, which seemed to have chosen the brightness, so after another restart, I saw the unlock message about the DLC(s). I was able to press enter quickly enough again, so that I can see now the screen where I can choose a new game and options. But it's still stuck then. I can see the mouse cursor in the top left corner but the image is blurry. Music keeps playing though. I also have set r_mode "11"in SteamLibrary/steamapps/compatdata/650500/pfx/drive_c/users/steamuser/Saved Games/MachineGames/Wolfenstein II The New Colossus/base/Wolfenstein II The New ColossusConfig.local which seems to be my native resolution of 1920x1080.

Tried Proton 3.16-9 beta and 4.2-7. Ubuntu 18.04 LTS, nVidia 430.26.
Wolfenstein: The New Order and Wolfenstein: The Old Blood work fine though.

I just found out, that when I let proton create the debug commands with PROTON_DUMP_DEBUG_COMMANDS=1 %command% +com_skipBootSequence 1 and start the game then via

cd /tmp/proton_$USER
./run

it works. So there seems to be a race condition or so?

edit:
I seems to be an issue with the steam overlay. Which is disabled when running through the run command. When disabling the Steam Overlay while in-game from the games' context-menu, it also works.

Water does not render. This bug can be observed in the first mission in "Section F".
Proton 4.11-9, Mesa Aco 20, Amd Rx480, Vulkan Renderer

Hi, I'm terribly sorry I'm answering this late. Anyways, here's my system info:
https://gist.github.com/DasCapschen/a366bf93f0a0859f3d82de2bae101b4a

I have just tried it using the llvm compiler, although now on Proton 4.11-10, and water does work!
But I have also tried with aco again, and it works there too. Although I did have water working before with aco, but only once... and once I saw it disappear during a level (like mmeyran described it above), so maybe it breaks over time?
Don't really have the time to test right now, but it looks good at the moment!

There's a regression with this game with Proton 5.0-1. With 4.11-12 everything runs perfectly. With 5.0-1 the mouse is jerky and reticent to move in menus and so on. It seems to be OK when controlling movement, just bad when it's moving a mouse pointer.

Sure. I've added both versions in case you wanted to see any differences between them. That's just loading up the game and wiggling the mouse on the main menu for a couple of seconds in each case.

5.0.1 steam-612880.log
4.11.12 steam-612880.log

@CKWarner could you give some more information about your setup? What GPU/drivers are you using? Do you have a non-standard mouse? Any other hints that might be relevant?

I was not able to immediately replicate the mouse behavior you are describing. I did notice that when I moved the cursor quickly, especially in a circular motion, the cursor would lag behind my hand a bit, but this was the same in 4.11-12 and 5.0-1, and I wonder if it is a game choice to not let the custom cursor move faster than a certain speed (I have seen this with some other games).

It's a perfectly straightforward setup: Kubuntu 18.04, RTX 2080 Ti with the 440.59 driver, SteelSeries Rival 310 mouse.

The pointer works perfectly in 4.11-12 and barely functions at all in 5.0-1.

@CKWarner Thank you for the details. That gives me a much better place to start since the issue doesn't seem to be universal to all setups, based on my initial testing :)

Edit: I happened to have access to the exact same mouse since there was another bug in the past that was specific to that category of mice. I was able to reproduce the issue with the mouse -- interestingly it also seems to be a NVIDIA specific bug.

I also noticed a similar thing in Proton 5.0.x. But I am on RX 580, DarkProject ME-1 mouse. Everything is OK in the main menu, but in the in-game menu and in the game itself mouse behaves weird. Small mouse lag was present in the menu in previous versions of Proton but this is a completely different thing. What I noticed:

• The strict horizontal or vertical movement works OK.
• Movement in both axis (diagonal, circular) leads to this issue but only if I move the mouse with enough speed. The cursor almost doesn't move. It does move correctly only when I move the mouse very slow.
• This "stuck" doesn't affect FPS.
• I see the same issue in Doom 2016 (379720).

steam-612880.log

Fixed in 5.0.3

I can confirm that it's fixed for Doom 2016 as well

The buffer size change (386f43d) in 5.0-3 has fixed it for me, too.

@alasky17 Unfortunately it appears this application fails to launch using a fresh Ubuntu 19.10 installation:

steam-612880.log

System Information

• GPU: RTX 2060
• Driver/LLVM version: NVIDIA 440.59
• Kernel version: 5.3.0-40-generic
• Link to full system information report as Gist
• Proton version: 5.0-3

@mimattr I have a feeling that you may have run into an inconsistent bug where the prefix is not created correctly on the first launch. Please try deleting the Wolfenstein II prefix (~/.steam/steam/steamapps/compatdata/612880) and try launching again.

I have a feeling that you may have run into an inconsistent bug where the prefix is not created correctly on the first launch.

@alasky17 Both ~/.steam/steam/steamapps/compatdata/612880 and ~/.steam/steam/steamapps/shadercache/612880 have been deleted before each launch but it appears the issue is actually due to using MangoHud, the application works as expected without the MANGOHUD=1 %command% launch option.

Apologies for any confusion, this issue has now been reported to the MangoHud tracker

Hello @mrjohnc, I suspect you're seeing an Intel vulkan driver issue and looking at the advertised minimum specs, Intel graphics are not supported. That said, you might get lucky mentioning your issue to the mesa devs.

Thanks very much, where would I do this?

Wolfenstein II: The New Colossus, unplayable, white flashing screen

Issue transferred from #3989.
@mrjohnc posted on 2020-06-15T17:48:41:

Compatibility Report

* Name of the game with compatibility issues: Wolfenstein II: The New Colossus

* Steam AppID of the game: 612880

System Information

* GPU:  Intel UHD Graphics 620 - 1024 MB, Core: 1150 MHz, Integrated

* Driver/LLVM version:  Mesa 20.0.7

* Kernel version:  Linux Kernel 5.6

* Link to full system information report as [Gist](https://gist.github.com/): https://gist.github.com/mrjohnc/5a8183d2829cf175ee593979b5a61922

* Proton version: 5.0.9

I confirm:

* [x]  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.

The log is over 20mb,

Symptoms

Some of the opening cutscene plays normally, the rest are just very fast white flashing, once game starts who screen is white flash
steam-612880.log
ing but with overlay visible. The game is running fine judging from the sound, just can't see anything...

Reproduction

Start game
Try any graphics setting (I've tried changing resolution and changing all graphics options
steam-612880.log

Posted bug at https://gitlab.freedesktop.org/mesa/mesa/-/issues/3138

Posted bug at https://gitlab.freedesktop.org/mesa/mesa/-/issues/3138

@mrjohnc Also posting result of the investigation here.

The issue is similar to https://github.com/ValveSoftware/Dota-2-Vulkan/issues/314 and boils down to old GLSLang not being able to generate NonReadable decoration for image types when compiling from HLSL.
In RenderDoc I see a dispatch call having R16_FLOAT image being used as r11f_g11f_b10f in shader:

If I add writeonly modifier to the image - it works correctly, since now type information in shader is not used. On Radeon there is no issue since it supports shaderStorageImageReadWithoutFormat.

So it is a game bug, however I don't think the game would fix this issue, since it isn't updated for a while. Most likely we would have to make a workaround in the driver.

@werman thanks so much for this, is this something I could try myself to confirm by changing a file permission or is it more buried than that? (I'm not a programmer)

@werman thanks so much for this, is this something I could try myself to confirm by changing a file permission or is it more buried than that? (I'm not a programmer)

Unfortunately there is no simple way to check it.

@werman ok, no problem :)

Current workaround for me at least is to reduce shaders quality a notch.

Current workaround for me at least is to reduce shaders quality a notch.

Thanks, can you expand on what you mean here? Do you mean a setting in game?

yeah, in-game advanced graphical settings - I have the bug at highest
quality setting, it goes away if I reduce it by one notch. I don't remember
if it's a specific water rendering setting or just shaders quality setting.

On Sat, Jun 20, 2020, 09:04 John Cummings [email protected] wrote:

Current workaround for me at least is to reduce shaders quality a notch.

Thanks, can you expand on what you mean here? Do you mean a setting in
game?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/1113#issuecomment-646955147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD67V7LCDWFVLSQUPC5SEM3RXRNRVANCNFSM4FSYORJA
.

yeah, in-game advanced graphical settings - I have the bug at highest quality setting, it goes away if I reduce it by one notch. I don't remember if it's a specific water rendering setting or just shaders quality setting.
…
On Sat, Jun 20, 2020, 09:04 John Cummings @.***> wrote: Current workaround for me at least is to reduce shaders quality a notch. Thanks, can you expand on what you mean here? Do you mean a setting in game? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <[#1113 (comment)](https://github.com/ValveSoftware/Proton/issues/1113#issuecomment-646955147)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD67V7LCDWFVLSQUPC5SEM3RXRNRVANCNFSM4FSYORJA .

Unfortunately this doesn't work for me, I tried all quality settings for all options in game and nothing gets rid of the white screen.

The game crashes for me after the "amd/ryzen/Bethesda" intro videos at the point where the menu should appear, with the "could not write crash dump" dialog.

steam-612880.log

System Information

GPU: Nvidia Geforce 1060 GTX
Driver/LLVM version: NVIDIA 440.82
Kernel version: 5.7.4
Proton version: 5.0-9

NOTE

My system does not use/have installed pulseaudio. And the crash (according to the log) happens in
FAudioVoice_SetChannelVolumes+0xbb9() in libfaudio.so.0

Maybe it is faudio + ALSA (snd_pcm_recover) related?

But other games, RAGE2, Wolfenstein: The New Order, Monster Hunter World, ... work just fine with the same audio setup on the same PC.

Steam overlay is disabled.

I tried using
"Proton 5.0 [debug]"
and
Launch Option:
WINEDEBUG="+timestamp,+pid,+tid,+seh,+debugstr,+module,+xaudio2" PROTON_LOG=1 %command%

Unhandled exception: page fault on read access to 0x00000000, invalid program stack in 64-bit code (0x00007fdfa5fb3e59).

...
Backtrace:

=>0 0x00007fdfa5fb3e59 FAudioVoice_SetChannelVolumes+0xbb9() in libfaudio.so.0 (0x00000000025442f0)
0x00007fdfa5fb3e59 FAudioVoice_SetChannelVolumes+0xbb9 in libfaudio.so.0: movq	(%rdi),%rdi

Hope this helps.

steam-612880.log

Game crashing with FATAL ERROR: getSwapchainImagesKHR failed with error (VK_SUCCESS)
Radeon RX 5700, Arch Linux, Proton 5.0-9
ErrorLog_07-03-2020__05-11-01pm.txt
steam-612880.log

@kisak-valve, thanks. Working with mesa-git

Hello All,

Looks like I found a new problem, it tricky:

When you load a save from steam cloud in a new installation, the game crash, you can see the attached log in this comment.
However if you start a new game, it works, please let me know any advice you may have

steam-612880.log

Got what seems to be a regression in Experimental. On the mission where BJ drives back to Mesquite, the entire screen goes black (seemingly due to a post-processing effect gone wrong, since the UI elements are still present) and it's impossible to navigate around. There's another report of this on ProtonDB.

Distro: Arch Linux x86_64
Kernel: 5.19.3-arch1-1
CPU: Ryzen 7 3700X
GPU: RX 6600 XT
RAM: 32 GB
Mesa: 22.1.7 (RADV)
Proton: Experimental

Proton 7.0-4 behaves as expected:

Here's my system information from Steam.

And here's the logfile (opened the game with a cleared compatdata folder, fixed video settings, opened relevant save): steam-612880-experimental.log

I will warn that it seems to be a bit touchy with reproduction. As far as I can tell, loading the scene with 7.0-4 even once fixes the problem entirely until the compatdata folder for the game is cleared and the level is entered again from a previous save.

@serebit Is it possible to post your save file somewhere to make this easier to investigate?

I'll have to get back to that point, but I can give that a shot, sure.

Got it to happen on a different level, start of New Orleans, on 7.0-4 no less. Trying to make a save that reproduces it.

Edit: I don't know why, but this is being really stubborn wrt reproduction on 7.0-4. Still trying, but it may take a bit for me to nail down a way to consistently reproduce it.

Actually, I think this should work to reproduce on Proton Experimental: wolf2-repro.zip

Toss the contents into pfx/drive_c/users/steamuser/Saved Games/MachineGames/Wolfenstein II The New Colossus/base/savegame.user/<UID> and hit "Continue" on the main menu. The issue only seems to happen sometimes, though.

@serebit Thank you for the save game! I tried it several times and unfortunately didn't see the black rendering failure which makes this difficult to diagnose :/ It would be easier if it was a regression, but it sounds like it is not? Could you see if you can also reproduce the issue on 6.3-8?

In lieu of that, I have two videos showing reproduction of the issue. The first contains 8 minutes of attempts with two partial reproductions (see description for timestamps), and the second contains one full reproduction in the New Orleans level, along with some messing around with video settings to fix the issue while the level is still loaded. I also have MangoHud up for both sets of attempts.

Video 1: https://www.youtube.com/watch?v=BsJvIbxe5RY
Video 2: https://www.youtube.com/watch?v=yAK5Xi-0TzU

Also worth noting that there's another report of this issue out there, specifically noting seeing it in the Mesquite level, and the report is from a Steam Deck: https://www.protondb.com/app/612880

This could imply that it's a RADV issue and not a Proton one, since this game uses Vulkan directly.

Hello All!

Switching off Vsync is working for you ? For me it's crashing:

It happens to me too @xcom169, I was able to disable it in the config file /home/user/.steam/steam/steamapps/compatdata/612880/pfx/drive_c/users/steamuser/Saved Games/MachineGames/Wolfenstein II The New Colossus/base/ in the Wolfenstein II The New ColossusConfig.local file, putting to 0 the value of r_swapInterval (if you don't have it you can write in a new line r_swapInterval "0")

Winsock Initialized
idCommonLocal::Init() time 20: 0.118s
------ Initializing File System ------
Current search path:
    - C:/users/STEA~WEN/SAVE~YWG/MachineGames/Wolfenstein II The New Colossus/base/
    - Z:/home/relwi/.local/share/Steam/steamapps/common/Wolfenstein.II.The.New.Colossus/base/
------ File System initialized.
WARNING: ReadJsonFile: could not read file: packagechunklist.json
Executing build.cfg...
------ Command Line ------
 "Z:\home\relwi\.local\share\Steam\steamapps\common\Wolfenstein.II.The.New.Colossus\NewColossus_x64vk.exe"
------ CPU Information ------
    1 CPU package, 8 physical cores, 16 logical cores
    3600 MHz    AMD CPU with MMX & SSE & SSE2 & SSE3 & SSSE3 & SSE41 & SSE42 & AVX & HTT
    32768 kB 1st level cache, 524288 kB 2nd level cache, 16777216 kB 3rd level cache
    15920 MB System Memory
idCommonLocal::Init() time 30: 0.134s
SearchDLC: found 0 dlcs
idLib::SetProduction( PROD_PRODUCTION )
idCommonLocal::Init() time 40: 0.158s
------- Initializing renderSystem --------
PreliminaryRenderSetup
...registered window class
-------------------------
Application Info
-------------------------
App    : Wolfenstein II The New Colossus - 1.0.3
Engine : idTech - 6.5.0
-------------------------
Instance Extensions
-------------------------
 + VK_KHR_surface
 + VK_KHR_win32_surface
 + VK_KHR_get_physical_device_properties2
-------------------------
Device Extensions
-------------------------
+ VK_AMD_shader_ballot
+ VK_AMD_shader_trinary_minmax
+ VK_AMD_gcn_shader
+ VK_EXT_shader_subgroup_ballot
+ VK_AMD_gpu_shader_half_float
+ VK_AMD_gpu_shader_int16
DeviceName: AMD Radeon RX 5500 XT (RADV NAVI14)
DeviceType: VK_PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
-------------------------
Using device: 0 - 'AMD Radeon RX 5500 XT (RADV NAVI14)' because of device type VK_PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
-------------------------
Device Extensions
-------------------------
 + VK_KHR_swapchain
 + VK_AMD_shader_ballot
 + VK_AMD_shader_trinary_minmax
 + VK_AMD_gcn_shader
 + VK_EXT_shader_subgroup_ballot
 + VK_AMD_gpu_shader_half_float
 + VK_AMD_gpu_shader_int16

-------------------------
Vulkan Device Info:
-------------------------
Vendor : AMD
GPU    : AMD Radeon RX 5500 XT (RADV NAVI14)
VRAM   : 8192 MiB
Driver : 21.10.2 (05802001)
VK API : 1.3.224


Setting GPU culling according to user option: on
Initializing Vulkan subsystem
ShowGameWindow: (0, 0) 1920 x 1080, full screen
FATAL ERROR: getSwapchainImagesKHR failed with error (VK_SUCCESS)
TIMER: idRenderSystemLocal::Init() took 80.8810 ms

@Relwi I tried with X.Org. It looks it's working. Only Wayland is problematic?

@xcom169 yes, only in Wayland

I have two bugs there , blackscreen when the start game, load same save , then black screen disappear .
and second one is the water not rendered in any mission
radeon 6600xt , last mesa
proton 7.0-6

@kisak-valve Hello!
steam-612880.zip
https://gist.github.com/koloved/e5e9ebde78c84383d87dedee54e4679b

and RADV_DEBUG=nodcc steam-612880_nodcc.zip

surprisingly Nodcc command help with both bugs, but its work sometimes , a attached the log when its works

and i notice its worked always when i put PROTON_LOG=1 before RADV_DEBUG=nodcc
without PROTON_LOG=1 its not working

thanks !

and also its not worked with full option RADV_DEBUG=nodcc,nodisplaydcc

Trying to disable vsync results in a game crash
Launch options: PROTON_LOG=1 RADV_DEBUG=nodcc,nodisplaydcc %command% +com_skipBootSequence 1
System info:
-RX 5600 XT
-Ryzen 7 3700X
-Kernel: 6.2.9-arch1-1 (64-bit)
-Driver: Mesa 23.0.1 / LLVM 15.0.7
gist
This first log was me booting up the game and attempting to switch vsync on:
steam-612880.log
This log is me playing the game for a while then crashing when changing vsync:
steam-612880.log

Here is a screenshot of the crash and error, same as what another user has shown above:

@clawwwie thank you for the report.
This have now been worked around in the newly released mesa drivers 23.1.2 and should be working when that version or above is used.

Thanks. Its really good news

On Sat, 22 Jul 2023, 03:33 kisak-valve, @.***> wrote:

Tracking note: Dropping the mesa and RADV labels because there doesn't
appear to be recent feedback that there's an active video driver issue to
follow.

Older Intel / ANV fixed by
https://gitlab.freedesktop.org/mesa/mesa/-/commit/ded9cb904f02cfe4206f88f8a41f49258f09f2b0
More recent AMD / RADV fixed by
https://gitlab.freedesktop.org/mesa/mesa/-/commit/34f9dd349177de8828ca9cec9b20a1d409663ec8

If you're seeing an issue with mesa 23.1.2 or newer, please add an updated
note with details.

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

Some areas have black lines or gaps between textures. This occurs with no custom launch options. "RADV_DEBUG=nodcc,nodisplaydcc %command%" also does not change the behavior.

System Info gist

steam-13956693457578754048.log

Driver: Mesa 26.1.3
Kernel: 7.1.2-2-cachyos
CPU: R7 9850X3D
GPU: RX 9070XT