John Dowson

I don't know, but if using the PMDG 777, you should look at the PMDG SDK for that aircraft to see if the information is held in the PMDG-specific offsets. First thing to do is to check the PMDG_777X_SDK.h file to see if anything in there looks like what you need. John

WideFS7 is what you need then. However, this should also work with FSUIPC7 running on the client machine, and would save you having to buy an additional license. So try FSUIPC7 on the client machine first, otherwise I will look into providing you with a trial license for WideFS7. Sure. I will create a separate topic for this later today or tomorrow. John

First, you are using quite and of version of FSUIPC6, v6.0.12. The latest (and only supported) version of FSUIPC6 is v6.1.6 - please update. After updating, produce a short log file showing your issue: activate logging for Axes controls, load your aircraft and then move each brake through its full range, then exit FSUIPC/P3D and show me the FSUIPC6.log file. As you are also using Linda, it may be a good idea to disable Linda for this test. And your log shows that you have installed FSUIPC6 under your Windows Documents folder. This can cause issues - it is better to install in a non-protected folder and just have your add-on.xml file under the Documents\Prepar3D v5 Add-ons\FSUIPC6 folder. You should consider installing in a different folder when you update (and remember to move all your files across to the new installation folder afterwards). John

They are available once you have registered your FSUIPC license. You do this by tunning the installer - there is a dialog at the end of the installation process to register your license. Enter your registration details there and click the Register button to validate and generate your FSUIPC7.key file. John

No. Its just that the Pan controls are not working correctly in MSFS via SimConnect. For view controls, best to assign your buttons/switches to the default MSFS key bindings for such controls. If there is no binding for that in MSFS, you can assign a key binding to the control in MSFS, and then assign your button to that key binding in FSUIPC. Try that and let me know if thats ok, or I can look into this further for you but will take me a couple of days to get around to this (working through the support backlog!). Cheers, John

Hi Ron, Why don't you just create a profile-specific calibration for the Arrow and reverse it there? You don't need to use profiles for anything else if you don't want to. But there is no issue with creating profiles. In fact, its a good idea to use profiles for most MSFS aircraft, especially add-ons, as there are many controls that can only be accessed via lvars or hvars, and as these are profile specific it is always better to use these in a profile. I do have the JF Arrow but have not noticed this issue. I have assigned to the Bravo trim wheel, which uses buttons, so I have assigned to the trim offset for both fast/slow increments and decrements. I don't assign to the elevator trim axis so haven't noticed this issue. If interested, I shared my Bravo assignments (including trim wheel) in this post: Cheers, John

Hi Tom, Presume you mean WideFS7. That product is still with Pete. I don't think he provides trial licenses for WideFS7, but I can ask him if its ok for me to generate one for you (assuming that a time-limited license is possible with WideFS7, not 100% sure on this). You can actually now run FSUIPC7 in a client machine. This is experimental and undocumented, but allows a full copy of FSUIPC7 to be ran on the client machine. It is different to the WideFS solution in that it will maintain its own offset table, and doesn't communicate to FSUIPC7 on the FS machine. However, all offsets populated by the FS should be available and the same. I have been meaning to create a post on how to set this up and use FSUIPC7 on a client machine for a while but have not had time yet. I could do this soon (i.e. in the next few days) if you would like to try this. Regards, John

Hi Gary, ok, no problem - glad you have found the cause of your issue, and thanks for reporting back. Cheers, John

Could you also attach your FSUIPC7.JoyScan.csv file please...

Could you attach your Runways.txt file please, if that exists (you can zip it if its large). Also, if there is a MakeRwys_Scenery.cfg file produced in the P3D root folder, please ZIP it and also attach. Thanks, John

Hi Torsten, please try the attached version. Let me know how it goes, and check your FSUIPC7.log file for a message starting '*** Calling OpenHid with ...' and post that if you have issues. BUT, looking at your HIDScanner output, it seems as of the issue is with the Manufacturer, Product or Serial number (and/or GUID, which seems to be the same for both cards), which are all null/empty. Even though the VID is 0000 (which IS ok, as your USBKeys card IS recognised), there is still a unique product ID for both cards. Given that, I don't hold out much hope. Have you tried OpenCockpits support to see why these fields are not being populated? John

Ok, sorry - missed that. And you are providing too many log files... I am only interested in seeing the latest ones, with P3Dv5.3, and I will take it from there. Your issue is very strange, not heard of anything like this before...Will probably need more logging added to trace this., but I'll wait until I see your initial log files. Also, please attach your FSUIPC6.ini with your FSUIPC6. log file. John

Your registration details (including key) are available from your SimMarket account, where you purchased the license. John

This sounds contradictory - does the firmware for UBSKeys (USBkeys?) have a vendor if or not (is it 0000)? Then I think you should contact the vendor to see if they can add a correct VID/PID for this card.... Yes, that is entirely possible and probably... I am not happy with this change, but I could provide you with a version where the null check on VID/PID is removed. I cannot test this though, but if it works for you then I could allow this on a new ini parameter. I'm pretty busy at the moment, but I'll provide you with an updated FSUIPC7.exe to try within the next few days. If I haven't posted by Monday, ping me a reminder.... John

The trial license has now been updated, valid until 30th December 2021. John

You cannot just install the P3Dv5.3 client - you need to uninstall P3D completely and install the full P3Dv5.3, including scenery and content. From the P3Dv5.3 release notes (https://www.prepar3d.com/news/announcements/2021/12/120925/😞 Please do that before I look at any of your logs. Thanks, John

If you want larger trim increments/decrements (deltas) for each button press/release, you can assign to the trim offset 0x0BC0 using the offset sword increment/decrement controls, and give the inc/dec delta that works for you. If you are not sure how to do this, check the user guide and this forum - the same question has been asked many times before! For example, this post has detailed instructions on how to set this up: John

What don't you understand? Just follow those instructions to monitor offset 0BD0, then move your spoilers through its range, then exit FSUIPC and attach your FSUIPC4.log file. John

Hi Ray, If you continue to get issues, you could maybe try setting the ReconnectMinutes WideClient ini parameter:

@General Novais Could you let me know which C152 you are using please - as I asked: I need to get the fuses jumped in the UI before I can let you know how you can do this programmatically (or via FSUIPC). John

Its John, not Pete!. P3Dv5.3 has also now been released, so also update and try with that before reporting back. John

Ok, thanks, And please make sure they are using the latest version of FSUIPC6. and get them to check/validate the license during installation. Temporary/time-limited licenses will not be validated by the installer, but if the user has a full license they can validate the details at the end of the installation process . John

First, you are using an old version of FSUIPC6. The current version is 6.1.6 - please update as only the latest version is sipported. But what exactly is the issue? I cannot help if you do not let me know what the problem is. Maybe check (and attach) the FSUIPC6.log. If its a registration issue, you (or your customer) needs to re-run the installer to register the purchased license (and remember to click the Register button to generate the FSUIPC6.key file). John

That option is no longer available in FSUIPC7 as the mouse-look (and mouse-move/trim) functionality is no longer available, due to the reasons previously mentioned. John

Ok, then these are the relevant WideServer log entries: The line in bold shows the disconnection, but I suspect that is from when you closed WideClient and then restarted around 29seconds later. Lets see what Pete has to say... John