John Dowson

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

I don't think there is a P3D Auto-Save feature, is there? Or do you mean the 'Prompt on exit' option? I have just tried with that unchecked and I see the same behavior - the call to save the previous flight succeeds but no previous flight file is created. No, I don't think so unfortunately. I can report this to LM. If the flight file is not saved as requested, I would at least expect the return status to indicate a failure. However, a suspect that this is due to the asynchronous way the messages are processed - without the pause (prompt on exit), the P3D is not able to process the save flight request before it quits. I hadn't noticed this behavior before. I will mention in the documentation. John

There probably is no offset for this. You first need to determine what, if anything, holds the condition of the fuses, and how to change this. Which FS are you using - MSFS? If so, I would first check to see if there are any relevant lvars for this. You can do this in FSUIPC7 via the Add-ons->WASM->List Lvars menu item. If any look applicable, you can try setting them to change the state, using the Add-ons->WASM->Set Lvar... menu item. There is no such thing. Offsets (mainly) hold simulator variables, or simvars, not actions. You can check the offset documentation to see what is available. But, it always helps if you let us know what FS and version of FSUIPC you are using. I have moved your post to the FSUIPC7/MSFS forum for the time being. John

First, you posted in an unrelated sub-forum (.Net dll cleint) and gave a title that means nothing ("Hi"). I have moved your post and updated the title, but please take care to post in the correct forum, as well as giving your post an appropriate title, for future posts. Open your FSUIPC7.ini file (located in your FSUIPC7 installation folder) in an editor (e.g. Notepad++) and remove the [Axes] section. You can also remove any [Axes.xxx] sections (where xxx is the name of a profile) if using FSUIPC's profiles. It will be regenerated (with no assignments) the next time you run FSUIPC. John

As I say, easier to check this while stationary on the ground, and logging the axis (with the console open) will allow you to see the values in real time and compare to the deflection/movement you see in MSFS. If the visuals don't correspond to the values seen, try switching to one of the FS Aileron controls (and try the different ones to see if they make a difference).

First, the next time can you please attach your full FSUIPC7.log and not start a continuation logfile (DO NOT select the New Log menu entry!), and also exit FSUIPC before attaching your log file. There is information at the start and end of the log that I need to see. Did you activate event logging as suggested? I can only see that you have enabled logging for Buttons + Keys, wjich is not what I asked, and I cannot tell if you enabled logging for Events as you only provided a continuation log. Well, the log shows one (Left) ALT + 1 keypress, but the second keypress is ALT + 2. What is the complete sequence of keypresses - any more? Anyway, please try the event logging, as suggested, and show me a full FSUIPC7.log file (you can keep the button _ key logging activated). I would like to see if any events are logged, as I would prefer sending these controls directly. However, if non are logged (which means they are internal events only and not available via SimConnect) then the lua can send the keypresses instead. That should be fine. You probably want to kill the script on a press of a button as well, no? Or do you want it to cycle through the views and then stop (or repeat)? John

Treat yourself to a decent powered hub (or PCI card) for christmas! There are various recomendations if you search the forum (and probably more on avsim.com). This is the one I currently use (and have not had any issues): https://www.amazon.es/gp/product/B0797NWDCB/ref=ppx_yo_dt_b_asin_title_o03_s00 John

No need to do a flight - you should have just sat on the runway and moved your ailerons through their full range... However, your logs do show that your ailerons are moving through the full range: You are not using the full range of your controller axis as this is your aileron calibration: i.e. maximum negative deflection (-16384) is achieved when your controller reaches -14255, and maximum positive deflection (16384) when your controller reaches 14364. You could try re-calibrating, if your aileron axes goes to -16384 and +16284. You can also try calibrating the axis in windows game controllers first if not seeing the full movement range. You are also using a slope on your ailerons: You can also try removing that if you are having issues - you can always add it back later. Other than that, your aileron axis seems ok from the logs, and I'm not sure why you think they have "stopped responding". You can always open the console log and see the (logged) values being sent in real time. Maybe do this with an outside view of the aircraft so that you can verify that the ailerons are moving through there full range - easier to do while on the runway than when in the air! Other than that, some add-ons don't play well when sending to FSUIPC calibration. If that is the case, you can try assigning to the FS control instead (and not Firect to FSUIPC Calibration) and remove the calibration entry for the ailerons, by clicking Reset in the calibration panel. John

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.