Not responding

[zombicadavre]

I have several "not responding" problem today, it was happened before also.

How does this happen? I play some time then I notice in HMD that capture freezes, I select OVRdrop window then voila: application not responding. This time I played ETS2, previous time I played nothing just test overlay function, if I remember correct.

Here I attach Output_log and steamvr report

steamvr report.txt
output_log.txt

Regards

[Hotrian]

So from your output log it's clear you're having capture issues:

Capture Error: CaptureFailed
Lost output, retrying..

HCA: Failed to duplicate Adapter: 1 Output: 0
Capture Error: CaptureFailed
Failed to grab capture

Capture Error: LostAccess
Lost output, retrying..

However, what isn't clear is why.

The CaptureFailed error means that Windows is denying access for some reason. I will improve my error handling here so we can find out why.

The LostAccess error means that desktop context has been lost for some reason. This can happen in certain instances, such as when the Window's DWM restarts.

Are you using a 32bit or 64bit OS?

Either way, OVRdrop should be recovering from these issues, not freezing. I will continue to look into this.

[zombicadavre]

I'm using 64bit OS.

[Hotrian]

Strange - this is built and tested on Windows 10 x64, same version as you're using.

I will continue to look into this more, but unfortunately your logs don't seem to reveal why this is happening and it hasn't happened to me so I'm not sure I'll be able to find the cause right now.

Can you try verifying the integrity of OVRdrop through Steam just in case?

[zombicadavre]

OK I'll try.

[Hotrian]

I just updated the Experimental Branch to give slightly better error messages. Can you switch to the Experimental Branch and see if you can get some errors again, and then upload your output_log.txt again?

Thanks

[zombicadavre]

I'll send output_log.txt as soon as I catch error again. Stay tuned :)

[zombicadavre]

output_log.txt

[Hotrian]

Very strange - OVRdrop froze from this? It should have recovered just fine.

It's possible there is an unhandled error in the capture dll, but I'm not seeing it right now.

[Hotrian]

I'll try pushing out an update later today with even more error handing - right now, can you try launching Steam as Admin? That should launch OVRdrop as Admin and fix any permission issues you might be encountering.

[zombicadavre]

It happens after a while and maybe after some actions, but I can't tell what exactly correlates with the problem. Possibly I will be more lucky to catch what actually cause the problem.

You say OVRdrop should recover, I'll try more patience next time, but I cannot say I was waiting too little :)

Okay, I'll try launch Steam as Admin, but if I have chance to resolve freeze this way, how can I be sure that I just don't encounter this problem just because of luck? I don't sure what cause this, so I can only wait until it happens.

[Hotrian]

You say OVRdrop should recover, I'll try more patience next time, but I cannot say I was waiting too little :)

It should happen very quickly, like just a few seconds. If it is freezing then it is not recovering properly.

I'll try launch Steam as Admin, but if I have chance to resolve freeze this way, how can I be sure that I just don't encounter this problem just because of luck

You'll just have to try it and see if you can get OVRdrop to freeze again. I can't get it to freeze on my system so I can't even begin to reproduce the issue - I can just add more error handling until I can get enough information from your crashes to track down what's going on.

[Hotrian]

I think I have fixed this one - I completely rewrote the capture driver and it seems to be able to recover properly now. I have to finish incorporating it into OVRdrop but the next patch should hopefully fix this issue.

Edit: I did figure out I could force OVRdrop to freeze by changing the Orientation of the monitor, such as switching from Landscape to Portrait. At least doing this it now properly recovers, so I assume this will fix whatever issue you were having.

[Hotrian]

Can you try the new v1.0.4p4 on the Experimental branch when you get a chance? I think this one is fixed - I still don't know what was causing you to lose capture access, but it should self fix now.

[zombicadavre]

Good news! I'll try it as soon as possible.

[zombicadavre]

I have no problems with this bug. I'll post here if suddenly I catch it again.

I changed GPU by the way, I hope it does not affect the issue.

[Hotrian]

Thanks for the update!

I marked this for the Experimental Branch since this fix is included there.

Planning to close all the issues marked for the Experimental Branch when I push the Experimental Build to the Main Branch.

If it does happen again, please let me know and attach your output_log.txt.

Thanks again :).

[Hotrian]

This fix is in the latest version which should be on the Main branch soon so closing this issue.

If it happens again please let me know.