hi guys,

been a while. Back to sim. Had to sell my desktop so i have a laptop now. My specs will not run p3d as fast, but just looking for some p3d tweaks.

I7 9750H @ 2.8GHZ (Big drop from my i5 8600K @ 5ghz haha), i will reapply thermal paste and try and get it up to 3.5GHZ without overheating (it does turbo upto 4 ish ghz)

RTX 2060

16GB RAM

Now this is weird,on my desktop(60hz monitor) 30fps was a blurry mess, laggy visuals when panning etc BUT on this laptop its very clear, smooth, feels like what "60fps" would have been on my desktop... (i have now a 120Hz monitor), but basically the sim is smooth at 30fps. So my main tweaks im looking for is to get the CPU+GPU to NOT get high FPS but to focus on loading the scenery to prevent slow terrain loading. Like i get crispy terrain without it going to a blurry mess. any ideas?

 

cheers ols

 

Hi @ols500

There's no magic tweek unfortunately.

Typically the tweeks that can be applied are more about improving the quality of the output.

The best options are to run the SIM internally unlimited and use a 30 Hz vsync if you've a monitor that supports 30 Hz, otherwise limit the frame rate externally to 30 fps (RivaTuner Statistics Server, Nvidia driver, etc.).

If the system supports it disable core threading as it typically allows a higher level of overclocking, or use an affinity mask to set P3D to just use the cores and not cores and threads.

Monitor the CPU and GPU use especially GPU as when it maxs out the frame rate drops significantly, use the monitoring as a guide to what overloads the system and reduce, for example Traffic uses quite a bit and 3D objects tend to choke the frame rate.

Example quaility tweeks.

Spoiler

[GRAPHICS]

// Rob Ainscough's vid showing the values https://www.youtube.com/watch?v=7vFgfBSSXeE
// MAX_TEXTURE_REQUEST_DISTANCE There's no cap on this value itself because it's intended as a limit.
// If you want textures requesting aggressively, you can set it something very high like 1000000.
// Units are memory allocation units (not distance). TBM 23/08/2021 may as yet be distance as the Learning Centre doesn't actually say what it is.
// There are two other checks that must pass before textures are requested:
// 1) Object is within the far clip distance. This varies by altitude.
// 2) Object pixel size at a given distance passes min radius check. This we made configurable in 4.3 using RS_MIN_OBJECT_PIXEL_RADIUS. (default is 2.0px)
RS_MIN_OBJECT_PIXEL_RADIUS=1.000000

MAX_TEXTURE_REQUEST_DISTANCE=320000.000000

 

[SCENERY]

//AUTOGEN_BATCH_LOD=2 //Default is 2, setting to 1 will greatly increase the amount of autogen buildings, almost double in some instances and tends to result in too many buildings cramped together, valid values are 1 to 9 with 1 the highest.
AUTOGEN_BATCH_LOD=1

 

[TERRAIN]

// P3D maintains a global terrain view for efficiency - if blurries start developing after a period of time or autogen stops loading trial setting to False.
UseGlobalTerrainView=False

// Relates to vegetation and how it is placed along side rivers and roads. The default and minimum is 16 and can be set up to 2048 in double values i.e. 16, 32, 64, 128, 256, 512, 1024, 2048.
// The higher the number the more accurately a curved polygon will be rasterised. 16 equals placement accuracy of ~80 metres, 2048 equals placement accuracy of approx 0.5 metres. Higher values come with more performance costs.
// Result will be treelines that accurately follow the curves in roads and bends in rivers as opposed to the old straight lines and angles of before.
// Surprisingly setting the value to 2048 appeared to have little performance impact, although there were some occasional bandwidth type vsync dropouts and in flight pauses.
// Will trial 512 as a value and use incrementing values to determine what is best for myself.
IMAGE_PIXELS_FOR_AUTOGEN_POLYGONS=2048

Cheers

Edited December 30, 20223 yr by Rogen

Thanks rogen 😁