All Activity

Hi John, Thanks. My files were ok, but the quote on a few seconds did it. I have found the problem by that. My install of P3D V5 starts the wrong view, and paused. I didn't think of it, but when I unpause and just have some patience, it seems it is just working. Now I need to find the way to have a startup in the right view and not in pause. Thank you again for the great help

I’m having a read this evening. But is there anything in my logs you see is not correct? Thanks

Hi John, Thanks for making Lvar names case insensitive in Lua scripts in the recent FSUIPC7 update! Al

No point changing any parameters if FSUIPC7 is not starting - they are for tuning the connection to MSFS. For all suto-start issues, see the FAQ section (or one if the several hundred posts where this is reported, that refer to the FAQ entry) where ALL information on auto-start issues xan be found.

Hi, FSUIPC was starting up with MSFS but today it fails to load up now. i have tried different parameters The initialstalltime is set at 15 delayauto set to 45 before it was 60 FSUIPC7.log FSUIPC7.ini EXE.xml

Hello, with the implemented autopilot unit on my Bravo trottle quadrant from Honeycomb I can control the autopilot of the CRJ from Aerosoft. But unfortunatly the altitude selector doesn't work, the other selectors for NAV/HDG/SPEED/VS are working correct. From the Aerosoft forum I received the following LVAR script for the altitude selector: INCREMENT : (L:ASCRJ_FCP_ALT_SEL,·Number)·10·+·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:ASCRJ_FCP_ALT_CHANGE,·Number)·++·(>L:ASCRJ_FCP_ALT_CHANGE,·Number) DECREMENT : (L:ASCRJ_FCP_ALT_SEL,·Number)·10·-·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:ASCRJ_FCP_ALT_CHANGE,·Number)·--·(>L:ASCRJ_FCP_ALT_CHANGE,·Number) But honestly I have absolute no clue how to implement these scripts in my FSUIPC so that my altitude selector is bound with these scripts. Can someone be so friendly to help me out ? Bernhard

I have rebuilt my PC and now wondering why Button presses arent transferring through to FS2020. I have checked the FAQ topic -MSFS: key assignments (including 3rd-party Hot Keys) not working (FSUIPC7) I can see the button movement being displayed in the open Console while button is being pressed (Mobiflifght AS1000 MFD FMS Upper INC or Dec ) but not seeing this being reflected in the simulator. This issue is with a licenced copy of FSUIPC 7 to a 3rd Party device (Emuteq GNS530). Is there anyting else required. I am running 2 Arduino UNO boards at the same time using Mobilflight events. Thanks

Thank you. I don't have a problem with the Asobo A310 because the throttle works like a Boeing; there's no CLOIMB or FLEX. It's different with the A320 or A380. I currently use the FBW A380 and the iniBuilds A350. I don't use the Asobo A310. I use the FBW A380 and the ini A350. However, I have no problem controlling the throttle when I'm at home, as I have a Honeycomb Bravo. The problem is when I travel (I often travel for work) with a laptop. I don't have enough experience programming Lua scripts. Yes, you need to know the throttle position/percentage for each of these positions (CLIMB, FLEX, and TOGA). And use an offset, for example. Maybe I don't know. Thanks.

Cheers John Many thanks

hi there, I realize that I am a little late in replying to this subject but the question has raised only after I installed MSFS 2020 early this year. I do have a Hardware Ecam equipped with an interface but still i can not figure out how to connect via FSUIPC, or where to put the above commands within fsuipc lastest edition of registered FSUIPC is installed thanks in advance for kind assistance regards CJK

That should be possible, either with direct assignments or if not then via a lua script. I think the default key assignments for throttle inc/dec in MSFSare F2 and F3. Did you assign for that or were these the default assignments? Have you tried the same in the Asobo A310? I am currently on holiday until next week (see post above) and so cannot really advise further or take a look until I return. But I am not that familiar with the Airbus/A310 - does it have fixed detents for these positions? I thought the throttle in the A310 was a full range throttle, and if that is the case (i.e. no fixed detents) then I would need to know the throttle position/percentage for each of those positions (CLOIMB, FLEX and TOGA). John

