Search the Community

I've been using FSUIPC forever, and currently have v.4 for my FSX/SE. With previous versions of MSFS, all I had to do was go into the FS set-up and turn off the control binding, then go to FSUIPC and re-assign all of it to my individual aircraft. However, with FS2020, each controller has its own binding, so in order to turn off the MSFS bindings, I have to assign null (empty) bindings for each controller before setting them up in v.7. Which I've done. My question now, to Pete & John and anyone else who has been successful in setting up FSUIPC 7 with FS2020, what is the suggested/best way to reconcile FSUIPC with FS2020? Do I just turn off the axes on FS, turn everything off and use FSUIPC, or something in between? I remember particular problems with FSUIPC, FSX and the PMDG planes, specifically with the throttles. So what do I need to know to use FSUIPC 7 efficiently with FS2020? I did try turning off all controllers in FS and tried using the FSUIPC BETA to control everything, and it didn't work too well. TIA, -= Gary =-

Greetings Pete, I am using registered version of FSUIPC and use the auto-save feature which is very useful.However, i find that fsx will freeze for about 5-7 sec after every 300sec (as set) to save the files. I realize that aerosoft airbus fsx being a complex add-on, Fsx will need time to process it to save the airbus state as well as fsx situation which is fine. I don't see the freezes when using FSX default aircrafts. I have also excluded fsx, its addon and related folders from windows defender in win10. I scanned through many post related to this in various forums. Alas!!! i was unable to find a working solution. What happens is that ; Like yesterday and many other times ; when i was landing i was less that 10FT RA and fsx froze. Concentrating so much on the sim, I didn't realize fsx had frozen. . As lot of control inputs were already given when FSX had frozen; FSX had to process that. After the 7th sec FSX resumed, The aircraft hit very hard on ground (315 FPM), which actually spoils all the fun of landing an aircraft. Changing or increasing the time interval for auto save won't help because if the time period ends at the critical phases, Fsx will definitely freeze. What I suggest is if you can introduce a new feature which can carry out below functions:- 1.If we can disable auto-save feature (as per user choice) automatically when certain conditions are met like:- (i can remember only of this) a. landing gear extended (when G button is pressed). b. when below a certain altitude (like disable autosave when below XXXXFT) or between certain altitudes. c. at a press of a key or joystick button. It is upto the user prerogative whether to use such a feature or not. Because, if fsx freezes permanently or crashes when the auto-save is disabled. Then, no way of restoring FSX and other complex add-ons to the desired state. I got this idea from weather addon opusFsi which has a nice feature to stop weather update when certain conditions are met like on approach, on certain distance from arrival airport etc. Hope you can shed some light into this. Please advise if more info needed.

Hello, I bought the registered version and it registers fine at the provided dialog window. In fact, seems to even run fine... but then there is this repeating beeping, like a nag, every couple secs, and I get a dialog that pops up and says the license is invalid. I think it's either FSUIPC, a Flight-Sim conversion to FSX-SE glitch, perhaps steam - but I'd suspect this is one area they would have handled decently; perhaps a pay plane but this just happens with any heli, stock or otherwise...but I am speculating surely. So I have no idea what is going on - but your program might be it - might not - you'd know best :) I have no idea if this is your program or not. I am not running to much. FSX, FSUIPC, HTR and the Oculus Rift DK2 (Virtual Reality) utility so I can fly in true 3d... which is free and doesn't require a license. Thank You. Jegas