When using multiple controllers (SteamVR, Oculus) in one VR session, Resonite seems to crash immediately upon startup and takes a few tries to start up properly.

[ModernBalloonie]

Describe the bug?

I've recently started using my index controllers with my Quest Pro, and i've encountered some issues due to this.

What will happen is that I'll start up steam link, start my index controllers, do the playspace calibration thing, and then start up resonite with the index controllers. What may happen is that I'll start up resonite, and then it'll crash. I'll try again, it'll crash again, and then it'll finally start up properly on the third try.

To Reproduce

Start up your Quest, using steam link.

Get some index or other steam VR controllers and calibrate the playspaces.

After that, launch Resonite.

It may give you an error in the log, and the game will refuse to start. You can try again, and it might fail to start and crash again, or let you in.

Expected behavior

For the game to not crash when starting up.

Screenshots

No response

Resonite Version Number

Beta 2024.5.7.505

What Platforms does this occur on?

Windows

What headset if any do you use?

Quest Pro, Index controllers.

Log Files

So, unfortunately I was using some mods in this log file, but it's not much (Just CherryPick, Impressive and Resonite Mod Settings.) Which I think Impressive and CherryPick are vetted mods (if what I was told by a team member was correct), but I could be mistaken. Please tell me if I should get a better log!

Failed Startup 1: DESKTOP-QBGCSAQ - 2024.5.7.505 - 2024-05-15 16_20_22.log

Failed Startup 2: DESKTOP-QBGCSAQ - 2024.5.7.505 - 2024-05-15 16_20_57.log

Additional Context

No response

Reporters

ModernBalloonie

[shiftyscales]

Please retest this without the use of any mods to see if you can replicate it, @ModernBalloonie.

When you do, please also collect other available log types, e.g. the player.log and crash log (if generated).

Do you also have the Quest touch controllers active alongide the Index controllers? What devices does SteamVR have registered/report as active? (A screenshot of the SteamVR panel would be useful.)

Is there any difference in behaviour if you try to force either of the SteamVR or Oculus native runtimes? Either via their respective options in Steam, or forced via command line arguments?

[ModernBalloonie]

Here's a log wihout mods, Started streaming to my quest pro, Turned on trackers and index controllers, and then launched Resonite. DESKTOP-QBGCSAQ - 2024.5.31.202 - 2024-06-01 20_53_17.log

[shiftyscales]

There were several unresolved questions/requests from my above message, @ModernBalloonie.

[ko-tengu]

I've started getting this bug from having the ALVR server plugin connected while also attempting to use the Oculus or Steam link apps. The game simply crashes silently and both logs are extremely unhelpful. It also does not generate a crash log. BUFU - 2024.6.25.1149 - 2024-06-29 04_25_53.log

Player.log

Launching specifically as SteamVR doesn't make a change; launching under Oculus link doesn't have the issue because the Oculus runtime only supports the two controllers and zero extended tracking or secondary inputs.