joebelter wrote:These are all great replies! Thanks so much for taking the time, really.
My biggest concern is that I HAVE set ALL the sliders in EACH app to the lowest setting possible, then the HIGHEST levels and and the FPS is always the same. It never varies by more than 1 or 2 fps. It stays under 20 and over 17. I understand the big impact CPU and sceneries have on FPS. I've been using P3d for many years and flight sims since they came out in the early 80's. I'm familiar with all the graphic sliders in P3D and now Flyinside. The framerate never changes whatever I do; high/low - whatever.
I can fly DCS ships in very high settings in my Oculus Rift with excellent results. Even with shadows and water on DCS is excellent. It has been the case with the new 2.5 version as well as previous Alphas and Betas. If it was my computer or graphics card DCS would bring the FPS to its knees...
One interesting comment someone made was that P3Dv3 worked better... I actually had it working BEAUTIFULLY with the last version of 3. For some strange reason Flyinside stopped working with it and crashed on starting the app. I tried everything to clean out P3Dv3, reinstall, the works - but Flyinside just won't work with it. I fired up P3dv4 and it's all working, just not the framerate. I have BOTH versions of Flyinside.
Any ideas?
Joe
I have the same setup , except less memory and overclocked up to 4.6Ghz. I also have full Orbx Suite.
I have the settings on medium/normal typically, dynamic lighting OFF (this is a must !!!) , HDR lighting off. Shadows off. Weather programs are a big killer, I dumped the big weather suites, namely Active Sky P3DV4 /ASCA in favor of FSrealWX and Soft clouds. I always keep volumetric fog off. Weather looks great in VR and no major performance drops. Right now in VR you are wasting resources on eye candy you can't even really enjoy with those weather suites.
For traffic I use UTLive, which is actually the most FPS friendly traffic package I've used. Still got a couple of quirks, but it sits outside the simulator and injects as it needs to based on your settings.
Be sensible with the settings in FTX Vector, no reason to show minor roads etc. I disable road traffic.
I typically fly an A2A Piper and get an FPS range from 38/90 to 60/90 or the Aerosoft CRJ900 which runs at 28/90 to 45/90. Its the number on the right that has the biggest effect, if its drops below 90, your system is over-taxed.
Finally, the latest NVidia drivers are dogs. Go back to the 388.xx drivers. I'm on 388.59. Opt out of Oculus Beta if you are in it.
If you search my login name I have posted my settings in much more detail in previous threads and also a procedure to ensure the sim is making the best use of the cores. When it loads up, it loads very heavy on one core. You can disable that core and re-enable it to get it to balance better. Process Lasso can be used for this too, but I just prefer to do it manually when I fire the simulator up.
At first I found V4 to be slower than V3, but after some experimenting I eventually had V4 running better and no longer having VAS issues like I did in V3 !!!
If you have a ZX motherboard and good cooling, you can push that CPU up a bit more that equals higher FPS more than anything else. The 4790K even a few years on is still one of the best processors for P3D. The 1070 is fine for FI and P3D.
Youi def. have the hardware to run FI fine with V4.
A complete reload of P3D is always a good starting place to zero out your system, adding one thing at a time. I gained about 5fps last time I that.
Alan.
Win10-64, i7-4790K OC to 4.7GHZ, 16GB DDR3, EVGA GTX1070 8GB OC, 1 Monitor , CV1, Saitek Rudder Pedals, CH Eclipse Yoke, P3DV4.5
FI P3DV4 Beta Tester. FlyInside Moderator.