John Dowson

It really isn't that difficult, you should just try it. How are your virtual buttons assigned to control the virtual camera positions? You could try activating logging for Events in FSUIPC, press those virtual buttons and see what events are logged. It is then simply a matter of sending those controls in the timer function. No, sorry. But if you activate the event logging as suggested and show me your FSUIPC7.log file, I can provide you with a basic script to send those controls on a timer for you to try. John

You can use a lua script. You can use the event.timer library function to call a handling function, in which you can send the control that changes your camera position (i.e. the control or one of the controls that you have assigned to your virtual button) by using the ipc.control function. You can either start the script manually or have it auto-ran from an [Auto] pr profile specific [Auto.xxx] section. John

No you didn't. There is only one version of FSUIPC7, which provides the unregistered facilities if no license is available, and will provide the full functionality if you add a license, either the time-trial one or a full license that you receive on purchase. You always need to download the FSUIPC7 installer, which you did. If you want to try the registered facilities, you then need to download and install the trial license as well. Ok. John

You need to look in the product description: I don't include the trial license in the download for various reasons....you have to download it separately and install it if you want to try the registered facilities. John

Sounds like you are using an unregistered version. Did you download the trial license and place in your FSUIPC7 installation folder? The trial license is available from here: Only a couple of days left on the trial license. I will update on the 2nd or 3rd of December. John

Please see the provide documentation, especially the Installation and Registration guide as well as the User guide. As FSUIPC7 is an executable, it tuns outside of MSFS. Previous versions of FSUIPC where dll's and were embedded within the FS. When you run FSUIPC7, it displays a splash screen and the iconises to your system tray. You can access it from there, or use the ALT + F hot key to display the main window, as you have found out. You cannot access FSUIPC7 from within the MSFS menu system. John

Please attach your full FSUIPC7.log file together with your FSUIPC7.ini file.

As you are using separate files for profiles, I need to see the ini for your F-104 profile. Also, your ini doesn't show much... Always close down FSUIPC7 before attaching your ini please - looks like FSUIPC7 was still running when you attached that file, or FSUIPC7 had crashed. Could you activate logging for axes controls, load your aircraft and then move your ailerons through there full range, then close FSUIPC7 and show me the FSUIPC7.log as well as your F-104.ini file.

Use the File => Open Installation Folder... menu option if you cannot remember where you installed FSUIPC7.

Ok, but sounds strange...! Sorry, missed this one.... Not relevant now your issue is resolved, but just remember not to start a New Log (i.e. don't use that menu option) when providing log diles for support. If you do, then yes - include the separate log files which are renamed with ',1', '.2', etc included in the name.

With P3Dv5, you do not need any SimConnect client libraries installed. The SimConnect server is built into P3D - which is at version 5.2.0.0, from your log: 24828 17652 Running in "Lockheed Martin® Prepar3D® v5", Version: 5.2.22.27615 (SimConnect: 5.2.0.0) and FSUIPC is currently bild against the SimConnect 4.3.x API (as it remains compatible with P3Dv4.3 and later). I am not actually using P3Dv5.2 at the moment, but I will check on my 5.2 system later today, but I'm pretty sure its not an issue there. It looks like the SimConnect call is failing for you, even though it is returning a success code. Very strange. I see you don't use the Auto-Save feature, but I suspect that would also be not working. Maybe you could try it? As this looks like a SimConnect issue, I can only suggest re-installing the P3Dv5 client (uninstall first). John

No, the issue is not present in FSUIPC6/7. What "unreliable behavior" are you seeing there? John

Please try the attached dll. I have added additional logging around the save flight calls. This is what I see when I pause then exit by clicking the red cross in top-right corner : FSUIPC6.dll John

Hi Urs, looks like this problem was introduced in v7.2.12 when I changed the method of determining the MSFS install type. Sorry about that. Should be corrected in the attached version if you would like to try: FSUIPC7.exe Regards, John

I presume that you are using an MS Store installed version, no? Could you tell me where your MSFS UserCfg.opt file is please - in your LocalState folder or LocalCache folder? Also, please attach your FSUIPC7.log file. Thanks, John

No it isn't... First, I asked for a full log file, and you provided me with a continuation log file: So you forced a new log file to be created by selecting 'New Log' when I EXPLICITLY asked you not to do this: " (do not start a new log!)" I am not going to look any further into this until you do this. And I would like to understand what is not clear about this - seems to happen all the time for some reason. I think I am going to remove this option from the menus, although useful, as it is always abused in this way, even when I ask OPs to provide FULL logs, and NOT continuation logs. Seems like you also didn't activate the log options that I advised, although I cannot tell from the files you provided.... John

Could you activate axes logging in FSUIPC7, and produce a short log file (do not start a new log!) where you move your tiller control through its full range, and then exit FSUIPC and attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look. Thanks, John

Hi Martin, Just took a look and it seems to be working ok here. Unfortunately there is no logging, error or not, around the auto-save feature. Are you sure there are no Previous Flight files under your Documents\Prepar3D v5 Files folder? If not, I can add in some logging and give you and updated FSUIPC6.dll to try to see why it is not saving for you. John

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