Forum Discussion
0.4.1 -> 0.4.2 regression / GZ3Doom status
I recently installed SDK 0.4.2 and upgraded the firmware on my DK2. I had hoped to continue porting my GZ3Doom doom game for the DK2, but now I am discouraged. Because I can not longer get the demo scenes to render acceptably. I have no desire to work on GZ3Doom when I cannot even get the demo scenes to perform acceptably.
The numbers in the table below are JUDDER RATES, i.e. how often the scene jerks in a non-smooth fashion, in units of Hertz (Hz), the approximate number of discontinuities per second.
[sorry I don't know how to render a table properly in these forums...]
Extended/Direct | SDK version | Desk Demo | Unity Tuscany Demo | Comment
Direct | 0.4.1 | 10-20 Hz | ? | Sickening
Extended | 0.4.1 | 0.1 Hz | 0.1 Hz | Acceptable
Direct | 0.4.2 | 2 Hz | 2 Hz | Sickening, rotation judder more than positional
Extended | 0.4.2 | 10-20 Hz | 2 Hz | Sickening, rotation judder more than positional
System specs: Windows 7; nvidia GTX 650 Ti; Two monitors 1920x1080, plus DK2.
I guess I got spoiled with the DK1, because I did not get started on GZ3Doom until six months after the release of the DK1. Perhaps I should wait until, say, February, for the SDK to settle down, before porting GZ3Doom to the DK2. Especially considering the sad state of OpenGL support in the latest SDKs.
What should I try next to get smooth tracking with that latest version of the SDK?
The numbers in the table below are JUDDER RATES, i.e. how often the scene jerks in a non-smooth fashion, in units of Hertz (Hz), the approximate number of discontinuities per second.
[sorry I don't know how to render a table properly in these forums...]
Extended/Direct | SDK version | Desk Demo | Unity Tuscany Demo | Comment
Direct | 0.4.1 | 10-20 Hz | ? | Sickening
Extended | 0.4.1 | 0.1 Hz | 0.1 Hz | Acceptable
Direct | 0.4.2 | 2 Hz | 2 Hz | Sickening, rotation judder more than positional
Extended | 0.4.2 | 10-20 Hz | 2 Hz | Sickening, rotation judder more than positional
System specs: Windows 7; nvidia GTX 650 Ti; Two monitors 1920x1080, plus DK2.
I guess I got spoiled with the DK1, because I did not get started on GZ3Doom until six months after the release of the DK1. Perhaps I should wait until, say, February, for the SDK to settle down, before porting GZ3Doom to the DK2. Especially considering the sad state of OpenGL support in the latest SDKs.
What should I try next to get smooth tracking with that latest version of the SDK?
3 Replies
- Yeah, I have heard a lot of issues like this (and seen on my own machine).
Can you try unplugging ALL external monitors? Meaning only the Rift plugged in as the primary display. "cybereality" wrote:
Yeah, I have heard a lot of issues like this (and seen on my own machine).
Can you try unplugging ALL external monitors? Meaning only the Rift plugged in as the primary display.
Thanks cybereality for the supportive advice, as always. Yeah, I was considering trying that; but was hesitant because it is so very tedious to use the Rift as the only/primary display. I will definitely try this next time I take a pass at the Rift. But not tonight; I need to rest up for my day job...- maybe try virtual desktop while monitors are unplugged.
