Jump to content
Sign in to follow this  
enrico10999

P3D V 4.5 useful tweaks ?

Recommended Posts

Hi

In the past with the former versions there were useful tips here and on YT for tweaking the "prepar3D.cfg" file.

For example: 

[DISPLAY]
TEXTURE_BANDWIDTH_MULT=160            
[SCENERY]
MaxRegionsPurgePerFrame=1

[TERRAIN]
UseGlobalTerrainView=True
TEXTURE_SIZE_EXP=9

etc...

Are there any new findings as to whether such tweaks also make sense in version 4.5?

Or keep it like it is? 

Beside everybody seems to wait for the hot fix from LM. 🙂

Greetings 

Enrico

 

 

 

 

Edited by enrico10999

Share this post


Link to post
14 minutes ago, enrico10999 said:

Hi

In the past with the former versions there were useful tips here and on YT for tweaking the "prepar3D.cfg" file.

For example: 

[DISPLAY]
TEXTURE_BANDWIDTH_MULT=160            
[SCENERY]
MaxRegionsPurgePerFrame=1

[TERRAIN]
UseGlobalTerrainView=True
TEXTURE_SIZE_EXP=9

etc...

Are there any new findings as to whether such tweaks also make sense in version 4.5?

Or keep it like it is? 

Beside everybody seems to wait for the hot fix from LM. 🙂

Greetings 

Enrico

The most important tweak for me is locking fps at 30 and

FIBER_FRAME_TIME_FRACTION=0.15  In Main Section of Prepar3d.cfg


A pilot is always learning and I LOVE to learn.

Share this post


Link to post
8 hours ago, DJJose said:

FIBER_FRAME_TIME_FRACTION=0.15  In Main Section of Prepar3d.cfg

This is highly individual and should not be put out there as a "useful Tweak" IMHO.. :unsure:

Edited by Bert Pieke
  • Like 3
  • Upvote 2

Bert

Share this post


Link to post

I've never seen any difference tweaking TEXTURE_BANDWIDTH_MULT in P3Dv4.  I just leave it stock.

TEXTURE_SIZE_EXP=9 can be set in the sim GUI by checking "Use high-resolution terrain textures" in the "Terrain" section of the "World" page.

With the release of P3Dv4.4 Rob Ainscough offered some new tweaks that do make a difference:

[GRAPHICS]
ENABLE_MEMORY_OPTIMIZATION=0

MAX_TEXTURE_REQUEST_DISTANCE=320000.000000


[SCENERY]
SCENERY_DRAW_DISTANCE=64000.000000  (on up to 128000.000000)

and Rob's explanations/definitions:

SCENERY_DRAW_DISTANCE is set via the P3D UI (User Interface) in the Graphics options.  This value is the one MOST likely to reduce AG black textures.  The max value that can be set via P3D UI is 64000.000000 via slider (far right setting), if you manually adjust this setting by editing the Prepar3d.cfg and entering a higher value on upto 128000.000000 then you must NOT go into the P3D UI Graphics section and hit OK or else it will overwrite your manual value with whatever the slider is set at (so if the slider is far right it will reset the value back to 64000.000000).

MAX_TEXTURE_REQUEST_DISTANCE is NOT subject to P3D UI changes and you can manually edit the Prepar3d.cfg to enter just about any value you like (and it will stick) as there is no cap, so values 1000.000000 to 50000000.000000 are valid.

ENABLE_MEMORY_OPTIMIZATION is either OFF (value = 0) or ON (value = 1) ... if you have VRAM to spare, there is no need to attempt any memory optimization so set the value to 0 (zero).

HTH,

Greg

  • Upvote 4

Share this post


Link to post
56 minutes ago, Bert Pieke said:

This is highly individual and should not be put out there as a "useful Tweak" IMHO.. :unsure:

What a weird response.  

  • Like 1
  • Upvote 2

Matt Wilson

Share this post


Link to post
12 minutes ago, mpw8679 said:

What a weird response.  

Sorry :smile:

  • Upvote 1

Bert

Share this post


Link to post
1 hour ago, mpw8679 said:

What a weird response.  

Not weird at all. The FFTF is NOT a one size fits all tweak and FFTF- 0.15 will easily cause issues in a system that is challenged. The valid ranges are from 0.10 to 0.99 with a default of 0.33 and depending on your system .15 may or may not work.

We have enough people blindly copying settings and running into problems. If one wants to post a "tweak" it would be best explaining the setting and noting what works for you.

IMHO, the weird response was yours.

Vic

  • Like 6
  • Upvote 3

 

RIG#1 - 7700K 5.0g ROG X270F 3600 15-15-15 - EVGA RTX 3090 1000W PSU 1- 850G EVO SSD, 2-256G OCZ SSD, 1TB,HAF942-H100 Water W1064Pro
40" 4K Monitor 3840x2160 - AS16, ASCA, GEP3D, UTX, Toposim, ORBX Regions, TrackIR
RIG#2 - 3770K 4.7g Asus Z77 1600 7-8-7 GTX1080ti DH14 850W 2-1TB WD HDD,1tb VRap, Armor+ W10 Pro 2 - HannsG 28" Monitors
 

Share this post


Link to post
33 minutes ago, vgbaron said:

