Hi all,

P35 V5. I run a high(ish) spec computer, but with V5 in particular, autogen is not loading at the other side on descent. It does load physcially behind the aircraft.

 

I have ample memory available, FPS are not an issue. What is going on?

 

https://imgur.com/s1mHORa

 

https://imgur.com/NAc8tLd

Edited June 30, 20205 yr by aceridgey

Your cpu couldn't keep up with the demand, either due to other apps taking up cpu time, or speed of aircraft.

Is this happening all the time, or did it just happen on one flight?

What is your cpu type and speed?

7 minutes ago, Mace said:

Your cpu couldn't keep up with the demand, either due to other apps taking up cpu time, or speed of aircraft.

Is this happening all the time, or did it just happen on one flight?

What is your cpu type and speed?

6700K @ 4.5GHZ. 

 

 

1 minute ago, aceridgey said:

6700K @ 4.5GHZ. 

 

 

Was this a one-off occurence or is it happening on every flight?

6 minutes ago, Mace said:

Was this a one-off occurence or is it happening on every flight?

Every flight

I don't know what else you have running, but I would recommend at least temporarily turning down Autogen and Scenery Draw Distance one notch.  Then see if the behavior continues...

You are running your CPU with Hyperthreading but you have no AM set i guess?

1 hour ago, JoeFackel said:

You are running your CPU with Hyperthreading but you have no AM set i guess?

Actually hyperthreading is off.

I'm not convinced this is a hardware problem gentlemen, I've been running v4 with little issues (only Heathrow sometimes did this). 

I'll turn down some settings in the mean time. 

 

Edit. I recently put in an extra 16gb of ram. Could that be it? 

Edited July 1, 20205 yr by aceridgey

1GB of RAM, are you sure?

Depends on the Motherboard but most of them you should upgrade RAM in pairs and the speed the whole RAM will be used is clocked by the slowest RAM module.

Hi

My understandxing is that the time allotted by P3D to each frame to load scenery textures and autogen is known as Fiber Frame Time Fraction (FFTF). If you limit your frames the default value for this in P3D is I beleive 0.33 (not sure what the units are). If you don't limit your frames this parameter does not operate, and like me you will tend to experience blurries and loss of autogen at your destination on descent. The autogen will eventually load but it can take an immersion destroying time to do it.

I don't think this happens to everyone, but depending maybe on  your system, the higher your texture resolution and autogen density settings the more likley this is to occur without some kind of action.

You could try adding a line in you P3D.cfg to set FFTF to 0.15 as this is receommended by some people. Add this line to the [MAIN] section of your P3D.cfg if you are comfortable editing this file i.e - FIBER_FRAME_TIME_FRACTION=0.15.

I use a tool from FSPS called Dynamic FTFF, which works for me. Again not everyone claims success with this but it works well enough on my fairly old machine with quite high settings.

Hope this helps.

Kind regards

 

Ray.

 

 

2 minutes ago, JoeFackel said:

1GB of RAM, are you sure?

Depends on the Motherboard but most of them you should upgrade RAM in pairs and the speed the whole RAM will be used is clocked by the slowest RAM module.

Yeah it's the same ram. Now 4x8. It was just a guess, still think it's software

10 minutes ago, aceridgey said:

Actually hyperthreading is off.

You should also try turning HT ON as V5 seem to make better use of it as V4 did.

Just keep core 0 away from it, with an proper AM setting like 12277 you should be good to go.

5 minutes ago, rayharris108 said:

Hi

My understandxing is that the time allotted by P3D to each frame to load scenery textures and autogen is known as Fiber Frame Time Fraction (FFTF). If you limit your frames the default value for this in P3D is I beleive 0.33 (not sure what the units are). If you don't limit your frames this parameter does not operate, and like me you will tend to experience blurries and loss of autogen at your destination on descent. The autogen will eventually load but it can take an immersion destroying time to do it.

I don't think this happens to everyone, but depending maybe on  your system, the higher your texture resolution and autogen density settings the more likley this is to occur without some kind of action.

You could try adding a line in you P3D.cfg to set FFTF to 0.15 as this is receommended by some people. Add this line to the [MAIN] section of your P3D.cfg if you are comfortable editing this file i.e - FIBER_FRAME_TIME_FRACTION=0.15.

I use a tool from FSPS called Dynamic FTFF, which works for me. Again not everyone claims success with this but it works well enough on my fairly old machine with quite high settings.

Hope this helps.

Kind regards

 

Ray.

 

 

HI Ray,

 

I've always run FFTF at 0.01 in old sims with good success. But I haven't done that in V5. 

I'll give it a go!

My troubleshooting is going to be as follows.

FFTF - =0.10

Reinstall of all P3d and all addons. 

Removal of 16 of the 32gb of ram. 

Return here with results.

 

 

Currently, there is only one truly working setup to avoid this: set autogen draw distance on nothing higher than "medium". Setting this any higher results in fine tuning of all other settings as such as the computer can keep up the autogen loading and differs from build to build. 

Have to agree that setting autogen to 'medium' is the safest bet to ensure that autogen appears smoothly and / or at all after takeoff.
No other setting seems to impact the appearance of autogen as much.