John Dowson

What have you tried? I don't see anything assigned to control the parking brake in the ini file you posted... First, I suggest that you update the aircraft name in your profile to catch more liveries - change to The easiest way to control the parking brake on the PMDG 737 is to use the available presets (see https://hubhop.mobiflight.com/presets/) : In FSUIPC7, select the 'Select for Preset' checkbox and you can assign to the inputs PMDG_B737-7_PARKING_BRAKE_ON and PMDG_B737-7_PARKING_BRAKE_OFF. For further details on how to use the MobiFlight presets, please see the WASM section in the Advanced User guide. John PMDG_NG3_SDK.h

Only the email address you used for registration - you can remove that if you like (near the top). Yes, if the aircraft name with that livery is not a substring match to the aircraft names listed under the [Profile.xxx] (where xxx is the profile name) section of your FSUIPC7.ini. You can add each aircraft name with livery as you use them, but better to edit the aircraft names in the profile section so that the string matches the aircraft regardless if the livery used, Please see the User manual section on profiles. John

These are functions provided by FSUIPC - just look at the Logging tab and it should be obvious...otherwise consult the User guide. Again, see the Logging tab, and yes the log messages are displayed in real-time - when you click a button/switch in the VC, and event is generated and FSUIPC picks this up and logs it, assuming logging is activated for that type of event. Correct - it is far easier to have the logging console open, which just shows the contents of the FSUIPC.log file, and note the events in real-time rather than looking at the log in an editor later. It really isn't complicated and certainly not worth making a video of this. Just open FSUIPC, selecting the logging tab and check the options you require (i,e, Events (non-axis controls) and Send to console window). Please take a look at this and consult the FSUIPC4 User Guide. I don't understand why you are not doing this before posting these questions.... John

You posted a continuation log - please always post a full log file for support, i.e. never use the New Log function if generating a log for support purposes. I really don't understand how the rudder and aileron trim can be seen in the calibration tab but not in the assignments tab. It is strange also that SPAD,next recognises the trim axes but not P3D or FSUIPC. Are the other axes on this device (DTA Rotary Encoder) recognised, i.e. PropPitch and Throttle: ? Are you using any specific drivers or software with this device, or are you using the default windows drivers? Can you download and try the HiDScanner program (available from the Download Links -> Useful Additional Programs section of this forum), run that and see if that recognises the rotaries you have assigned to the trim controls. Also try connecting it to a different USB hub, to see if that helps - and check you have power management disabled on all your hubs - windows has a tendency to reset this on updates. Finally, you could try disconnecting the device, uninstalling any specific drivers (if installed), cleaning the registry entries for the device, reboot and then reconnect to see if that helps. Something must have changed to cause this, and I suspect either a registry issue or maybe a hardware fault somewhere... John

Yes, they should. Where have you installed FSUIPC? If you have installed under your windows Documents folder, or under any other windows-protected folder such as Profram Files, then please re-install into a different nin-windows protected folder and try again - you can copy across your FSUIPC7.ini and FSUIPC7.key files (together with any *.lua, *.mcro or *.dll fies that you may use) to the new location. Otherwise, please show me your FSUIPC7.ini and FSUIPC7.log files. Yes, you can....the calibration panel should show the calibration being used, whether it be profile-specific or not. No. As I said, they are independent. FSUIPC knows nothing about your MSFS assignments/calibration, and MSFS knows nothing about your FSUIPC assignments/calibration. You should only assign/calibrate any given axis in one place - either MSFS or FSUIPC, not both. No, You can only calibrate in FSUIPC if assigned in FSUIPC with 'Send Direct to FSUIPC Calibration) (since SU10), and if you have assigned in FSUIPC then the axis should not be assigned in MSFS. Also, as you are using FSUIPC7, this post should be in the FSUIPC7 support sub-forum. I will move it to the correct location. John

Does it run ok when you click yes/Si? If you continue to get that message each time you start FSX, please see John

I think LINDA is your easiest option, but if you don't want to use LINDA then you will have to write your own lua scripts to handle your VRInsight MCP. As I don't have this device, I cannot help you with this. I have already referenced some posts by other users who have written lua scripts for this device - try using them as a starting point and updating the controls used to the ones needed for the aircraft you are using. If you need help with a specific control, I can assist with that. John

