SoonerST

Doesn't look like anyone has been on this thread in years, but I'm new to Flight Monitor (I think it is great BTW). My problem is that I think the Vertical Speed Limit gets measured all the way to touchdown and triggers a penalty if you get higher than -100fpm just prior to landing? The graph shows I was higher than -400fpm the entire approach, until just before touchdown and then assigns a penalty for being -382fpm (so I guess I as at -18fpm during roundout and flare)? This is in a C172 (like I said, I'm a beginner) - not sure if the settings are right for this light A/C or if I'm just not understanding something. I've been struggling with this penalty for a while, so FWIW, the above experience was on an ILS landing in APR mode. I didn't even go AP off until after crossing the threshold. Any idea what I might not be understanding?

Just in hopes of getting some type of output, I opened up a command prompt, navigated to the folder and ran aviaServer.exe through DOS. Everything worked just fine. ?!? Still not sure what the problem is trying to run via native Windows, but y'all might add that to your troubleshooting steps.

After purchasing a license for Flight Monitor, I followed the new user instructions in this forum. When I try to run aviaServer.exe, it does nothing. No screen pops up, no icons in the system tray or hidden icons, no log files generated in the folder I extracted the files to, nothing running in task manager. Tried it with MSFS running and not running. Tried running it by a standard double click. Tried running it with right click and "Run as administrator". It is like Windows won't even let it start. Nothing looks related in the Windows Event Viewer. It just does nothing. Any support, help or ideas would be appreciated!