Error: Failed to initialize player

[Tianmaru]

Hello everyone, I am using Debian 9 with a Radeon HD7790 graphics card.
I recently bought "The Turing Test" and "The Room 3", because I thought, I could play them via Proton. Turns out, I was wrong. When I try to launch one of those games, I get an error message:

Failed to initialize graphics.
Make sure you have DirectX 11 installed, have up to date
drivers for your graphics card and have not disabled
3D acceleration in display settings.
InitializeEngineGraphics failed

I installed mesa-vulkan-drivers (couldn't install mesa-vulkan-drivers:i386 because it was colliding with the other one) like its stated in the requirements for proton and I tried some other things, but nothing seems to work.
Also, I am wondering, if this problem can be fixed at all, because "lspci -k | grep -EA3 'VGA|3D|Display'" resolves in:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
        Kernel driver in use: i915
        Kernel modules: i915
--
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon HD 7790/8770 / R7 360 / R9 260/360 OEM]
        Subsystem: ASUSTeK Computer Inc. Bonaire XT [Radeon HD 7790/8770 / R7 360 / R9 260/360 OEM]
        Kernel driver in use: radeon
        Kernel modules: radeon

So I believe, my graphics card is too old to be combatible with the newer amdgpu drivers, which I may need?
I would be really glad if someone could help me with this.

[thetargos]

You need to explicitly enable AMDGPU for that generation of graphics chips (GCN 1.1) As far as I know, for vilkan support through RADV. I have little experience with AMD graphics GCN 1.x and Vulkan.

[Aoi Blue]

Originally posted by thetargos:

You need to explicitly enable AMDGPU for that generation of graphics chips (GCN 1.1) As far as I know, for vilkan support through RADV. I have little experience with AMD graphics GCN 1.x and Vulkan.

If that doesn't work you need to set your launch parameters to:

PROTON_USE_WINED3D=TRUE %command%

[Marlock]

Originally posted by thetargos:

You need to explicitly enable AMDGPU for that generation of graphics chips (GCN 1.1) As far as I know, for vilkan support through RADV. I have little experience with AMD graphics GCN 1.x and Vulkan.

Here is how, from my post in an older thread:
(reccomended path is using the radeon.si_support=0 and amdgpu.si_support=1 boot parameters)

Originally posted by Marlock:

to use amdgpu instead of radeon on r9-200 and r9-300 series cards you'll need to jump through some extra hoops...

in short, you need to enable experimental usage of amdgpu and block the preferential use of radeon

Valve's proton requirements page now has a section with instructions for this because only amdgpu has support for Vulkan (which DXVK needs for proton support to DX10/DX11 games):
https://github.com/ValveSoftware/Proton/wiki/Requirements#enable-vulkan-on-radeon-r9-200300-series

these instructions involve blocking the radeon module with modprobe and I'm not sure how easy it would be to revert to the old config if it can't boot, freezes, goes to a black screen or falls to a terminal instead of GUI... It should cause no permanent damage to the OS, but maybe having a liveboot usb will help make recovery easier (always good to have one around)...

...and maybe you should try another route to the same result first, via kernel boot parameters, since it is trivial to revert boot parameters to the original in case something goes wrong

just get to the boot menu, select the default boot entry, type "e" to edit the entry and type all the code below into the entry at the end:

radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dpm=1 amdgpu.dc=1

this is an example of how editing the boot menu looks like (but with different edits):
https://linuxmint-installation-guide.readthedocs.io/pt_BR/latest/boot_options.html#nomodeset-boot-option

that should be enough to test if amdgpu works for your card, and next time you boot it will have reverted to radeon on its own already, because the entry editing via grub is not stored for later

There is a way to make the change permanent (and can be reversed, but test it via grub entry editing at least once first):
https://askubuntu.com/questions/927601/i-think-im-using-radeon-instead-of-amdgpu-how-do-i-change

for me with an AMD HD 7770 this was enough to have AMDGPU working (a little before I retired it), without altering modprobe blacklists or anything

[Tianmaru]

Originally posted by Aoi Blue:

Originally posted by thetargos:

