John Dowson

in FSUIPC6 and earlier, you need a simple lua script to write the lvar value to an offset when the lvar value changes, using the event.lvar function. See the following post where i explained in more detail on how to do this: You can also enable writing to the offset to update the lvar if you like, by using the event.offset function. In FSUIPC7, a mechanism is provided to add lvars to offsets for both reading and writing by using the FSUIPC7.ini file. This is explained in the Advanced User guide. John

I am not sure where the problem is, so do not know where the fix will be coming from. There is no fix for this in fsuipc4, which is closed for development and has been for several years. I use FSX-SE on Windows 11 without issues, although i don't actually use it that often - only to investigate user support issues. I have not seen any CTDs at start-up. John

Sorry but I do not understand your last post at all. Why are you looking at the event viewer? And I know nothing about the fenixbootstrapper - suggest you talk to fenix if you have issues with that. As I said in my previous post, if you want help auto-starting FSUIPC7, show me your EXE.xml and your InstallFSUIPC7.log file.

Writing to a non-existent lvar should create the lvar, but I am not 100% sure on this (may be for MSFS2020 only), as the documentation does say: If the variable is not currently available, nothing happens. To create an lvar in lua, you should use the ipc.createLvar function: John

This is from the InstallFSUIPC7.log file and indicates that your EXE.xml file is corrupt. I don't understand this - where did you find those errors if not in the InstallFSUIPC7.log file? I don't understand this - what has the UserCfg.opt file got to do with this? Yes, that could have corrupted your EXE.xml. Everything you need to know to correct this issue is in the FAQ entry I referenced in my original comment on this issue. If you are having difficulties with this, please post/attach your EXE.xml and I can take a look. Also attach your InstallFSUIPC7.log file. John

The msfs.bat only displays a splash screen and starts MSFS. It does nothing else. You can, howver, modify this file to also start fsuipc7 if having auto-start issues. Please see the following FAQ entry on FSUIPC7 auto-start issues: John

It is just a txt file, it does not execute anything. It just associates a string/preset name to a calculator code string. This file is provided by MobiFlight and is available from https://hubhop.mobiflight.com/presets/. Using the Add-ons->WASM->Execute Calc. Code menu option, you would just paste the calculator code to execute it. This method is just used to test if a calc code string is working/has the desired affect. To execute calculator code from a program, you can use the WAPI (WASM API) interface that I provide. This is a C/C++ API, but a C# wrapper is also provided. And, as I previously said, you can also use Paul Henty's client dll for C#, which is the preferred option fir C# developers. To write to offsets using C#, you would need to use the FSUIPC SDK. However, as this is for C/C++, you would be better off using Paul Henty's dll for .Net if using c#. I suggest you look into using this - http://fsuipc.paulhenty.com/#home They are not presets, they are 3rd party custom event files. You use these by copying/moving them to the main FSUIPC7 installation folder, where FSUIPC7 will find and load them when started, and make these custom events available for assignment. Custom events are a distinct and older method than presets. You don't need these if using presets, which is the preferred method these days. See the section Add-on Custom Events on page 38 of the Advanced User guide for further details, but I wouldn't bother with these and just use presets, which can also trigger custom events without the need for using event files. Sorry, but I can't help you with using C# or Paul's dll. Please use Paul's sub-forum for any questions on using his dll. Cheers, John

Do you mean the power drops (i.e. in HUD display)? Do the throttles stay in the same position? Have you checked/disabled any MSFS assistance options? In the other post on this topic, you also said: Did you ask them about this? I do not see the same problem. I am away from my flight set-up for the next few days, back next Wednesday so I cannot check again until then. Can you set logging for Axes Controls, and reproduce your issue - load the C510 and advance to full throttle and leave running until you see the "engines both drop to ~30%" and then exit FSUIPC7, compress/zip your FSUIPC7.log file and show me/attach that file together with your FSUIPC7.ini file.

You are asking the same question in multiple topics. i am closing/locking this one now - please use the other topic you have opened:

