Leaderboard

There's no copyright claim on the original script, so I've uploaded my version of it here... Original file courtesy of Manolo Velez. You'll need to open this in the SIOC utility. Open SIOC.exe Choose "Edit Script" Files -> Import TXT (and select this attached file) Save As... (it'll compile as an .ssi file) Once compiled you may need to click the "Reload" button in the man SIOC utility window. All done! (hopefully) I'm a novice when it comes to this stuff, so I'm afraid I can offer no support. (See latest version below...)

Hi @jonas_llubi, @Abt. I share you frustration with this. In fact, I spent the last 6 hours vibe coding an AI-assisted solution for a SIOC script that correctly handles the COM1/2 active/standby frequencies for both 25kHz and 8.33kHz frequencies. I also changed the logic so that it truly does work as a slave device, in that if MSFS changes the frequency itself (or another app like BATC etc does) then the updated frequency will appear in the panel, and it won't keep overriding MSFS. Limitations: It's really nasty code, made with the assistance of AI. Works with MSFS2020, but not yet tested for MSFS 2024. The SIOC script also doesn't appear to work for the Nav radios. I based it off the originally provided SIOC scripts from opencockpits (I'm not sure if I can share it openly with you, but there is no copyright notice on the original), and that original script doesn't work for Nav radios in MSFS2020 either. For me, the COM 1/2 radios were much more important. I can revisit the NAV modes later perhaps. In testing, the display does sometimes go black, and the panel appears to fail. To fix it, you have to just press the "Reload" button in the SIOC utility. I changed the logic so that it always initialises with the active COM1/2 frequencies from MSFS so that it doesn't reset anything if you have to restart multiple times in the middle of a flight. I hope it works as a stop-gap until something better comes along though! Edit: The NAV VOR and ADF radios don't work, but the ILS mode frequency and course values do work! If you're interested, let me know and I can send the script to you privately. Linguini

Urgent Fix / Update Some Things slipped through, sorry for the Inconvenience! Version 0.8.9 - Fixed Lua Scripts not properly stopped/started (and therefor not working) - Fixed InputEvents.txt (detected B-Vars) not being created - Fixed Version-Check not notifying about new Dev-Builds

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

Thanks John. Greets..Hope you are well..

No problem - permission granted (well, not even needed really!). You could also add it to the User Contribution section if you like, and/or I could include it in the FSUIPC SDK download. Let me know. Regards, John

Thanks John Followed your instructions and now works great Thanks for your time and knowhow. I started Flight Sim about 20 years ago and using the mouse didn't appeal so building switch panels became part of the hobby, but it was only with FSUIPC with yourself and Pete (hope he is keeping well) that i could get them to work. Kind Regards Brian

Thank you, I moved FSUIPC to starting first, and changed the MaxClients to 128. Now Everything is working well.

Thanks very much John, as always, just done what you explained, works perfect.

I've been struggling with this BlackSquare mixture thing for ages. Today, thanks to this thread, I've cracked it! As John said earlier, "Why not? Have you tried? It is incredibly easy and explained well:' I've used FSUIPC since forever and I maintain that it's like brain surgery, Easy when you know how. 🤣

First, to understand profiles you should read the section User profiles for all control settings, on page 22 of the FSUIPC7 User manual/guide. Profiles are enabled automatically. Having profiles in separate files is generally only used if you have many profiles and these are quite large, as it separates them into different files. You do not have to use this feature when using profiles if you don't want to, but if you have already switched to profiles-in-separate files then thats ok. The changes you made will only be saved in the profile (and in the profile-specific file) if you clicked the profile-specific checkbox (in the assignments panel) when adding the assignment, and when you have added the currently loaded aircraft to a profile (or have created a new profile for the aircraft). Check your FSUIPC7.ini - they will have been added there to the general sections if you did not specify profile-specific. Note that when you create a new profile for an aircraft, or add an aircraft to an existing profile, it is a good idea to shorten the aircraft name (listed under the [Profile.xxx] section of your FSUIPC7.ini file) to a substring that matches all variants of that aircraft. This will prevent issues with the profile not being loaded when you use a new variant. Alternatively, you can set the UseAirLocForProfiles in parameter to Yes to perform matching on the aircraft folder name instead, but if you want to use this then do it now before adding the aircraft name/title to the profile. Again, see that section in the User manual for more details. John

