10-15-2013 05:33 PM
03-16-2016 06:31 AM
"Trisk" wrote:
OK, if I missed the memo and this is incredibly stupid of me, I apologize. I finally figured out how to get this and several other games which wouldn't start in Rift DK2 working: I opened the Oculus Configurator window. With that window up, the camera light comes on, and the game starts in VR with no issues. Is this something I should have known to do? Other games like Town of Light are the same way, and I've been bashing my head against the wall trying to understand why they won't work, even wondering if my computer, which tested both Oculus and Vive ready, was not going to work. Other games work fine, however.
But all I have to do is open the Configurator? Huh. Does anybody else have this? Is this something everybody knows and I'm just a doofus? I can't recall ever being instructed to do this...
03-17-2016 07:24 PM
"cmbruns" wrote:
This is interesting. Thank you Trisk for continuing to investigate this. It sounds like GZ3Doom is failing to fully initialize the headset or something, if opening the Configuration Utility is required.
In fact I probably usually have the Configuration Utility open when I am developing GZ3Doom. So it would be easy for me to miss a problem like this.
I'm pleased you at long last found a workaround, and a clue to the problem, so you can go back to enjoying rifty doomy goodness.
03-28-2016 12:39 PM
03-28-2016 04:27 PM
RABID said:
any chance of getting this updated as it is now broken with the new 1.3 runtime?
03-28-2016 04:53 PM
03-28-2016 07:54 PM
cmbruns said:
RABID said:
any chance of getting this updated as it is now broken with the new 1.3 runtime?
I just installed the 1.3 SDK about an hour ago. You probably remember that it usually takes me a while to update GZ3Doom for a new SDK, and this time will be no exception (especially if my HTC Vive arrives sooner than my Oculus Rift CV1). Remember that in the past I have diligently upgraded from SDK 0.2 to 0.3 to 0.4 to 0.7 to 0.8, and I will likely get to 1.3 as well. So maybe May or June if nothing goes horribly wrong?
03-29-2016 05:24 AM
cmbruns said:
RABID said:
any chance of getting this updated as it is now broken with the new 1.3 runtime?
I just installed the 1.3 SDK about an hour ago. You probably remember that it usually takes me a while to update GZ3Doom for a new SDK, and this time will be no exception (especially if my HTC Vive arrives sooner than my Oculus Rift CV1). Remember that in the past I have diligently upgraded from SDK 0.2 to 0.3 to 0.4 to 0.7 to 0.8, and I will likely get to 1.3 as well. So maybe May or June if nothing goes horribly wrong?
03-31-2016 06:47 PM
MisterNegative said:
Is it wrong to say that makes me sad, if only because of how awesome your port is? It's one of the first bittersweet thoughts I had when installing 1.3 today.
04-02-2016 05:12 AM
04-02-2016 09:41 AM
cmbruns said:
Good news! My HTC Vive order just got cancelled by the Keystone Kops at HTC. So the chances of my CV1 arriving before my Vive has increased slightly. And thus the chances I would keep my focus on the Rift has increased.