The code snippet you've provided is a configuration file for...

August 18, 2025 at 07:45 AM

This snippet of code comes from a recommended setting by the developers of Falcon BMS 4.38 flight simulator

// Generic CPU and Multi threading Performance Config Variables suggested by Devs:
set g_nObjListWorkSizeHint 280 		// Default value: 1500 (a good balance) – Valid values are 100 - Maximum parallelism, 3000 - almost no parallelism
set g_nAdditionalWorkers 2 			// Default value: 0 a value of 2 will add threads, -8 to reduce HT cores.
set g_nMinFrameTimeMs 4 			// Default value: 4 which should promise no more than 250 FPS on Sim thread. 18 ms = 60 FPS 11 ms = 90 FPS Higher values may cause some problems.

set g_fNewTerrainTessellationFactor 0.35 // Reduced terrain mesh Tessellation distance - Medium-High on Terrain only (was 0.1
set g_fAnisotropicLevel 1.000000 // Lower filtering for iGPU

Here are some actual figures for what is happening with my AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx, 2000 Mhz, 4 Core(s), 8 Logical Processor(s).

g_nObjListWorkSizeHint set to 280 gives me 34.6 FPS on the ground, CPU 54%, Memory (16 GB) 70%, RX560 90%, Radeon Vega 8 9%. What setting do I use to improve this?
I have Vertical Sync on which limits the max FPS to 60 because my monitor is a 28" Phillips 284E which has a resolution of HD 1920 x 1080 @ 60Hz. 

Falcon BMS 4.38 is also started with Priority High and Affinity set to 2-5 cores of 8 cores, the rest are set to Normal and for use with TrackIR5 and VoiceAttack

Ok just tested it with the following settings and it seemed to fix a lot of the stutters, if any they are very small and not locking the screen view as before.


// Generic CPU and Multi threading Performance Config Variables suggested by Devs:
set g_nObjListWorkSizeHint 300 		// Default value: 1500 (a good balance) – Valid values are 100 - Maximum parallelism, 3000 - almost no parallelism was 280.
set g_nAdditionalWorkers 2 			// Default value: 0 a value of 2 will add threads, -8 to reduce HT cores. was 2
set g_nMinFrameTimeMs 4			// Default value: 4 which should promise no more than 250 FPS on Sim thread. 16 caps the sim closer to 62.5 FPS due to VSync which is ON.
set g_fNewTerrainTessellationFactor 0.25 // Reduced terrain mesh Tessellation distance - Medium-High on Terrain only (was 0.1

This config seemed to improve what I had at 280.
CPU 42-49%, Memory (16 GB) 71%, RX560 84%, Radeon Vega 8 11%.
Do you think I should got 330?

The code snippet you've provided is a configuration file for the Falcon BMS 4.38 flight simulator. It consists of various settings that optimize performance for systems with different hardware profiles. Here's an explanation of what each line does and how it impacts your system:

Code Breakdown:

set g_nObjListWorkSizeHint:
- Purpose: Sets the size of the object workload for multi-threaded processing.
- Implications:
  - Lower values (e.g., 100) prioritize parallelism by splitting tasks among multiple CPU cores, which can improve performance on systems with many cores or logical processors.
  - Higher values (closer to 3000) reduce parallelism, which may be better suited for single-threaded optimized CPUs.
  - In your case, 280 seemed to improve performance slightly, but when set to 300, it further reduced CPU usage and improved overall performance.
set g_nAdditionalWorkers:
- Purpose: Specifies how many additional threads/workers should be used for processing.
- Implications:
  - A value of 2 means that two additional worker threads are added, effectively utilizing more CPU cores for the flight simulator. This is good for multi-core CPUs like your Ryzen 5 2500U.
  - Negative values reduce the number of worker threads by disabling certain hyper-threaded (HT) cores.
set g_nMinFrameTimeMs:
- Purpose: Defines the minimum frame time per simulation thread.
- Implications:
  - At 4 ms, it caps the FPS at a theoretical maximum of 250 (1000 / 4).
  - You have V-Sync enabled, which caps the FPS at your monitor's refresh rate (60 Hz). Hence, increasing this value won't raise your FPS. However, ensuring it stays at or below 16 ms (the refresh time for a 60 Hz monitor) will keep the FPS smooth and in line with your monitor's capabilities.
set g_fNewTerrainTessellationFactor:
- Purpose: Adjusts the terrain tessellation factor, which determines the level of detail for 3D terrain rendering.
- Implications:
  - Lower values (e.g., 0.25) reduce the detail level of the terrain, which reduces GPU load and improves performance.
  - A value of 0.1 (higher detail) was causing more strain on your system, but reducing it to 0.25 has improved performance by lowering the tessellation distance.
set g_fAnisotropicLevel:
- Purpose: Configures the anisotropic filtering level, which affects texture sharpness at oblique angles.
- Implications:
  - A value of 1.0 minimizes anisotropic filtering, reducing GPU load, which benefits integrated GPUs like the Radeon Vega 8. Higher values (e.g., 16.0) produce better image quality but increase GPU utilization.

Recommendations and Explanation for "Should I set it to 330?"

Your settings at 300 for g_nObjListWorkSizeHint are already showing improved performance, with slight reductions in CPU and GPU usage. However, increasing it further to 330 could have specific consequences:

At 330, there will be slightly less parallelism (more work is done in fewer threads), which could reduce the workload spreading among your CPU cores. This might or might not improve performance, depending on your specific hardware and game scene. Test it to see if there's further improvement.

General Thoughts:

Monitor Refresh Rate and V-Sync:
- Since your monitor is capped at 60 Hz and V-Sync is enabled, increasing FPS beyond 60 won't provide additional visual benefits. The key is to optimize performance without overburdening system resources.
Resource Balance:
- Your Radeon RX560 usage is around 84%-90%, which is healthy for a GPU running a game. Further reducing GPU workload (e.g., lowering the tessellation factor or anisotropic filtering) might not be necessary unless you experience stutters.
Testing Values:
- Adjust and test incrementally. For example:
  - Start with g_nObjListWorkSizeHint = 330.
  - Observe performance metrics (FPS, CPU, and GPU usage).
  - If CPU usage spikes or FPS drops noticeably, revert to 300.

TL;DR:

This configuration file tweaks CPU and GPU workloads, frame timing, and visual settings for Falcon BMS 4.38. Setting g_nObjListWorkSizeHint to 330 might improve or worsen performance slightly. Test it on your specific hardware to make an informed decision, but 300 seems to already work well with your setup.

Generate your own explanations

Download our vscode extension

Read other generated explanations

Built by @thebuilderjr