You need to explicitly enable AMDGPU for that generation of graphics chips (GCN 1.1) As far as I know, for vilkan support through RADV. I have little experience with AMD graphics GCN 1.x and Vulkan.

If that doesn't work you need to set your launch parameters to:

PROTON_USE_WINED3D=TRUE %command%

Thank you! That worked for "The Room 3". The solution seems kind of simple, yet I have fount it nowhere.

Originally posted by Marlock:

Originally posted by thetargos:

You need to explicitly enable AMDGPU for that generation of graphics chips (GCN 1.1) As far as I know, for vilkan support through RADV. I have little experience with AMD graphics GCN 1.x and Vulkan.

Here is how, from my post in an older thread:
(reccomended path is using the radeon.si_support=0 and amdgpu.si_support=1 boot parameters)

Originally posted by Marlock:

to use amdgpu instead of radeon on r9-200 and r9-300 series cards you'll need to jump through some extra hoops...

in short, you need to enable experimental usage of amdgpu and block the preferential use of radeon

Valve's proton requirements page now has a section with instructions for this because only amdgpu has support for Vulkan (which DXVK needs for proton support to DX10/DX11 games):
https://github.com/ValveSoftware/Proton/wiki/Requirements#enable-vulkan-on-radeon-r9-200300-series

these instructions involve blocking the radeon module with modprobe and I'm not sure how easy it would be to revert to the old config if it can't boot, freezes, goes to a black screen or falls to a terminal instead of GUI... It should cause no permanent damage to the OS, but maybe having a liveboot usb will help make recovery easier (always good to have one around)...

...and maybe you should try another route to the same result first, via kernel boot parameters, since it is trivial to revert boot parameters to the original in case something goes wrong

just get to the boot menu, select the default boot entry, type "e" to edit the entry and type all the code below into the entry at the end:

radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dpm=1 amdgpu.dc=1

this is an example of how editing the boot menu looks like (but with different edits):
https://linuxmint-installation-guide.readthedocs.io/pt_BR/latest/boot_options.html#nomodeset-boot-option

that should be enough to test if amdgpu works for your card, and next time you boot it will have reverted to radeon on its own already, because the entry editing via grub is not stored for later

There is a way to make the change permanent (and can be reversed, but test it via grub entry editing at least once first):
https://askubuntu.com/questions/927601/i-think-im-using-radeon-instead-of-amdgpu-how-do-i-change

for me with an AMD HD 7770 this was enough to have AMDGPU working (a little before I retired it), without altering modprobe blacklists or anything

I tried doing that by blacklisting the radeon module, resulting in me being stuck after the grub screen (I guess because xserver wasn't starting). Had to solve this by adding "nomodeset" to the grub script and undoing the blacklist. So I guess, my graphics card isn't compatible with amdgpu.

[Marlock]

you have to whitelist amdgpu AND blacklist radeon simultaneously, also the other parameters (for display code and power management) were necessary in my case, so the best attempt is all at once (at most skipping cik entries that should be for later models but no harm in keeping those):

radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dpm=1 amdgpu.dc=1

if you edit the grub entry on boot via grub itself, it should only require a reboot to eliminate the changes, at most a power-off and power-on to erase any lingering data/state in the gpu itself that might get in the way of a new attempt

[Corona]

Lots of games suddenly don't work on Proton recently, I thought it was my problem, but I found out that other games could run without issue with WINE+DXVK, so it is a game specific or Steam problem.
Or...they have bad compatibility with my CPU......

[nHail]

Originally posted by Aoi Blue:

Originally posted by thetargos:

You need to explicitly enable AMDGPU for that generation of graphics chips (GCN 1.1) As far as I know, for vilkan support through RADV. I have little experience with AMD graphics GCN 1.x and Vulkan.

If that doesn't work you need to set your launch parameters to:

PROTON_USE_WINED3D=TRUE %command%

Hey i'm sorry to ask a stupid question, but where do I change the launch parameters?

[Rashkavar]

To change launch properties:
Bring up properties (right click the game in your library's list, click Properties
There should be a button near the middle of the General tab labeled "Set Launch Options"
Copy text into the space provided, hit OK.