If you have UI scaling issues

Right‑click your EXE
2. Choose Properties
3. Go to Compatibility
4. Click Change high DPI settings
5. Enable:
• Override high DPI scaling behavior
• Scaling performed by: System or System (Enhanced)
Which one to choose?
• System → safest, most predictable
• System (Enhanced) → sometimes sharper, but not always supported by WinForms
Start with System.

I'm attempting to update but cannot find the folder rksoftware/Cache to paste the Db5file into.

Hi,
some time ago I write about the same problem on the old forum here with version 3.0:
https://forum.flightsim4fun.com/NF/viewtopic.php?t=1234 

Now with version 3.2 the problem persist. I can't get the correct clock time when reload a saved flight, I have to adjust manually the FlightSave24 clock to correct VC clock when I reload the flight.

Try to explain me better:

1) the clock in my VC cockpit show for example 07:00 and my system time is 23:30 (I always noted the VC time on the filename before time stamp generated by FlightSave24 file)
2) save the flight at 23:30
3) next day reload the flight and the VC clock is completely different from my original one, it's not more 07:00, but a random one

see the screen here, underline in red are my VC time (I write it when save the flight to remember) and then there is the time stamp of FlightSave24 with my sistem time. 

Take the first on the list for example, when I reload the saved flight I can't get the exacly 06:57 but get a random time and I have to adjust it in FLightSave24 untill fit the VC one match with one I noted to the moment of saving.

Any idea to get reloaded the correct saved time? 

Is it possible to avoid the view get centered on the map each time you click on a Traffic ? If you want to double click on it it requires every time to re-target the plane on the map.
Thanks!

Vincent B.

Hi everyone,

first of all, congratulations for the excellent work on OI4FS2024.
The software connects perfectly with the PMDG 737 under Microsoft Flight Simulator 2024 and overall it looks like a very solid and promising solution.

However, we are currently experiencing a couple of important issues with our OpenCockpits setup and we would like to understand if we are missing something in the configuration.

1. Overhead switches affecting DU selectors / GPWS tests
Sometimes, when operating certain switches on the overhead panel, the DU selectors on both CPT and FO sides suddenly change position/state by themselves, and at the same time the GPWS warning tests start triggering (WINDSHEAR, PULL UP, etc.).
This behavior appears random and is extremely annoying during operation.
Has anyone experienced something similar?
Could this be related to overlapping offsets/events or incorrect variable mapping?

2. Servo gauge configuration problems
We are also having major issues configuring the servos.
Compared to the original standard OpenCockpits configuration package, we only managed to discover that:

• Servo 1 for EGT is actually driving the Fuel indication instead.
  

• How are the servos supposed to be configured correctly in OI4FS2024?
  
• Is there a reference mapping table available for OpenCockpits gauges/servos?
  
• Do we need to manually remap every servo output?
  
• Is there a calibration procedure or recommended setup method?
  

Bugs related issues for the Value apps should be here:
FStarter- FlgihtSave
Snapflight - Spotty

General questions and issues related to any of the Value apps
FStarter - FlightSave  
Snapflight - Spotty

Oi4FS24 bugs should be reported and addressed here.

Post you Oi4FS general Oi4FS24 issues and questions here.