Sooo Smooth

Hey everyone,

I have just loaded the game up and quickly took the oculus back off to inform you lot of my finding.

I have a sli 970 setup and love it to bits. However upon loadup while in the cockpit of my Vulture if I turn my head fast I get ever so small jumping/delay. It doesn't affect the gameplay I Just look through it and ignore it.
But, now, I have just installed the 356.04 Nvidia driver and booted up again. Holy spaceballs. Absolutely NO judder no matter how fast or slow I move my head to look around. It really was a day/night difference.

I really, really hope others try it and find it is the same for them. I'm truly amazed at the difference.

Fingers crossed for you all.

Alan

Oh by the way, I am running Windows 8.1 and on SDK 0.6.0.1
 
Last edited:
I'm using SDK6 here it works but occasionally I get glitches with the head tracking, moving and pressing F11 normally fixes that. I'm having the dreaded SC judder though, so I'll try the new driver and see if that helps :) (nvidia driver that is)
 
Last edited:
Yeah, but from what I was reading, there seems to be a lot of negative feedback on the 358.50 ones. I'm playing it safe and staying with what works good for me.

Alan
 
358.50 plays fine. FD, fix the sc stutter plz.

I never said it wouldn't play, just that there are a lot of negative posts around them. Anyway, the thread is about my SLI setup not a single card. And with 2 cards, I don't get any SC stutter. On a side note, the drivers I am using I can't seem to find anymore on the Nvidia site even if I check the archived drivers.
 
Last edited:
I never said it wouldn't play, just that there are a lot of negative posts around them. Anyway, the thread is about my SLI setup not a single card. And with 2 cards, I don't get any SC stutter. On a side note, the drivers I am using I can't seem to find anymore on the Nvidia site even if I check the archived drivers.

Can you attach your config files? I get the same SC stutter with SLI on or off.
 
I tried updating nVidia drivers and also setting low graphic settings, V-sync off, I've attached my MSI afterburner screen grab to show the FPS drop in and out of SC, you can see here I'm following a plotted course through about 5 jumps, lowest point is 41fps on my approach to my final destination, watch the FPS shoot back up after I drop out of SC and dock!

PC spec; AMD 8350 (8 core 4ghz) 8gb Ram, GTX970, driver version 358.50, Win7 64 and SDK 0.6.0.1 - DK2 as Primary Display @75hz

ed_ab.jpg
 
Last edited:
The SC frame drop problem doesn't appear to be VR related (we might notice it more though) as non VR users reported the same problem.

- - - Updated - - -

I run the AMD FX8350, 16GB 2400 DDR3 RAM, Rift runtime 0.5, have 2 MSI 980Tis SLI and have virtually all the GFX setting to either ultra or high (except for shadow which I have off) and SS set to 2.0 and there is only slight (very slight) delay when I turn my head.

The big difference I find is set the vertical sync in the Nvidia 3D settings to 'Adaptive' instead of 'On' (or 'On smooth'). When I have it on all the time then I get terrible problems. Adaptive brings everything up to 90+% perfection I'd say. The remaining 10% I put down to the game not being optimised at all for an SLI set up (which FD have admitted) or VR 3D SLI features. That stuff will get better.
 
With 1.3 I never had this problem, I played on high settings with vsync on and it was locked at 75fps all the time, even in SC so it's a bug that has been introduced with the update
 
With 1.3 I never had this problem, I played on high settings with vsync on and it was locked at 75fps all the time, even in SC so it's a bug that has been introduced with the update

Indeed and I think this has been acknowledged by FD. Fixing it seems to be another thing though. It does seem to vary in intensity though. When there are no other ship around then it is bearable but as soon as more than 2 appear then the framerate really drops.
 
I never said it wouldn't play, just that there are a lot of negative posts around them. Anyway, the thread is about my SLI setup not a single card. And with 2 cards, I don't get any SC stutter. On a side note, the drivers I am using I can't seem to find anymore on the Nvidia site even if I check the archived drivers.

Yes, I've searched them just after ur post. They're gone. Thought of a typo. No offense.

Look what I found in the driver notes:

Total Available Graphics Memory Reported Incorrectly
Background–TAG Memory
In the Windows Display Driver Model (W
DDM), Total Available Graphics (TAG)
memory is reported as the sum of

Dedicated Video Memory (video me
mory dedicated for graphics use)

Dedicated System Memory (system memo
ry dedicated for graphics use), and

Shared System Memory (system memory shared between the graphics subsystem
and the CPU).
The values for each of these components ar
e computed according to WDDM guidelines
when the NVIDIA Display Driver is loaded.
Issue
Some TAG-reporting APIs represent video me
mory using 32-bits in
stead of 64-bits, and
consequently do not properly report ava
ilable graphics memory when the TAG would
otherwise exceed 4 gigabytes (GB). This resu
lts in under reporting of available memory
and potentially
undesirable behavior of applications
that rely on these APIs to report
available memory.
The under reporting can be extreme. For example, 6 GB might be reported as 454 MB,
and 8 GB might be reported as 1259 MB.

quote_icon.png
Originally Posted by Beavis Tingleball
i found those drivers.. https://developer.nvidia.com/gamewor...driver-support ..it's an update to 356.04 that i didnt see on the regular driver page or archive..
Loverley - thanks :)

Thank u too :D
 
Last edited:
Yes, I've searched them just after ur post. They're gone. Thought of a typo. No offense.

Look what I found in the driver notes:

Total Available Graphics Memory Reported Incorrectly
Background–TAG Memory
In the Windows Display Driver Model (W
DDM), Total Available Graphics (TAG)
memory is reported as the sum of

Dedicated Video Memory (video me
mory dedicated for graphics use)

Dedicated System Memory (system memo
ry dedicated for graphics use), and

Shared System Memory (system memory shared between the graphics subsystem
and the CPU).
The values for each of these components ar
e computed according to WDDM guidelines
when the NVIDIA Display Driver is loaded.
Issue
Some TAG-reporting APIs represent video me
mory using 32-bits in
stead of 64-bits, and
consequently do not properly report ava
ilable graphics memory when the TAG would
otherwise exceed 4 gigabytes (GB). This resu
lts in under reporting of available memory
and potentially
undesirable behavior of applications
that rely on these APIs to report
available memory.
The under reporting can be extreme. For example, 6 GB might be reported as 454 MB,
and 8 GB might be reported as 1259 MB.

https://forums-cdn.frontier.co.uk/images/elite/misc/quote_icon.png Originally Posted by Beavis Tingleball [url]https://forums-cdn.frontier.co.uk/images/elite/buttons/viewpost-right.png[/URL]
i found those drivers.. https://developer.nvidia.com/gamewor...driver-support ..it's an update to 356.04 that i didnt see on the regular driver page or archive..
Loverley - thanks :)

Thank u too :D

No worries. The reason I put the thread up was from seeing all the comments regarding two card setups, and the angst regarding the stutter. I may get a ever so slightly pause for a microsecond when entering hyperspace from one system to another, but apart from that, smooth as butter. I know sometimes bad performing high end cards can be attributed a lot of times to motherboard issues or Motherboard drivers.

Not saying its not a bug that people have hit on, but I consider myself lucky that mine is running how I want it to,, hence I am staying with these. lol. But funny how these specific drivers aren't in the archive, but only on the VR part of the site. As I said before I hope that many others get the same performance I seem to have.
 
Last edited:
Back
Top Bottom