Ah, good to know John, I was not aware there is a little delay. Glad I could help and thanks again for all you do. Regards,

New Version for the Plugin (only): v0.8.8 - Plugin - Version Reporting: The Version now also includes its Buildtime to help differentiating between Development-Builds - Rewrite of the MSFS Connector: Almost everything is now done natively through SimConnect, the MobiFlight Module is now only required for Calculator Code! - KVAR Command Syntax Change: KVAR Commands can be either a Sequence with each KVAR having exactly one (!) required Parameter -OR- can be exactly one KVAR with 0 to 5 Parameters! - KVAR as Variable: K-Vars or SimEvents can be used as Variable. The initial Value will always be 0 and only change if the Event is ever received (and only reflects the first Index) - Support for FSUIPC Byte Arrays: The Offset Variable now Supports reading a whole Offset Range as Byte Array (Contributed by ngreatorex) - e.g. reading the whole PMDG CDU Offset Range at once. Note that they are only intended to be used in Lua Scripts! - The AVAR Variable Syntax now also supports the Prefixes 'E:' and 'L:' to read Environment and Local Variables (aka L-Vars) - Lua Scripts: the 'SimCommand' Function does not support vJoy Commands anymore. Use the new dedicated 'JoystickCommand' Function which allows sending separate down/up Commands. - Fixed: B-Var Commands not working after switching a Session - FSUIPC Connector (FSX/P3D/MSFS) now allows Commands to be sent when the Simulator is paused - MSFS Connector now allows Commands to be sent when the Simulator is paused - XP Connector now allows Commands to be sent when the Simulator is paused - Visual Overhaul of the Action Designer UI: Elements and Commands now have separate & collapsable Trees and their Appearance was overhauled - Action Designer UI: Copy & Paste now also supports a whole List of Items - i.e. Copying all Manipulators from one Element to another. - Action Designer UI: Added Increment/Decrement Buttons for some Text Fields - Gauge Element (Composite Action): A Range of Markers is now saved as such and the whole Ranged can be edited/changed at once (only for new Marker Ranges). The Syntax for a Marker Range is now '$start:end:step'. - Added an "REST-ish" API to the Plugin to get/set Variables and even send Commands (only understands GET, zero JSON, everything encoded in the URL ). This is mainly intended for Testing and other Edge-Cases, it is not intended as a Replacement for Middleware as FSUIPC or SPAD! - Added Support for X-Plane's WebAPI (12.1.4+) - disabled by default due to an open XP Bug (XPD-16752) 😕 - X-Plane Commands now have an "Command Once" Option (enabled by default) to configure if a Command is send as one Command or different active/release Commands (only relevant when WebAPI is enabled) - The Version Check now also reports if a new Development Build is available - Logging for Errors/Exceptions in Lua-Scripts is bit more detailed now - Updated Libraries / Dependencies - Fixed Event Log Error on Shutdown - Profile Manager - Improved Checking if a Profile was installed during Package Installation. All Profiles in a Package must be either installed or ignored for the Installation to continue! - Now offers to start the StreamDeck Software again if it was closed by the Profile Mapping View - New 'Create Package' View to assist with creating & updating Packages for Distribution - Installer - Rewrite of the Installer to have a shared Code-Base across all Tools - The Installer now shows the current installed Versions (on future Installs / Updates) - The Installer now offers Options for Install & Update (i.e. if FSUIPC7 is used as secondary Connector or if the vJoy-Driver should be checked) - Improved Logging for the Installer

Hi, Try this function in LUA to toggle the fuel switch: function SetFuelPump(joynum, button, downup) -- toggle FuelPump if ipc.readLvar("L:cap10") == 0 then ipc.writeLvar("L:cap10",1) ipc.writeUB( 0x3104 ,1) else ipc.writeLvar("L:cap10",0) ipc.writeUB( 0x3104 ,0) end end -- track every change of the FuelPump toggle switch event.button( <your joystick letter> , <your joystick button> , 1 , "SetFuelPump" ) I use P3Dv5 - but I assume, this won't have changed from FSX. Rgds Reinhard

