Yep, same for me. Had fantastic performance in beta 2 but these, seemingly random, huge drops in frame rate make it difficult to play. Might sit this out and wait for a fix. Did you create a ticket?
ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread
Yep, same for me. Had fantastic performance in beta 2 but these, seemingly random, huge drops in frame rate make it difficult to play. Might sit this out and wait for a fix. Did you create a ticket?
Just to add my experience to the list.
Since the update to beat 3.0x things are really stuttering.
I have used fraps to capture the FPS that is shown in the lower corner and they are hanging around 40 fps (extended mode) (fraps is not causing this as it's also without it stuttering).
This is in any play mode tutorial/open
If i don't use the oculus my fps on a normal monitor is 110fps (at least it renders that, the lcd is @ 60hz)
Before the update things where better i'm not sure what this issue is.
I have played around yesterday with everything you are all talking about and more...... (Lcd hz, drivers, direct,extended, quality settings, head tracking, reinstall SDK, and more...)
I just wait and see what happens in coming updated
My specs:
i7 970 (1366 socket), 20 GigRam, 2x AMD HD7950 in crossfire
Since the update to beat 3.0x things are really stuttering.
I have used fraps to capture the FPS that is shown in the lower corner and they are hanging around 40 fps (extended mode) (fraps is not causing this as it's also without it stuttering).
This is in any play mode tutorial/open
If i don't use the oculus my fps on a normal monitor is 110fps (at least it renders that, the lcd is @ 60hz)
Before the update things where better i'm not sure what this issue is.
I have played around yesterday with everything you are all talking about and more...... (Lcd hz, drivers, direct,extended, quality settings, head tracking, reinstall SDK, and more...)
I just wait and see what happens in coming updated
My specs:
i7 970 (1366 socket), 20 GigRam, 2x AMD HD7950 in crossfire
Last edited:
I am still struggling getting decent results out of the DK2. I have the display set at 1080 x 948 at 75Hz, that is correct isn't it? I have not changed anything else. I don't seem to get the jittering now, but still find writing almost impossible to read. Threads are that long here which makes it very difficult to find simple, definitive setup instructions.
Now I don't remember the voice in the menu, but on the top of the graphic options there is one for the cockpit effects, try turning it
off.
Last edited:
Hi Casastevo,
It's nice to see others tinkering with Direct mode. I'm getting very similar results to you. In Beta 2 nothing would get me above 37.5fps. In Beta 3 I'm getting 75fps in space, 37.5fps in hangar (LOW & High/full Oculus quality slider). I can get 75fps in the hangar but only by lowering the Oculus quality slider which for me makes it unplayable.
I have a GTX 970 which in Extended mode gives 75fps in hangar. This suggests to me rather than a GPU issue - Direct mode with ED need further development. The basic mechanics are now there and getting better
Last edited:
native res of the rift is 1920*1080@75Hz for optimal quality
Well im not sure but i will just post my settings and my events to see if it will help anyone or raise questions but...
I have max settings on elite.. apart from bloom is medium and AA is off, downsample to 2560x1440 using the DK2
setup is a AMD FX-8320 oc' at 4.11Ghz, 8GB RAM, GTX 680.
I have logged in and sometimes this jumping and skipping people are talking about gets bad as mentioned above to unplayable states.
but other times i logged in, it is gone, runs smooth with no issues, just a small stutter while coming close to a system while in jump speed or in a wormhole jump.
adjusting settings are in my opinion not needed! i leave my settings always as they are above and do not try and fix these issues by tweaking graphics because i know when the game wants to runs smooth it is a sweet spot with good performance and readable txt.
Set your graphics to high/medium depending on your rig, i suggest a small down sample just to make the txt ''more'' readable and not a big hit on performance and just leave it at that... if the game jumps about, its the game not your setup, and just wait until they fix it or it clears up for a while as it did with me.
I have max settings on elite.. apart from bloom is medium and AA is off, downsample to 2560x1440 using the DK2
setup is a AMD FX-8320 oc' at 4.11Ghz, 8GB RAM, GTX 680.
I have logged in and sometimes this jumping and skipping people are talking about gets bad as mentioned above to unplayable states.
but other times i logged in, it is gone, runs smooth with no issues, just a small stutter while coming close to a system while in jump speed or in a wormhole jump.
adjusting settings are in my opinion not needed! i leave my settings always as they are above and do not try and fix these issues by tweaking graphics because i know when the game wants to runs smooth it is a sweet spot with good performance and readable txt.
Set your graphics to high/medium depending on your rig, i suggest a small down sample just to make the txt ''more'' readable and not a big hit on performance and just leave it at that... if the game jumps about, its the game not your setup, and just wait until they fix it or it clears up for a while as it did with me.
you stated above that you run in 1080 x 948 ... i think you mean 948 x 1080, which is the lowest setting on the DK2,
Right click your desktop, go to screen resolution, select the rift DK2 screen, and make sure your resolution is on (Recommended) which will be 1920x1080)
Are you running Oculus Extended or Direct mode? The reason I ask is most are using Extended, but there is a know issue with that res and Direct.
I am running in extended mode as that was the mode that most people seemed to advise. I have managed to get 1920 x 1080 it was the last on the list. The text is a lot clearer but I get juddering on head movement now which I presume is framerate. I had this at the beginning. Setting graphics from high to medium or bloom to low and AA off doesn't seem to do anything either. The smoothest I have seen it was when I had that low resolution set by accident. I think it was 1080 x 948 but it looked awful.
You may already be doing this - but one of the best tips given to me on this thread was to move as far away from screen as possible, press F12, then return to your normal position (for me it makes a massive difference to text).
As you said the judder could be fps (others are reporting another issue with Beta 3.x). What GPU do you have? Mine is a GTX 970 and I find the preset LOW works best for me. Maybe install software to check your fps? Sounds like you are on the right path
No, that displays you half of the resolution, you should have 1920x1080, you may need to rotate the display in windows display settings if it shows rotated 90 degrees in your Rift..
Yes, I have it set like that now. Just trying to get rid of the juddering.
- - - - - Additional Content Posted / Auto Merge - - - - -
You may already be doing this - but one of the best tips given to me on this thread was to move as far away from screen as possible, press F12, then return to your normal position (for me it makes a massive difference to text).
As you said the judder could be fps (others are reporting another issue with Beta 3.x). What GPU do you have? Mine is a GTX 970 and I find the preset LOW works best for me. Maybe install software to check your fps? Sounds like you are on the right path
All testing has been done mainly in Dahan Gateway. I set the display setting to low and it did improve quite a bit from high. So tried launching out and found that the graphics looked fairly smooth. It must be the complexity of Dahan thats really taxing the graphics. I did post system specs above.
Please HELP! What did I do wrong? Seems here is another who can only use Amiga and such properly...
So, I installed OR DK2 2.04 with drivers, and according to my Win 7 Ultimate 32bit all installed fine. Although head tracking camera were installed last, as I runned out of USB 2.0 and 3.0 slots, and connected it through my 2.0 USB hub (that installed it´s drivers at same time with camera and my X52 Pro Flight Stick, all succesfully according to Windows).
Now my head tracking camera only blinks blue light when I turn my desktop on, then nothing. All cable connections made as in instructions. Does it matter what end of sync cable is in camera and what in cable connector box?
As I try ED withouth head tracking (and just kb+mouse), when I look fast into some direction with head move, or start barrel roll my ship near Azeban Orbital (head not moving), it´s structures near me seem to "stretch", and even come closer, until I end my movement. Where did I fail here? In monitor/option settings, having no head tracker still, or is that just how it (OR 3D) should/will work?
Thanks in advance for all who take time for this, please be detailed in instructions!
So, I installed OR DK2 2.04 with drivers, and according to my Win 7 Ultimate 32bit all installed fine. Although head tracking camera were installed last, as I runned out of USB 2.0 and 3.0 slots, and connected it through my 2.0 USB hub (that installed it´s drivers at same time with camera and my X52 Pro Flight Stick, all succesfully according to Windows).
Now my head tracking camera only blinks blue light when I turn my desktop on, then nothing. All cable connections made as in instructions. Does it matter what end of sync cable is in camera and what in cable connector box?
As I try ED withouth head tracking (and just kb+mouse), when I look fast into some direction with head move, or start barrel roll my ship near Azeban Orbital (head not moving), it´s structures near me seem to "stretch", and even come closer, until I end my movement. Where did I fail here? In monitor/option settings, having no head tracker still, or is that just how it (OR 3D) should/will work?
Thanks in advance for all who take time for this, please be detailed in instructions!
Just to add my experience to the list.
Since the update to beat 3.0x things are really stuttering.
I have used fraps to capture the FPS that is shown in the lower corner and they are hanging around 40 fps (extended mode) (fraps is not causing this as it's also without it stuttering).
This is in any play mode tutorial/open
If i don't use the oculus my fps on a normal monitor is 110fps (at least it renders that, the lcd is @ 60hz)
Before the update things where better i'm not sure what this issue is.
I have played around yesterday with everything you are all talking about and more...... (Lcd hz, drivers, direct,extended, quality settings, head tracking, reinstall SDK, and more...)
I just wait and see what happens in coming updated
My specs:
i7 970 (1366 socket), 20 GigRam, 2x AMD HD7950 in crossfire
If i may add to my own comment above........
If the quality has been improved or changed and that my low fps is due to that great!
I will get other hardware than ;-)
But hopefully somebody knows if that is the case, otherwise i'm just getting new HW for no reason ;-)
I think you have followed the instructions, but does the desk DEMO work? I think your problem maybe the hub is it powered? As this is in development I ripped all the USB connecter out and only installed what I needed making sure Rift to USB2.0 then K/B for basic setup and one other for stick. Hope this helps get your camera working.