John Dowson

What FS and version of FSUIPC are you using? Presumably not MSFS with FUIPC7, as there is a specific sub-forum for that. To list available lvars in FSUIPC4/5/6, you can use the provided lua plugin but it is easier to just assign a button or key to the FUIPC-added control List local panel variables and use that. John

I don't know the API you are using - if its Paul Henty's FSUIPC client dll for .Net client, please use his support sub-forum: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ John

Offset 0x3340 only supports up to 9 devices, as you say. You can use offset 0x7F00 which supports up to 16 devices with 128 buttons. John

I can't help with SIOC - maybe try asking how to read/use a string with SIOC on opencockpits. John

It looks like you assign the FSLabs Airbus A32X profile with the original letters: Compare this to your general profile: So it looks like some assignments were made AFTER the ids switched.... You need to go through your ini and change the letter to the correct device, i.e. for the FSLabs Airbus A32X try John

How are you trading the offset? For example, in lua you would use n = ipc.readSTR(offset, length) John

I doubt this will be possible for all aircraft (GA, Jets & Airliners), and would also depend on the number of engines, i.e. you would normally have a selector for each engine. I would start with one aircraft (type) and see what the fuel tank selector offsets hold for that and go from there. You could probably do something clever in lua, checking the number of fuel tank selectors available, etc, but I would do this on an aircaft-by-aircraft basis, or maybe aircraft type (single engine, twin, turbo, etc). John

I've had visitors for the past 4-5 days and so not had much time for support... I answered in your other post on this - FSUIPC has no knowledge of any P3D windows except the main one, so I don't think this is possible. John

You posted in the wrong forum - I have moved your post to the specific sub-forum for FSUIPC7 / MSFS. The additional variables provided by the PMDG SDK are added to an FSUIPC offset area. For example, APU_EGTNeedle is on offset 0x64E8: 64E8 4 FLT32 APU_EGTNeedle Please see the document Offset Mapping for PMDG 737-700.pdf in your FSUIPC7 Documents folder. You need to enable data broadcasts in the PMDG 737 ini file first (explained in the document). John

I think you can have up to 300 devices in total, virtual or otherwise, with 256-299 being reserved for VRI, and 0-15 for standard joystick type hid devices. John

FSUIPC only knows the window handle of the main P3D window, so it is not possible to give the focus to any other P3D window I'm afraid. John

Please try the attached - I have just switched your Bravo throttle and your CH pedals, by changingL to You can switch other devices similarly, if needed, I have also simplified/updated your profile aircraft names to use substrings. Let me know if you still gave ant issues. John FSUIPC6.ini

Sorry for delay...and glad you found a solution! John

Looks like your device ids have changed, This can happen with windows updates. You should really be using the "joyletters" facility which prevents this happening when the ids change. You are also using an old and unsupported version of FSUIPC6 - 6.1.7. The latest version is 6.1.9 - please update. Once updated, can you change this line in the [JoyNames] section of your FSUIPC6.ini: Then run/start P3D/FSUIPC and exit once loaded, and then attach your FSUIPC6.ini and FSUIPC6.log files and I will update your ini for you with the correct id-to-letter mapping. John

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.