FAQs

Very little.

SimFly Linker mainly interacts with MSFS through API, and the underlying code is written in C++. When running normally, SimFly Linker almost 0 CPU, even in streaming video mode, the usage of CPU is still around 2%.

The only performance fluctuation may occur during video recording, but due to the use of Windows’ latest screen recording function (this is the main reason why Windows system requires version 1903 or above), the performance fluctuation is quite small. According to tests, in a host configuration with a 6900XT graphics card + 32GB memory + AMD 6800, using the 60fps 1080p recording option, the game’s frame rate fluctuation is about 2-3%.

Also, at the end of the recording, SimFly Linker’s use of memory will spike briefly because the program needs to read the recorded video into memory for processing and writing to disk.

Very little.

The FDR plugin will automatically start every time you fly (there is no need to start SimFly Linker in advance). Due to the use of asynchronous reading and writing technology, and the data read and recorded is very small, so the impact on performance can be ignored.

The FDR plugin filters out records under the following conditions – flight time is less than 2 minutes or there are less than 10 valid record entries. If you find that you meet these conditions but still can’t see the FDR record, you can click the “Open Files” button at the bottom of the FDR page to check if the corresponding files have been created in the folder that appears. If the folder does not exist as indicated, it is likely that some third-party plugins have changed the path where the data is saved. Please contact me at [email protected], and I will help you investigate the issue.

If you find that your game’s FPS has dropped after transmitting real-time video to SimFlyPad using the pop-up window mode of Fenix MCDU or G1000, this is a “normal” phenomenon. The reason for this issue is that the current MSFS does not support good performance for pop-up windows, and it has little to do with the video transmission feature of SimFlyPad itself. Microsoft’s official development plan indicates that this issue is expected to be fixed in SU 15.

Tip: For some users, turning off vertical synchronization can significantly improve the performance of pop-up windows. (Needs to be turned off in both game settings and graphics settings)

After using the pop-up window transfer feature of SimFly Linker, you might find that in your next gaming session, no matter how you click Right ALT + Left Mouse Button, you can’t see the window pop up anymore. Don’t worry, it’s not that the window can’t pop up; rather, after the window pops up, MSFS immediately moves it to a remembered location by MSFS. (This happens because SimFly Linker moves the window to a hidden position during streaming. If the window’s position remains hidden when you exit the game, MSFS will remember this incorrect position.)

• To reset the position of your current pop-up window: You can click the RESET Popup Windows button on the Tools page of SimFly Linker.
• To make MSFS remember the “correct” position of the pop-up window again, after clicking the “RESET Popup Windows” button, keep the pop-up window open and return to the game’s main menu.

If your mouse does not become a zoom icon when you press the RightAlt key, Go to the MSFS’s Control Option, search “NEW UI WINDOW MODE” and rebind the Right Alt key to it.

Very little.

The Core plugin only starts working after SimFly Pad switches to the Cockpit page and executes “Connect”. Because it uses update notification and asynchronous refresh mechanism, even when using a panel like B737 with hundreds of data variables, the impact on the game FPS is very small.

At the same time, since SimFly Linker and Core plugin communicate through API via memory, the efficiency of data transmission is also very high.

This issue is usually due to unstable graphics card drivers. For AMD graphics card users, changing the drivers can solve the problem.