Very interesting piece of news, thanks! :).

Also,

Quoting: jonorokBut there's no reason the launcher wouldn't finally run on Linux, right? Right?

Quoting: jonorokAnd I think I've logged 50 hours in 3dmark on steam just trying to get it running on Linux.

Well, if you didn't try to do it for some time - nowadays launcher works in Proton OotB, and some tests like Fire Strike and Night Raid work OotB also. Even Time Spy is launchable with some shenanigans (and great performance hit).

Interesting. Thanks for the update. I did manage to get firestrike running on my Steamdeck. I see I am a bit behind the times as the reddit threads are a year old. :)

Launcher is mostly functional, but you have to edit in your license codes (if you have them), system_info of course, fails.

I also had to use steam menus to download the individual tests as "dlc". Manually ticking the box actually got the tests to download.

Steamdeck gets a firestrike 3001-3024 after about a dozen runs. I guess I'll have to get my desktop going and compare the hardware to my windows results.

Well, here are back to back runs on my desktop. 23479 vs 29549, Pop! 22.04 vs Windows10. Still quite the disparity.




How did you manage to get Time Spy to run? I have a 2 year old at home so though I did try searching I can't tell if I didn't find anything or if I just got distracted again.

Quoting: jonorokHow did you manage to get Time Spy to run? I have a 2 year old at home so though I did try searching I can't tell if I didn't find anything or if I just got distracted again.

Hello.

Not sure what you already did, so I tryed to write a short guide from the beginning. Hope I remember everything, it was some time ago… Anyway:

1) You need to install 3dmark and run it (launch a test) at least once.

With Proton 8.0-4 or higher launcher and common Fire Strike test should just run OotB.

2) If 3dmark launched as Advanced Edition, ignore this step. If it’s recognized as Basic Edition:

• 2a) Right click on 3dmark in Steam, go Manage > CD Keys.



• 2b) Copy your “3dmark Advanced” key. (Just left click on it).



• 2c) Find your 3dmark prefix. (Steam id 223850, path depends on where you installed it. For example it can be /home/[username]/.steam/debian-installation/steamapps/compatdata/223850/pfx/).



• 2d) Edit user.reg file in pfx folder. Find a part “[Software\\UL\\3DMark] _something_ #time=_something_ “InstallId”=”_something_””



• 2e) After “InstallId”=”_something_” add a line "KeyCode"="_your 3dmark Advanced key_", and save file.

That should give you access to all tests you payed for, but you would need to install them all manually from the launcher. All three Fire Strike tests should work now.

3) Getting Time Spy test to run is possible, but require some more shenanigans, including launch options that greatly reduce performance…

• 3a) You need to install protontricks (from flatpak or somewhere else) and use it to install Windows’ d3dcompiler_43 and d3dcompiler_47 dll’s into 3dmark prefix.
  
  This will let you to launch Time Spy test, but it will hang (and hung the whole system) shortly after.



• 3b) To avoid the hang you need to add RADV_DEBUG=hang %command% _OR_ RADV_DEBUG=syncshaders %command% launch option to Steam.

This will let you to finally run Time Spy, but will also greatly (20+ %)(!) reduce performance of all(!!!) 3dmark tests. So you basically need to add and remove those launch options (and restart 3dmark) depending on what test you want to launch…

P. S. I think RADV_DEBUG=hang was a bit better than RADV_DEBUG=syncshaders, but it’s still a big hit. :(.

Quoting: jonorokWell, here are back to back runs on my desktop. 23479 vs 29549, Pop! 22.04 vs Windows10. Still quite the disparity.




How did you manage to get Time Spy to run? I have a 2 year old at home so though I did try searching I can't tell if I didn't find anything or if I just got distracted again.

At lest you have a 2 year old to blame on distracting you. I don't even have that and just get distracted by the most random of things.