*Grr*.. I can't play E: D until VR bugs are fixed

saviornt

saviornt
I've been trying to play the gamma version, but.. I just can't. It seems that the Obs2PredMatcher failing and the Position resets due to vision latency changes (screen goes grey for a split second, like you lost positional tracking, or the position of the camera "fixes" itself) are killing this game for me atm. Not too mention the insufferable judder I'm experiencing, textures / objects not being rendered by, in my case, the right camera (or, in common terms, the right eye).

Couple this with the constant game freezes..

Now, the really sad part is.. everything was working perfectly before 3.9 :(
 

777Driver

777Driver
Post your specs, I think quite a few of us are seeing quite a big improvement in Gamma, perhaps we can compare settings and take it from there.

Cheers
 

Wolfox

Wolfox
Yesterday I set everything on high. Surprise I got the same performance of 1.06.
Didn't see the FPS, but I could play. AA MUST BE OFF it ruins everything.
It resetted only 2 times in the beginning. I won't be surprise it's related to some datalog update while game is starting.
Now I'm updateing my pc and doing a nice scan. Never know what can pass through in space :D
 

thafred

thafred
saviornt said:
i7-950 3.06ghz
12gb RAM
gtx 980

current drivers and all that.
Click to expand...

Have a little slower system than you but same age.
i7-920 4ghz, 12gb ram, gtx 970

for me the game runs absolutely smooth now. I also have almost everything on high, shadows are on low and aa off (as wolfox mentioned I didn´t get low persistence with aa on) even ambient occlusion is on high.

When you say "screen goes grey for a split second, like you lost positional tracking, or the position of the camera "fixes" itself" .. do you mean the core parking bug by any chance? Our 4 core i7 cpu´s lower the core frequency when idling and this seems to upset the positional tracking. there is a tool to disable core parking. Never had a problem with flashing ever since. I played since the last Beta 2 patch with the Rift and only had the issues starting with 3.01. Maybe you were lucky until now?

From my evening yesterday with the Rift and Gamma (played a solid 4 hours...my best experience in the Rift yet) I noticed that it seems to loose my position as I have to reset more than in 3.06..(a button on my Hotas..no big deal, although mildly annoying)
 

CATPAIN KIRK

CATPAIN KIRK
I have a worse system than you and don't have any of the problems you mentioned. I got the brief losses of tracking constantly during premium beta and beta 1 to a varying degree - sometimes just once every couple of minutes and sometimes almost constantly, but could get rid of it by disabling CPU parking.

As for the right eye not rendering: the only occasion where I get it is during the spinning ship loading screen - never exprienced any issue in the game.

Frame rates are smooth - I usually run default high with AA and blur disabled - I get dips into the sixties in stations, but otherwise it runs fine. I only have to downscale graphics settings when running the second window dev hack.
 

saviornt

saviornt
I'll try to core parking, however, from my understanding all it does is make the CPU use 100% power at all times, which I have natively set in the OS. There is another thread on the tracking resets, which I supplied the logs to. I'm not sure if it's related to the CPU, since it deals with vision latency changes. Only happens in elite: dangerous.
 

RobinsonUK

R
saviornt said:
I've been trying to play the gamma version, but.. I just can't. It seems that the Obs2PredMatcher failing and the Position resets due to vision latency changes (screen goes grey for a split second, like you lost positional tracking, or the position of the camera "fixes" itself) are killing this game for me atm. Not too mention the insufferable judder I'm experiencing, textures / objects not being rendered by, in my case, the right camera (or, in common terms, the right eye).

Couple this with the constant game freezes..

Now, the really sad part is.. everything was working perfectly before 3.9 :(
Click to expand...

Someone else had a problem with Obs2PredMatcher. Might help. Tried different USB ports?
 

saviornt

saviornt
Yea, during my initial setup of the DK2. It's not only the Obs2PredMatcher, but also the vision latency changes. Keep in mind too that this just started occuring (again) after the gamma patch, it happened during 3.04 (iirc), fixed in 3.05 and no issues in 3.06

Also, it only happens in elite: dangerous. if it happened with other programs, then I would chalk it up to being on my end. But as it's only with this program, then it must be the program, not hardware.

From looking at the logs, I'm thinking that when the vision latency changes, the Obs2PredMatcher fails, then the ransack fails (the verbose log is in my bug report). Also, I'm not the only one this particular issue is happening to.

Ah, and this is only the biggest problem. There are several other issues (all combined) that are making me.. not enthusiastic.. about playing the game. If it was only one thing, then I could live with it; but with everything combined, death by a thousand paper cuts.
 

CATPAIN KIRK

CATPAIN KIRK
saviornt said:
I'll try to core parking, however, from my understanding all it does is make the CPU use 100% power at all times, which I have natively set in the OS. There is another thread on the tracking resets, which I supplied the logs to. I'm not sure if it's related to the CPU, since it deals with vision latency changes. Only happens in elite: dangerous.
Click to expand...

What's your OS? And where did you disable core parking? Not sure if I remember correctly, but I think I've read that core parking is quite clingy in Windows 7.

(Personally, I've changed ValueMax to Zero under key 0cc5b647-c1df-4637-891a-dec35c318583 in the registry to stop it.)

Anyway - your system should be running ED in the rift smooth as silk.
 

the_wretched

T
I'm only playing solo, but Gamma has so far been great for me technically. Less judder despite higher graphical settings. I notice the vignette (surely will get better when Oculus release a new SDK and that gets integrated), but latency and loading times are better. Really strange that people are having such contradictory experiences!
 

Shigawire

Shigawire
saviornt said:
I've been trying to play the gamma version, but.. I just can't. It seems that the Obs2PredMatcher failing and the Position resets due to vision latency changes (screen goes grey for a split second, like you lost positional tracking, or the position of the camera "fixes" itself) are killing this game for me atm. Not too mention the insufferable judder I'm experiencing, textures / objects not being rendered by, in my case, the right camera (or, in common terms, the right eye).

Couple this with the constant game freezes..

Now, the really sad part is.. everything was working perfectly before 3.9 :(
Click to expand...

Too bad our DK2 is not a consumer product, otherwise it might have been appropriate to react with the dismay of a consumer.

I have a 2x980 SLI + DK2 (I play with SLI disabled due to AFR) and haven't had any problems with juddering.

Current system:
Asus P9X79
Core i7 4930K 6 cores (12 threads) @ 4.5Ghz
4x4GB DDR3 G-Skill Ripjaw 1866mhz
Revodrive 3 x2 240GB Pci-ex
MSI Geforce 980 GTX 4GB (enabled)
MSI Geforce 980 GTX 4GB (SLI disabled pending VR Direct SFR, due to 15ms latency add from AFR)
PSU Corsair AX1200i

Have you made absolutely 100% sure that all your Intel chipset drivers have been installed, for both your motherboard and CPU?

Of course, as you say this came after you had installed 3.9, but correlation does not mean causation. It could be that you had installed some software in between 3.05 and 3.9 that you may have forgotten about. It could be an issue with the Gamma update. But it would be helpful if we could figure out what changed in the game and what separates your system from ours. It must be something software related. Chipset drivers, or some other drivers.. conflicts.. maybe even malware.
 
Last edited:

saviornt

saviornt
Once we get closer to a consumer release of the HMD, I am sure we will start seeing more VR improvements. I made another post in some thread about my view on this. My belief is that FD would prefer to squash bugs and add content that are in the game that are not just VR related, and I do agree with this, since we are using development hardware that is not consumer ready.

As far as anything changed, software- or hardware-wise, nothing was changed. I know this because during going from 3.06 to gamma, I went to the F: D forums and Oculus forums, read a few threads, and then went to bed.. long days at work.

I do find it odd that there are alot of contradictory reports in regards to VR, and I am sure it's about our configurations / drivers. I've seen reports that it could be Logitech drivers causing issues, however, I can't test this out since I don't have any non-Logitech keyboards or mice :\ Once again though, I'm only getting this in the E: D game, not in Alien: Isolation or other Rift demos that I tried to see if it was my system before I submitted a bug report to F: D

PS: Ran into another bug yesterday.. when I entered supercruise, there was a couple of "stars" that shot into me :eek:
 
Last edited:

RobinsonUK

R
I started playing ED when my DK2 arrived. I'd never used VR before then and I'd never played ED before then either, so as you can imagine it was a real "wow" experience. But as I had let someone borrow the DK2 over the weekend I played ED on traditional screen and it's much better as a game. With the current state of the DK2 I get pretty severe eye-strain after an hour or so, especially the absolutely horrific text rendering.

Everyone who's put the headset on has had a "wow" moment too, so I'm sure it's going to be massive. It's just not quite there yet is it.
 

777Driver

777Driver
RobinsonUK said:
I started playing ED when my DK2 arrived. I'd never used VR before then and I'd never played ED before then either, so as you can imagine it was a real "wow" experience. But as I had let someone borrow the DK2 over the weekend I played ED on traditional screen and it's much better as a game. With the current state of the DK2 I get pretty severe eye-strain after an hour or so, especially the absolutely horrific text rendering.

Everyone who's put the headset on has had a "wow" moment too, so I'm sure it's going to be massive. It's just not quite there yet is it.
Click to expand...

Take the time to set it up to match your eyesight. Took me a few day's to get it right. I have no issues with text or eyestrain.
 

RobinsonUK

R
I did. I fiddled with pretty much all parameters I could find. I measured my eyes with a rule and I measured my eyes with the configuration utility (69.9). The test scene in the configuration utility is pretty clean and clear, but ED is quite horrific. I assume it's the high detail coupled with the low resolution. I whacked down all settings to low and it really didn't make a huge difference.
 

[VR] Mad Mike

[VR] Mad Mike
777Driver said:
Take the time to set it up to match your eyesight. Took me a few day's to get it right. I have no issues with text or eyestrain.
Click to expand...

ditto here as well. yes the resolution is a little low but not so much as to make it unsuable, and i must admit, personally I never plan to play on a flat screen again.

different strokes i guess.

cant wait to get a new gpu for xmas and i can up the detail from what i have on my gtx 670
 

RobinsonUK

R
Including that feeling of nausea when you roll to align with your docking bay inside a station?

barf! >>>>>>>>>>>>>>>>>>>>

It's much, much better in terms of immersion, much much worse in terms of productivity if you're trying to get ahead in the game.
 
You must log in or register to reply here.
Back
Top Bottom