John Dowson

I am not that familiar with helicopter flight controls, but the method to determine which controls to assign to is to activate logging for Axis Controls, open the logging console (Log -> Open Console) and move the desired axis in the VC and see what control is logged, and then assign to that. For example, in the Guimbal Cabri G2, I see the controls Throttle1_Set and Prop_Pitch1_Set logged for the collective and throttle respectively - i.e. Prop_Pitch1_Set seems to control the throttle and Throttle1_Set the collective. It is probably different for each helicopter, so use logging to determine which control to use and use profiles for each helicopter or helicopter group (if they use the same controls). John

Maybe@Chuck100 or @Phil4125 could help you, and maybe check on avsim. I know nothing about CRGSIM, sorry. John

Could you please activate logging for Events in FSUIPC, and as Pete said change the following lines in your PFChid64.ini: LogDevices=No LogDeviceChanges=No then show me/attach your FSUIPC7.log, FSUIPC7.ini and PFChid64.log files, showing the console buttons that are registering (in the log) but not having any affect in the FS. What is the exact model/name of your PFC Radio Stack? Is it a hid or com device? John

I am not sure I understand your issues, and there is no such bug in FSUIPC... Can you please activate logging for Buttons & Keys as well as Events, and generate a log file showing your issue, then attach both your FSUIPC7.ini and FSUIPC7.log files and I will take a look. Male sure you exit FSUIPC7 before attaching the files. John

No, that is still not clear... what is/are the button assigned to? Is it a key press or something else? Or does this apply to all button assignments regardless? Could you activate logging for Buttons And Keys as well as Events, and generate a log file showing your issue, and attach that (exit P3D/FSUIPC6 first please) together with your FSUIPC6.ini file. Focus should only affect keyboard input, nothing else, and those parameters previously mentioned should force the focus back to P3D before sending any key presses.. John

