John Dowson

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

Hi @light_blue_yonder . Fis you manage to resolve your issues? I finally got the CRJ installed and working. Setting up the forward thrust seems relatively straightforward. However, for reverse thrust, it looks like you need to send Throttle Decr controls (1-4 times depending upon reverse thrust required), when at idle, to activate the reversers. Or are you calibrating with a reverse zone on your throttle axis (via the EFB)? If so, you can calibrate so the bottom part of your throttle range automatically activates the reversers.

What is the client PC on which you are running RC4 - is it DELL-XPS15 or FSSUPPORT? Your WideClient.log doesn't show any disconnects or issues, but the WideServer log shows a few reconnections. Did you try just restarting RC4, to see if the issue is there? Maybe try that next time, before restarting WideClient. Otherwise @Pete Dowson may know more - he is still in charge of WideClient. John

So the logs are from different times? Can you please confirm if this is a one off issue that happened yesterday, or is a repeatable issue that happens often or a lot. If the former, I do not know why you are sending me log files. If the latter, I need to see the WideServer.log and WideClient.log BOTH from the session where you had your issues. I am very busy at the moment and certainly won't have time to look into this for a few days (maybe next week), but I am just trying to determine if there is an actually issue to investigate. If this just happened once, yesterday, and seems ok now, I don't see any need to look into this. John

The log from what? Did you experience the issue again then? And as I said, its the WideServer.log and WideClient.log files that are relevant if your issue is with Wide Client.

Hi Ray, Nope. Probably not - the WideServer and/or WideClient.log may show something. Is this repeatable or was it just a one off? if the latter, show us the log files, otherwise I wouldn't worry about it.... John

Could you tell me what this option actually is please? I doubt it, as now FSUIPC7 is an executable, and not a dll embedded into the FS, FSUIPC7 does not have access to mouse input (when MSFS has the focus). But I can check if you let me know what the ini parameter option is that you are using in FSX/P3D. John

Yes, but either tomorrow afternoon or Friday morning, when I get a chance... John

Can you check the Windows event viewer to see if there are any crash reports, for FSUIPC6 and/or P3D, and if so show them to me. Does this happen regardless of location/airport? Is this a new issue? If so, what has changed? Also, do a full reboot and try again, if not done already...