This code snippet configures performance-related settings for **Falcon BMS 4.38**,...

August 18, 2025 at 07:42 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.

This code snippet configures performance-related settings for Falcon BMS 4.38, a flight simulator, to optimize the game for better CPU, GPU, and overall system performance. Here's what the specific settings do:

  1. g_nObjListWorkSizeHint:

    • This sets the object list work size hint, which directly affects the level of parallelism used when processing objects in the simulation. Lower values use more concurrent threads (maximizing CPU parallelism) while higher values trade off parallelism for other performance gains.
    • In your case, setting it to 300 (slightly higher than 280) increases the workload per thread, improving overall performance by reducing overhead and stutters.

  2. g_nAdditionalWorkers:

    • This determines how many additional worker threads are spawned. A value of 2 adds two extra threads for multi-threading, helping distribute work across cores, especially on CPUs with multiple physical and hyper-threaded cores.
    • Setting this to 2 leverages more of your Ryzen 5 2500U's logical processors for the simulator, balancing CPU usage.

  3. g_nMinFrameTimeMs:

    • This controls the minimum frame time per simulation tick in milliseconds, setting an upper limit on FPS based on the simulation thread.
    • A value of 4 ensures up to 250 FPS. With VSync enabled and your monitor refresh rate capped at 60Hz, the simulator FPS won't exceed 60.
    • Lowering the frame time too much may add instability; keeping it at 4ms or adjusting conservatively helps avoid visual issues or stutters.

  4. g_fNewTerrainTessellationFactor:

    • This controls the terrain tessellation detail. Lower values (e.g., 0.25 here) reduce the level of detail of the terrain mesh, improving rendering performance at the cost of graphical fidelity.
    • A value of 0.25 provides medium-to-high quality terrain rendering, as opposed to the more performance-intense 0.1 setting.

  5. g_fAnisotropicLevel:

    • This sets the anisotropic filtering level for textures. A lower value reduces texture quality to improve performance, which is particularly relevant for integrated GPUs like the Radeon Vega 8.
    • A value of 1.0 reduces strain on the GPU by keeping the filtering at a more conservative setting.

The updated configuration seems to tailor the settings to your hardware (Ryzen 5 2500U, Radeon Vega 8 iGPU, RX 560) to improve your gaming experience. Specifically:

  • Increasing object work size hint reduces stutters by balancing multi-threading and parallelism,
  • The small tessellation adjustment optimizes terrain rendering overhead,
  • And VSync with adjusted minimum frame times ensures smoother gameplay at your monitor's refresh rate.

Recommendation:

For further improvement:

  1. Experiment further with the g_nObjListWorkSizeHint. A slightly lower or higher value (e.g., 350 or 250) may yield better results depending on your specific CPU core load patterns.
  2. Consider setting g_nAdditionalWorkers to a higher value (e.g., 3 or more) if stutters persist, as it may further balance CPU usage, though careful monitoring of overall CPU load is required.
Generate your own explanations
Download our vscode extension
Read other generated explanations

Built by @thebuilderjr
Sponsored by beam analytics
Read our terms and privacy policy
Forked from openai-quickstart-node