John Dowson

First, remove the calibration on the elevator axis in FSUIPC's calibration window (by clicking Reset), or remove the following line from the [General] section of your FSUIPC7.ini file: Elevator=-5982,-512,512,16380 If you still see issues, try switching to using the 'Direct to FSUIPC Calibration' assignment option for the elevator assignment, and then calibrate your elevator axis in FSUIPC. If you still have issues, activate logging for axes controls and produce a short log file where you start MSFS/FSUIPC, load your aircraft, and then slowly move your elevator/pitch axis through its full range. Then exit FSUIPC and show me your updated FSUIPC7.ini and FSUIPC7.log files.

I did some more checking on this. There is also an lvar called ENG FUEL VALVE. However, no combination of setting lvars and sending controls seems to have any affect on the condition lever. i have also looked at the MSFS assignments. If you search for 'condition' you will find that there are many controls that should control this lever (under the CONDITION LEVER settings): Increase/Decrease Condition Lever Increase/Decrease Condition Lever 1/2/3/4 Condition Lever Low Idle Condition Lever High Idle Condition Lever Cut Off Condition Lever 1/2/3/4 Low Idle Condition Lever 1/2/3/4 High Idle Condition Lever 1/2/3/4 Cut Off Condition Lever Axis Condition Lever 1/2/3/4 Axis I have also tried assigning to some of these controls (in MSFS) but also with no success. It therefore looks like this is currently not possible. If you could assign to this in MSFS, you would be able to assign in FSUIPC. I think you need to report this to Asobo if you want this corrected. John

Then this is a PM issue - did you ask them about this? Ok - as 0x5648 is a PM offset, I guess that is what PM is using for this. Strange though. Thanks for the update. Regards, John

I have done this now and it seems to work as expected in the few default aircraft I tried. As I said, I suspect that ProSim (especially the new version) is using its own electrics implementation, and so this function won't work with that add-on, sorry. John

That does sound like good progress! Maybe the lua can be adapted? Could you post/attach the reverse toggle lua, or provide a link - I can take a look if/when I can get the CRJ installed and working properly... Ok. I can't really help with this aircraft, sorry (not that I have helped much with the CRJ up till now!). Ok, that would be good to know if you can track this down. Ok, thanks. This is different from what I am seeing, but I don't think I have the CRJ has been installed correctly on P3Dv5... I may try switching to the P3Dv4 version while I am waiting for Aerosoft to respond, to see if I have more luck with that - I'm guessing it should be similar to the P3Dv5 version... John

