Unhandled Exception Key in Use #23
Comments
|
Have you tried this? |
|
Huh, thought I had looked for a troubleshooting guide, apparently not well enough. This happened the very first time I tried to launch it so there shouldn't have been an already running instance, however that terminal output isn't from that first attempt, I think that one may have been longer, I definitely saw the same main error but perhaps it was able to register itself with SteamVR before that as when I check tonight it does show in my startup list. However there is still no sign of it running, nothing has been visible in SteamVR at any point, and checking now (with SteamVR running, but without having tried to manually start WlxOverlay) there's no sign of a process with the right name, and Attempting to manually start WlxOverlay now (with no sign of an existing instance) results in the same error. |
|
Can you show what |
|
Okay, so, tonight, when trying to run the same as every other time, the error doesn't happen. Terminal output starts the same as above, but the unhandled exception and everything after it never appears. Running your command before this has no result, and in a separate terminal after outputs: Trying to run WlxOverlay again from a second terminal results in the error above as expected. Even with everything appearing to work fine from the terminal, I still have no sign of WlxOverlay anywhere in the headset. |
|
no watch on your left hand? try double tapping left b/y |
|
I just put the headset on for one last look before turning everything off for the night and saw a brief glimpse of something as I went to take it back of, yes if I turn my hand aroud backwards now I can see the UI and interact with it. |
|
Yep, rebooted and tested immediately without touching anything else, and it still needs to be manually started, SteamVR doesn't autostart it despite being in the startup list, but it does work seemingly flawlessly otherwise. I'm trying to think of what I've done to my system that might have affected this, but all I've done is install LOOT from the AUR along with it's dependencies, which I doubt has anything to do with this. I guess I'll see what happens tomorrow evening and close this issue if there are no more problems, unless you'd like me to do some testing of some sort to find the root cause? |
|
Also FYI on exiting SteamVR the terminal for WlxOverlay outputs Which I assume is standard and you're aware already. |
|
please run it with |
|
So while After this SteamVR had not actually started, however my one other overlay (OVR Advanced Settings) set to automatically launch on startup is running, despite the lack of SteamVR. After Ctrl-C'ing in that terminal Regarding Drivers, GPU is AMD RX 6900XT, and headset is HTC Vive. |
|
you're getting that error because starting wlxoverlay will start steamvr, and then steamvr will try to start its own wlxoverlay. if you want to do that then disable the auto-start in steamvr. |
|
From a clean reboot, started SteamVR, checked whether WlxOverlay was already running, no, tried launching WlxOverlay, everything looked good, killed WlxOverlay and relaunched via gdb, run, and this time it segfaulted without me doing anything at all. This didn't seem right so I reran WlxOverlay without gdb, worked fine, then reran with gdb for the same result. |
|
the original issue is solved, so going to close this. please open a new ticket if you still run into the segfaults |
Followed instructions as in Setup Instructions How to Run, received following error:
Hyprland as compositor.
Let me know if you need any more info.
The text was updated successfully, but these errors were encountered: