Raptor Computing Systems Community Forums (BETA)
Software => Applications and Porting => Topic started by: Hasturtium on January 15, 2023, 12:16:10 am
-
I can't believe I'm typing this, but - with some caveats - Quake II RTX compiles and runs under Fedora 37 with an RDNA2 Radeon on Power9. The gotchas:
* If you're copying your Windows folder over and you care about preserving your saved games, make sure the contents of Q2RTX/baseq2/save are moved to ~/.quake2rtx/baseq2/save. If you don't, and you leave the Windows save folder intact, the executable will throw an error when trying to load a new game or save because it can't rectify the presence of the Windows folder with the presence of the Linux folder.
* For some reason I can't get timedemo functionality to work - attempting to load a timedemo from the console results in "Couldn't load maps/demo1.dm2.bsp: No such file or directory".
EDIT: * The game may bomb out at startup complaining that it can't find a Vulkan-capable GPU (despite the logs indicating it successfully queried both your Vulkan GPU as well as llvmpipe). In that case, manually edit ~/.quake2rtx/baseq2/q2config.cfg and change the line seta ray_tracing_api value from "auto" to "query". I tried setting this to “pipeline” on a lark to test the other raytracing method it supports, and that crashes the executable because it apparently can’t find the extensions it’s looking for.
Nevertheless it runs at around 60 fps at 1080p on an RX 6600 with resolution scaling set to 65%, which doesn't trail the Windows version with the same card too much at all. There is some minor visual corruption at the periphery of the screen, but with some more testing and bugfixes that can probably be fixed. Back to Stroggos I go...
-
Coooool. Got a screenshot?
-
I can't believe I'm typing this, but - with some caveats - Quake II RTX compiles and runs under Fedora 37 with an RDNA2 Radeon on Power9. The gotchas:
* If you're copying your Windows folder over and you care about preserving your saved games, make sure the contents of Q2RTX/baseq2/save are moved to ~/.quake2rtx/baseq2/save. If you don't, and you leave the Windows save folder intact, the executable will throw an error when trying to load a new game or save because it can't rectify the presence of the Windows folder with the presence of the Linux folder.
* For some reason I can't get timedemo functionality to work - attempting to load a timedemo from the console results in "Couldn't load maps/demo1.dm2.bsp: No such file or directory".
EDIT: * The game may bomb out at startup complaining that it can't find a Vulkan-capable GPU (despite the logs indicating it successfully queried both your Vulkan GPU as well as llvmpipe). In that case, manually edit ~/.quake2rtx/baseq2/q2config.cfg and change the line seta ray_tracing_api value from "auto" to "query". I tried setting this to “pipeline” on a lark to test the other raytracing method it supports, and that crashes the executable because it apparently can’t find the extensions it’s looking for.
Nevertheless it runs at around 60 fps at 1080p on an RX 6600 with resolution scaling set to 65%, which doesn't trail the Windows version with the same card too much at all. There is some minor visual corruption at the periphery of the screen, but with some more testing and bugfixes that can probably be fixed. Back to Stroggos I go...
That's interesting that you could get it loaded. It does not really work for me. 1stly I need to enable the raytracing flag for mesa. 2ndly the game came back with error "This GPU is not supported"
-
Nice theres a competent benchmark for the system now.. i was going with an older card for my build for now but i'd definitely like to try vulkan raytracing. maybe in a year or two when support is more stable.
-
I can't believe I'm typing this, but - with some caveats - Quake II RTX compiles and runs under Fedora 37 with an RDNA2 Radeon on Power9. The gotchas:
* If you're copying your Windows folder over and you care about preserving your saved games, make sure the contents of Q2RTX/baseq2/save are moved to ~/.quake2rtx/baseq2/save. If you don't, and you leave the Windows save folder intact, the executable will throw an error when trying to load a new game or save because it can't rectify the presence of the Windows folder with the presence of the Linux folder.
* For some reason I can't get timedemo functionality to work - attempting to load a timedemo from the console results in "Couldn't load maps/demo1.dm2.bsp: No such file or directory".
EDIT: * The game may bomb out at startup complaining that it can't find a Vulkan-capable GPU (despite the logs indicating it successfully queried both your Vulkan GPU as well as llvmpipe). In that case, manually edit ~/.quake2rtx/baseq2/q2config.cfg and change the line seta ray_tracing_api value from "auto" to "query". I tried setting this to “pipeline” on a lark to test the other raytracing method it supports, and that crashes the executable because it apparently can’t find the extensions it’s looking for.
Nevertheless it runs at around 60 fps at 1080p on an RX 6600 with resolution scaling set to 65%, which doesn't trail the Windows version with the same card too much at all. There is some minor visual corruption at the periphery of the screen, but with some more testing and bugfixes that can probably be fixed. Back to Stroggos I go...
That's interesting that you could get it loaded. It does not really work for me. 1stly I need to enable the raytracing flag for mesa. 2ndly the game came back with error "This GPU is not supported"
It came up pretty easily with my RX 6600 with the 6.1.5 kernel that was pushed out over the weekend. Biggest thing to do is to manually edit that line in the config file in the original post to specify "query" versus "auto" - I think something in Quake II’s feature polling mechanism breaks when it can't find the "pipeline" method it's looking for exposed in the driver. Give it a try and let me know what you think... It'll be a lot more interesting to see this on Intel's xe driver for Arc cards in a few months' time, given that their early fork of the old i915 driver already comes up on arm64. Intel’s raytracing speed is much more competitive with Nvidia’s - having tried an A750 and the RX 6600 in Windows, it isn’t a stretch to say Intel’s card manages at least as well at 1440p as the Radeon does at 1080p.
ClassicHasClass, I'll be happy to in a bit.
-
So. Screenshots.
(https://i.imgur.com/ivPE6jU.jpg)
(https://i.imgur.com/XmD50Yu.jpg)
(https://i.imgur.com/XzXVAd2.jpg)
Not much to start, but I can provide more soon. Performance is kinda variable and slower than it is in Windows, but it's still entirely doable. As said before I'd expect Arc support via the xe driver to be much faster whenever that lands. Early days - I'd expect subsequent Mesa revisions to continue improving speed for RDNA2 on Power.
-
well now I'd like to get a new gpu to play it, but i think i'll wait a bit for driver updates.. Still one of the best gaming benchmarks out there, and runs on POWER too..
-
Yeah, some glitches, but not many. Looks way better than the original.
-
should I wait for the intel arc gpu drivers over AMD? i've wanted to play this since it came out and I'd rather wait for power9 support to play it. I might opt for an a770 gpu over an AMD card if it plays well. Maybe a bit off topic but should one even trust an intel gpu moreso over an amd/nvidia lol..?
-
should I wait for the intel arc gpu drivers over AMD? i've wanted to play this since it came out and I'd rather wait for power9 support to play it. I might opt for an a770 gpu over an AMD card if it plays well. Maybe a bit off topic but should one even trust an intel gpu moreso over an amd/nvidia lol..?
In x86_64 land Intel’s the gold standard for open video drivers - hassle-free, exposed features that work without too much fuss, and as well-behaved as the hardware’s capabilities allow. They’re at an inflection point now that xe is being forked from i915 to provide dedicated support for 12th Gen and Arc hardware, but they have a funded and capable driver team and it’ll probably come up pretty fast. I can’t tell you where to spend your money, but once Arc has become a going concern on ppc64le I’m planning to swap the RX 6600 into my Windows machine so the Arc can be in my Blackbird. The video encoding is stupid good - if I can get OBS working, that’ll make everything from Blu-Ray transcoding to desktop capture overwhelmingly nicer on the platform for me.
-
Finally get the game working! Yay!
-
The q2rtxded was complaining about "Could not load library gamex86.so" so what I did is I copy my `gameppc64le.so` to `gamex86.so`. Not the best way but I could not find much details how the game workout the library filename.
-
Btw I submitted a Pull Request upstream https://github.com/NVIDIA/Q2RTX/pull/260
-
@tle, also being a Fedoran, which card and which kernel (I'm currently on 6.1.6)?
-
The game was complaining about "Could not load library gamex86.so" so what I did is I copy my `gameppc64le.so` to `gamex86.so`. Not the best way but I could not find much details how the game workout the library filename.
Ack! I forgot to mention that step. I could’ve sworn mine compiled to gamex86_64.so, but I copied the file to gamex86.so and then it didn’t give me any hassle.
@tle, also being a Fedoran, which card and which kernel (I'm currently on 6.1.6)?
I’m running on 6.1.6 with an XFX Radeon RX 6600, though it also worked with kernel 6.1.5. Both have worked with Fedora’s current Mesa release. Reported framerate didn’t necessarily correlate to onscreen framerate, though it did become more consistent when vsync was enabled. It’ll be interesting to see how this improves as time goes on.
-
have you tried playing it with SMT disabled? i'm curious if theres a performance difference.
-
have you tried playing it with SMT disabled? i'm curious if theres a performance difference.
I wouldn’t expect much - Quake II’s CPU demands are trivial. I genuinely think the Ogg Vorbis support for music playback would dwarf the demands of the game itself. Running Q2RTX with the OpenGL renderer reliably nets between 920-1000 fps on my config at 4K!
The overwhelming share of the computational grunt needed will be demanded of the GPU itself. I expect any weird stuttering to be down to things like vsync being enabled by some part of the display stack despite what Q2RTX expects, or similar issues. Out of curiosity how do you configure or disable SMT? I’ve been meaning to try it in order to determine its impact on some other titles, chief among them GZDoom…
-
Ah, thanks for that. I've been toying with getting a new GPU, and maybe this is what pushes me over the edge. Do you have the firmware loaded for Petitboot?
-
i think SMT is configured in petitboot but i'm not sure. haven't booted my system yet. I dont think it would do much for quake 2 rtx either though.
also, you play it online yet lol?
-
Ah, thanks for that. I've been toying with getting a new GPU, and maybe this is what pushes me over the edge. Do you have the firmware loaded for Petitboot?
I do not - never got an answer for which subset of Radeon firmware should be loaded, so I have the BMC’s video going to HDMI2, then toggle over to DisplayPort for the Radeon.
No multiplayer yet - my twitch skills are mostly intact, but I’d have to find servers!
-
https://www.quakeservers.net/quake2/servers/
tastyspleen always has players on their DM servers usually.
-
@tle, also being a Fedoran, which card and which kernel (I'm currently on 6.1.6)?
I am using 6600 XT. Kernel is 6.1.x. AFAK 6.1.6 works perfectly
-
Here we go, I know why the `q2rtxded` was complaining about missing `gamex86.so`
Let's hope this PR get merged upstream soon https://github.com/NVIDIA/Q2RTX/pull/305
-
:D The PR has been merged! I can say the game now can be compiled successfully on PPC64LE without any downstream patch