First, you posted in the Announcements sub-forum where it explicitly states NOT for support requests. I have moved your post to the correct forum for FSUIPC7 support requests. But events are for controlling not reading, and the PMDG offsets are read-only. If you are trying to read those offsets and they do not contain the information as advertised, then there is not much that can be done at the moment as the PMDG SDK has still not been published. You can check what the offsets are holding by using FSUIPC's offset logging functionality, available from Log->Offsets.... Try logging those offsets (as type AsciiZ) - this will yell you if those offsets are holding the correct data or not. If so, then your issue will be with MobiFlight and/or your configuration. If not. there is not much that can be done until PMDG publish the SDK. I will also check those offsets in the next few days and get back to you. John

Many aircraft, especially add-ons, can continually emit such events (different for each aircraft) - these are just noise. You can ignore these by using the DontLogThese ini parameter, best used in your [Profile.xxx] section (where xxx is the name of the profile). See the Advanced User guide for details. Also check that you are using an empty profile in MSFS for you controllers in MSFS. You can mix-and-match assignments between MSFS and FSUIPC if you wish, but best to start with an empty profile in MSFS if assigning in FSUIPC.

Thanks. I'll take a look at the log in detail when I get time to see if I can do anything about the phantom xbox controller.

As I have said several times, I do not support LINDA. Use the LINDA support forum: https://www.avsim.com/forums/forum/429-linda-support/ John

You should not need to do that unless you are running MSFS with admin privileges. And if not running as admin implies your FSUIPC7.ini file (where your profiles are saved) cannot be updated then this usually means that you have installed in a windows-protected folder, such as under Documents. You should not install FSUIPC7 in such folders, so if you have you should re-install and choose another location. John

The content of all offsets is documented in the offset status document - for 0x3124: Ok, thanks. Looks like that is a payware/subscription service, so I can't help with that. You need to contact their support to see why it isn't connecting I'm afraid as there is nothing more I can do or suggest. FSUIPC is functioning as expected. If you do get a response and a solution, please re-post here. John

If using LINDA, then you need to use LINDA support. I cannot help if using LINDA. As I keep telling you, standard controls do not work for many add-on aircraft (and even some default aircraft). For example, for the hdg in the FBWA320, the HubHob site shows these presets (amongst others): HDG Increase, HDG Decrease. These are using the FBWA320 custom controls: (>K:A32NX.FCU_HDG_INC) (>K:A32NX.FCU_HDG_DEC) However, there is already a LINDA module for the FBW A320 in MSFS - see https://www.avsim.com/forums/topic/599979-a32nx-linda-module-msfs/ I presume the LINDA module for this aircraft will be using the correct controls.... John

No. A preset is a label that identifies a calculator code string. You assign to a preset and when that preset is called, the corresponding calculator code is executed. I have mentioned this several times now and provided you with a link to the HubHop preset list (it is also mentioned in many places in the documentation), Uf you want to control aircraft in MSFS, you should familiarise yourself with presets. Look at the WASM section of the Advanced user guide, and the MF HubHop site. If you are using LINDA, you are better off with support from LINDA. I do not support LIINDA. Have you asked there? Again, if you are using LINDA, please use their support channel. If this is assigned in FSUIPC not using LINDA, disable LINDA and show me your FSUIPC files showing the configuration and the error.

Before I look at this in detail, could you clean your FSYUPC6.ini fil please. You have multiple sections for these when there should be only one: [General], [WideServer], [GPSout], [GPSout2], [AutoSave]. Also, I suggest that you clean-up your profiles to use substrings, so change to and to and similar for your other profiles For the profile you were using (P-51 MIL), you also have the same axis control assigned to multiple axes, e.g. 2=BZ,256,D,3,0,0,0 -{ DIRECT: Rudder }- 3=BR,256,D,3,0,0,0 -{ DIRECT: Rudder }- 19=JR,256,D,3,0,0,0 -{ DIRECT: Rudder }- 5=SY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 6=SR,256,D,2,0,0,0 -{ DIRECT: Elevator }- Its generally not a goof idea to assign multiple axes to the same axis control as they can interfere, especially when on the same controller. Do you mean these assignments: So you don't see anything when you move those axes (DR, DU, DV)? If you see another axis instead, just hit the Ignore button and try again. Otherwise, please clean your ini as suggested and show me the updated ini and an FSUIPC6.log file, this time with LINDA disabled (temporarily), logging for Axes controls enabled, load your aircraft and move one of the unrecognised axes through its full range, then exit. John

