Odd problem using my Oculus Rift

[baumgi]

Not unacceptable, unacceptable for me (something that should have been clear in the post you referenced) it is entirely subjective. Personally I don't like the graphical glitches ASW introduces BUT I do think its an amazing bit of tech. I find the glitches are very obvious from the hud shimmer / wobble when your ship rotates on the landing pad (which also affects the thinner framed cockpits such as the vultures) and when turning in your SRV to the tell tale hitch of ASW kicking in and stopping.

ASW is there to pickup the occassional dip in FPS, it's not ideally to be used to punch above the weight of the hardware you have. Although many do, which is fine if they're happy doing that, get results they're happy with and can overlook the issues they will get by doing it.

Anyway, glad to hear you worked out the issue OP. Those original settings did look a little on the high side to me and even ASW can only do so much.

Thanks mate fly safe

 

[Stanis]

Indeed, my ASW kicks in in stations, RES and planets. I cannot see a difference if I'm honest. It's almost impossible to play without ASW kicking in if it's enabled as it kicks in as soon as you drop below 90FPS. I managed to tweak my settings so that I always had 90FPS and the graphics looked bloody awful lol.

I have a gtx1070 with a 6700K, and i'm also very happy with HMD 1.5, SS 1 and the ASW. So.. Everyone is different.

 

[dape]

Ok, I think I've fixed it.

I hate to admit that I was wrong but it but it was the graphics settings (sort of).

I found that if I started the game with rubbish settings 0.65 on both SS and HMD the problem didn't occur BUT if I start the game with my normal settings and lowered the settings to the same rubbish settings the problem didn't go away. I needed to restart the game after changing the settings to actually see if it makes a difference, that's why I didn't think it was the graphics settings because lowering didn't help.

My guess is my actual framerate was lower than 45fps in stations but AWS was trying to get to 45fps which was causing the shuddering.

After 2 hours of tweaking my settings (restarting the game each time) I finally found settings that look almost as good but with zero shudder or ghosting. 90FPS out in space, 60-70FPS in stations and 50-60FPS in a highly populated RES or Engineering planet base.

https://imgur.com/a/qxHXt

Thanks to everyone for your help.

those settings look plausible. You could try without AA and instead up SS from 1.25 to 1.5. I can barely notice any difference with different AA settings but I can see an improvement of aliasing when going from 1.25 to 1.5

 

[dape]

may I ask you as I have the same Mobo... Do you have two sensors connected and if so does the Z170 pro Gaming handle it well?

 

[baumgi]

those settings look plausible. You could try without AA and instead up SS from 1.25 to 1.5. I can barely notice any difference with different AA settings but I can see an improvement of aliasing when going from 1.25 to 1.5

Hello, the problem I have it I lose way more framerate going from 1.25 to 1.5 than I do just turning off AA and I HATE the jaggys without AA turned on. It's the one thing in games that really REALLY bugs me.

may I ask you as I have the same Mobo... Do you have two sensors connected and if so does the Z170 pro Gaming handle it well?

I plug one sensor in the back of the mobo on a USB3 and one in the front on a USB3 and it works very well.

 

[Full_Ninja]

Ok, I think I've fixed it.

I hate to admit that I was wrong but it but it was the graphics settings (sort of).

I found that if I started the game with rubbish settings 0.65 on both SS and HMD the problem didn't occur BUT if I start the game with my normal settings and lowered the settings to the same rubbish settings the problem didn't go away. I needed to restart the game after changing the settings to actually see if it makes a difference, that's why I didn't think it was the graphics settings because lowering didn't help.

I had that same issue where changes wouldn't really show until I restarted. It was driving me nuts.

I really wish software that requires a restart would be more explicit about that. In Assetto Corsa using openVR when you change ss settings you need to do a restart for the change to take effect. The developers stated it so people wouldn't be wasting their time trying to figure out why it was not having the intended effect.