John Dowson

I have released the next version (which contains a fix for this bug) as a beta if you would like to try it, available here: John

I have released a beta version of the next release with the PMDG 777 offsets enabled if you could try it:

I have released a beta version of the next release with the PMDG 777 offsets enabled if you could try it:

Offsets are just a 65535 byte memory are in FSUIPC, starting from 0000 and going to FFFF. No. An offset address is just a memory area. Offset address can be populated from reading simvars or lvars, cna be used internally by FSUIPC or can be used to hold client data from specific aircraft (only PMDG airliners supported for this). The client data held in offsets is based upon the the data structures provided by PMDG, but this data is split into different offset areas. See the specific PMDG offset data documents for how to access PMDG data via offsets. Note that in the current release of FSUIPC7, only the offsets for the PMDG 737 are enabled. I have enabled the offsets for the 777 now and will be releasing this shortly (i.e. in the next few days) , as 7.4.14. Take a look at the FSUIPC7 Offset status document, and also the specific offset documents for PMDG aircraft. I have attached the one for the PMDG 777 below. Not sure what this means. You can read any offset at any time, but whether that offset holds any relevant data depends on the offset and possibly the aircraft loaded. The PMDG offsets will not hold any relevant data for the 777 until I have enabled this (the next release), but they will hold data for the 737, if enabled both n FSUIPC7 and in the aircraft itself. John

There is a known issue with the WASM that has been identified and fixed, although this fix has not yet been released (officially) - see the following post where the fix is available: I will be releasing this fix officially in a couple of days, with the next version of FSUIPC7 (7.4.14). This just sounds like windows is not giving much time to FSUIPC7. This can happen if you have a lot of logging enabled and are logging to a HDD (and not an SDD). You can send logs if this happens, but I doubt they will show anything. John

I am currently looking into adding/re-activating the PMDG 777 specific offsets. They will be available in the next release of FSUIPC7, which I am currently planning on releasing towards the end of the week. John

This is because you have installed the FSUIPC7 auto-start component. If you do not want FSUIPC7 to start with MSFS, re-install and de-select the auto-start component (there are two distinct methods of using auto-start - make sure both are unchecked). 'Open on Start' means to open the FSUIPC7 main window on start-up. Usually it starts iconised to your system tray. Yes, you come across as very impolite. I provide a lot of documentation with my software. You should at least try looking at that before posting. Try starting with the Installation and Registration guide. You should also actually look at what you are installing - it should be obvious that you are installing a component called 'Auto-Start'. John

Thanks for the update. Not sure why an earlier version would work. You do have your DetectToConnectDelayAuto ini parameter set quite high, which means that it will take a short while (2mins) between when FSUIPC7 is started and when it will connect to the sim (and thus be ready for use). It will reduce gradually over time (auto-tuning wiil do this), but maybe better to set this to a lower value (in your FSUIPC7.ini file) and let FSUIPC7 tune itself from there, e.g. set DetectToConnectDelayAuto=60 John

The problem with this is that the flight would already have been loaded/started by the time the lua is started, so this function will only be called if/when a new flight is loaded. Lua scripts are not started until AFTER the aircraft (and also initial flight data) is loaded and once lvar/hvars have been received,