Understood. But if its working with FSX, I don't see why it won't work with MSFS. The main difference between the two, for control/assignment purposes, is that many aircraft in MSFS, particularly add-ons, don't use the standard controls, and any custom controls used by aircraft in FSX will be different in MSFS. It should be just a matter of updating the controls you used in FSX to whatever works for the aircraft you are using un MSFS, whether it custom controls, lvars, hvars or presets. The basic plumbing should be the same - except maybe if previously using any 32-bit drivers you would need to switch to 64-bit, but hopefully that is not the case. Many folks are having difficulties controlling MSFS aircraft, especially the more complex add-ons. You should really be looking to use the available presets for such aircraft, and update your FSX scripts to use those.

No harm in trying/posting, event though its an old post, and you can also try tagging the post's author (using the @ notation). But it seems that the author went on to use LINDA for managing his lua scripts anyway... Did you look at the documentation and scripts he provided - you could use that as a starting point and update to MSFSFBWA320, as the scripts were written for FSX and PMDG. You may need to update the script to use/call presets rather than controls (custom or otherwise). See the HubHop site for a list of available presets available (https://hubhop.mobiflight.com/presets/). For any further assistance, you need to show me how you are currently assigning, together with a log file showing any issues. John

Maybe try posting for further information in that User Contribution topic: VRInsight MCP Combo and FSUIPC Lua scripting, as that seems to be what you are looking for. Maybe also see: https://forum.pmdg.com/forum/main-forum/pmdg-737-for-msfs/187760-vrinsight-mcp-combo-fsuipc-nothing-with-the-new-pmdg-737 John

All programs must be ran at the same privilege level, so if one program is ran in admin mode, then all programs, including the FS, must be ran in admin mode. This just shows that an external program with pid 17172 (is that Pegasus?) is reading those FSUIPC offsets: 3304: FSUIPC version number: 3308: FS version, as determined by FSUIPC 3124: The specific version of FSX or P3D being used. 290C: Number of Hot Joystick Button slots available for Application Programs to use 320C: Number of Hot Key slots available for Application Programs to use. If I log those offsets when FSUIPC7 is connected to MSFS I see these values: Which are all correct (N.B. you will see 0x73110000 at offset 0x3304 if using the latest version). This all seems correct to me, so if Pegasus cannot connect you need to contact support for Pegasus to see why. I also have no idea what Pegasus is - do you have a link? John

You attached the log file when FSUIPC6 was still running. Please always exit FSUIPC before attaching a log file. I really don't see how FSUIPC can stop ASP3D connecting to P3D. You are using the latest version of FSUIPC (i.e it is not outdated) and FSUIPC does not store any login information - it only uses your FSUIPC registration details which your log shows are valid (as well as having nothing to do with ASP3D!). I suggest you go back to ASP3D support for this issue. John

You posted this in a topic 'Max Throttle causes sim to change to outside view using P3D v4': You again posted in the User Contributions sun-forum. I have deleted that post. This is the second time - the next time your posts will just be deleted. As for your issue, I have already told you what you need to do: If you want help with specific assignments, please attach your FSUIPC ini and log files, the latter generated showing your issue and with relevant logging enabled e.g. usually axis controls for axes assignment issues and events (non-axis controls) for buttons a & key assignments. For your issue, activate logging for both. Also, check your assignments in FSX - if assigning in FSUIPC, we recommend disabling controllers completely in the FS.

Why is this different from your previous topic posted:?

No point running it if the entries are not there, but it won't do any harm either. Can you set a Log->Custom value of x200200 and show me a log with that logging added.

How are these knobs assigned? Do they work as expected when using Linda? If you can share how they are assigned, I can take a look. Also try activating logging for Events to see if that reveals anything. If using the FBW A320, many of the standard FS controls don't work as expected - check to see if there are any presets for the functions you want to implement on the HubHop preset site https://hubhop.mobiflight.com/presets/