John Dowson

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

I have no knowledge or information on the VRI CDU III - you should really try VRI support for this, or from the place where you purchased, Does it not use the VRISim software to interface to the FS? Otherwise, if the CDU III is similar to the CDU II, then see Appendix 3 in the Advanced User guide: Handling VRInsight serial devices in FSUIPC. and also take a look at the document Lua Plugins for VRInsight Devices.pdf. As I don't have any VRI devices, I cannot add to what is already documented in these devices, Also see the following support forum posts: John

It is available from here. Leave that. Its the id of the CH throttle that you want to change. Its more of an annoyance than a problem, no? You can still assign to and use the throttle, it is just that the name is empty in the FSUIPC logs and ini files. John

Thats strange - did you do this when FSUIPC7 was running? You need to make this change when FSUIPC7 is not running as these options will only be read at start-up. Anyway, glad its working for you anyway without this. John

Try changing the id from 1 to 3 for the CH throttle, using the JoyIds program, as advised. The problem is nothing to do with MSFS - you have the same problem with FSX. It is a registry issue, and looks to be common with that throttle. I would recommend you stick to the Steam version - the store version uses a complicated system of links which did cause issues with some add-ons and when updating, although I think these have been resolved by now. But there is no point changing, especially if it is for this issue. John

That is normally what I would recommend... You can edit the name of the aircraft in the FSUIPC7.ini under the [Profile.xxx] section to remove the livery name and yse a short as string as possible that matches the aircraft you want to use (e.g. "PMDG 737", "Cessna Skyhawk", "TBM 930", etc). There is also an ini parameter you can set that will match in the aircraft folder name instead id the title, which should catch all variants/liveries id the same aircraft: UseAirLocForProfiles=Yes From the Advanced User guide (P6): Also see the User guide section Profile matching on aircraft with different liveries on page 21. Note that if you change to use this. you will need to associate each aircraft back to its profile again (i.e. load the aircraft, open FSUIPC's axis assignment panel, check the profile-specific box and select the profile. After you have done this for the profiles you use, you can the clean-up your FSUIPC7.ini by removing the aircraft names from the Profile sections. John

You could try assigning a different id (e.g. 3) to your CH THROTTLE QUADRANT in the registry. You can do this using the JoyIds tool - see the following FAQ entry: John

In FSUIPC7, profiles can only be loaded for specific aircraft. This is not the case in MSFS - you have to manually switch profiles. So, if you are using MSFS to control your TQS for some aircraft, and are using FSUIPC7 for other aircraft, then you need to make sure that you do not have dual assignments, i.e. have an axis or button assigned in both FSUIPC7 and in MSFS. To do this for axis, in FSUIIPC7 you can create an empty axis and axis calibration profile for the aircraft for which you are using MSFS assignments. In MSFS, you will have to create a new empty profile for your TQS, and manually switch between this and your TQS default profile, depending on which aircraft you are using and if it is assigned in MSFS or FSUIPC. I believe that having aircraft-specific controller profiles in MSFS is in the feature wishlist and is in the Planned stage. Not sure on the timescales for this to be developed/released though. John

Please see the documentation provided - in this case the Installing and Registering FSUIPC7 guide, section Invalid Key Problems. The problem will be that your VC++ redistributaables will need updating. Please also check the documentation and the support forum for similar issues before posting. This same question has been asked many many times... John

I also posted this yesterday - but in the wrong thread (sorry about that!) : I also found other threads with the same issue, e,g, So I don't think the solution I proposed will work, but please still try that and let me know. Seems to be an issue with this device for some reason. if this doesn't work, which I suspect due to the other posts on this issue, I will take another deeper look next week sometime. John

First, open the windows regedit program and take a back-up of your registry and exit - you should always take a back-up of your registry before making any changes. Next download and run (i.e. double-click in Windows Explorer) the attached .reg file - this will remove the current registry entries for those xbox devices. Then, reboot your PC and start FSUIPC7 and look at the log file to see if this has corrected the issue. If not, please show me your updated files (for FSUIPC7 only - they should be the same in FSUIPC4 but if not we can look at that later). John removeXboxDevices.reg