John Dowson

You can reverse the axis by editing your FSUIPC7.ini file. See the section Additional parameters to scale input axis values in the Advanced User Guide (P38). To reverse the axis, add ',*-1' to the end of the axis assignment line in your FSUIPC7.ini. @Martin99 You could also try scaling your axis using this method (to get 0 at your detent) rather than using lua.

Macros are available in FSUIPC7, it is mouse macros that are not implemented. To activate a hvar, first you need to create a macro file. e.g save the following content as G1000.mcro: You will then be able to assign to those hvars in the assignments drop down menu. It does look like I missed hvars from the macro section in the Advanced User Guide. I will update.

No, not for this specific use case. There is documentation on the functions you need to use... First, assign the axis to an FSUIPC offset - you can use one of the free ones, eg A000. In your lua script (which you would have auto-started from your [Auto.xxx] profile section), use event.offset to monitor the chosen offset. Your receiving function will receive the axis value. You can then adjust this (i.e. apply your manual calibration), then sent to the sim using ipc.control.

Using ipc.control

I think thats the way the _EX1 controls work, as they are used in a/c that have a reverse thrust toggle, so the full axis range is used for forward thrust, and also revers thrust (once toggled). If you want to calibrate using the EX1 controls, you could assign to a lua script, adjust the parameter value accordingly (your calibration), then send the axis control from the lua. Alternatively, I could provide you with an FSUIPC7 version to test that allows the EX1 controls to be calibrated. However, that development branch is quite old now, so I would need to update this first.

When windows flashes a task bar icon, it means that there us something there for your attention. Not sure I understand this. There are two main (i.e. can be minimised to the task bar) windows in FSUIPC7, The FSUIPC7 main window and the log console window. When you click the tray icon you should just see the context menu. Double-clicking will open the FSUIPC main window. You can only open/close the (log) console from the Log menu. I was suggesting that you try with the log console open, and see if any messages are logged when this occurs. Could it be that FSUIPC is requesting focus for some reason? Maybe check if any ini parameters are set to do this (e.g. KeyboardFocus=Yes in [Buttons] section) and maybe try changing that.

Do this as Pete suggested. Then start P3D/FSUIPC, load an aircraft, then exit, and show me your FSUIPC6.ini, FSUIPC6.log and FSUIPC6.Joyscan.csv files.

Ok, thanks for reporting. The *_EX1 controls don't go through to calibration - they are for direct to FS assignments only. I did start looking into allowing the _EX1 controls to go to calibration instead of the standard controls, activated via an ini parameter. I think I have this working in a dev branch of the code, but the problem was that it would apply to all aircraft as it turned out to be more complicated to allow this just for specific profiles. I could take another look at this, but I don't think it would be useful for the PMDG aircraft due to priority issues - it has been known to cause issues with PMDG aircraft, although I don't know much about the DC-6... Thats also useful to know, thanks.

PMDG aircraft don't usually like the throttle axis going through FSUIPC calibration. Try assigning direct to the FS controls instead. Also maybe try the *_EX1 controls. I also noticed this on the Asobo forums, posted yesterday:

Thanks @Blake Buhlig!

What controls are logged when you move the throttle and prop levers in the UI? You could try activating logging for Axes Controls and also Events, move the throttle/prop levers in the UI to see what controls are logged, then try assigning to those. The same logging should also show you what is happening when you do this. You can attach your FSUIPC7.log (with the logging activated, and the throttle/prop moved in the UI and also from your assigned axis) and also your FSUIPC7.ini and I can take a look. However, not having this aircraft it may be better if PMDG could advise on what controls to use.

@Grendel and @Blake Buhlig I got the gear lights working by making the following changes: - Change the initialization of GearIsRetractable variable (line 211) to GearIsRetractable=ipc.readUB(OFFSET_IS_GEAR_RETRACTABLE); NB. It would be better if all of the offset variables were initialized this way, as you won't get the correct value unless event.offset is called (i.e. when the value changes). - You could also add the following at the end of the script: event.offset(OFFSET_IS_GEAR_RETRACTABLE,"UB","offset_event") However, as this value doesn't change (it should be fixed!), this isn't really needed once the GearIsRetractable variable is initialized correctly. John

The gear lights don't seem to be working with that script, at least not for me with the G36. I will take a look when I get a chance. Make sure you are actually running the lua by adding it to the [Auto] section of your FSUIPC7.ini file, e.g.: You should at least see the PARKING BRAKE light work.... Also, the lua file should be in your FSUIPV7 installation folder - you should see it listed under the [LuaFiles] section of your FSUIPC7.ini (do not add it manually there - it will be added automatically when detected).