Btw, if the throttle keys F1-F4 are working for you and show the throttle animation (they don't for me, but do for some according to this post: https://forum.aerosoft.com/index.php?/topic/162671-throttle-issues/), you could assign your throttle to the controls they use for different ranges of your throttle axis, using the right-hand side of the axis assignment panel. This should give you Idle ->CLB->TOGA->MAX and back, but no manual range.

Yes, I agree... I'm currently having issues installing the CRJ pro in P3Dv5. Got an error during installation regarding P3Dv4 (!), and the add-on.xml wasn't created. I created this manually, but when I load any of the CRJs I can't get any power or access to the EFB. Awaiting a response from Aerosoft on this. However, I did try to configure the throttle, but with little success. But, it does seem that thrust is applied, its just that the throttle in the UI isn't moving. If I use the default throttle keys (F1, F2, F3 & F4) I can also apply thrust, but again the throttle lever doesn't move in the UI. Does the throttle move for you if you use those keys (e.g. F4 for full power)? Is thrust applied, i.e. can you hear the throttle being applied to the engines? It looks like the throttle may be applied, but that there is just no animation in the cockpit throttle - could that be the issue? For the Aerosoft Airbus, maybe try what is suggested here: https://www.avsim.com/forums/topic/561341-aerosoft-airbus-professional-throttle-settings-using-fsuipc/ That uses multiple throttle assignments as well, as you previously tried, but has the multiple assignments in FSUIPC and not any in P3D. However, the two engine throttles are assigned to the same axis/throttle lever, not one for each engine. I will update again if/when I discover anything useful.... John

Which CRJ are you trying to set-up - the 550, 700, 900 or 1000? Or doesn't it matter (i.e. same issue in all)? Got hold of a copy of this aircraft now so I can take a look later and get back to you. John

The 'add-on.xml' is an installation method, where P3D loads FSUIPC due to the presence of an add-on.xml file in a specific location, under your Documents/Prepar3D v5 Add-ons folder (or v5). I recommend not to use this location as the actually FSUIPC installation folder as this can cause issues (especially if using OneDrive). It is far better to choose an installation folder, whether using the xml add-on method or the dll method, outside of a Windows protected folder (such as Documents or Program Files). This sounds that you changed to use the add-on.xml installation method, but you did not necessarily change the installation location, which always defaults to the previous installation location, so would have re-installed into your Modules folder. You MUST have seen this during the installation process and accepted this installation location without changing it. The uninstaller is there as that is where you installed it. If you select to install one copy of FSUIPC for both P3Dv4 and P3Dv5, then only one copy will be installed but an add-on.xml will be created for both v4 and v5. Your install log showsv4 and v5 uninstalled ok, and FSUIPC installed for both v4 and v5 under C:\Users\djzuu\OneDrive\Documents\Prepar3D v5 Add-ons\FSUIPC6 (which is a BAD folder to choose). Note that you CAN get into a bit of a mess if you select to install for both v4 and v5 and then later amend/update just one of the solutions. There will not be anything there - it will be in the location you chose as the installation folder, which is: C:\Users\djzuu\OneDrive\Documents\Prepar3D v5 Add-ons\FSUIPC6 So you really do not have any issues as far as I can see. You should really re-install into a different folder though. Also decide if you want to use one installation folder or two - if the latter, you must manually run the uninstaller before running the installer again (twice, once for v4 and once for v5). If you want to keep just one installation just run the installer again and select a different folder for installation this time. I suggest that you read the provided Installation and Registration guide. John

It is just using the text display features provided by P3D. It is explained in the User manual, with screenshots as examples with the macro names entered for Warning and Caution. Hmm, that is strange. You did press the eESC key to create the first macro before starting the second? You could also have given the same macro filename if you did this a second time, and the 2nd macro would have been appended to the same file. Anyway, glad you got it working. John

Then did you give the macro file a name there? If not, it won't have been created, and the file won't be created as there is no macro defined. Please be aware of the difference between a macro file and a macro. A macro file can contain multiple macros. This should be obvious from the documentation. You enter the name in the same box where it says 'Press TAB to test', which you said you did. Try creating it again and enter the name there, don't press the TAB key. P.S, Finishing now for the day. Please re-read the instructions and try again before posting again...

Ok, but you did say: "I have NOT used the calibration page." !

Please also see this in the documentation, if you are NOT seeing the message window to give your macro (not the macro file) a name:

No, that is the macro file name.... Please re-read the documentation and try again. This facility has been around for many years without any issues. If you are not giving the macro file a name AND each macro that you create in the file, you are doing something wrong.

But you must have given this BEFORE you created the macro...when you clicked the button to start making the macro, you should have seen a pop-up box where you enter the macro name, as described in the User guide. Did you not see this?

When you assign to Send directly to FSUIPC Calibration you MUST calibrate in the FSUIPC calibration page. That doesn't sound right at all - you must assign either in P3D or in FSUIPC, not both. I will see if I can get hold of the CRJ to investigate. John

Is that the macro file name or the macro name? Remember, a macro file can have many macros. You do not need to search your computer, just look in your FSUIPC5 installation folder (i.e. under a folder called Modules, under your P3Dv4 installation folder - here : C:\Lockheed Martin\Prepar3D v4\Modules\). Did you end the macro creation process, by clicking the End Macro Making button? The macro file is created once you do this - as explained in the User Guide: John

FYI, FSUIPC4 v4.977 has now been released.

For the stable A320neo, the MobiFlight hubhop preset list has this calculator code and comment for the A32NX THROTTLE FULL REVERSE BUTTON preset: (A:GENERAL ENG THROTTLE LEVER POSITION:1,percent) -0.1 < if{ -9830 } els{ -16383 } (>K:THROTTLE_SET) Intended for a button press. It will toggle throttle between full reverse and idle. If throttle lever is anywhere idle or above button press will activate full reverse. Pressing again will cancel reverse and go to idle. This doesn't seem to be available in the dev version. If using that, maybe ask about this on the MobiFlight discord channel. John

@light_blue_yonder Are you still having issues setting up your throttle in your add-on aircraft or is this now resolved? Did you check the thrust lever set-up document mentioned by Reingard? John

Ok, I now understand what is happening. It is actually a very old bug where an array is updated out-of-bounds, and the problem with vPilot/Squawkbox has only just showed itself due to the memory re-alignment in the new build. I have corrected this now in the attached build, which i will release officially in the next few days: FSUIPC4.dll Thanks for your assistance in tracking this down. Regards, John

It is fixed, but I won't be releasing yet as I want to understand why it broke, and if this could cause any further issues. I will let you know once I have done this. John

You didn't say you had tried anything, just that you didn't understand anything... Just look at the logging tab in FSUIPC. Check the box next to Events (non-axis controls). That will log your events. If you check Send to console window, that will open the (logging) console window. Please consult the provided FSUIPC User manual, at least initially, not google. Yes of course, what else would I be referring to? This is support for FSUIPC after all.... Skip the lvars if you are not familiar with them (although there is plenty of provided documentation on how to use these). Mouse macros are also explained in the FSUIPC documentation. John

I cannot see any spoiler assignment: ? And what is the Custom control? Did it go directly from the high number to 0? If so, sounds like the axis is registered as a digital / on/off axis. If this is the case, see: Also, try calibrating the axes you are using for flaps/spoilers first in the windows calibration panel. to see what range of values you get there. John

Ok, but this was only suggested as a temporary work-around. I will fix this, but now I know what is causing it I am trying to determine why this changed between the two builds... John