John Dowson

Note also that such issues may be dur to a poor com cable/adaptor used - see John

Why? The version you are trying to install is v7.2.16 - the latest and only supported version is 7.3.20. Please download and install the latest version, available from fsuipc.com. Are you using the MS tore version of MSFS? If so, the UserCfg.opt file should be in one of the following locations: $LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt $LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\UserCfg.opt If you get the same issue, determine where your UserCfg.opt is located, and check that the windows environment variable $LOCALAPPDATA is set correctly. See https://www.howtogeek.com/787217/how-to-edit-environment-variables-on-windows-10-or-11/. John

What does this mean - do you actually have a question? The message is self-explanatory... Any issues, please explain what they are and attach your InstallFSUIPC7.log file. John

Please try the attached version, 7.3.21b. To use/activate this feature, you need to add the following to the [General] section of your FSUIPC7.ini file: LogLuaNew=Yes I don't think I will add a UI option for this, as I doubt it will be used much - lua logging has worked this way for many years and nobody has requested this before. Cheers, John FSUIPC7.exe

Can you please attach your FSUIPC ini file so that I can see your assignments & calibration. This sounds like you have the No Reverse Zone box checked, but if that is the case then this should really apply to all throttles - it isn't which is strange. Your ini file will tell me what is happening.... John

Yes - you are not using the joyletters facility (you should!), and the j and b letters are just placeholders for the joystick id/letter and button number Change to You should also switch to using JoyLetters. Just change to AutoAssignLetters=Yes This will prevent issues if your joystick ids change. John

Then something else, e.g. the GoFlight Interface Tool, that must be controlling the lights - the driver I provide does not do this, for FSX, P3D or MSFS. As I said, the driver does not know what the switch is assigned to, and cannot set the light to the correct state for the assignment. If you still have P3D installed, please check this. The GF driver is the same for P3Dv4, P3Dv5 and MSFS. John

This would be a huge amount of work and complicate the UI, as well as the ini file format, for little benefit - I will not be adding this. I could add a menu option to Reload Presets so that any changes to the events.txt and myevents.txt are made available for assignment without restarting FSUIPC7. John

I have checked in P3D and it is the same - are you sure that you weren't using a lua script to handle the lights in P3D? If so, you can probably use the same scripts for MSFS. The lights aren't controlled by the driver as this would just indicate the switch position (up or down). What you want is for the light to indicate is if the function assigned to the switch is on or off, so to do this you have to use an offset (or maybe an lvar) to determine if the light should be on or not, and so this depends on what the switch is assigned to. There are quite a few support requests on getting the GF indicator lights operational - for example, see the following: But if you are setting/assigning your GF switches in MSFS the same as in P3D, the lua scripts you used for P3D should also work (although can depend on aircraft) in MSFS. John

Ok. Also, if you don't need repeat, which you don't if these buttons are rotary buttons, then you should use 'CP' and not 'CR'. If these are rotaries, then there are also other ways do achieve fast/slow assignments. - see John

The sequence number is not that important, as long as it is unique - it is fine to have gaps. Ok, glad this problem is now sorted. John

Really? The driver is the same so this surprises me...I will take a look later, but please check that you weren't using a lua script for this in P3D. You would need to write your own or check the forums to see if any are available. But I will check this in P3D and get back to you (probably tomorrow). John

Thats the main support forum - there is only a sub-forum for FSUIPC7. I will move your post there. Yes. Don't forget to either comment out the current assignment (using the ';' character, placed AFTER the '=' sign to preserve the index number) with the FSUIPC button assignments tab visible and click to reload your assignments once changed. You add them manually to the ini file, but you do not select them - they are added to the assignment so this is not necessary. In fact, once you have multiple assignments to a button, you can no longer do anything with this assignment in the UI. One assignment will be shown but grayed-out and not you cannot change it via the UI. You don't need that additional 'P' (press), as 'CR' already indicates a conditional (C) repeat (R). And the control numbers should be preceded by a 'C'. Those controls do not take a parameter, so doesn't matter what you use, but 0 is best. Comments will be added/re-written by FSUIPC. So: John

Please look at your installation log. This was your problem: Remove that file...(sorry, missed the Roaming sub-folder in my previous message) Also, as you have switched MSFS versions, you must manually uninstall FSUIPC7 before re-installing - you can do this either via the windows app management panel or by running/double-clicking the uninstaller file uninstallFSUIPC7.exe. If you don't do this first, your previous installation details will be taken from your registry.

Sure, I can look into adding that, maybe for the next release. I will let you know once implemented. John

Yes. You need to overload the assignments, i.e. have two assignments on the button press, one for the small increment and one for the fast increment. To achieve this, you can comment out the slow (small inc/dec) assignment and then add the fast (large in/dec) assignment via the UI. Then you need to edit your FSUIPC7.ini file to re-instate the first/slow assignment, and add a compound button condition - see the Advanced User guide (P21) on how to do this. Note, if/when editing the ini file, make sure that FSUIPC7 is either not running, or do this when the button assignment window is open, and after you have saved your changes click to Reload all buttons. John