There is no 'key assignment package'. If you are referring to the MF preset list, I only update this on each release. If there are some new MF presets that you wish to use not available in the preset file (events.txt) installed with FSUIPC, such as the PMDG 777 presets, then you should download and install this yourself from the MobiFlight HubHob sight (https://hubhop.mobiflight.com/presets/). Attached is the latest file, but please learn how to update this yourself. John events.txt

This is almost certainly due to the fact that you have not selected No repeats! on the assignment, so multiple toggle controls will be being sent. If you activate logging for Buttons & Keys and look at your log then you can confirm this. It is always better to assign toggle controls with no repeats enabled.

That is strange then. Maybe try logging the rudder position, as well as steering well tiller position, to check that these are not having an effect. You can set the centre position wherever you like, but I don't think this will help, as no rudder is sent when at the central position, and if it was setting a little right rudder when central, then this would also effect the rudder when in flight, no? You could maybe have a small lua script that will apply a little right rudder when rudder central and you are taxiing. I haven't noticed this, but I don't fly those aircraft except for testing purposes. I can take a look in to PMDG and ATR later to see if I notice any drift.

Sure - license sent.

Not sure what you mean by 'without FSUIPC7' - without FSUIPC7, how can you read the offsets? Anyway, the list of data available for the PMDG 777 is detailed in the header file - PMDG_777X_SDK.h in the Documentation\SDK folder of your PMDG 777 Community installation folder. I am currently working on adding the PMDG 777 specific offsets to FSUIPC7, and I will release this next week. I have attached the document for the 777 but this is still a work in progress so may be updated again before release. Can you also post in the FSUIPC7 / MSFS sub-forum for all questions related to FSUIPC7 / MSFS. John Offset Mapping for PMDG 777.pdf

Ok...I have PM'ed you a trial license, but this will be the last one. John

Ok. But as you are using an unregistered version of FSUIPC7, FSUIPC7 is not doing anything with your hardware at all and so your issue is nothing to do with FSUIPC7 anyway. John

Can you show me/attach your FSUIPC7.ini and FSUIPC7.log files please - attach them once you experience the issue and have exited FSUIPC7.

You already tried the trial license in October 2023. Why do you want to trial again?

No, not at the moment. I will add a File -> Reload Presets menu option in the next release. John

Ah...that is interesting... Do you have this more or less working then? The main problem with using RC with MSFS, or so I thought, was the display of messages and menus which isn't working correctly due to the broken SimConnect_Tect functionality in MSFS. I would be interested to know if this is working, or how you got this working.... Which offsets is RC reading for the METAR information? Offset 0x0EC6 is incorrectly flagged as not available in MSFS, but I have checked the code and that offset should be populated. However, the weather offsets starting at 0xC000 are disabled in MSFS, so I am not sure spoofing a read to that area will work. Id RC reading the (sea level) pressure at offset 0xC028 then? And doesn't it require the altimeter pressure, not the sea level pressure?

The InstallFSUIPC7.log file will be in your FSUIPC7 installation folder, the same folder as the files you attached. I need to see this file for installation issues. Do you want to use FSUIPC7, or just install the FSUIPC7 WASM module for use with SLC? Your installation log may also shed light on this, but for all start-up issues, see But if you just need the WASM, you don't need FSUIPC7 running anyway. John

I have the PMDG 777 now so it will be easier for me to advise on how to assign for this aircraft now. I have also noticed that some presets (130) have now been added to HubHop for the PMDG 737 now, so those not comfortable using custom controls can check to see if a preset is available. I have attached the latest events.txt file (from MobiFlight) below - use this to replace the one in your FSUIPC7 installation folder, and restart FSUIPC7 if running. I will now look into adding / enabling the additional PMDG 777 specific FSUIPC offsets. John events.txt

Please read this thread.... the 737 presets will not work with the 777 as the custom control numbers, used by the presets, will have changed. You can assign to the custom control numbers (for the 777) directly - I posted a link to show you how to do this. However, I now see some presets for the 777 have been added to HubHop, inclusing ones for the fuel cut-off: PMDG 777 FUEL CUT OFF ENGINE 1 & PMDG 777 FUEL CUT OFF ENGINE 2. These are available in the events.txt file attached below - save this to your FSUIPC7 installation folder, overwriting the one there, and restart FSUIPC7. John events.txt

Of course - you have to send it multiple times (i.e. on repeat) if you want multiple increments. Alternatively, you could try sending that control with a left mouse click on button press, and a left mouse release on button release, using the rotor brake control method. Well, if you no how to use custom controls you don't need the link, but here it is again, as well as the older one that sends mouse operations via the Rotor Brake control: Thanks, but that has a copyright and you should not share it, especially on public platforms. John

Note also that the PMDG presets use the Rotor Brake method for custom controls, which emulate mouse clicks. Using the custom controls directly has more benefits, as you can send an actual parameter (when needed) rather than just a mouse click. This is explained (I think) in that post I referenced. There is also a similar post (deprecated) that shows you how to use the custom controls via the Rotor Brake control, which is what a lot of the PMDG presets use. John