sultim-t / xash-rt

Fork of the Xash3D FWGS with a real-time path tracing
1.09k stars 23 forks source link

Artifacts on AMD on Linux #15

Open KyleGospo opened 1 year ago

KyleGospo commented 1 year ago

Everything works great minus some artifacts at the bottom and right edges of the screen. Below are some example photos: Screenshot from 2023-02-22 16-09-13 Screenshot from 2023-02-22 16-02-25

I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

gremble commented 1 year ago

Everything works great minus some artifacts at the bottom and right edges of the screen.

I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

How did you get this running on Linux?

MixedVictor commented 1 year ago

Same here, but on RADV's software raytracing (i'm running on Vega 10 graphics)

OhaDerErste commented 1 year ago

Everything works great minus some artifacts at the bottom and right edges of the screen. Below are some example photos: Screenshot from 2023-02-22 16-09-13 Screenshot from 2023-02-22 16-02-25

I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

How did you even get it to work? tells me to check my video drivers with proton experimental

MixedVictor commented 1 year ago

Everything works great minus some artifacts at the bottom and right edges of the screen. Below are some example photos: Screenshot from 2023-02-22 16-09-13 Screenshot from 2023-02-22 16-02-25 I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

How did you even get it to work? tells me to check my video drivers with proton experimental

Use Winetricks and try installing VCRun2019

MixedVictor commented 1 year ago

I think bloom causes this, i disabled it and the artifacts were gone

materusPL commented 1 year ago

Everything works great minus some artifacts at the bottom and right edges of the screen. Below are some example photos: Screenshot from 2023-02-22 16-09-13 Screenshot from 2023-02-22 16-02-25 I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

How did you even get it to work? tells me to check my video drivers with proton experimental

Use wine instead of proton, install dxvk and vcrun2019 with winetricks

gremble commented 1 year ago

Use wine instead of proton, install dxvk and vcrun2019 with winetricks

Thanks. Are you doing that in 64-bit prefix? I can only get winetricks to do a 32-bit install for vcrun2019 but the xash3d.exe is 64-bit. Which OS are you using? Any more clues?

materusPL commented 1 year ago

Use wine instead of proton, install dxvk and vcrun2019 with winetricks

Thanks. Are you doing that in 64-bit prefix? I can only get winetricks to do a 32-bit install for vcrun2019 but the xash3d.exe is 64-bit. Which OS are you using? Any more clues?

Yes in 64-bit. Winetricks give me some warning about 32bit but vcrun2019 install both x86 and x64 I'm using NixOS.

I've checked on clean prefix, installed only vcrun2019 and it starts. Without vcrun2019 I'm getting error about renderer.

KyleGospo commented 1 year ago

I think bloom causes this, i disabled it and the artifacts were gone

I can confirm this, disabling bloom removes the artifacts completely.

KyleGospo commented 1 year ago

Since this is kind of the de-facto Linux issue, if anyone else wants to try this on their Steam Deck this is what I'm doing for playable framerates:

In-game settings:

Bloom: Off
FSR: Performance
Vsync: Off
Controls -> Adv Controls -> Autoaim: On

Steam quick menu settings:

Framerate limit: Off
Manual GPU Clock Control: 1600

Powertools Decky Loader Plugin:

SMT: Off
CPU Frequency Limits: On, 400-1500

Launch Options in Lutris (With VC2019 installed): -width 1280 -height 800 -fullscreen +sleeptime 0 +fps_max 31 +rt_ef_crt 1 +rt_shadowrays 1 Be sure to also add RADV_PERFTEST=rt to your environment variables in Lutris.

The CRT is to hide the ugly from the very aggressive FSR at lower resolutions. 20230223145618_1 20230223145341_1 20230223145217_1

a1batross commented 1 year ago

@KyleGospo Another Steam Deck option that will help with the performance a bit: sleeptime 0. Read my explanation here: https://github.com/sultim-t/xash-rt/issues/25#issuecomment-1442661030

Zinput commented 1 year ago

Everything works great minus some artifacts at the bottom and right edges of the screen. Below are some example photos: Screenshot from 2023-02-22 16-09-13 Screenshot from 2023-02-22 16-02-25

I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

How is yours so crisp? My game looks like one of those meme backrooms videos. It's a fuzzy mess. Running on Linux with a 6900 XT at 1080p.

KyleGospo commented 1 year ago

How is yours so crisp? My game looks like one of those meme backrooms videos. It's a fuzzy mess. Running on Linux with a 6900 XT at 1080p.

