search

webaverse / metachromium-bin

Metachromium binary release
0 stars 1 forks source link

examples on metachromium crash once SteamVR displays "headset not detected" #12

Open michaelybecker opened 4 years ago

michaelybecker commented 4 years ago

Avaer's Dropship and Dark Booth crash Metachromium upon entry or shortly thereafter (once SteamVR boots) every time. MetaRTC does seem to work.

This is on a pretty basic machine with a very VR-incapable NVIDIA GeForce MX150 but decent specs otherwise: 16GB of RAM, i7-8550U CPU, I can try to repro on my VR machine.

avaer commented 4 years ago

This is probably because we don't check for presence of headset in the node part -- an error there means we will exit. Which makes some amount of sense since Metachromium isn't all that useful without a headset currently.

We can and should handle this more cleanly though.

I'm curious about whether this reproduces on a headset-connected machine.

michaelybecker commented 4 years ago

followup: same crashes on the VR machine (GS63VR, GTX1060) when no headset connected, but no crashes when the headset is connected but SteamVR isn't running. (Headset is Oculus Quest via Virtual Desktop - SteamVR treats it fully like a Rift S as far as I can tell). SteamVR launches when link is clicked, dropship loads up fine.

avaer commented 4 years ago

Ok makes sense, so then the crashes are due to a non-present headset.

It's still a bug since we should at least not exit out myseriously on that case.

avaer commented 4 years ago

@shu8 this might be the issue you were experiencing in the qrvr module.

shu8 commented 4 years ago

Definitely looks like it, I'll try to get it fixed today! :)