Oculus Free Flight = 150FPS, anything with AI = 75FPS

[hansangb]

So if you use Free Flight for any Instant Action mission, the FPS is more or less locked at 150FPS.

 

But if you pick any other mission, e.g. Huey Oil Rig Landing, Gun Practice, the FPS drops to 75 before you even take off. Just sitting on the pad w/o taking off, it drops to 75FPS.

 

It's the same with A10, and I believe P51D Sim.

 

Others in the Oculus thread are reporting similar issues.

 

FWIW: My system is I7-4790K, 16GB, GTX-980, SSD, Win 10 Pro. 0.7 version of Rift and no overclocking involved.

 

Thanks

 

Hansang

[RoyMi6]

I was just signing in to post this.

 

It's always been a problem in the past that DCS was never really that well optimised when it came to models, but it seems to be a problem that remains.

 

I was tinkering for a few hours on Sunday and managed to get my graphics tuned enough that the FPS drops only happened when the other aircraft where in my field of view. Even at extreme distances where I couldn't actually even see the target I'd have a solid 75FPS then drop the instant I turned my head to look at even a single target.

 

The test missions I was doing it with was the F15 Intercept mission.

 

Unfortunately unless ED specifically work on model optimisation I'm willing to bet the "fix" is lowering your graphics until the game runs acceptably. Which is fair enough, but with twin GTX980's I was kind of hoping to get above "low/medium" graphics settings in EDGE.

[hansangb]

I'm thinking that because this is repeatable, it's fixable. So I'm hopeful that with future upgrades we'll get 75 FPS X 2. Also, *IF* DCS supports SLI for RIFT, I'll grab another 980 in a heartbeat!

 

PS: We all knew that 150 FPS was really 75FPS X 2. But the math is still the same. 150 = 75 FPS per eye. and 75 = 37.5 FPS X 2.

 

hsb

[RoyMi6]

PS: We all knew that 150 FPS was really 75FPS X 2. But the math is still the same. 150 = 75 FPS per eye. and 75 = 37.5 FPS X 2.

hsb

 

You're not doing anyone any favours with that logic.

 

With the various ways the graphics card architectures, drivers and game optimisations work running in the rift does not equal an instant 50% decrease in FPS - at least not long term.

 

If you're getting 75fps with vsync enabled in the Rift you cannot, with any certainty, say you're getting "150fps" and expect that to be a useful metric.

 

Also, as someone with two 980's, I know you're pain - DCS has always been slow on the uptake of the latest and greatest technology but I really hoped SLI would have been on the cards out of the gate with the new engine.

[hansangb]

You're not doing anyone any favours with that logic.

 

With the various ways the graphics card architectures, drivers and game optimisations work running in the rift does not equal an instant 50% decrease in FPS - at least not long term.

 

If you're getting 75fps with vsync enabled in the Rift you cannot, with any certainty, say you're getting "150fps" and expect that to be a useful metric.

 

Also, as someone with two 980's, I know you're pain - DCS has always been slow on the uptake of the latest and greatest technology but I really hoped SLI would have been on the cards out of the gate with the new engine.

 

 

It's more simple than that. I was just referring to the fact that in HF2 (and prior) FPS counter was doubled by DCS. When you hit CTRL-PAUSE, the counter is incorrect. And with HF3, it's back to the 'real' FPS.

 

As for SLI, perhaps it'll be included in 2.0? Although, the one post I saw recently showed both GPUs working at ~45% which I found interesting. It was in the "Does DCS support SLI?" thread. Something like that...I don't recall exactly what thread it was in.

 

But the original problem description still exists. In free flight, the FPS counter shows 150. With AI involved it immediately drops to 75. I'm hoping it gets addressed and that something about AI is not a gating factor.

 

hsb