The FFTF is NOT a one size fits all tweak and FFTF- 0.15 will easily cause issues in a system that is challenged. The valid ranges are from 0.10 to 0.99 ....

I recall that in some of the threads discussing use of the program FFTF Dynamic, FFTF values down to 0.01 are suggested. So just wondering in the above did you mean the valid range starts from 0.01 or in fact are values below 0.1 not valid (or perhaps values below 0.1 would not be useful with the FFTF Dynamic program)?

Thx,

Al

Edited by ark

Share this post


Link to post
16 minutes ago, ark said:

In some of the threads discussing use of the program FFTF Dynamic, FFTF values down to 0.01 are suggested. So just wondering in the above did you mean the valid range starts from 0.01 or in fact are values below 0.1 not valid (or perhaps values below 0.1 would not be useful with the FFTF Dynamic program)?

Thx,

Al

Don't want to start this battle again but when Aces put in the FFTF the valid ranges were 0.10 to 0.99. I have no knowledge that LM has ever messed with that. However, there still those that swear they see a difference between 0.01 and 0.10.

So unless someone from LM wishes t correct me, I will continue to list those as valid ranges.

That said, exceeding the ranges has no bad effects, it just defaults to the first valid range so 0.01 would become 0.10.

edit: with reference to the FFTF program, I would think it would be possible to MANUALLY insert the value but putting it in the P3D.CFG file will revert to the default.

Vic

 

 


 

RIG#1 - 7700K 5.0g ROG X270F 3600 15-15-15 - EVGA RTX 3090 1000W PSU 1- 850G EVO SSD, 2-256G OCZ SSD, 1TB,HAF942-H100 Water W1064Pro
40" 4K Monitor 3840x2160 - AS16, ASCA, GEP3D, UTX, Toposim, ORBX Regions, TrackIR
RIG#2 - 3770K 4.7g Asus Z77 1600 7-8-7 GTX1080ti DH14 850W 2-1TB WD HDD,1tb VRap, Armor+ W10 Pro 2 - HannsG 28" Monitors
 

Share this post


Link to post
2 hours ago, Bert Pieke said:

This is highly individual and should not be put out there as a "useful Tweak" IMHO.. :unsure:

I did say for me. 😀

IMO, it's a tweak every simmer should try with different values to fit their system. YMMV


A pilot is always learning and I LOVE to learn.

Share this post


Link to post
3 minutes ago, DJJose said:

I did say for me. 😀

IMO, it's a tweak every simmer should try with different values to fit their system. YMMV

Agreed!


 

RIG#1 - 7700K 5.0g ROG X270F 3600 15-15-15 - EVGA RTX 3090 1000W PSU 1- 850G EVO SSD, 2-256G OCZ SSD, 1TB,HAF942-H100 Water W1064Pro
40" 4K Monitor 3840x2160 - AS16, ASCA, GEP3D, UTX, Toposim, ORBX Regions, TrackIR
RIG#2 - 3770K 4.7g Asus Z77 1600 7-8-7 GTX1080ti DH14 850W 2-1TB WD HDD,1tb VRap, Armor+ W10 Pro 2 - HannsG 28" Monitors
 

Share this post


Link to post
2 minutes ago, vgbaron said:

Don't want to start this battle again but when Aces put in the FFTF the valid ranges were 0.10 to 0.99. I have no knowledge that LM has ever messed with that. However, there still those that swear they see a difference between 0.01 and 0.10.

So unless someone from LM wishes t correct me, I will continue to list those as valid ranges.

That said, exceeding the ranges has no bad effects, it just defaults to the first valid range so 0.01 would become 0.10.

Vic

OK Vic, thanks for the info. Being somewhat new to the FFTF discussion I didn't realize there had been 'debate' about the lower FFTF range limit.

Al

Share this post


Link to post
Just now, ark said:

OK Vic, thanks for the info. Being somewhat new to the FFTF discussion I didn't realize there had been 'debate' about the lower FFTF range limit.

Al

No problem AL, just like in those who say they changed the LOD radius to 8 or 9 to get better visuals. LM had it capped at 6.5 no matter what and FSX was much lower but people still swore it made a difference.

:biggrin:


 

RIG#1 - 7700K 5.0g ROG X270F 3600 15-15-15 - EVGA RTX 3090 1000W PSU 1- 850G EVO SSD, 2-256G OCZ SSD, 1TB,HAF942-H100 Water W1064Pro
40" 4K Monitor 3840x2160 - AS16, ASCA, GEP3D, UTX, Toposim, ORBX Regions, TrackIR
RIG#2 - 3770K 4.7g Asus Z77 1600 7-8-7 GTX1080ti DH14 850W 2-1TB WD HDD,1tb VRap, Armor+ W10 Pro 2 - HannsG 28" Monitors
 

Share this post


Link to post
41 minutes ago, DJJose said:

I did say for me. 😀

IMO, it's a tweak every simmer should try with different values to fit their system. YMMV

If you like experimenting with these settings, the following discussion might be a good read..

 


Bert

Share this post


Link to post
19 minutes ago, Bert Pieke said:

If you like experimenting with these settings, the following discussion might be a good read..

 

Preaching to the choir.


A pilot is always learning and I LOVE to learn.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...