Fair enough - it might be worth adding a check to FSUIPC where it creates the log file but then verifies it actually exists, and if it doesn’t, pop up a little “hey I couldn’t create the log file, tell me where to write it to instead:” with a folder browse button? (and then maybe save that folder location in a single . ini file stored in local AppData. That way if it’s there, easy to load in, if it’s not, no need to change where FSUIPC writes logs to). That way, no one who’s already using FSUIPC is impacted, but folks who practice security a little more stringently than others won’t have to compromise on application security.
Because the reason it lives in Program Files on my system, even though it doesn’t have an installer, is for security reasons: having it live in Program Files (a one time admin copy) secures it against modifications by any other application, virus, worm, or what have you. Windows will flat out disallow any modifications unless those are run with admin rights. So it’s generally just good practice to put any executable in the Program Files and Program Files (x86) folders, even if they’re just a standalone .exe distributed as an archive.
Ah, found an Asobo plane that has negative flaps, too: the Pipistrel Virus SW 121 (should be included in deluxe/premium) has flaps angle -5 degrees at flaps notch 0, 0 degrees at notch 1, 9 degrees at notch 2, and 20 degrees at notch 3. It looks like SimConnect reports the correct values for those using TRAILING EDGE FLAPS LEFT ANGLE, so there’s something funny going on with the Maule M-7 where MSFS knows the angle is -7, correctly displays it in the in-game HUD, but somehow SimConnect doesn’t have the same information that the game has for this specific plane.
Ok, that is interesting. Sounds like an issue in the Maule M-7 then, which should be reported to the aircraft developers. Not sure how MSFS can display the correct negative angle in the HUD display though, it must be using something else internally rather than those simvars…
As for the log file location, it is a lot more complicated than that as there are various other files that I read and write and runtime to the FSUIPC7 installation folder and sub-folders - the FSUIPC7.ini file, profile-specific ini files, joyscan.csv files, lua /log files, etc., and further log (and .ini) files can be created by other dlls that are loaded and used by FSUIPC (e.g. PFC drivers). I am not going to change this after so many years. You can install and use under Program Files (or other windows-protected folders) if you like, but you would need to run with Admin privileges, and any FSUIPC client applications would also need to be ran at the same privilege level.
John
Hello @RoscoHead and my apologies for missing your question.
When no FLAPS_LEVEL section is defined in cockpit.cfg, it will fall back to the AIRCRAFT FLAPS HANDLE ANGLE gamevar which contains what’s configured in flight_model.cfg flaps-position parameter.
Regards,
Sylvain
That section exists, though.
file:
MSFS2020\Official\Steam\pilotexperiencesim-maule-m7235\SimObjects\Airplanes\pesim-maule-m7235\cockpit.cfg
flaps levels content:
[FLAPS_LEVELS]
slats_level_1 =0
flaps_level_1 =-7
slats_level_2 =0
flaps_level_2 =0
slats_level_3 =0
flaps_level_3 =24
slats_level_full = 0
flaps_level_full = 0
slats_level_4=0
slats_level_5=0
slats_level_6=0
slats_level_7=0
slats_level_8=0
slats_level_9=0
slats_level_10=0
flaps_level_4=40
flaps_level_5=48
flaps_level_6=0
flaps_level_7=0
flaps_level_8=0
flaps_level_9=0
flaps_level_10=0