Hello!

Today I upgraded to Gigabyte RTX 2070 Super. I ran some benchmarks and everything looked great, GPU boosted to about 1950 MHz. Then I made a test flight with FSLabs A320 from LJLJ to LFPG (without changing settings that I had with old GPU). It was running 1500MHz core speed in LJLJ (RFScenerybuilding) and I expected to see that GPU will work even faster while approaching to LFPG (Taxi2Gate). I was on a approach above Paris and autogen was loading behind me and GPU was running at 1000MHz. My previous GPU GTX 1060 3GB was working almost always at 1850 MHz and autogen was loading fast enough. I don't know where is the problem. I don't think there is a bottleneck because I have 750W Gold Plus PSU from Gigabyte and i7-7700 running at 4.2 GHz.

At LJLJ my new GPU was working better than my previous one but at LFPG my previous GPU was working better.

I also tried deleting the old shaders and it didn't help.

My PC specs:

I7-7700 (4.2 GHz, HT enabled)

16 GB DDR4 RAM

Gigabyte RTX 2070 Super OC

240GB SSD, 500GB SSD

1TB HDD, 2TB HDD

Gigabyte G750H Gold Plus

 

Do you know what is causing this problem?

 

Thank you!

Edited September 20, 20196 yr by Branimir

Why do you expect the GPU to work harder the new GPU will not need to, on the same settings for less powerful GPU, CPU performance GPU icandy you should be able to run with high graphic settings with the new GPU.

Moving from a 1080 to a 2080ti on the same setting my new GPU was just idling the fans did not need to run, but push up the settings to make it work harder.

PS when you installed the new GPU did delete the config file and the shaders and let the sim rebuild them. 

I was expecting more FPS, but I am I think it runs much smoother now. It is interesting that it runs with lower core clock in LFPG comparing to LJLJ. 

How can I fix autogen that is loading behind my aircraft? I have autogen draw distance set to HIGH.

Probably not see much in FPS which is CPU bound but you should see textures loading significantly faster across the board!

Whenever Nvidia GPU is roughly above 15% in D3D application, core will run at maximum operating frequency. Having lower than maximum utilization does not mean that it will downclock. Make sure you at least delete your prepar3d.cfg configuration file and shaders.

Regarding autogen loading, set in-game frame rate limiter. If running unlimited, then you assign virtually no resources to terrain loading. You could also mess with FFTF, but I recommend to do your tuning with in-game sliders.

Edited September 20, 20196 yr by Evros

Thank you for answers! I tried some tweaks like TEXTURE_SIZE_EXP=10 and it was using 7.5 GB of VRAM and GPU had no trouble at all.

I found a fix for slow autogen loading. I tried locking FPS to 30 but it affected performance because locking your FPS sets FIBER_FRAME_TIME_FRACTION automatically to 0.33 and unlimited automatically sets it to 0.01. I decided to add FIBER_FRAME_TIME_FRACTION=0.10 and then lock FPS to 30 and then test these settings. I put FSLabs A320 to slew mode and set it to 820kt and leave it like this for several minutes. Autogen is now loading perfectly in front of me!

There is also the option of FFTF Dynamic P3Dv4 which will Dynamically change the FIBER_FRAME_TIME_FRACTION according to either frames per second or height above ground.

I was sceptical at first, but hey at the time I bought it was on special and there was a particular airport approch that at a certain point would have blurry textures (on P3D unlimited), yes they went away when locking P3D internally to say 30 FPS, however P3D is poorly optimised for the internal framerate limiter and I've always had trouble with P3D maintaining the set frame rate via the P3D internal limiter.

With FFTF Dynamic P3Dv4 the blurries disappeared and I had the best of both worlds, running unlimited in P3D and have FIBER_FRAME_TIME_FRACTION under my control.

Also meant an external vsync / frame rate limiter such as RTSS was suddently a valid propostion for maximum smoothness and performance.

I use  a range between 0.01 and 0.33 using the FPS option for when flying GA and the above ground option for when flying high in jets.

Some things to note RE: FFTF Dynamic P3Dv4:

• It's a huge and pretty crappy user interface relying on mouse only, there is no typing or using the arrow keys to manage values which makes it fiddly.
• It doesn't follow normal window rules e.g. no "snapping to size" or any resize for that matter.
• Fortunately it can be minimised and can auto start and shutdown with P3D.
• It's very license controlled and will connect to license servers and check it's validity every startup, not normally an issue unless the license servers are down (which happened a few weeks back for a few hours).
• Otherwise it seems to do what it advertises.

The product page has more info if you'r interested.

https://www.fspsstore.com/fsps-products/fsps-fftf-dynamic-p3dv4.html

Cheers

On ‎9‎/‎21‎/‎2019 at 8:20 PM, Branimir said:

I decided to add FIBER_FRAME_TIME_FRACTION=0.10 and then lock FPS to 30 and then test these settings.  I put FSLabs A320 to slew mode and set it to 820kt and leave it like this for several minutes. Autogen is now loading perfectly in front of me!

Do you mind telling us the position of your autogen sliders? What setting do you use for "autogen draw distance", "autogen vegetation density" and "autogen building density"?

Just wondering, keeping autogen updated at 820kt is quiet an achievement.

After I added TEXTURE_SIZE_EXP=9 it struggles to keep up at dense autogen areas with 820kt but it is working perfectly with 400kt (FSLabs A320). So 400kt works fine at large cities (tested above Paris). If I put it into a slew mode with 820kt at countryside area it has no problem at all.

My settings: 

 

UPDATE: I have just found a FPS killer - road traffic. I have never realised it has such a huge impact. Now I always have 30 FPS+

Edited September 23, 20196 yr by Branimir

2 hours ago, Branimir said:

After I added TEXTURE_SIZE_EXP=9 it struggles to keep up at dense autogen areas with 820kt but it is working perfectly with 400kt (FSLabs A320). So 400kt works fine at large cities (tested above Paris). If I put it into a slew mode with 820kt at countryside area it has no problem at all.

My settings: 

 

UPDATE: I have just found a FPS killer - road traffic. I have never realised it has such a huge impact. Now I always have 30 FPS+

 

What did you set your road traffic slider to...???