John Dowson

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...

They should respond the same in the air as on the ground... You can try logging the axes values to check that full deflection is being sent, but I don't see why it should be any different in the air from when on the ground. Are you sure its not just the aircraft handling? Have you tried any other aircraft - do they have the same problem?

It should be there as Lua CycleViews ... (amongst other entries)... Ah - you just responded and have found it - good! Sorry about that...you should really check before you buy! Your additional donation will go to Pete, as he still is on control and has ownership of FSUIPC4 at the moment. Thanks for this additional donation! Regards, John

👍

That used to be how things worked, and still is for aircraft that use the old/legacy simvars, but things have changed quite a bit with the release of MSFS2020. I still need to go through the documentation and decide how to handle the new simvars in MSFS2020. These have only been made available recently, and I still need to go through the MSFS documentation to see what I can use and where/how to store, whether I can use existing offsets or if I need to add to new offsets.

Hi Chris, please try the attached lua. You can assign it to run on a button or key press. Save it to your FSUIPC7 installation folder. You can adjust as needed - its pretty simple. Cheers, John cycleViews.lua

Yes, I know, but these do not work in the stock C152 or C152 Acrobat. At least not for me... Are you using any sort of mod or is it an add-on C152 that you are using? There is not even any tooltip when I move the mouse over those fuses.

But what did you assign to within FS2020? I can't see where to assign there to change the view....

The standard way of doing this is to use the elevator trim offset (0x0BC0) with the Offset Sword Increment/Decrement controls. See this post: John

I suspect that FSUIPC would still see the joystick input from windows, not the re-calibrated output of JoyStick gremlin. But if Joystick gremlin takes the windows input and sends that to a vjoy device, then you can then assign the vjoy axis/buttons in FSUIPC. So you would need to change your settings to use the virtual inputs rather than the windows ones. However, this is just a guess. Why don't you try it - and report back! Regards, John

To implement fast/slow turning on a rotary that has only 1 button in each direction, you can use a lua script. There is one provided, called rotaries.lua (see the Lua Plug-ins document, and the examples are in the zip file). This converts your rotary button presses to fast and slow virtual button presses in each direction, to which you can then assign your controls. John

This topic is for P3D. You have already raised a topic on failures for MSFS - please stick to that if using MSFS. Just read it! Some of the simvars (and so offsets) were working, others not responding properly which I have reported to LM. Yes, for some of them and for P3D.

How are you doing this? I didn't think this was possible in the stock C152... The BUS BREAKER PULLED is a simvar from the new electrical system and is not held in any offset. May also not be available for the aircraft, you would need to check the NEW ELECTRICAL SYSTEM simvar. I doubt the C152 uses this. John

Can you tell me how you did this please? John