John Dowson

Can you first check that you are using the latest version of FSUIPC7 (7.3.21) as calibration when using Send to FS as normal axis was disabled for a time in earlier versions. If you get the same issue, please activate logging for Axes Controls and Extras (no others), and generate a short (but complete) log file - load aircraft, move throttle to max then back to min then exit FSUIPC7). Then show me/attach your FSUIPC7.log file, together with your FSUIPC7.ini file.

You keep attaching your FSUIPC4.ini file, which just tells me that you have not added: NoWeatherAtAll=Yes to the [General] section of this file and tried with this, as I keep asking you to do. Please try that. If it still crashes, please attach your FSUIPC4.log file, and also check the windows Event viewer and post details of the crash events.

There are 3 things to try: 1. When assigned with Send direct to FSUIPC calibration, did you calibrate? If not, try that, and make sure you have checked for NRZ. If using protiles, also make sure the profile box is checked in the calibration tab. 2. You can also try calibrating (inc. reversing) when using Send to FS as normal axis. 3. Some aircraft don't play well with FSUIPC calibration, mainly some complex add-ons. For such aircraft its best to not calibrate. Note that the default calibration section will apply if there is no profile-specific calibration section, so best to create a profile-specific calibration section and Reset (i.e. remove) the relevant throttle calibration. To reverse the axis, you can then use the Additional parameters to scale input axis values functionality (see p43 of the Advanced User manual), by adding ',*-1' to the axis assignment line in your FSUIPC6.ini file. John

Try using FUEL_SELECTOR_OFF (65955) instead of FUEL_SELECTOR_SET (65962) in assignment line 62. If that doesn't work, let me know and I will take a look in more detail. John

You should be able to do this in the FSUIPC7 calibration tab. Just set the lower limit at your throttle 20% position. Any issues I can check tomorrow - I am travelling today. John

I have PM'ed you a trial license. John

Well, not that patient... I am actually on holiday at the moment, a family wedding, flying back home tomorrow... In the zip file you downloaded that contains the installer, there is also an installation and registration guide. This tells you where everything is installed. The documentation is installed in a folder under your Windows Documents folder, in a sub-folder named FSUIPC6. Start with the User Guide. There is also a separate document for the specific offsets for the PMDG 777, but save this for later. Axis assignments for the PMDG 777 should be straightforward, but best to assign with 'Send to FS as normal axis' as some folks have issues when assigning with Send direct to FSUIPC calibration, although the latter is better if you don't have issues. For button/switch assignments, PMDG aircraft use their own custom controls. See the following FAQ entry on how to use these: 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 to the main support forum, where it belongs. Please see the provided documentation - I provide extensive documentation so that I do not have to continually answer such basic questions. Read the documentation and try assigning as indicated in the documentation. If you have any specific questions, you can ask in the support forums - but please search the forums first, as most questions have already been asked and answered. John

All offsets are documented in the FSUIPC Offset Status document. The ones you can use are documented as "Free for general use" in this document. The offset area starting at 66C0 is free for general use and is 64 bytes in size. it is up to you how you use this - you can divide this up as you see fit. Just remember that you need to respect byte boundaries, so if you are storing a 2-byte integer (short), then that needs to be on a 2-byte boundary (i.e. last digit must be 0,2,4,6,8,A,C or E), a 4-byte value (e.g. int) must be on a 4-byte boundary (last digit must be 0,4,8 or C), etc. There is no maximum - you can use all of the offset areas designated as free for general use. You can also use any offset area allocated to 3rd-party aircraft or utilities that you do not use, e.g. you can use the PMDG offset area starting at 0x6420 (512 bytes) if not using PMDG aircraft or the PMDG data broadcasts. What do you mean by 'generate errors'? If an lvar value can be stored in a byte (in range 0-255 or -127 - +127) then you can store in consecutive bytes. However, all lvars are, by default, 8 bytes - although you can treat/convert them to byte values (usually for Boolean 0/1) or 4-byte values (for standard integers), but would usually need 8 bytes for storing floating point values. So the size of the offset would be dependent on the data that it is holding. So, for example, to store 4 lvars that hold integers, you would use (for example) 0x66C0, 0x66C4, 0x66C8 & 0x66CC.

Just move it to the screen and size position as you like it. The position and size are saved and will be restored the next time you start or open FSUIPC. The size and position of the main FSUIPC window are stored in your FSUIPC ini file under the Window ini parameter - for example, this is mine: Window=2652,0,3446,393 Also note that for all questions on FSUIPC7 / MSFS you should use the specific sub-forum for FSUIPC7, not the main support forum (where this is posted). John

No, sorry - I do not have any experience in gauge programming - that is a completely different ball game. I am only familiar with the SimConnect Sdk, not the gauges API. John

I have PM'ed you a trial license. For PMDG issues, please use the PMDG support forums. I would be very surprised if you can adjust the height of the cabins - that is a very strange thing to do nd would change the aerodynamics of the aircraft.... License PM'ed. John

Sorry, I cannot help with the PM offsets - you need to ask Project Magenta. In FSUIPC, we just allocate 88 bytes to PM, starting at offset 0x04E0. But looking at the PM offset document (available from https://www.projectmagenta.com/downloads/), offset 0504 is 2 bytes in size (and so also covers 0505): 0504 2 AP Mode 3 (Annunciator Values) (Read Only) Autopilots Active (Bits 0 = none or any combination of 1, 2, 3 (bit 3), i.e. value 5 would be A/P 1 and 3 active) Thrust Channel (Speed modes) Vertical Cannel (ALT etc.) Horizontal Channel (HDG etc.) 0xAuto * 0x1000 + 0xThr * 0X100 + 0xVer * 0x10 + 0xHor This value is just an anunciation, i.e. it doesn't set any mode! John

@MIKE MCCARTHY Can you please stop creating further posts for this same issue. If you want help with this problem, I suggest you try what I have suggested first and report back using this thread. Any further threads/topics you create for this same issue will be deleted without response. John

On you new computer, first update to the latest combined VC++ redistributables (See Installation guide on how to do this)). After installing MSFS, run MSFS at least once before installing FSUIPC7. Once you have installed FSUIPC7 (you can skip registration), you should copy the following files across from your old computer's FSUIPC7 installation folder to the new one: FSUIPC7.key - your registration details FSUIPC7.ini - your settings: and any/all of the following files if you are using them: *.lua - any lua files you use *.mcro - any macro files that you may use *.dll - any additionallibraries/drivers that you way use Profiles\*.ini - profile files when using profiles-in-separate-files That should be all. However, when moving your controllers to the new PC, you may find that they are given new ids or GUIDs. FSUIPC7 will handle the case of new ids, if using the joyletters facility (which is enabled by default), but some manual changes to your FSUIPC7.ini may be needed if your GUIDs change. If this is the case, you can post/attach your FSUIPC7.ini and an FSUIPC7.log file from your new PC here and I will take a look and correct forr you. John

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