There are various WASM ini parameters that control scanning for new lvars, but this should only be done in the fist few minutes after aircraft load, as that is generally when all useful lvars will be created. If any lvars are created after this period, then you will need to request a WASM reload (via lua, the provided control or the Add-ons->WASM menu->Reload WASM item) for them to be known by FSUIPC. However if the lvars are specifically created by FSUIPC, either via using lua ipc.createLvar or via offset 0x0D70), then the new lvars will automatically be pushed out to all WASM clients (including FSUIPC) and so no reload is necessary, although a short delay will still be needed before the lvar becomes available. This does not apply if the lvar is created in an ad-hoc manner via executing calculator code as you are doing (although there is nothing wrong doing it this way). Just FYI. Cheers, John

I tested 7.5.4a as provided above. Confirm that the enter key work in both 2020 and 2024

Yes, but it is a different sim, and I have no idea what the issue currently is - previously it was due to the WASM not starting, which looks to be due to the strange permissions issues you are having. Are these now solved after a re-install? Did you try renaming the Community folder as I suggested? I really cannot help you if you do not tell me what you are trying and at least answer my questions - I have no idea what you have done and what the current state is... Is the WASM now running? Is an FSUIPC_WASM.log file now generated? Do you still have the same permissions issues? I am still waiting for this information and to see a log file if available....if the WASM isn't running, then you need to determine why, and if it the permissions are still an issue.

Yes, thanks Paul.

