This is driving me crazy I have the distance set at max and all of my cores and threads running P3Dv2 but the ground textures around a few miles ahead aren't fully loaded until I'm almost over them. In FSX I would run an Lod of 8.5 to fix this but LOD settings in P3DV2 don't seem to change anything. Anyone found a work around?

Try selectively turning down your settings and see which one is affecting the load. Simply, your system cannot load them fast enough. Remember, the settings in P3D are considerably more than in FSX. Normal in P3d might be Max in FSX. Also try REDUCING the LOD radius and see how that plays out.

 

Vic

From what I understand FSX has a maximum distance of 9.5 miles while P3D is 6.5 miles and cannot be expanded.  I believe this was to reduce the possibility of OOM's.  Someone please correct me if I am wrong on this.

From what I understand FSX has a maximum distance of 9.5 miles while P3D is 6.5 miles and cannot be expanded.  I believe this was to reduce the possibility of OOM's.  Someone please correct me if I am wrong on this.

 

That is correct.

Yep... I'm starting to fly FSX for my GA stuff so I can fly at 8.5. It looks so much better than a blurry P3D.

This is one of the main reasons (apart from the R6025 error) that I got a refund and went back to FSX DX10.

 

Pointless having "non popping autogen" if you can't actually see it.

Tweaking this may help.  I have mine increased to .40, and have gone as high as .50.  It's a percentage.  Try going higher, even .70 ... you know you can always set it back.  So even try lower.  But I think the issue you describe you'll need to increase up to 20% maybe more.

 

Prepar3D Learning Center

Advanced Performance Tuning

 

[MAIN]

FIBER_FRAME_TIME_FRACTION=0.33
  Non-Default entry. This entry will not exist in your Prepar3D.cfg file by default and must be added to the file.

Performance Tuning Tip:
This setting, which defaults to a value of .33 (33%), defines the percentage of each frame that is devoted to loading scenery. Increasing this number can reduce "the blurries", but it can cause stutters, and can also reduce the overall frame rate. Try reducing the number to the lowest level where you still get smooth scenery paging. This will vary depending on disk speed as well as the type of flying, as well as the selected scenery settings. 

Tweaking this may help.  I have mine increased to .40, and have gone as high as .50.  It's a percentage.  Try going higher, even .70 ... you know you can always set it back.  So even try lower.  But I think the issue you describe you'll need to increase up to 20% maybe more.

 

Prepar3D Learning Center

Advanced Performance Tuning

 

[MAIN]

FIBER_FRAME_TIME_FRACTION=0.33

  Non-Default entry. This entry will not exist in your Prepar3D.cfg file by default and must be added to the file.

Performance Tuning Tip:

This setting, which defaults to a value of .33 (33%), defines the percentage of each frame that is devoted to loading scenery. Increasing this number can reduce "the blurries", but it can cause stutters, and can also reduce the overall frame rate. Try reducing the number to the lowest level where you still get smooth scenery paging. This will vary depending on disk speed as well as the type of flying, as well as the selected scenery settings. 

 

This has nothing to do with what the OP or I described, but it's good info for folks.

From what I understand FSX has a maximum distance of 9.5 miles while P3D is 6.5 miles and cannot be expanded.  I believe this was to reduce the possibility of OOM's.  Someone please correct me if I am wrong on this.

I've never had an OOM, I wish LM would allow us to edit that field if I got an OOM at 9.5 I'd just reduce the LOD not bother LM about it.

I agree it would be nice to give the User the option.  Maybe some window pops up when a user goes beyond 6.5 warning them they could experience OOM's.  Maybe the extra message would keep complaints down to a minimum.  It would be LM's way of saying  "we warned you",

 

 

but the ground textures around a few miles ahead aren't fully loaded until I'm almost over them

 

 

 

This has nothing to do with what the OP or I described

 

Sure it does.  I am using photoscenery at 1/3meter resolution and I am quite satisfied with the draw distance.  You WILL see LOD change in relation to whether or not your processor is given enough time.  It's not just about blurries.

Also, I did experience my first OOM with P3D2.2.  But the only change to my system or any config was going to 3200x1800 monitor (which was not as satisfying as 5760 x 1080 I normally run at).  I am suspecting that it has to do with the display buffer more than anything.  The display buffer can actually be smaller than the display itself AS AN OPTION, cutting out much of the memory problem.  ie you can still get as many displayed objects, sacrificing very little in resolution when it comes to what the final display shows.   It may even be something that changes on the fly.   I'm wondering if LM has looked at it from that angle.

I've a question, at what LOD setting in FSX does it become pointless. For instance for a long time I was running at 8.5, but this last month I've been running at 10, and I'm not sure if I'm seeing actual improvement or if its just my mind playing tricks.

Sure it does. I am using photoscenery at 1/3meter resolution and I am quite satisfied with the draw distance. You WILL see LOD change in relation to whether or not your processor is given enough time. It's not just about blurries.

Also, I did experience my first OOM with P3D2.2. But the only change to my system or any config was going to 3200x1800 monitor (which was not as satisfying as 5760 x 1080 I normally run at). I am suspecting that it has to do with the display buffer more than anything. The display buffer can actually be smaller than the display itself AS AN OPTION, cutting out much of the memory problem. ie you can still get as many displayed objects, sacrificing very little in resolution when it comes to what the final display shows. It may even be something that changes on the fly. I'm wondering if LM has looked at it from that angle.

Trust me, I know what you are saying but it has no affect on what the OP or I am describing. It's clear as day when you can set the LOD higher in FSX and see how much better it looks.

 

My CPU is hardly taxed no matter what fiber fraction I use and any change to that does absolutely nothing to the blurries.

Hello, Guys,

 

After using photoreal scenery Megascenery Earth ( MSE v2 ) for months on FSX using Lod radius 9 or more, I´m very disapointed with Prepar3Dv2 which has Lod_radius fixed at 6.5 - I get very blurry screens, or sharp textures appearing only when aircraft comes very close. This is terrible !!! - If there´s some guy here from LM, I´d like to ask to give us back the control of Lod_Radius in config file. Using Prepar3D with MSE this way is almost useless, so I went back to FSX, where I get sharp textures almost to the horizon, as the real thing.

If you want a LOD radius higher than 6.5, simply go to the Prepar3D forums and request it. If you don't make some noise about the matter, don't expect them to lift the radius cap. Explain to them that a high LOD radius is vital for photoscenery.