John Dowson

Hi @light_blue_yonder, just checked this again and if I assign to "Axis ThrottleN Set" and 'Send to FS as normal axis' (no calibration), and you calibrate for 'hardware has reverser axis' and set the positions in the CRJ EFB (in options, second page), then the reversers activate in the lower part (that defined in the EFB) of each throttle axis. Have you tried this? Or is this not what you are trying to achieve? If you are trying to set this up as a type of 'reverse thrust toggle', i.e. to use the full throttle range for reversers, then this isn't going to work with this aircraft. John

Sorry for the delay in this... As Reinhard has said, your right brake calibration for the FSLabs profile looks strange (and very different from your general calibration). And it is always better to disable Linda, even if you think its not being used, as I cannot tell from the logs. You can try to calibrate in windows first (to check the range of the brake axes), but I think this is difficult/nit possible due to the need to 'press a button' to start the calibration, that normally isn't available from pedals (as far as I remember!). You could try with a stock/default aircraft. to see if your brakes work there - you can attach a log and I will take a look. Otherwise, some complex 3rd party add-ons sometimes don't work correctly when using FSUIPC's calibration facilities due to priority levels. You could try deleting the calibration for your brakes in the FSLabs profile, and re-assigning to the FS control, as opposed to 'Direct to FSUIPC Calibration'. Also, your logs show that controllers are ON in P3D. This may be ok, but we recommend that you disable controllers as P3D has a tendency to automatically re-assign your axes. As controllers are on, double check that you don't have also have assignments in P3D. John

Corrected in the attached version. FSUIPC6.dll All 3 of your attempts should work with this version. John

Yes, looks like a relative path is no longer working. I will look into this and get back to you. John

First, you posted in the Download Links sub-forum, where it explicitly states Not for support requests. I have moved your post to the main support forum. The last update to the PMDG 747 offset data was in April 2020 (in FSUIPC6 v6.0.4) - has the PMDG 747 been updated since then? Maybe you could show me the PMDG_747QOTSII.h header file that you have, and if you could identify the first offset that has shifted 4 bytes (I presume, not bits). And check that you are using the latest version of FSUIPC6, v6.1.6. Thanks, John

Hi Craig, the run programs facility should be working fine in the latest version. If there are entries in your [Programs] section then there should be log messages, even if the program was not started, so I think something else may be going on. Can you show me your FSUIPC6.log and FSUIPC6.ini files please. John

Ok, glad you resolved, but strange to bump the sane issue/topic after 9 months....! John

👍

Yes, understood. You could try sending the keypress on the button release as well as the key press, i.e. sending the control twice. You would still get the switch to the default view, but you would only have to press (and release) once. May be better and worth a try.... John

First, you posted in the FAQ section that it over 10 years old. If you would like support, and it is related to FSUIPC (or one of the other products we provide), please post in the main support forum: https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/ And please DO NOT POST a video. We require a description of your issue together with any relevant files, usually at least your FSUIPC ini and log files. Please read this: John

FSUIPC will auto-start with MSFS, if you selected that option during installation. But FSUIPC7 is quite different from other versions, in that it is no longer a dll embedded into the sim but a separate progtam/executable. When it is ran it shows a splash screen and then sits in your system tray, where you can access it, or use Alt + F (default hotkey, can be changed) to open the main window. PLEASE read pr at least peruse the User guide. You should also take a look at the Installation and Registration guide. I provide extensive documentation to not have to answer support questions such as this all the time... John

Button assignments are greyed out when they have multiple assignments. That assignment is on Joystick 4 button 8, and assigned to THROTTLE3_DECR, so must be this one: That should be obvious, especially if you check the format of the button assignments in the manuals... These are the other assignments on that button:

Strange - maybe check the power management settings on your USB hubs... I will check to see if I get the same behavior, just out of interest. I don't think it can be related to your actual trim wheel, more to do with the JF Arrow I would think... John

Strange, as they should be fired regardless of how triggered, but that must be due to the PMDG implementation. I guess its ok for you as long as you only change the state via 3rd party apps that use the custom control. You could check to see if any lvars hold the states you require, as suggested by Paul, which would be more reliable (if there are any!). John

The latest version of FSUIPC6 is only compatible with P3Dv4.3 and later. You should update your P3Dv4 installation to the latest available - there is no reason not to do this, it is a free upgrade. Compatibility with P3Dv4.1 was removed many versions ago... I cannot see how this happened after a mainboard battery change either, unless you (or your customer) was previously using an older v4.1 compatible version of FSUIPC6. Regards, John

Hmm, sounds strange - especially as you say only sometimes.... You could try logging (Buttons + Switches and keypresses) to see if the log reveals anything when you need to press twice. And what do you mean by 'first press takes me to wherever I was looking at'? If you are already 'looking at that', then do you mean there is no change in the view on the first press? Ok, but probably not of much interest. Its just a lua script that cycles between camera views. John

Adding to what Paul has said, MSFS sends various pause/unpause events while starting-up and I think the ready-to-fly flag also changes during start-up, but this behavior has changed over the various updates and am not sure of the status of this offset at the moment, I will check it when I get a chance, However, a useful offset for MSFS in 0x062B (PLANE IN PARKING STATE). This contains 1 when in the main MSFS menu system, and 0 otherwise, and so can be used as an indicator if a plane is loaded or not, regardless if the pause state. John

I have moved your post to the MSFS/FSUIPC7 forum. I don't know. Why don't you try it? I time-limited trial license is available in a post at the top of this forum. John

The events should be logged, and you should be able to intercept them using the event.control lua function, as Paul said. I don't know why you are not seeing those (or any) events logged...maybe they aren't being used? Try assigning a button press to those events, and see if they are logged when you send them. John

No, I didn't think it would make much difference... Ah, ok....I should have asked to see your logs first.... Yes, forget that version I posted - I will remove. Ok. Did you try closing the com object before FSUIPC exited? You can do this in an event.terminate function. John

These are SimConnect controls, and can be seen in the exported controls list document, in your FSUIPC document folders. No, they won't - the camera system is very different in MSFS. To implement a 'pan reset' function, you can do the following: - first, create a 'custom camera' for your view. You can do this by hitting Ctrl + Alt + a numpad key (0-9). The number will be the number of the view. You can then switch to this view using Alt + the assigned numpad key you selected - assign your button to the Alt + numpad key in FSUIPC, using the left-hand side of button assignments dialog I recently provided a lua script to cycle between views for another user - see the following if interested: John

The throttle configuration can be tricky for the aerosoft airbus. There is plenty of information on the various support forums that may help, but I don't have this aircraft and can't really advise. Also, you don't say what FS or version of FSUIPC you are using, or what type of controllers you have... The following links may help with the throttle configuration: https://forum.aerosoft.com/index.php?/topic/143380-airbus-professional-fsuipc-settings/ https://www.avsim.com/forums/topic/561341-aerosoft-airbus-professional-throttle-settings-using-fsuipc/ There are also various posts on using lvars and/or Linda with the airbus. But it really depends on what you want to achieve - your question is far too general to help any further. I suggest you try and configure and post more specific questions if you have any issues (and can't find an answer already posted!). John

No idea. I'll try switching to using an axis control here to see if its the same for me. But I don't think this is an issue to be worried about. John

But using an axis is fine. Just reverse it in a profile specific calibration for the JF Arrow. Why don't you just try that? John

No, just one of them. You cannot run both at the same time (well, you can by changing the class name of the WideClient, but there should be no need to run both...). I'm a bit busy at the moment but will post the details when I can....within the next few days, sorry but I can't do this any earlier. John