The ! symbol is the logical not operator so !TRUE is FALSE, and !FALSE is TRUE (or, in RPN, TRUE! is FALSE, and FALSE! is TRUE. So the expression (L:someLvar, bool) ! (>L:someLvar, bool) flips/toggles the value of the lvar, i.e. changes it from TRUE to FALSE or from FALSE to TRUE. John Also explained here: https://docs.flightsimulator.com/flighting/html/Additional_Information/Reverse_Polish_Notation.htm

John, thank you. I modified the FSUIPC.ini file to add the CONNECTED (Spad.next) and READY (Vpilot) on the RUN instructions, and to adjust the DetectToConnectDelayAuto as per the link you provided (the value now set for me is 86). Now everything is working well. Thanks a lot for your help Ezio

Well then that needs to be looked into and fixed. Is the 'Exit with FS' active/checked? If so, and FSUIPC7 is not exiting cleanly when MSFS exits, can you please show the FSUIPC7.log file.

Version 3.3.16 of FSUIPCClientDLL is now on NuGet. When using FSUIPC7: Connection will now fail with FSUIPCError.FSUIPC_FS_NOT_READY if the flight sim (MSFS2020 or MSFS2024) is not running or is not ready Version 1.1.4 of the WebSocketServer is now on the website: http://fsuipcwebsockets.paulhenty.com Fixed problem of not detecting the Flight Sim version when using FSUIPC7 and the sim is still starting up. Paul

I think I solved the problem. I followed this guide: https://flightsimulator.zendesk.com/hc/en-us/articles/360015893879-Checklist-How-to-troubleshoot-crashing-CTDs-issues and did the following. #1 SYNCHRONIZE TIME SETTINGS My time was set to "Adjust automatic daylight saving time" I turned this off. #2 Then “Set time zone automatically” to ON #3 Then "Synchronize your clock" Then this section. "LAUNCH MICROSOFT FLIGHT SIMULATOR AND TRY AGAIN" I bought msfs via Microsoft store, so now I did this. #1 install the Xbox app to my computer. #2 launch Microsoft Flight Simulator from the Xbox App. I was able to create a shortcut from the Xbox app that I was using. For now, this seems to have solved my problem, and I'm happy. 😊👍. Hope it might help others too. Kind regards Per, from Denmark.

I did look at it. I didn't know "Path of Flight Simulator installation" == "InstalledPackegesPath". I meant look at the value in the offset, i.e. log its value. I will update the offset status document to make this clear. Cheers, John

Trim wheels usually work on buttons, not an axis. Some have two buttons in each direction (one for fast movements and one for slow), others just one. For those using just one button, you can use the Rotaries.lua script to convert this to use two virtual buttons instead, to enable fast/slow trim in each direction. The Bravo trim wheel has one button in each direction. I showed how to configure the Bravo for basic operation, including the trim wheel, in the following post: That should work for quite a few aircraft, but it won't work for all aircraft, especially many add-ons, as those assignments use the default FS controls. For such aircraft, you should use a profile and override these with the specific controls for that aircraft, whatever they may be - usually using presets, input events or lvars. There are also many other ways yo assign trim, and it is up to you to decide what works best for the aircraft you are using. For example, see the following post: John

I don't have a physical trim wheel so have no experience with that, but I don't see why it would not be recognized as an axis in the sims. When you turn it does FSUIPC7 recognize it as an axis similar to what I showed above?

There is no point adding that line again if its already there, and that is to dix a specific problem - to fix issues with 3rd-party programs that are expecting a value in that offset even when FSUIPC is not connected to the FS (i.e. basically for software not yet updated for MSFS2024). If you get any issues with a new release, you should always raise a new support topic. John

Sorry but can you please five your topics a more appropriate title... I will update it... 7.4.18 attached below - save and remove the .7418 extension... John FSUIPC7.exe.7418

Hi John - thanks for the update and appreciate you spending the time looking at this.

You are a freaking genius! Worked like a charm. Thanks again for your assistance and Happy Thanksgiving!

Hello John A big thanks All it’s OK Roland

*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!

Ok, thats good to know...and rather surprising! At least the installer needs to be updated to install the auto-start component. You could try manually adding the FSUIPC7 entry to the MSFS24 EXE.xml file, which should enable the auto-start. Did you try installing the FSUIPC WASM module into the MSFS2024 Community folder? Just copy from your MSFS2020 Community folder. This is needed for the functionality for presets, lvar & hvars. Well, they always have been, hence the need for presets... Anyway, I will review the MSFS2024 documentation on the available events/controls, when available. John

@Gabe_62 & @Ray Proudfoot: someone has RC4 working (more-or-less!) with MSFS, using ShowText for the menus. See the following post:

Many thanks John, I'll pass details to the other (P3D) user who was having problems.

Sorry, I should have been clearer - would you be able to put the same 'ground altitude' fix into FSUIPC6?

Ok, although i don't know why you previously said 'The Workgroups are the same'! Once that is corrected, try again. If you still have issues, try setting the ServerName (or ServerIPAddr) and the Protocol - see the WideFS User guide, and also the WideFS Technical guide for troubleshooting network issues. Ok, but you need to sort this out - I can;t help with this... John

Thanks for the reply. The 777 ini file is enabled. I worked around with FSUIPCConnection.WriteLVar("L:FOBaroKnob", -1); which seems to work. Greetings

Read that link on RPN! $Param 16384 + : adds 16384 to the axis input value ($Param) to give a value between 0 and 32768 327.68 / : divides the result by 327.68 to give a value between 0 and 100 near 0 max 100 min: I think near just converrs the result to an integer, and the rest ensures the value is between 0 and 100 (>L:BKSQ_MixtureLeverPosition_1) : sends the result to set the name lvar' value So up is one button, (as seen by FSUIPC), and down another? You can do this in 2 ways: 1. Create one preset: BKSQ_Duke_CowlFlapSwitch_L#$Param (>L:var_cowlFlapSwitch_L) Then assign the press on your up button to that preset with a parameter of 1 and also assign to it with a parameter of 0 for the release, and your down button with a parameter of 2 on press and also a parameter of 0 for release. This is what I mean by 'you give the parameter value in the assignment' 2. Create 3 distinct presets: BKSQ_Duke_CowlFlapSwitch_Up_L#1 (>L:var_cowlFlapSwitch_L) BKSQ_Duke_CowlFlapSwitch_Down_L#2 (>L:var_cowlFlapSwitch_L) BKSQ_Duke_CowlFlapSwitch_Off_L#0 (>L:var_cowlFlapSwitch_L) and assign to those in a similar manner. This is what I mean when I say 'Alternatively, you can hard-code the value into the preset and just use that'.

Just wanted to come back and report everything has been working flawlessly since the adjustments you recommended.

Yes, you don't want to use the HSI BEARING variable to sync the heading bug. The SDK shows this:

I don't have the GFC500 AP, but the below works with the Flysimware Lear35, and with the C414 which has a Garmin 605 AP. A user defined preset: SYNC_HDG_BUG_TO_CURRENT_HDG#(A:PLANE HEADING DEGREES MAGNETIC, degrees) (>K:HEADING_BUG_SET) or basically the same thing as a one line Lua script called SyncHeadingBug.lua ipc.execCalcCode(" (A:PLANE HEADING DEGREES MAGNETIC, degrees) (>K:HEADING_BUG_SET) ") Al

Don't worry about it - its not an issue. I have checked further and it is an issue with this preset defined in MobiFlight. It will be ignored. John

It appears that many users have problems with Saitek Quadrant drivers setting up the Registry incorrectly for one or more of the levers, with the result that either only 50% of the range use used or the values you get are only on (max value, 16383) or off (min value 0 or -16384). Here is the way to edit the Registry and fix this, at least until Saitek fixes their installers. (Thanks to a main forum reply by "goaround"): ==================================== Here is our registry calibration guide: One way to re-calibrate your device is to reset the raw data values that are held in Windows registry. To do this: 1. Remove the USB plug for your controller from the PC. 2. Press and hold the Windows key on your keyboard and then press the letter R. This will open the Run box. 3. Type regedit and then click ok. For Windows Vista/7/8/8.1 4. The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name. + HKEY_LOCAL_MACHINE + System + CurrentControlSet + Control + Media Properties + Private Properties + Joystick + OEM 5. Delete any folder inside the Direct Input folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID. 6. Then navigate to the DirectInput folder + HKEY_CURRENT_USER + SYSTEM + CurrentControlSet + Control + Media Properties + Private Properties + DirectInput 7. Delete any folder inside the Direct Input folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID. 8. Once deleted, close the editor, then plug the USB back into the original port. Move all the axes of the controller through their full range of movement four times. This will rebuild the data range for all axes.

I have created Voice-Interactive Checklists (using Windows Speech Recognition and Text-to-Speech facilities) for a variety of airplanes in FSX, though not by using this LUA script, but using a third party freeware: VoiceMacro. For details please visit: https://voicemacro.net/ and then proceed to my post in the VoiceMacro forums at: https://voicemacro.net/ForumVM/discussion/405/flight-simulator-co-pilot-for-cockpit-checklists-fsx-and-windows-7-x64#latest Checklists and Profiles I have already created for some common aircraft are referenced here: PMDG B747-400: https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/pmdg-747-queen-of-the-skies-ii-forum/71104-voice-interactive-checklists-for-the-b747-400-qots-ii PMDG B737-800 NGX: https://forum.pmdg.com/forum/main-forum/pmdg-737-ngx/75062-voice-interactive-checklists-for-pmdg-b737-800-ngx PMDG MD-11: https://forum.pmdg.com/forum/main-forum/pmdg-legacy-products/67885-voice-interactive-checklists-for-the-pmdg-md-11 SimCheck A300B4: https://forum.aerosoft.com/index.php?/topic/154190-voice-interactive-checklists-for-simcheck-a300b4/&tab=comments#comment-986217 Flight One ATR72-500: http://atr.flight1.net/forums/voiceinteractive-checklists-for-flight1-atr72500_topic6739.html?SID=10078-f5dc6bdea27f27a7bdf42075462963 Flight Sim Labs A320 X: https://forums.flightsimlabs.com/index.php?/topic/25728-voice-interactive-checklists-for-fslabs-a320x/ Majestic Dash 8 Q400: http://majesticsoftware.com/forums/discussion/793/voice-interactive-checklists-for-mjc8-q400 Level D B767-300: https://www.dropbox.com/sh/51bgejl2j83anjf/AACmtjJDcMbJBLvvcTL7oJMwa?dl=0 PMDG B777-200: https://forum.pmdg.com/forum/main-forum/pmdg-777-forum/71229-voice-interactive-checklists-for-pmdg-b777-200 Chakko Kovoor.

Sometimes corrupted code or data might cause strange errors, usually crashes (CTD's) immediately the Sim becomes ready for flying. The only such data which FSUIPC would instigate FSX reading and processing are the weather-related files, the wxstationlist.bin file in this folder: C:\Users\<yourusername>\AppData\Roaming\Microsoft|FSX (or the LockHeed Martin\Prepar3D equivalent) and the .wx files in your FSX (or Prepar3D) documents folder (the folder where your saved flights are). If any of those are corrupted, possibly from a previous crash of FSX, then they can cause unpredictable errors when loaded. Unfortunately FSX's SimConnect doesn't check these files before use. So, the first step is to try deleting all of those files. The .bin file will be rebuilt, and .wx files will be created for new flights, and are largely irrelevant if you use an add-on weather program. Another test would be to insert "NoWeatherAtAll=Yes" into the [General] section of the FSUIPC4.INI file. That will stop FSUIPC asking for the weather data. Of course this will stop any FSUIPC applications you may have getting weather data, but perhaps you have none.