John Dowson

I am not sure this is a goof thing to do as changing your system clock may affect other licenses...but if it works then I guess thats ok... So everything else is working? If so, its strange that just these 2 functions are not working... If using the ProSim737, maybe try asking about thus on their support forum. I am not in a position to assist you any further with this, but maybe others can help... Good luck - and please update if you find a solution. John

I still don't know what FS you are using and what version of FSUIPC (FSX with FSUIPC4?), but there is nothing in FSUIPC related to those offsets. They are in an area reserved for various people / systems, and I cannot see anything related to CRGSIM - although that may use that area. What makes you think that writing to that offset should activate LNAV / VNAV? Have you tried using any of the standard controls (GPS VNAV Button maybe...) - or, better, activate logging for Events (non-axis controls) and see what is logged (in your FSUIPC4.log file) when you activate LNAV and VNAV and try using that. Alternatively, you could try listing the available lvars (local panel variables) to see if any of those look applicable. Sorry I can't be of further assistance - you may have be better asking about this on avsim where other CRGSIM users may be able to help... John

You would assign a button or key press to this as you would for assigning to any other control - open either the button or key assignment tab, press the button or key so that it is registered, then select the control List local panel variables from the drop-down menu, then click Ok to save the assignment. Then just press the assigned button or key, and the lvars will be listed in the FSUIPC6.log file. Why don't you try reading the documentation - this is all explained in the provided User guide, with further details in the Advanced User guide. John

It is not documented. Probably should be added to the FORMAT OF BUTTON DEFINITIONS section on page 18 of the Advanced User guide. But really this is internal to how FSUIPC works - you don't need to know about this. You just set this up in the assignments window. John

CL indicates the button is assigned to a Lua script control, and the following number is the index number of the lua file under your [LuaFiles] section of your FSUIPC6.ini. The letter after the colon is the lua control, with K indicating LuaKill and R indicating just Lua (shorthand for Lua Run). There are also other letters for the other Lua Controls - LuaSet, LuaDebug, LuaToggle, LuaValue and LuaClear. The comment on the button assignment line will tell you the lua dile name and lua control used. John

The last update to FSUIPC6 was in May 2022 with the release of version 6.1.9. There has been no update since then as there has been no need. P3D and FSUIPC6 are pretty stable these days. Most support and development I am doing these days is for FSUIPC7 / MSFS, not P3D, although I still support FSUIPC6 / P3D as I have always done. John

Maybe you could use the windows keyboard shortcut to cycle through application windows...i.e. restore focus to the FS, and then send the appropriate windows key shortcut to cycle through its windows? Not sure what that shortcut key combination is, but google can help with that... There is/was an FSUIPC control to List all FS windows, but looking at the code this has actually been removed in FSUIPC6 and FSUIPC7 (and possibly other versions), so I don't think its possible for FSUIPC to know anything about FS windows, John

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