Is this a recent regression? This was one of the first games that ever worked with DXVK and I have never seen issues like this.
Also, does this happen without vkbasalt?
Is this a recent regression? This was one of the first games that ever worked with DXVK and I have never seen issues like this.
Also, does this happen without vkbasalt?
I just tested this game out recently so I've only used 2.5.2 on Bioshock 1, 2, and now infinite. (Was in the mood to play them 😅) Infinite was the only one that produced this issue. To answer your second question: Yes it does still happen without vkbasalt. I turned everything off in heroic launcher (in the game settings) only thing that was left selected were proton experimental for one test and wine ge for another test. Much appreciated for your time looking into this. Thank you
Fwiw from what i can tell i have not been able to reproduce this issue so far in game. Tested on both a Intel Arc b580 and a AMD rdna2 iGPU.
This is using the Steam version of the game
Fwiw from what i can tell i have not been able to reproduce this issue so far in game. Tested on both a Intel Arc b580 and a AMD rdna2 iGPU. This is using the Steam version of the game
I'm using the non steam version. I'm using a drm free gog copy that I bought a long time ago. Heroic game launcher is what I am using for tests.
Just to make sure I even added my GOG game exe to steam using proton experimental and it's doing the same thing. Seems like steam has preapplied fixes or something when using the steam official version?
Seems like steam has preapplied fixes or something when using the steam official version?
No, that's extremely unlikely. What is more likely is that it's a driver bug exclusive to RDNA3 GPUs.
Seems like steam has preapplied fixes or something when using the steam official version?
No, that's extremely unlikely. What is more likely is that it's a driver bug exclusive to RDNA3 GPUs.
Alright bout to download the steam version just to see.
Steam will download the native linux port using opengl by default unless you force proton as compat tool though. But i'm sure @Blisto91 was aware of that.
Ye i made sure it was the Proton version
Downloading now and forced proton experimental. I am keeping my settings the same as in heroic launcher with esync, fsync, gamemode, mangohud, and vkbasalt enabled.
Still same issue even on the steam official version. Maybe it only shows up when on 7000 series gpus? I've noticed some games recently add fixes for the 7000 series so it could be possible that what mbriar is saying is true. Kinda weird cause out of all the bioshocks this is the only one to have this issue. Never had issues in any other games, most of the unreal engine 3 as well.
Driver bugs that trigger only in specific games on some specific GPUs aren't really all that uncommon.
You could try https://github.com/GPUOpen-Drivers/AMDVLK and test if it happens with that as well.
Driver bugs that trigger only in specific games on some specific GPUs aren't really all that uncommon.
Just hope there is a fix, love this game. If not i'll just be content. Much appreciated for the advice so far.
You could try https://github.com/GPUOpen-Drivers/AMDVLK and test if it happens with that as well.
I'm a noob to linux, only really devoted myself full time to it 2 days ago. I am afraid I'll break something, unless I know how to install properly and be able to uninstall while keeping my current drivers.
Just hope there is a fix, love this game. If not i'll just be content. Much appreciated for the advice so far.
Driver bugs can be fixed. You can report it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues
I have a rdna3 GPU in the pile, so i can check it out next time i switch if needed.
I have a rdna3 GPU in the pile, so i can check it out next time i switch if needed.
Would be appreciated if you could, if not no worries.
Just hope there is a fix, love this game. If not i'll just be content. Much appreciated for the advice so far.
Driver bugs can be fixed. You can report it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues
What gpu driver is it using on the times that I didn't have issues? (I am on nobara 40)
Just trying to make sure before I make a gitlab account and post on there.
This has been fixed for some reason. Nobara 40 was the issue. Upgrading to 41 ended up fixing the problem... maybe some better packages???? Having some weird issues at the moment so I'll close it once I've confirmed a few things
Fedora 41 comes with newer drivers than 40 (Mesa package), so not surprising that it could fix such issues.
Spoke too soon lmao. Turns out it was not fixed after reboot lol. Could changing themes affect the game? Literally the only thing I did different.
Found out what it was, Mip-map LoD bias. I had it set to -16 and it made the game shiney. Set it to 0 and it fixed it. This was in goverlay which edits mangohud. THIS IS NOT THE FAULT OF DXVK. My deepest apologies
proton experimentalx3 2025-01
LOOK AT HAT AND JACKET ON THE RIGHT IN THE PICTURES
I am on Nobara 40 (Linux)
DXVK ON
DXVK OFF
Software information
Bioshock Infinite GOG Version (32bit Game)
(Used Heroic Launcher and Ultra settings at 4k)
System information
Software Used: Heroic Launcher
GPU: AMD Radeon RX 7900 XTX
Driver: Mesa 25.0.0-devel
(1st Option That I used) Proton version: Experimental
(2nd Option That I used) Wine version: wine-ge-8-26-x86_64
DXVK version: 2.5.2
Another Screenshot with DXVK ON
As you can see Elizabeth doesn't have this problem. I've noticed after playing for a bit that sometimes the twins will have a glossy sheen/shine and sometimes they don't.
Log file for proton and wine included as an attachment. I used heroics built in log maker for the game.
(protonexperimental_dxvk2.5.2)71ZiF1GVqjA4uXoVxRmw9r-lastPlay.log
(wine-ge-8-26-x86_64_dxvk2.5.2)71ZiF1GVqjA4uXoVxRmw9r-lastPlay.log