See

Ok, thanks for the update. Your install log did show that it did not detect your MSFS2020 installation: The installer looks for the UserCfg.opt file for each MSFS version to determine if it is installed or not, which should be in a specific location for both Steam and MS Store versions. If this file can't be found, it won't detect that version. It is strange that the UserCfg.opt file for MSFS2020 was removed though... John

John, I have now resolved my issue - not sure how my 2020 file got corrupted but I reinstalled it and reinstalled FSUIPC7 and everything is back to normal.

Here is the log file... InstallFSUIPC7.log

translate.google.fr Hello, I hope you are all well. I would like to know if I can use the keyboard to control the throttle, especially for Airbus aircraft in the 2020 simulator. For example: Case 1: Throttle increases. When F4 is pressed, the throttle moves from IDLE to CLIMB. When F4 is pressed again, the throttle moves from CLIMB to FLEX. When F4 is pressed again, the throttle moves from FLEX to TOGA. Case 2: Throttle decreases. When F1 is pressed, the throttle moves from TOGA to FLEX. When F1 is pressed again, the throttle moves from FLEX to CLIMB. When F1 is pressed again, the throttle moves from CLIMB to IDLE. Is this scenario possible? I think this is what happened when I was using the FSLabs A320. I hope you can help me create this procedure.

Why not just update? It only takes a few minutes... Otherwise check the documentation or search this forum...I am sure this has been asked before... I think the OpenOnStart (or similar) ini parameter set to Never may prevent this, but I am not sure... I am on holiday now until next week, and can check further then. John P.S. Please use the FSUIPC7 sub-forum for all questions/issues with FSUIPC7. I have moved this post.

The GUIDs of your devices have most probably changed. To redolve this, you need to update the [JoyNames] section in your FSUIPC7.ini file. New letter entried will have been added to that section. You need to copy the GUID strings from the new entries and use those/paste them in the original letter entries, then delete the new letter entries. Do this when FSUIPC is not running. If you attach your ini file, I could do this for you. But I am now on holiday and cant do this until next week (difficult on a phone!), so please try yourself. Any issues, attach your ini and I will take a look when possible. John

*** Moved to FSUIPC7 support sub-forum *** Hi there, is there a way to somehow disable the update popup message / check, if I would like to keep an older version for a while? Thanks

Hi I have recently had to do a clean install of Windows 11 and also MSFS2020. That's all gone fine. I had saved my config file for FSUIPC which contained all the settings for binding the buttons and switches for my Hotas Throttle and stick for the Fenix A320. However, when I have transferred my saved config file back into the fresh installation of FSUIPC 7.5.3 the bindings are not being seen by FSUIPC and all the button/switch assignments are blank. Hope you can help. Regards Barry

Then MSFS2020 was not detected. Please show me / attach your InstallFSUIPC7.log file. You should ALWAYS attach this if you have installation issues.

I just installed FSUIPC7.5.3 and it removed MSFS2020 as well as MSFS2024 but only reinstalled MSFS24 (MSFS2020 did not reinstall), there was no option to choose one or both.

I don't understand why you keep messing around so much with your devices and creating such a mess. Looking at you registry, you have all these entries: and the log file is reporting duplicate ids: You need to do exactly the same as I suggested the last time this occurred - clean your registry and update the GUIDs to the new ones on your assigned JoyLetters, and remove the other entries. Sorry, but I just don't have time to look at this in any more detail at the moment (and I am on holiday from the 2nd - 7th April). I can help again sometime later next week, but I am just too busy to look at this in detail at the moment. Go over the last post and try and understand what you did to resolve it the last time. Report back after the 8th AApril if you require further assistance.

Thank you for your support! Kind Regards, André

Ok, that probably changed with the SU1 update - that offset holds the version number (major*10 + minor) as received from the FS. I will update the documentation to reflect this. Thanks for reporting. John