Leaderboard

A brief note to thank your and Pete for your wonderful FSUIPC product. I've been using it for about 20 years and have found it superior for controlling my aged CH products. They are still working in spite of their aging POTS while FSUIPC irons out the bumps and jerks of the old systems. Keep up the good work! Jim Driskell

This really shouldn't happen... I have realized that I made a mistake with the 7.4.18 release...I have been testing the SDK for MSFS2024 and accidentally built the final release of 7.4.18 with the SDK from this version, instead of the version for MSFS2020. Sorry about that - I have corrected this now and have updated the installers with this correct build. Could you therefore please re-download and try again. if you get the same issue, please show me / attach your FSUIPC7.log file. Note that I have kept the version number the same, at 7.4.18, but the build date has been updated to 3rd November, so please check thar you are using this version (you may need to clear your browser cache to download this version. I have also attached this version below, but you should really re-install as the WASM has also been rebuilt. You can prevent this by setting the following ini parameter under the [General] section of your FSUIPC7.ini file: OpenOnStart=Never John FSUIPC7.exe

While people in the MSFS forum are complaining about having to spend all that time setting up their controllers, once I got MSFS2024 running, I fired up CLS2Sim (for the Brunner yoke) and FSUIPC, acknowledged the "CrashIO" dialog (haven't seen that for a while), disabled the default layouts MSFS had picked for the devices it recognized, and went flying. I'm sure I'll find problems in time, but having working controls within a minute, that was, for me, the highlight of this launch day. ❤️ FSUIPC ❤️

I haven't got time now to do a proper beta release, will do this tomorrow. but for now can you try the attached version, which is 7.5.0a. This is for both MSFS2020 and MSFS2024. I wo; release this in the Announcements sub-forum tomorrow. John FSUIPC7.exe

Thanks for the feedback! You had a better experience than me... Managed to install and ran it for the first time to download the remaining files. I then quit to install the FSUIPC WASM module, but after that I couldn't use it due, I think, to server issues. On the first restart it got stuck at 97% loading, the 2nd time at 0% loading, and then i was permanently in a log-in queue...I gave up after several hours... Seems to load ok today though. To use lvars/hvars/presets/etc, you can copy the FSUIPC WASM module (folder fsuipc-lvar-module) from your MSFS2020 Community folder to your MSFS2024 Community folder. I will be releasing a beta version of FSUIPC7 later today (hopefully!) with better compatibility with MSFS2024, and will also update and release the installer in the coming days. John

The new ATIasHold program with a Image Gallery is here: https://www.intrasystem.it/ATIas/ATIasHold.html Raimund .

The new ATIasHold program with a Image Gallery is here: https://www.intrasystem.it/ATIas/ATIasHold.html Raimund .

Hi John, Thanks for the quick reply. Your suggestions verify what I had thought so I'll give it a try. As usual, your support is par excellence. Jim Driskell

Hello John A big thanks All it’s OK Roland

That is the install location for FSUIPC5 and earlier versions. From FSUIPC6 and onwards, you must select/choose the installation location - if you don't, a default location will be used - maybe now C:\FSUIPC6 but in earlier versions it was under the P3D add-ons folder, under Documents. John

It is installed in the folder you chose when you installed - this may be under your Documents folder... To uninstall FSUIPC6, run the uninstaller, either via the windows app management panel or by running the uninstaller directly from the installation folder.

*Version-Bump* Plugin updated to Version 0.8.0 Major Plugin Overhaul - it is basically a new Plugin under the Hood! Please make an Export/Backup of your Profiles your created with PilotsDeck! The Intention is that existing Profiles just continue to run (with a bit smaller Fonts), but it is better to be safe than sorry Installer Improved UI Check & Installs all Requirements (either automatically or by starting the Setup for you) Check for the vJoy Driver now tests for the Brunner Version/Fork - which should work on both Win 10 & 11 Ability to remove the Plugin (including all Customizations!) New Profile Manager Application Enables easier Profile Installation in a few Clicks - extracts & copies the Files for you, assists with adding the Profiles to the StreamDeck, automatically removes old Profiles on Updates Own Package Format to distribute Profile Files, Images and (Plugin) Scripts as one File Allows much easier Profile Mapping to switch Profiles automatically depending on the Aircraft (or Sim) Profile Switching now only can switch back to specific Profiles when the Simulator exits These Profile Mappings will automatically be transferred to new Profiles on (Profile) Updates Plugin Property Inspector is now tabbed to allow easier Navigation Option to add a Guard (Image & Command) to an Action (Guard Images can also use Image Mappings) Added Image Mapping to more Actions Top and Bottom Image for the Korry Action can independently enabled/disabled Most Actions can now be used on an SD+ Encoder (except Simple Button and Gauge Dual) B-Var Support added - per default handled as Command-only but can also be used as a Variable Added dedicated Command Type for K-Var (allows to define a Sequence) HVAR Command supports passing a Value to the H-Var New Calculator ("C:") Variable to read the Result of Calculator/RPN Code (read only) Added Internal (X:) Variable to share Data within the Plugin Added Copy and Paste Buttons to all Actions to share single Actions between Users (or to copy between a Keypad and Encoder) Added a new "Composite Action" that gives you much Freedom to design your own Action (Display and Command wise) - most Feature Requests should be now possible with that Action (and can even replace Actions that would only be possible with Lua Scripts) This new Action is configured through its own dedicated "Action Designer" UI (opened via the Property Inspector) The Script now has its own Engine to run Lua Scripts (does not need external Engines like FSUIPC or FlyWithLua anymore) The Functions of these Lua Scripts can be directly addressed as a Variable or Command - like all other Variable/Command Types Multiple Script Types available to be run on-demand (Variable, Command) or constantly when the Session runs The Scripts can read all Variables and send all Commands the Plugin supports FSUIPC7 is now only the secondary Connector for MSFS - it is possible to use it without FSUIPC7 installed if needed! Remote X-Plane Setups are now supported Images can now be stored in Sub-Directories to better Organisation of different Packs and easier Navigation Image Drawing overhauled - Images are now drawed on top of each other (i.e. on the Dynamic Button) Added an Icon in the System Tray / Notification Area to restart the Plugin or show the Developer UI The Developer UI offers Links to some Reference Source to look up Variables or Commands and to access the Plugin's Folders easier The Developer UI has also a Monitor View to look up the current Aircraft-String/-Path or the Plugin's State, Ressources & Statistics Changed vJoy Driver Library to the Brunner Fork Plugin Configuration is now persistent between Updates and allows much more Tweaking Removed Error Image (and Error State) Sim Connection, State Handling Variable Handling completely overhauled Moved to .NET 8 (LTS) and upped minimum OS to Window 10

I experienced the exactly same problem when I had a new programmable keyboard that has rotary encoder, where inputs were very unreliable probably due to the too short interval between keydown and keyup events. After I added " UseKeyboardHook=Yes" to the ini file, FSUIPC works like a charm to capture the encoder input. Thanks!

There is a developer named Oudoum working on a solution to allow FDS (and some other) hardware to work with FSUIPC and with PMDG 737 (and 777). It is called Device Interface Manager. It is available here: https://github.com/Oudoum/DeviceInterfaceManager and there is a live Discord channel for latest discussion and feedback. https://discord.com/channels/1024920961939669052/1236087452637204571 Cheers!