I am not sure what you mean.... There are many ways to do things, but you usually have one rotary that selects speed, heading, altitude, etc, and another rotary to increase/decrease the selected value. The first selection rotary will show a different button press for each position, whereas the 2nd rotary will show either one or two button presses in each direction. You assign the buttons on the 2nd rotary to the inc/dec controls for each function (speed, heading, altitude, etc) and add a compound button condition to these entries using the selector rotary buttons so that each inc/dec is only sent when the selection rotary is in the corresponding position. See the Advanced user guide for details on compound button asignments. I also provided details on how to set this up for the Bravo in this post (sorry, I don't have the TCA): If you need further assistance, can you please provide more details of what you want to achieve, John

Yes, you will need a registered copy of FSUIPC to use LINDA, as the Lua facilities are only available in the registered version. There is a trial license available in the FSUIPC7 sub-forum, where you should post all questions/support request for FSUIPC7, not here. See John

Login to your SimMarket account and go to Your Orders, then select your FSUIPC4 purchase order and your key details will be there.

Probably because Exclude THROTTLEn_SET is checked by default (i.e. in a clean installation)... John

Sorry, I just explained how you should edit the ini. Looking at what you are trying to do: What is this? This is an invalid button assignment definition. If you want to send multiple keys on a button press, you have to duplicate the lines (and change them), not add the 2nd keypress to the same assignment line. Please see the Advanced User guide for the button assignments format. Try: i.e. add two additional assignment lines for the same buttons, and change the vk code and shifts parameter. No need to change the comments - this will get added by FSUIPC7 when it runs. I think you are possibly confusing button assignments with key assignments, where the latter (key) format allows you to send a control (+ parameter) on key press and release. For buttons, these appear as distinct assignments. John

Yes, maybe that is what the macro is doing, but difficult to tell from a single log entry (especially as mask = X00000000) - you can only tell that bit 2 was changed by comparing to the previous value (1015). I just tested offset 0x0D0C by writing the value 0x3F7 to confirm the correct events were being sent with this value, which they are, rather than just changing a single bit.

That makes sense, and that will trigger the event LANDING_LIGHTS_TOGGLE - this event should work in most default aircraft (but maybe not all), and some add-ons but certainly not all of them. It certainly works in the C172, as does writing 0x3F7 to 0x0D0C, which results in: taxi lights off, beacon, landing, nav and strobe lights on (as well as others, which the C172 doesn't actually have) . 0x3F7 = 001111110111 so that is as expected (bit 3 is 0 so Taxi off). John

Yes, thanks - that explains it. I can maybe check what offsets are being used (from the PFC log) and can see if they are working for the aircraft being used if @jimbooo could attach an FSUIPC7.log file, together with a PFChid.log file, both generated with the logging changes that you have already suggested. John

It shouldn't make a difference if assigning in FSUIPC with 'Send direct to FSUIPC calibration', but will if assigned in MSFS or in FSUIPC with 'Send to FS as normal axis' (depending on the axis controlled you have assigned to). However, as I said, your ini file shows no assignments. Try assigning your axis in FSUIPC7 as well,. John

Yes there are: 76141: Macros not found: "C:\FSUIPC7\PFC.mcro" The OP attached a file named PFC.MCRO.txt - he needs to remove the .txt extension - but is it really an issue if this empty macro file cannot be ran? What offsets are being used, and for what- (where is this info? The PFChid64.log shows some macro's being called in PFC.mcro (which is empty!): 76235: Full macroname for decoded switch = "PFC:LandingLight", mask = X00000000 ... 76375: Full macroname for decoded switch = "PFC:Obs1", mask = X00000000 ... 76391: Full macroname for decoded switch = "PFC:CRSencode", mask = X00000000 etc I am not sure what those are and why they don't have an error if the PFC.mcro can't be found...maybe Pete could explain? That is a good idea - and please attach your FSUIPC7.log file as well. John

As well as having no axes assignments in FSUIPC7, you also have the checkbox for Exclude THROTTLEn_SET checked (page 3 of calibration screen) - uncheck that and try again. John

The log file you attached shows that FSUIPC7 was still running when you attached it, and only contains 13 seconds worth of log information. Can you please leave FSUIPC7 running a little longer (a minute or so), and make sure that you have exited FSUIPC7 before attaching the log file. You also have an ipcInit.lua that is ran on startup - what is in this? Maybe try disabling that (i.e. rename it to ipcInit.lua.off) to see if that is causing your issue. John

No. Yes - the X just closes the window and is the same as File ->Close. You can also press Alt followed by F followed by x to exit FSUIPC7 - the keyboard shortcut. Why don't you just have MSFS auto-start FSUIPC7? Yes - use the keyboard shortcut. If FSUIPC is iconised, you can also press Alt+F (together) first to show the main window. John

Your registration details will be available in your SimMarket account. Note that f you have a license for FSUIPC4 (which is compatible with FSX and FSX-SE), this will not be valid for FSUIPC7 (which is compatible with MSFS2020). John

👍

Not really...to confirm: In the axis assignment tab, you can see the joystick and axis letters detected there, and the In / Out numbers changing. You then assign to Throttle1 with Send direct to FSUIPC Calibration, and on page 3 of the calibration tab, you cannot see the In / Out numbers changing there? If that is the case, I do not understand as the axis input values are coming from the same place... Can you try this with just running FSUIPC7 without MSFS and see if you get the same behavior? Are you assigning using profiles for both the assignments and/or calibration? Can you attach your FSUIPC7.ini file as well please.

What version of FSUIPC7 are you using? Calibration of axes not assigned in FSUIPC7 (or assign with 'Send to FS as normal axis') was removed in 7.3.9 due to issues introduced in SU10, but was re-enabled in 7.3.13. The latest version is 7.3.15. If that is not your issue, can you please explain what you mean by 'cannot be calibrated within FSUIPC.7', and please let me know how that is assigned, and attach your FSUIPC7.ini file. John

This is not correct...they are working, I was using the wrong parameters. I tested using the following two simple lua scripts for prev/next page on the left CDU: Prev page: ipc.writeUD(0x3114, 0x20000000) ipc.writeUD(0x3110, 70191) Next page: ipc.writeUD(0x3114, 0x20000000) ipc.writeUD(0x3110, 70192) where #define MOUSE_FLAG_LEFTSINGLE 0x20000000 So I am not sure what your issue is... You could try setting a custom log value in FSUIPC7 of x800 to check the events are being transmitted. You should see lines such as the following logged: 6625734 ExSendEvent(70191, 536870912, 0) 6625734 ... evnum mask=0, preval=0 6625734 ... not intercepted or in options 6625734 Transmitting "????" 70191 [0x1122F], Param 536870912, Priority 1 (Axes flag = 0) 6626313 ExSendEvent(70192, 536870912, 0) 6626313 ... evnum mask=0, preval=0 6626313 ... not intercepted or in options 6626313 Transmitting "????" 70192 [0x11230], Param 536870912, Priority 1 (Axes flag = 0) John

Sorry - forget this, they are working...I was using the wrong parameters.... John

Still no issue here when using the A310 Enhanced add-on....