FSUIPC5 is always available from the download section here, and also in www.fsuipc.com. It is only the license that is no longer for sale. But if you have already purchased a license, you can always retrieve your license details from your SimMarket account. However, you should really move to FSUIPC6 if you have a license for that, and resolve your Linda issues with that version. FSUIPC5 is still supported (for P3Dv4.5), but is closed for future development.

@Dan A A trial license is now available here: Fir all future license requests, please use that topic. This topic is now closed/locked.

Please find a trial license for FSUIPC7 attached below, valid until 1st November 2025. Just save this key file to your FSUIPC7 installation folder and you are good-to-go. Note that trial licenses are NOT validated by the FSUIPC7 installer. John FSUIPC7.key

Sorry, looks like some hidden/control characters got inserted into the script. Try the following one: A320ParkBrake.lua

Strange. When this happens, do you already have the FSUIPC icon in the task bar (i.e. is the main window already open and/or iconised?)? Or does it move from the system tray (where it usually sits) to the taskbar? Do you have the console window open (with this open, there will also be an FSUIPC icon in the task bar)? Maybe try with the FSUIPC7 console window open (with FSUIPC in the system tray), to see what (if anything) is logged when this occurs

If that is the case, then it sounds like the lvar values are not being updated. But in your second post, you have different values for pBrakePosition, so is this problem resolved? There will not necessarily be a parking brake event as the A/c is using the lvar. Did you try logging the parking brake offset to see what the value is when the lvar value changes? Maybe try that,. Looking at offset 0BC8, the description says: Parking brake: 0=off, 32767=on Currently the script is just writing the value of the lvar, which is 1 for on. You therefore need to adjust by adding: if pBrakePosition == 1 then pBrakePosition = 32767 end (after you have read the lvar value and before you vall ipc.writeStruct). Updated script attached. A320ParkBrake.lua

Try: ipc.writeStruct(0x0024, "1UW", spoofOffset, "1UW", 1, "1UB", doorMainState )

@Dan AApologies - forgot to do this, will be first on my list tomorrow... John

Ok, then what you need to do is spoof the offset value with the modified lvar value. Just take the lua script I previously told you about and linked the post where available, change that script to use the offset you want to spoof, i.e this: local spoofOffset = 0x0BC8 -- Parking Brake offset, unsigned word (2 bytes) to this: local spoofOffset = 0x3367 -- Exit Open offset, bit per door (1 byte) Change the variable to read your lvar: ... local pBrakePosition = 0 ... pBrakePosition = ipc.readLvar("L:A32NX_PARK_BRAKE_LEVER_POS"); ... to ... local doorMainState = 0 ... doorMainState = ipc.readLvar("L:DOOR_MAIN_DOOR_POS"); ... Then you can apply whatever transformation on that value you require to write/spoof offset 3367. If it is as you say, its very easy to assign a new local variable to the value you want to set, based upon the lvar value, then adjust the ipc.writeStruct statement to your requirements. Hopefully that should give you enough information to do what you require.

Maybe an example will help you.... Door 1 is bit 0, so to open just that door, you would set bit 0, i.e. write 0x1, or just 1. Door 2 is bit 1, so to open just that door, you would set bit 1, i.e. write 0x2, or just 2. Door 3 is bit 2, so to open that door, you would set bit 2, i.e. write 0x4, or just 4 If you write 0x3, or just 3, that is 0b11, so that would open doors 1 and 2 (bits 0 and 1 set). So, as I said, if you write 100 (in decimal), that is in binary 0b1100100, which is: - door 1 closed 0b1100100 - bold is bit 0 - door 2 closed 0b1100100 - bold is bit 1 - door 3 open 0b1100100 - bold is bit 2 - etc To change single doors, you need to read the offset value as it is, then change the bit (using the lua logic library) for the door you want to control. You should or the original value with the bit flag you want to set, or and to clear. I understand this may sound advanced for your understanding, but it really isn't that difficult. If you can tell me exactly want you want to achieve (i.e which aircraft and, if applicable, which mod, and which doors) then I can maybe help you further if you have issues. John [Note some folks call bit 0 bit 1, which is confusing. But you can usually tell by context]

An offset is just a memory starting address. You also need to consider the size (1 byte in this instance) and the data that it holds (bit-oriented flags for that offset address). I'm sorry, but this is not the place for a tutorial on these concepts - there is google (or other search engines) to help you with basic understanding, And I'm sure its the same in xplane/xuipc. You just need to understand the concept of bit-wise flags. Its really not that difficult. Try by re-reading what I have explained. And, if you still don't understand, just do it by example: log the offset values for the different states, and write the value for the state you need when necessary....

And the solution? Always helpful if other users have the same problem and come across this topic, so please post what resolved your issue.