John Dowson

Sorry, but I have no details on the SDK for the PMDG 737-800, and the SDK for the 737-700 has not even been published yet. I cannot look into the PMDG specific offsets until PMDG have published the SDK details. Try asking on the PMDG support forum. John

It, then that indicates that something in your TBM profile is causing this issue. I have just looked at your ini again and it is a bit of a mess....you have this a the top, that is not part of any section: That needs to be removed. This is the [JoyNames] section that is used, which indicates missing devices: You still have many assignments to those missing devices, which presumably were previously your Homeycomb Alpha and Bravo. I have tried to correct these issues for you in the attached ini, so could you please try this: FSUIPC7.ini Note that there are still some axis duplications that can cause issues, so please review these: 1. Throttle an PropPitch axes assigned twice in Axes.TBM930 : 2, Throttle1 axis assigned twice in [Axes.FBW 320 NEO]: 3. Throttle2 assigned twice in [Axes.CJ4]: 4. Rudder assigned twice in [Axes.Drone]: So, download that and and review and correct those axes assignments mentioned above, if needed, and then try the updated ini. John

Btw, maybe you just need to use the trim controls rather than the primary surface controls?

The PMDG data is just supplied as received from the aircraft, and I only have the information supplied in the SDK header file. You should check that file for any further information, otherwise I suggest you redirect your question to the PMDG support forums, as it is they that supply this data. Sorry I canny be of any further assistance with this. John

No need to do this.... First, your ini shows that you have two missing controllers: There are no GUIDs associated with these, but you still have quite a few assignments those controllers - I suggest you clean-up your inii by removing them. Restore the full ini and remove the TBM from its profile, i.e. change to and see if you get the same issue. Are you using a VRInsight device?

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 your issue. I don't have the Fenix so it is difficult to advise, but first check to see if there are any controls logged when you do this in the VC - activate logging for Events, open the FSUIPC logging console window and flip the switch to see if anything is logged, and if so you can try assigning to that. If nothing is logged, you can try listing the available lvars to see if any of them look appropriate, and if so see if the value of the lvar changes when you flip the switch. If so, you can try manually changing the lvar value to see if that has the same effect, and if so then you can assign to use that lvar either by adding to an FSUIPC offset, using a macro or defining a preset. John

You should really have tried with the trial license first to see if FSUIPC7 is suitable for your needs.... There are various things you can try to achieve this. The first, an easiest, would be to assign your key presses to the *_UP, *_DOWN, *_LEFT, *_RIGHT controls, but this would probably just duplicate the movement that you see when assigning in MSFS. For more refined control, you would need to write a lua script which would wait for your key press (using event.key) and in the handling function read the offset with the current value, most probably offset 0x0BBA for rudder, then adjust thus value with the required change and then write the value back to the same offset. I am a bit busy at the moment but when I get time I can look inot providing you with a lua script that does this for the rudder to get you started. What keys are you planning to use? Noe that if you have keys assigned in FSUIPC, you should remove any assignments to those keys in MSFS. John

It is no secret...just perform the operations in the VC with event logging activated, as you did before, and you should see the control and parameter logged, then use those. I cannot help you with this if you do not show me your FSUIPC7.log and FSUIPC7.ini files, the former with logging for Buttons & Keys as well as Events activated. You need the FSUIPC WASM module installed and the WAPI enabled, but that should already be the case, but your log files would tell me.... John

Yes, thats fine. If you are using the same controllers, you can also copy across your FSUIPC7.ini file, although the GUIDs will probably change and your ini will need manually updating to handle this. If you want to do this, you can show me your FSUIPC7.ini and FSUIPC7.log files from your new computer and I can take a look and adjust for you. By the way, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post to the correct support forum, but please take care to post in the correct place, John

If you cannot change the offset that the IVAO client is using to read (0x0574) the altitude, you can spoof the offset to the value of this new offset (0x0590) using FSUIPC's spoofing facility at offset 0024.. To do this, you need an auto-running lua script. I have attached a similar spoofing lua script that some folks use for the FBW A320 parking break - you should be able to adapt this to your needs. You need to adapt to read the offset value (as opposed to the lvar value that he script currently uses) of the new offset, update the spoofOffset and adjust the type/size of the value being spoofed from 1UW to 1UD John A320ParkBrake.lua

This is very strange. I cannot understand how anything can stop/prevent mouse interaction in all other programs except MSFS Also FSUIPC7 does nothing with the mouse at all - except receive input (button presses/releases) from it, of course. As a final test, could you maybe rename your FSUIPC7.ini so that a new empty/default onw is created and try again to see if you get the same issue. If not, show me your (renamed) FSUIPC7.ini. John

Just tried the TBM930 and its working ok here (except that I can't seem to get the Throttle axis working....). I also trued with the TBM improvement mod - FSUIPC7 still functioning normally by that mod is broken (half of the aircraft has disappeared!). Try with Linda disabled (just temporarily rename your ipcReady.lua) - if FSUIPC7 functions normally then it will be an issue with Linda and should be reported to the Linda support forum. John

I am asking you NOT to create a new log - just don't use the 'New Log' menu entry, and just one log file will be created. The 'New Log' button closes the existing log file and starts a new one. As it says in the User guide: I have just release 7.3.10 - please update., This fixes an issue where presets assigned in the general Buttons and Axes sections were lost, as the preset file was loaded after these assignments, resulting in them not being found. John

FYI, 7.3.10 has also now been released, This contains a minor update that prevents general button/axes assignments to presets being lost. John

FYI, 7.3.10 has also now been released that should resolve this issue. John

FYI, 7.3.10 has also now been released, This contains a minor update that prevents general button/axes assignments to presets being lost, which looks like the issue you were experiencing. Please update to this version. John

FYI, 7.3.10 has also now been released, This contains a minor update that prevents general button/axes assignments to presets being lost. John

7.3.10 has now been released. John

Please try the attached - I am going to release this shortly. John FSUIPC7.exe

Please try the attached - I am going to release this shortly. John FSUIPC7.exe

It looks like the assignments are now loading before the presets have been loaded, resulting in presets to the general buttons being lost. I will fix this asap.... Sorry about this - I will post an update soon... John

It looks like the assignments are now loading before the presets have been loaded, resulting in presets to the general buttons being lost. I will fix this asap.... Sorry about this - I will post an update soon... John

The log file you posted is useless to me as it is a continuation log - I always need to see a full log file, not a continuation one, so please never use the New Log function when posting logs for support issues. The latest and only supported version is 7.3.9, so please update and try again. You should always check that you are using the latest version before requesting support, as only the latest version (+ any betas) is ever supported. John

ok, thanks for the update. That is interesting, not heard of that. I have always used Everything for searching. Cheers, John

If you have set FSUIPC7 to be ran as Administrator, then MSFS must also be ran as administrator. I am not sure that setting the MSFS desktop icon to be ran as administrator will do this...if using Steam, for example, it is the Steam app that starts MSFS and the Steam app must be set to be ran as administrator. If using an MS Store install, you will need to find out how to run MSFS as admin with that installation type. If you are running both MSFS and FSUIPC7 as admin then something else must be going on. Please see the following FAQ entry for MSFS auto-start issues: You could first try running both MSFS and FSUIPC7 without admin privileges, to check that auto-start us configured correctly, If not, that post should help you correct that. Once it is working with non-admin privileges, try setting both FSUIPC7 and MSFS to both run as admin and try again. If you have an MS Store version of MSFS. if you can let me know how you start MSFS as admin then I can also add these details to that FAQ entry. John