Forum Replies Created
-
Posts
-
I didn’t test this solutoin with the vorpX version I had while opening this topic. However, I had another/similar behavior with the newer version 17.2.0: After a while of playing one screen/lense starts flickering. This lasts a view seconds before both screens turn to black, even though the game seems to be running just fine on my regular display.
Anyway, the solution suggested by forlaunchcast helped me to avoid this issue from occuring again. Thanks for that!
Though I would be glad if that would get improved even more with a upcomming version.
I think it depends on the game itself. I already played Diablo 3 with some kind of 3D support provided by vorpX. Actually, that is one of the “supported” games and no steam game. Further, all of these games can be bought somewhere else. So, I think you won’t need Steam to use vorpX.
Disabling the async rendering reduces performance? Ok, that might be the reason why the view starts quaking once I turn that function off.
However, if I play a game that is expensive in resources it does fade out and fade in just as the problem I do have with vorpX, but they don’t crash at the end.
Drivers and Vive firmware are up to date.
Is there any log or debugging ability that I could use for further investigation? Or does someone else have another idea?
I’ve just found out that turning off “direct mode asynchron renders” seems to avoid the crash (or increased the time till the same). However, if I disable that setting, the whole VR environment is quaking slightly while moving my head. The game runs great though (no lags and “enough” FPS).
By the way: I shouldn’t have saying that the “game” is crashing in my previous post. Only the VR environment crashes. The game runs just fine on my screen after that crash.
Still looking forward to a solution.