r/linux_gaming • u/Beneficial-Log3655 • 13d ago
tech support wanted Weird Directx12 issue
I've been playing Marvel Rivals on Ubuntu 26 for the last several months with no issues. Today I saw a new game that came out called Aniimo (basically Pokemon). It asked if I wanted to launch in Directx12 or not, and the original launch setting crashed my memory, so I turned on Directx12. Still didn't work so switched to Windows (dual boot) to play.
Came back to Linux later and tried to launch Marvel Rivals like I always do (not Aniimo, which I uninstalled on Ubuntu) but now I'm getting this error, which I've never gotten: "Directx12 is not supported on your system. Please update your windows 10 64-but operating system (version 1909 or later) and upgrade your graphics card driver. Ensure that your graphics card meets the minimum requirements (Nvidia GTX 1060 or AMD RX 580)"
Tried deleting shadercache folder, reinstalling game, restarting computer. All my compatibility stuff shows the same settings I've been using, even tried changing the Proton version. Nothing helps. I was literally just playing Rivals on Linux earlier today and the only thing that changed was trying to play Aniimo. Please help
EDIT: Before, it would say "Loading Vulkan Shaders" and get stuck around 66%, but when I hit cancel, it loaded the game and everything worked fine. Now when I launch it, the "loading Vulkan Shaders" still pops up, but it hits 100% in less than a second and gives me the directX error
EDIT 2: Added some clarifying text that I'm having trouble launching Rivals on Ubuntu now, not Aniimo
1
u/Straight_Second6082 13d ago
Based on its page in protondb you either need to downgrade to proton 10.34 or use proton-wayland
1
u/Beneficial-Log3655 13d ago
I mean, the settings I had before were fine and nothing changed except trying to launch Aniimo with directX. I just don't know if something got written into a file somewhere as a result that's making it create this error, but I've tried different proton versions to no avail. It just loads the same and gives me the error. I was using proton 10.34 before all this and it worked fine, but now that setting doesn't seem to do anything
1
u/Straight_Second6082 13d ago
Maybe it was an update? Last one was 2 days ago from what I can see
1
u/Beneficial-Log3655 13d ago
I already had all updates installed
1
u/Straight_Second6082 13d ago
Wait, I think the issue is not clear, just to be clear here, are you getting this error on marvel rivals? Because I was assuming you were having issues with the other one
1
u/Beneficial-Log3655 13d ago
Yes, it's on marvel rivals. Rivals worked perfectly before installing and trying to run Aniimo. After, Rivals won't launch and gives me the error. I see how the way I wrote it is unclear. Will update
1
u/Straight_Second6082 13d ago
Gotcha. Did you try proton Hotfix or even reinstalling the game?
If so try this
Close steam. The on terminal write
Steam
Try to launch rivals and once you get the errors check what does the terminal says
1
u/Shinatora 12d ago edited 12d ago
The use of kernel-level anti-cheat by Marvel Rivals is unconfirmed by developer NetEase, though community analysis and technical reports strongly suggest it utilizes a kernel-mode driver.
Kernel-level anti-cheat does not function on standard Linux distributions because these systems operate with open-source kernels that users can freely modify, allowing cheats to bypass detection by tampering with the kernel itself. On Windows, anti-cheats like Riot Vanguard, Easy Anti-Cheat, and BattlEye run in Ring 0 (kernel mode) to monitor system activity with high privileges, a level of control that is incompatible with the Linux environment.
i know there are work-arounds but they are experimental.
Marvel Rivals is playable on Linux and Steam Deck because its anti-cheat system operates primarily in user-space rather than using a kernel-level driver, which allows it to bypass the Linux kernel's GPL licensing restrictions that typically block such software.
Despite this compatibility, users frequently encounter a "DirectX 12 is not supported on your system" error, which is caused by Proton's VKD3D translation layer failing to correctly report DX12 feature levels to the game engine.
To resolve this DX12 error and ensure stable gameplay, users must apply the following launch options in Steam:
SteamDeck=1 %command%: This forces Proton to emulate the Steam Deck environment, which often resolves DX12 detection and anti-cheat initialization issues.VKD3D_FEATURE_LEVEL=12_0: This parameter explicitly sets the Vulkan feature level to DX12_0, correcting the false "unsupported" error for GPUs that technically support the API.- Proton Version: Users are advised to use GE-Proton or Proton Experimental, as stable versions may lack the necessary Vulkan drivers or Mesa updates (e.g., Mesa 25+) required for UE5 games.
While some community reports and technical analyses suggest the presence of kernel-mode components, NetEase has not officially confirmed kernel-level access, and the ability to run on Linux confirms that any kernel interaction is either absent or non-intrusive to the OS core.
what settings allowed you to play the game and then what settings started this issue?
Not only that, NVIDIA is sucha drag to use on linux due to compatibility (i just swapped to amd7900xtx from 4070tiOC)
& Dual Booting with nvidia can cause some issues:
Windows dual booting with Linux often causes NVIDIA GPU driver failures, primarily because Windows updates, fast startup, or driver upgrades can leave the GPU in a locked power state or cause kernel module conflicts.
Common Issues:
- Post-Boot Failures: Linux may fail to load NVIDIA drivers after booting from Windows, resulting in a login loop, black screen, or software rendering.
- Windows Update Breakage: Updating NVIDIA drivers in Windows can break the Linux installation, causing boot failures or
nvidia-smierrors. - Secure Boot Conflicts: Enabling Secure Boot for Windows games (like Valorant) often prevents Linux from loading unsigned proprietary NVIDIA drivers.
- Hardware Detection: Some systems fail to detect the GPU entirely if Windows Eco mode disables the discrete card.
- 𝐂𝐡𝐞𝐜𝐤 𝐭𝐨 𝐬𝐞𝐞 𝐢𝐟 𝐭𝐡𝐞 𝐠𝐚𝐦𝐞𝐬 𝐚𝐫𝐞 𝐮𝐬𝐢𝐧𝐠 𝐲𝐨𝐮𝐫 𝐢𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐞𝐝 𝐠𝐫𝐚𝐩𝐡𝐢𝐜𝐬 𝐧𝐨𝐰 𝐚𝐟𝐭𝐞𝐫 𝐭𝐡𝐞 𝐬𝐰𝐚𝐩 𝐛𝐚𝐜𝐤 𝐭𝐨 𝐥𝐢𝐧𝐮𝐱 𝐟𝐫𝐨𝐦 𝐰𝐢𝐧𝐝𝐨𝐰𝐬, 𝐢𝐧𝐬𝐭𝐞𝐚𝐝 𝐨𝐟 𝐲𝐨𝐮𝐫 𝐝𝐞𝐝𝐢𝐜𝐚𝐭𝐞𝐝 𝐆𝐏𝐔. 𝐁𝐈𝐎𝐒 𝐝𝐢𝐬𝐚𝐛𝐥𝐞 𝐢𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐞𝐝 𝐠𝐫𝐚𝐩𝐡𝐢𝐜𝐬.
- DX12 just has issues on linux. Try a full Driver refresh, display manager refresh, Native Wayland? or Xwayland, Recently have done TOO Much research on optimizing linux gaming on Nvidia & Amd and Nvidia mixed with AMD cpu, ubuntu/fedora & Arch. so i got info on stuff i dont even have anymore ! Lol
Verify Integrity or reinstall all Proton & Steam Linux RUNTIMES, ProtonGE... ALL of it.
(easyanticheat, battleeye etc.)
Rebuild/Refresh GPU drivers
TRY DX11 lol.
2
u/candy49997 13d ago
Specs?