If that offset is not populated for the 737, then you should report to PMDG. if using the 747, try this one: 6C2B 1 BYTE SIGNS_SeatBeltsSelector Can you not do this in your installer? You really need this enabled if you want to use the extra data provided by the PMDG SDKs. Ok, thanks. Regards, John

You still haven't said which aircraft you are using. Check the PMDG SDK document for the aircraft you are using - looking at the 737 document, there is this offset: 649F 1 BYTE COMM_FastenBeltsSelector 0: OFF 1: AUTO 2: ON So maybe try that one. Note that you must have enabled data broadcasts in the PMDG aircraft to have the PMDG-specific offsets populated - this is explained in the document itself. John

It is not complicated at all. You just check Select for Preset and then select the preset you want to use from the down list. Exactly the same as assigning to an FS control, except for that you need to check Select for FS control instead.

No, sorry - try avsim

As I said, please look at the MF presets. For example, for the landing lights alone, there are 28 presets available:

No - please read my previous comment...

No, as the dll is not loaded by WideFS/WideClient. I am waiting for a license for ASP6 - I will take a look when I have a license, and when I am back from my holidays (end of next week). John

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct forum for support. I have moved your post for you. It is not a problem caused by FSUIPC. Changes to ground friction tables was possible in FSUIPC4/FSX using a hack but this is not possible om FSUIPC5/6 with P3D4-6. See the following thread for further details: John

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct forum for support. I have moved your post for you this time. Your FSUIPC6.ini file will be located under your FSUIPC6 installation folder, here: C:\P3Dv5 Addons\FSUIPC6.ini If you cannot see this file then you have windows explorer set to hide the extensions of known file types. See the addendum in the Installing and Registering FSUIPC6 document for details: Addendum: Identifying Files in Windows Explorer

You should have tried the trial license first, available from a post at the top of this forum. PMDG aircraft are mainly controlled by using presets. See the following website for a list of available presets, where you can search for a preset for specific aircraft and function: https://hubhop.mobiflight.com/presets/. All presets are available for assignment in FSUIPC7 by selecting the Select for preset checkbox. There are also additional offsets for the PMDG 737 that you can use but you must first enable the SDK data broadcasts in the aircraft. See the provided document Offset Mapping for PMDG 737-700.pdf. Your question is also very general - If you have a specific question on a switch assignment I can try to answer that.

Which PMDG aircraft? Check the SDK documents - for the 737 there is the following SDK variable at offset 0x6477 (and at offset 0x643D in the 777): ELEC_IFEPassSeatSw And the variable SIGNS_SeatBeltsSelector at offset 0x6C2B in the 747. If it isn't any of those, you are probably better off asking about this in the PMDG support forums. John

I don't know why you are repeatedly posting the same file. And I have already told you what to try, several times now: It really isn't worth you posting anyting until you have read my comments and tried my suggestions. You need to eliminate the possibility of aa corrupt weather file before anythung else. John

Well, the larger the value, the less likely you are to have the issue (remember this setting was previously ignored and defaulted to a value of 25, regardless of what it was set to). And a negative number means that only a message is logged and it does not try to re-open the connection, so the initial connection attempt will be given all the time it needs to generate a response. If you set InitialStallTime=25 then you should get similar behavior to before, except that I have added additional code to retry the connection even if/when the simconnect open call returns an error. Looking at your log, it is taking around 65seconds for the initial open call to return a result. I would therefore recommend using a setting of InitialStallTime=70 which should give plenty of time for it to complete. John

The shift key does work as a key modifier. Why do you think it doesn't? Please show me/attach your FSUIPC ini and log files if you continue to have issues. John

This is correct - the control is independent of what triggers it (a button or keypress). Can you please activate logging for Buttons & Keys and Events. If you then open the logging console (check the Send to console window checkbox) you should then be able to see what is happening both when you press an assigned button or an assigned key. If you cannot see what is happening, you can post/attach your FSUIPC6.log and FSUIPC6.ini files here and I can take a look, John

FSUIPC7 is not compatible with FSX - you need FSUIPC4. FSUIPC7 is for MSFS2020 only. John