John Dowson

For the altitude, try offsets 0x0818 (AUTOPILOT ALTITUDE LOCK VAR:3) and/or 0x07D4 (AUTOPILOT ALTITUDE LOCK VAR). For heading, try 0x07CC (AUTOPILOT HEADING LOCK DIR).

I can't really advise. If you are getting frequent CTDs, then yes I would start removing simconnect clients, one at a time, until it was stable,

SPEED_SLOT_INDEX_SET is a control/event, not a data value stored in an offset. The FSUIPC log entry is just logging that this event was received. There is no way to read the parameter of this event via the SDK. But really, is that what you want to do? This (undocumented) control alters the FCU authority, so what you probably want to read is where the actual authority of the FCU lies. Not sure where thats held (if at all!)- if there is a sim variable for this then I could add that to the offset area for you to read - if you let me know what it is! John

So, not using FSUIPC but SimConnect directly? You can use them as any other client event by registering them using the SimConnect_MapClientEventToSimEvent function, using IDs in the appropriate custom event range. John

First, please download the latest zip package and try again. If it still crashes, please provide more details - when does it crash? Do you see anything at all when you run the installer? John

Sure - you can create your own event file just for the events needed. Just make sure that that the events have consecutive index numbers and max of 256 events (0-255) per file. As I mentioned in a previous post, I think it would be better to create an event file for each device (e.g. G1000.evt, G3000.evt, etc), and then just add the ones for the systems you use. I guess I could also look into making the [EventFiles] ini section profile specific if different event files will be used for different profiles. And make sure that you do this before you assign to the events, or changing event files when you already have assignments will make previous assignments invalid. John

That's also out-of-date - latest version is v6.0.12 (just released), so can you please also update that. John

Just follow the instructions in the link posted above. If you have issues with Windows Defender (or any other antivirus software) blocking you, then just temporarily disable until you have it installed.

Are the parameters you are using for those controls correct? Can you check that (and let me know what header file you are using, as I asked, so I can see if I have a copy somewhere....): I guess these are the controls that are giving the problem: No, me neither - I can't see any assignments to that control in either your general assignments or the profile assignments for that aircraft. Maybe these are events that the PMDG aircraft use internally and can be ignored - if thats the case, you could use the DontLogThese ini parameter to ignore these (also available for Profiles). Could you active logging for Buttins & Keys, and produce another log file please, so I can see what buttons you are pressing to send the controls. Also, let me know which are the log entries produced when you use the mouse/UI to change the values. Also, you have controllers active in P3D: 1906 Controllers are set to ON, using RawInput within P3D Can you either disable controllers in P3D, or check that you don't have any assignments there. John

That should be straightforward by using an 'offset condition' on your button assignment (on offset 0x0366 - please see the advanced user guide for details. The basic method to do this is to make one assignment to your button for when on the ground, then add the offset condition to that assignment by manually editing your ini. Then comment out that assignment, and make your second assignment (when in air) to the same button. then edit the ini again, adding an offset condition to that assignment, and also re-enabling the assignment that you commented out earlier. You then have tow assignments for that button, one which will apply in the air and the other on the ground. This is also possible but trickier. You would have to have a lua script to have different functions on an axis. This post should help: John

Yes, those macros are using the same rectangle ID (RX27400800), so they would perform the same funtion. I'm not sure why this is if they behave differently when you click them in the UI... Sorry, but not having this add-on aircraft, I don't know what to advise if you cannot find a suitable lvar for this instead... John

In v7.0.4, FSUIPC7 is no longer started from the batch file, but from MSFS's EXE.xml file. So do as Pete suggests - set FSUIPC7.exe to run in admin mode. John

What version of FSUIPC7 are you using? There were some changes in the latest SDK w.r.t. key presses, so make sure you are using the latest version, v7.0.4 Also check key press assignments are working in FSUIPC7.

The issue is with the SimConnect SDK, but its not clear what the actual issue is. However, it seems that the more SimConnect is used, the more likely the chance f a CTD. So reducing the amount of data going though simConnect (by removing some clients), could delay the issue, but I doubt it will prevent it ompletely. John

First, if its FSUIPC assignments, could you disable Linda for the time being. Otherwise, if you are using Linda, you should use their support forums. Activate event logging and button & keys (already activated), then produce a short log where you press one of you assigned buttons. Then attach the new log, together with your FSUIPC6.ini file and I'll take a look. John

I've corrected the problem with multiple *.evt files in the attached version. v7.0.5a. Its probably a good idea to make one evt file per instrument (e.g. G1000.evt, G3000.evt, etc) and then just add the event files for the instruments you use. John FSUIPC7.exe

It is working, but with restrictions (only use one *.evt file at the moment). Those are lvars, not events, so currently not possible to use. John

I don't know, but if the SPAD.next WASM module works in the same way as the MobiFlight one, I don't see why not. You need to determine what are the string names that SPAD.next is using (your ??????). Do they publish them?

@Stinger2k3 Ok Keith, but also note my post above about using two event files. I will look into this, but for the time being its probably best just to use one event file. John

Yes. You need to install and run it initially, to enable beta updates and to download the WASM module. Once that is done and you have placed the WASM folder in the community folder, you don't need to run Mobiflight anymore. Just follow the instructions here. John

There seems to be an issue using both event files, in that if you assign to a control provided by one of the files, the event with the same index number in the second file is also triggered. I will investigate, but for the time being please just use one event file containing the events needed. John

Here are two event files that contain all of the MobiFlight events: MobiFlight-Events2.evtMobiFlight-Events1.evt For users who want to try these with the MobiFlight WASM module to control the G1000, please see: https://forums.flightsimulator.com/t/full-g1000-control-now-with-mobiflight/348509 John

I said 'There is currently no way to access lvars in FSUIPC7. '! i.e. not at the moment! Thats what I mean by currently! I'm not angry, sorry if it came across that way. Its just that, as I said, you seem to be asking me the same question that I answered for you a few days ago, and I'm not sure why or if I am misunderstanding you, or you have misunderstood my previous comment on this matter.... John

@Stinger2k3 You can use the MobiFlight events by creating an *.evt file with the events you want to use, and they will then appear in the FSUIPC assignments drop-downs. See my latest post on this here: I will look into providing some event files for all of these MobiFlight events. John

I just tried this and it works - I see the events in the dropdown list (at the beginning): I've attached the event file I have used (I've just added the first 54 events for the time being):MobiFlight-Events1.evt John