Yes. I have both the GF T8 and P8 modules and they work fine here. That shouldn't be the case...can you try assigning one of the switches to a lights on event on press, and a lights off on release. Then activate logging for Buttons & Keys and Events, and then show me a log extract when you switch on and then off. This is what I see when I assign to the taxis lights: There you can see the taxi lights on event being sent when push up (press) and the taxi lights off being sent on push down (release). The lights are not operational, and never have been (as far as I am aware (I can check in P3D of needed), without the use of an additional lua plugin. You need a lua script that uses the GoFLight library (gfd) to get the lights working. John

This also change the id of those phantom xbox controller registry entries to 3: This would indicate that those entries are somehow related to your CH throttle quadrant. Do you have any specific drivers or other software running for this device? If so, you can try uninstalling that, reboot and let windows install default drivers and then try again. If you are already using windows drivers for this device, then maybe ask on CH support about this issue. Ok, I don't see a problem if it woeks as expected, and only the name is missing. This is only shown in the log and ini files anyway, and should not affect functionality. Yes, the exact same issue has been reported at least once (and probably several times) before - see an earlier comment where I referenced one of these threads. Ok, that is interesting...I know there are some controller settings in steam, but I have never used or looked into these. I think you need the xBox app installed if usinf MSFS even oon Steam, but not sure about the xbox game bar... No bother... There will be remnants of the steam installation installed under your user' AppData folder. You need to remove (or rename) this file (its presence will indicate a steam installation for the FSUIPC7 installer): $APPDATA\Microsoft Flight Simulator\UserCfg.opt (where $APPDATA points to your user' AppData folder, usually C:\Users\<accountName>\AppData) John

A local lua variable is not an lvar. An lvar is a local panel variable and lives with the aircraft model. As I said, you can use the ipc.createLvar function to create an lvar, Cheers, John

I find your post rather confusing.... It is not a "sim" is it? Looks to be a helicopter hardware console to be used with a simulator... Which of Pete's programs does it need? Why? 32-bit programs can run on 64-bit systems, but not the other way around. And what sim are you referring to here? A sim (flight simulator) is FS9, FSX, MSFS2020, P3D, etc.. The TRC2244 is a controller/hardware device to be used with a flight simulator. What software is this? How does this intigrate? Maybe ask the providers of this software... Do you have this hardware working with any other simulator, and if so, how? Have you tried FSUIPC7 with MSFS to see if this device is detected? A trial license is available in a post at the top of this forum if you would like to try it. John

What is the position of your idle gate switch? If that is in the in position, F2 will not decrement into reverse. You can also try activating logging for Events and open the logging console - do you see the THROTTLE_CUT event when pressing F1, and the THROTTLE_DEC event when pressing F2? I think it would also be better to not have any axis scaling on the throttle assignments, and configure in the EFB if not using a reverse range on your axis.

There is only the dll - if its in your FSUIPC7 installation folder it will be loaded, if it is not there it won't. There are no remnants. Do you mean the PFCcom64.dll? You don't need the PFChid64.dll if not using PFC USB devices, and this should have no affect if installed but not used. You need to determine what is happening when it fails. Is the button/switch press being detected? Is the appropriate control being sent? You can use FSUIPC's logging facilities - activate logging for Buttons & Keys as well as Events, and see what is logged (with the console window open) both when its working and when not working, See if there is any difference in the logs in these cases. Also please check the PFC driver console for any logging options there, also check the PFC.DLL User Guide on how to use this correctly for your console.

But why does it need to detect MSFS? It is used by FSUIPC7, not MSFS, and you need to assign in FSUIPC7. You will also need a registered/licensed copy of FSUIPC7. If you do not have a license, try the trial license available in a post at the top of this sub-forum. As I have said, I no precious little about VRInsight devices, and nothing about the CDU III. I can only suggest that you try and set it up the same way other people have setup the CDU II with FSUIPC7 and MSFS. Some people use SerialFp2, others not. Try without first, and then maybe try with as well. As I don't have this device, you will to read the documentation as well as maybe those support requests I have referenced. If you have any issues, you can try tagging (using the '@' notation) the users who are using the CDU II with FSUIPC7 and MSFS. If you configure correctly with SerialFP2 and the buttons/switches are not recognised by FSUIPC7, then it is probably because the device isn't supported. Sorry, but that is not my problem... John

Offset 281C is 4 bytes, not an unsigned byte - and certainly not just 1 bit. Try with event.offset(0x281C, "UD","Batteryswitch") Also, are you sure the lvar exists? If not, as the documentation on the ipc.writeLvar function says says: If the variable is not currently available, nothing happens If not sure, just add a call to ipc.createLvar before the event.offset call. John

Thats not quite what I meant... I meant that you would select an actual preset from the tree view (not a group of presets), which would then be used to select the item from the drop-down list. There are issues involved if the tree selection was used to filter the preset drop-down by aircraft or aircraft sub-system, For example, when a button is pressed, any exisiting assignment on that button needs to be displayed, and this could be to a preset that is not in the filtered list. Anyway, I will have a better idea how this will work once I have started to look at this in detail, and will implement what I can... John