Don't use the CRT shader.

zt64 commented 1 year ago

Installing VCRun19 was the trick. This should be added to the README or somewhere

londiebrondie commented 1 year ago

@KyleGospo

Since this is kind of the de-facto Linux issue, if anyone else wants to try this on their Steam Deck this is what I'm doing for playable framerates:

In-game settings:

Bloom: Off
FSR: Performance
Vsync: Off
Controls -> Adv Controls -> Autoaim: On

Steam quick menu settings:

Framerate limit: Off
Manual GPU Clock Control: 1600

Powertools Decky Loader Plugin:

SMT: Off
CPU Frequency Limits: On, 400-1500

Launch Options in Lutris (With VC2019 installed): -width 1280 -height 800 -fullscreen +sleeptime 0 +fps_max 31 +rt_ef_crt 1 +rt_shadowrays 1 Be sure to also add RADV_PERFTEST=rt to your environment variables in Lutris.

The CRT is to hide the ugly from the very aggressive FSR at lower resolutions. 20230223145618_1 20230223145341_1 20230223145217_1

Hey It'd be nice if you (or anyone else who can get this to run) makes a tutorial video. I keep getting the same error when launching through lutris even though I used the above settings: image image image

image Maybe it's the way I put the files in the Half-Life directory? I extracted them into their respective folders (rt and rt_bin) and then took the contents of those folders and dropped them in to the Half-Life folder.

KyleGospo commented 1 year ago

Use winetricks to install vcrun2019

londiebrondie commented 1 year ago

Use winetricks to install vcrun2019

How do I do that? I've been searching all over the web and still can find no result.

KyleGospo commented 1 year ago

Use winetricks to install vcrun2019

How do I do that? I've been searching all over the web and still can find no result.

image image image image

londiebrondie commented 1 year ago

My game still won't launch. It keeps giving me an error. Do you think it's the way I placed the folders? I've already tried "verifying the integrity of the game files" in the properties tab of steam. I followed the instructions from before and installed vcrun2019. Here's the error I got, and here's my placement of the files: image image image image

KyleGospo commented 1 year ago

Yeah that's not installed correctly, the hl1-rt folder shouldn't be there at all.

londiebrondie commented 1 year ago

...and now that I've dragged and dropped the contents of rt and hl1-rt, it's giving me that original error. image Here's what my file system looks like: image

If you can't find a fix, just tell me what you did to install it in the first place.

KyleGospo commented 1 year ago

Installed exactly as the readme said to, then installed vcrun2019 as shown above. I would just start over and do it again.

londiebrondie commented 1 year ago

But the thing is, the readme is unclear. Do I do this? image image

londiebrondie commented 1 year ago

If we could call over discord that would be great, I'm London#8708

gremble commented 1 year ago

Everything works great minus some artifacts at the bottom and right edges of the screen.

I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

Now I've finally got it running, I too get the artifacts, but moving between FSR 2.1 settings can make them disappear. Try moving from performance to balanced once or twice.

osirase commented 1 year ago

@KyleGospo

Since this is kind of the de-facto Linux issue, if anyone else wants to try this on their Steam Deck this is what I'm doing for playable framerates: In-game settings:

Bloom: Off
FSR: Performance
Vsync: Off
Controls -> Adv Controls -> Autoaim: On

Steam quick menu settings:

Framerate limit: Off
Manual GPU Clock Control: 1600

Powertools Decky Loader Plugin:

SMT: Off
CPU Frequency Limits: On, 400-1500

Launch Options in Lutris (With VC2019 installed): -width 1280 -height 800 -fullscreen +sleeptime 0 +fps_max 31 +rt_ef_crt 1 +rt_shadowrays 1 Be sure to also add RADV_PERFTEST=rt to your environment variables in Lutris. The CRT is to hide the ugly from the very aggressive FSR at lower resolutions. 20230223145618_1 20230223145341_1 20230223145217_1

Hey It'd be nice if you (or anyone else who can get this to run) makes a tutorial video. I keep getting the same error when launching through lutris even though I used the above settings: image image image

image Maybe it's the way I put the files in the Half-Life directory? I extracted them into their respective folders (rt and rt_bin) and then took the contents of those folders and dropped them in to the Half-Life folder.

@londiebrondie your environment variable should be set like this: image

gremble commented 1 year ago

