Nuclear Option on Proton (Linux) - Issues and Feedback

[fly_AirCal]

Is anybody running this successfully on Linux?

I'm getting a freeze/segfault after the initial splash screen and have to kill the process.
Tried Proton Experimental, Proton 8.16-GE and Proton 8.0-4.

Log output (steam-2168680.log):

2079.381:0198:019c:warn:seh:dispatch_exception backtrace: --- Exception 0xc00000fd.
2079.381:0198:019c:trace:seh:dispatch_exception code=c00000fd flags=0 addr=000000006592EE32 ip=6592ee32
2079.381:0198:019c:trace:seh:dispatch_exception info[0]=0000000000000001
2079.381:0198:019c:trace:seh:dispatch_exception info[1]=0000000000021f78
2079.381:0198:019c:warn:seh:dispatch_exception EXCEPTION_STACK_OVERFLOW exception (code=c00000fd) raised

All reports on Protondb[www.protondb.com] says it works out of the box.

Am I missing something here?

Arch Linux, kernel 6.5.7, AMD 7950X3D, AMD 6900XT with Mesa 23.2.1-2.


- Edit: Works with Proton 6.3-8.

[fly_AirCal]

Good to know. Thanks.

[fly_AirCal]

So I've tried Fedora 39 with Cinnamon and KDE Plasma, with X11 and Wayland, and a completely fresh installation of Steam. The exact same issue occurs.

Out of ideas. Since I broke the 2 h barrier trying to get this to work, I'm not sure I can still get a refund on this.

[Sora]

Do you have any accessories plugged in? (Wheel?, Joystick?) I know a lot of games hate my Logitech G920, and will crash, or play fine but continuously scroll through menus and make it harder to actually input things. My Logitech Extreme 3D Pro has caused several of my games to crash, and others just "work" without issues. I contribute it mostly to Wine/Proton as its only Windows games that seem affected in my case. I currently have my wheel plugged in and it works fine, minus endlessly scrolling. I've yet to try my joystick though.

All I can suggest is double check accessories and plug the bare minimum to try to determine if its physical hardware causing it.

You also mentioned you had used Protontricks.. Have you tried wiping the Proton installation directories, and redownloading them? They might be corrupted due to Protontricks following, the symlink and overriding the original file resulting in actually breaking Proton. I've only had this happen a handful of times, so I dont know if this could be a reason. (File validation will not see them as failures atleast, in the past for me you must manually wipe and validate, or reinstall Proton completely)

Another thing, is do you have the required vulkan libraries installed? ICD Loader, and AMDGPU support? Without them most proton games will fallback to WINED3D with major artifacting or crashing they will also fail outright at times.

[fly_AirCal]

Nuclear Option works (with Proton 8.0) if I plug out my Thrustmaster FCS devices (T.16000M, TWCS, Pedals).
As soon as I plug in either device again, it refuses to launch.

Using a different USB port does not make a difference.

Disabling Steam Input for NO does not help.

[Desdinova]

I have UI problems on Steam Deck, but its fine once in the air.

However, on my Linux Mint desktop I can't play anything under Proton.

[Sora]

fly_AirCal eredeti hozzászólása:

Nuclear Option works (with Proton 8.0) if I plug out my Thrustmaster FCS devices (T.16000M, TWCS, Pedals).
As soon as I plug in either device again, it refuses to launch.

Using a different USB port does not make a difference.

Disabling Steam Input for NO does not help.

Sounds like an issue with Proton/Wine with device enumeration or accessing the device(s) in that case. Nothing you can really do, but report that to either upsteam WineHQ if you're able to use the latest devel version of Wine from WineHQ or as previously mentioned report to Valve's Proton Github the findings and hope they can resolve it and push it upstream.

Thistle Honeymead eredeti hozzászólása:

I have UI problems on Steam Deck, but its fine once in the air.

However, on my Linux Mint desktop I can't play anything under Proton.

I haven't tested on my Steamdeck so I can't give input for that. However the issue with not being able to play anything under Proton is either a GPU lacking capability of Vulkan 1.3 which became a standard for Proton >=8 or, missing vulkan libraries related to your GPU from the distro's software repository which would likely break Proton overall.

[fly_AirCal]

Sora eredeti hozzászólása:

Sounds like an issue with Proton/Wine with device enumeration or accessing the device(s) in that case. Nothing you can really do, but report that to either upsteam WineHQ if you're able to use the latest devel version of Wine from WineHQ or as previously mentioned report to Valve's Proton Github the findings and hope they can resolve it and push it upstream.

I've reported this to the Proton issue tracker on Github, but so far got zero replies from any developer.

Note that my HOTAS system works without issues in DCS, Tiny Combat Arena and other simulations using Proton (Experimental), so I think this issue is likely more on NO's or Unity's side than Valve's.

[Sora]

Do you have any other unity games that function with the device, or cease functioning but do without the device to test the issue against?

I'm sorry that they haven't given any response as of yet. Sometimes they don't always respond and just fix things instead.

[fly_AirCal]

As posted before, "Tiny Combat Arena" and "Helicopter Gunship D.E.X.", both using Unity work just fine.

Interestingly, I just found out that "Reentry - an orbital simulator" using Unity suffers from the same bug as Nuclear Option. Freezes with devices plugged in, works with devices plugged out. Hm.

- Edit: Yep, it's the exact same issue.

Back to NO though:

On system WINE's and Proton's joystick control panel, the input devices work perfectly and all axes are detected.
Disabling the input devices from the control panel does not prevent the startup freeze.

[fly_AirCal]

There is now a fix for the device issues in Proton Bleeding Edge (aka Experimental's beta mode), which finally makes the game work!

Axis bindings (except the rudder's toe brakes) also work now.

[fly_AirCal]

The aforementioned fix is now part of the regular Proton Experimental.

And 0.27's TrackIR implementation works using Opentrack with WINE output.

[FERdeBOER]

fly_AirCal eredeti hozzászólása:

The aforementioned fix is now part of the regular Proton Experimental.

And 0.27's TrackIR implementation works using Opentrack with WINE output.

Could you explain how you did it? I'm not able to use opentrack. I'm using Proton experimental.

[NP-Tryhard]

The game and TrackIR worked out of the box for me on OpenSUSE, using Proton 8.0.5. I use the Delanclip for head tracking rather than TrackIR itself; OpenTrack compiled from the current master branch (make sure the SDK Wine option is enabled).

For me the Wine output for OpenTrack works only if I select the Proton (steam play) variant, matchig version to Proton 8.0, Steam application id 2168680. At least in my case, the game has to be started first, OpenTrack tracking second.

[FERdeBOER]

Thanks for the help. No joy.

I have to say that my version of opentrack is old-ish but, until now, it has worked with every game I tried. I will recompile it... but not today (yes, I'm scared of breaking it XD).
Meanwhile, windows version inside the prefix is working well for me.

[fly_AirCal]

FERdeBOER eredeti hozzászólása:

Could you explain how you did it? I'm not able to use opentrack. I'm using Proton experimental.

I run this fork: https://github.com/JT8D-17/opentrack

Picked "WINE (or Proton with manual paths)", then pointed "Prefix" to "[...]/SteamLibrary/steamapps/compatdata/2168680/pfx" and "Runtime" to "[...]/SteamLibrary/steamapps/common/Proton - Experimental/files".

ESYNC and FSYNC selected, protocol to "Both" and WINE wrapper to "opentrack-wrapper-wine.exe.so".