Hey It'd be nice if you (or anyone else who can get this to run) makes a tutorial video. I keep getting the same error when launching through lutris even though I used the above settings: Maybe it's the way I put the files in the Half-Life directory? I extracted them into their respective folders (rt and rt_bin) and then took the contents of those folders and dropped them in to the Half-Life folder.

So you should set the wine prefix there too, before running the winetricks.

EpicSentry commented 1 year ago

Hi im also having a similar issue, im on a steam deck and i set up lutris and proton with vcrun2019 as the earlier comments said however when launching the game i get this error: image

KyleGospo commented 1 year ago

Hi im also having a similar issue, im on a steam deck and i set up lutris and proton with vcrun2019 as the earlier comments said however when launching the game i get this error: image

Did you add the RADV_PERFTEST=rt environment variable?

EpicSentry commented 1 year ago

Hi im also having a similar issue, im on a steam deck and i set up lutris and proton with vcrun2019 as the earlier comments said however when launching the game i get this error: image

Did you add the RADV_PERFTEST=rt environment variable?

Yes I did and it still gives that error

londiebrondie commented 1 year ago

So I tried uninstalling and reinstalling it over and over and eventually it worked lol. Thanks for the help.

osirase commented 1 year ago

Hi im also having a similar issue, im on a steam deck and i set up lutris and proton with vcrun2019 as the earlier comments said however when launching the game i get this error: image

Did you add the RADV_PERFTEST=rt environment variable?

Yes I did and it still gives that error

Show us a screenshot of how you've entered it. I've found that error is specifically when RADV_PERFTEST=rt is not set properly.

DiarrheaMcgee commented 1 year ago

i have the same issue when i try to run it (note im not using the steam version)

Toughbook-CFC2 commented 1 year ago

I tried to set everything up as shown here, using lutris. I'm on Arch with an AMD Vega M GH. I get the following error message all the time: image I added the environment variable 'RADV_PERFTEST=rt,emulate_rt' I'm using 'lutris-7.2-2-x86-64' and I tried three different wineprefixes. Any ideas ?

gianluca-calcagni commented 1 year ago

Thanks all for the great comments! They helped a lot! I really wanted to run this on the Steam Deck; it wasn't easy, but now it works. If you want to try, please find below my instructions:

  1. buy and install Half-Life on the Steam Deck
  2. follow Sultim's instructions to install the mod
  3. in the Steam Deck, go on Desktop mode and stay there for the rest of the instructions
  4. open the Steam app and go to your library
  5. include a non-steam game (I called it "Half-Life RTX") in your library; the executable must be xash3d.exe from the folder rt-bin
  6. in the launch options, use the following string: RADV_PERFTEST=rt %command% -width 1280 -height 800 -fullscreen +sleeptime 0 +fps_max 31 +rt_ef_crt 0 +rt_shadowrays 1
  7. (optional step) in the compatibility mode, I chose GE-Proton7.55. I guess that doesn't matter and you can skip this step
  8. run the game once. Expect it to fail immediately - but that's okay, you need to run it anyway or steam won't generate some necessary configurations for the game
  9. now, install ProtonTricks from the Discovery app. The Discovery app is pre-installed on the Steam Deck and it is equivalent to flatpak
  10. launch ProtonTricks and follow the instructions provided by ProtonTricks in the terminal (or it won't be able to access your games)
  11. if everything was correct, you can now see "Half-Life RTX" as a valid game when launching ProtonTricks
  12. click "Half-Life RTX" on ProtonTricks then: (a) select the default wineprefix, (b) install a windows DLL or component, (c) select vcrun2019, (d) follow the instructions on screen and ignore any warning message, (e) at some point, ProtonTricks will show again one of the previous screens - when that happens, it means that it's all done and you can close ProtonTricks by clicking cancel. In case of doubt, you can also find some screenshots in this thread
  13. in theory, the game is ready. Launch it from the Steam app!

Despite my hype, I was disappointed with the end result... I guess the Steam Deck is not able to manage the graphics. The controls are terrible as well, I was forced to play with a keyboard and a mouse. But maybe I am doing something wrong or I am using the incorrect settings

john123903 commented 2 months ago

Everything works great minus some artifacts at the bottom and right edges of the screen. Below are some example photos: Screenshot from 2023-02-22 16-09-13 Screenshot from 2023-02-22 16-02-25

I am using an RX 6900 XT on Mesa/RADV, 22.3.5, I can also confirm the same behavior on the Steam Deck. Let me know if there's any more information I can provide or anything I can tweak in the console for you.

How Did you run on linux? I want to run it on the steam deck, but i dont want to dual boot windows!