John Dowson

Yes I did. It may be a good idea for you also to report this. John

No, sorry I was mistaken. This lvar doesn't exist for those aircraft. It appeared that they did, but that was because I had the FBW A320 installed in my Community folder and I had forgotten top remove this before checking. John

Hi Emile, I am reluctant to change the functionality of the existing master battery offset, 0x3102. However, I could add a new bitwise offset that would hold and change the state of the different indexed batteries. However, there is an issue with this. The problem is that if I request the ELECTRICAL MASTER BATTERY simvar for indices > 1 and only one battery is available, this will not produce an error but will flood the MSFS logging console with error messages, making the logging console impossible to use. This was an issue when I recently added offsets for FUELSYSTEM PUMP ACTIVE and FUELSYSTEM PUMP SWITCH for indices up to 16. To get around this, I added a new ini parameter NumberOfPumps that controls how many indices of these simvars are requested. This applies to all aircraft, so it is not an ideal solution, but there is no way that I know of to determine the actual number of pumps available, and for this update there would be no way to know the number of batteries available, and so there is a similar issue. Not sure what to do about this at the moment - I will have a think about this.... However, there may be an alternative solution. For example, in the C172 there is a lvar XMLVAR_BatterySTBY_SwitchState. You could add this lvar to a free FSUIPC offset (using the lvarst-to-offsets functionality) and read the state of the standby battery from that. If the lvar is writeable, you can then also write to the offset to switch the standby battery on and off. The same or a similar lvar may also be available in the SR22, although I haven't checked this. I am planning on going through the MSFS documentation on available simvars (and events) this week (hopefully!), to see what new simvars and events are available. I will consider this request again once I have done this. Regards, John

Throttle axis animation seems to be broken when assigning this via simconnect (i.e. using any external program). I don't think there is anything that can be done until MSFS/Asobo fix this. John

Sorry, forgot about this. I don't know much about using VRInsight devices (I don't have any!) so can't help you with this. Maybe @Pete Dowson can shed some light on this. John

Hi Andrew, That was the delay that worked for me around 6-8 months ago. This will depend on many things (hardware, software running, MSFS version, FBW version, etc). It is up to each user to determine what delay works for them, and this should be checked on each MSFS release and for each aircraft update (for the aircraft you are using). I am not going to be checking each aircraft on each release to determine what this should be, it is up to the user. I guess I could add this. But only when using that menu option, not when using the control. I will add in the next release. John

So, the 3-position button should indicate what the middle SEL button does. So, you should program the SEL button for one function, eg. for altitude you would assign the left/right buttons to Ap Alt Var Inc/Dec. Then, comment out these assignments, and then assign to the second function, HDG/TRK, by assigning to the Heading Bug Inc/Dec controls. Again, comment out these assignments when done, and then assign to the third function, IAS/Mach, by assigning to Ap Spd Var Inc/Dec. Once you have assigned all three, you can edit your FSUIPC ini file to add a Compound Button Condition on those assignments to the state/position of the 3-position button. See the Advanced User Guide on how to do this. The controls I mentioned in the above are the default P3D controls for these functions. These may not work in all aircraft or the aircraft that you are using (you do not say!). It is up to you to determine what controls should be used for each function. If you are not sure, you can operate each function in the aircraft UI and see what events are logged - turn on logging for Events in FSUIPC and open the logging console and you can see what events are used when you activate these functions. John

What does this mean? FSUIPC7 is a separate executable, it starts and iconises itself to your system tray. You can open it from there, or use the default hot-key Alt + F to display the FSUIPC7 main window. Your FSUIPC7 installation is in C:\FSUIPC7, not Z:\FSUIPC: Reading options from "C:\FSUIPC7\FSUIPC7.ini" The log file you attached is very short - did FSUIPC7 crash or was it still running when you attached the log file? Maybe check the windows event viewer to see if there is a crash event. And try starting FSUIPC7 manually (by double-clicking the FSUIPC7.exe) to see if it runs ok. If not, you may need to uninstall/update your VC++ redistributables - details in the provided README,.txt. John

Did you read the comments in this topic? So, did you have a plane loaded and ready-to-fly? There is no menu entry when you are in the MSFS main menu - you need to load an aircraft. John

Pete helped you out with offsets for your Parking brake - see You don't need to use offsets for the gear ip/down - the standard controls work. Just assign to those - if the saitek gear lever is recognised....i did ask:

The log file would have been in the same place, but it was removed when you uninstalled FSUIPC6. However, the FSUIPC6.dll should also have been removed when you uninstalled - the .key and .ini files are not removed when you uninstall, as these are needed if/when you re-install. Not sure what is happening in your case, but the uninstall log should tell you what files were removed. Check which options you want to install. If you are not sure, just install everything, i.e. leave the defaults. This is not the case. The FSUIPC6 option is always checked and grayed-out - you cannot uncheck this. Please see the Installing and Registering FSUIPC.pdf for details on the installation process. Once you have installed (choose a non-windows protected folder outside of your P3D installation folder), copy/move your FSUIPC6.key and FSUIPC6.ini files to the new FSUIPC6 installation folder. You can skip registration when you install. John

Make sure 'Hide extensions for known file types' is unchecked. That is most probably your reason. I am not here for windows help, just FSUIPC.... John

Depending where that is, it shouldn't be a problem. But always better to install in a different location. The log and ini files will be in the same location as the FSUIPC6.dll. There is nothing more I can say on this issue... If you still can't find those files, show me your InstallFSUIPC6.log file. That will also be in the same location.... John

I can see this for the number of your posts - 4.1k - quite impressive! Let me know if you need assistance. Regards, John

Ah, one more thing that is relevant to this request.... Currently this facility is only available to registered/licensed copies of FSUIPC. I can allow this facility to be used in unlicensed copies if needed/requested. I have no issues allowing this. I was previously going to allow this but decided not to due to some strange responses from other freeware developers when I broached this subject... John

Hi Volker, I will not be adding/allocating offsets for lvars for specific aircraft. If I started doing this, there would be endless requests for this in MSFS - I hope you understand this. I have implemented a mechanism to allow users to add any lvar to a free offset area. This is, hopefully, relatively straightforward to do. Please see the Advanced User guide, P44 section Adding Lvars to Offsets. If you have any issues doing this, I can help. To be clear, this post concerns adding simvars, or A type variables, not any other variable types. Regards, John

Where have you installed FSUIPC? If you have installed in a windows protected folder, such as under Documents or Program Files, then re-install under a different location. There must be an ini and log somewhere, or FSUIPC will not function as expected. Try re-installing in a different location. I really cannot help you without seeing these files, and they must be in the same location as the FSUIPC6.dll, the FSUIPC6 installation folder. John

Activate logging for Buttons & Key presses in the FSUIPC logging tab, and also activate logging for events to see the events from the FS. Yes - use the DontLogThese ini file option - see the Advanced User guide for details. Many aircraft, especially in MSFS, continually send various events, which are different for each aircraft. You can ignore these by using that ini parameter, best used in the [Profile.xxx] sections as they are different for each aircraft. John

Do you have an FSUIPC4.key file in your installation folder? The error message indicates that this file is not available. Have you tried entering your registration details again to validate/re-register?

So the gear lever button isn't recognise, in FSUIPC SPAD.next or the sim? Are the other buttons/switches recognised? If it is just the buttons for the lever, then this would indicate that the buttons on the gear lever are no longer working. Does it still work in FSX? If so, and this is configured in FSUIPC4, then the same config should also work with MSFS. And are you assigning in SPAD.next or FSUIPC? If assigning in SPAD.next, then you should contact support for that program. John

Your log and ini files will be in the same folder as the FSUIPC6.dll. As I said: Check if you have numlock on or off - this will affect what is being sent when using the numeric keys. John

Have you assigned the switches in FSUIPC? Does FSUIPC recognise the switches so that you can assign? I really think that you need to contact support for from OpenCockpits on how to configure this device. Have you tried that? John

Me neither! Let me know how you get on. I could look into adding an MWV sentence at some point if absolutely required, although I'm not sure when I will have time to look into this at the moment. I will add it to my 'todo / to investigate' list, and let you know when I get time to look into this in more detail. I am currently very busy just keeping up with the MSFS releases (as well as the P3D ones....)! John

Then maybe ask in that forum about this... I can't really help when you just keep saying 'it doesn't work'. What are you trying to do exactly with FSUIPC? What gave you tried? Are you talking about a button or key press, or something displayed? I really have no idea what your issues is at the moment... If using PMDG aircraft, then many standard offsets and controls do not work. To use this aircradt with FSUIPC, you need to use the provided PMDG SDK (custom controls), and for display/output/.read offsets you should look at the provided document Offset Mapping for PMDG 737NGX.pdf. Maybe also take a look at this FAQ entry: John

FSUIPC will not affect any features like this in P3D. Maybe try renaming the FSUIPC6.dll to FSUIPC6.dll.unused (temporarily) so that it is not running to see if this is still working as you expect in P3D. So shift+2 is assigned to accomplish this (default assignment) in the sim? This should still work, unless you have changed this or assigned the same keypress in FSUIPC. So you had the red button assigned in P3D to achieve this? Did you assign to the same control in FSUIPC? Do you have controllers still active in P3D or are they disabled? I am still unsure of what your actual issue is, or where your assignments are. Can you attach your FSUIPC6.log and FSIOPC6.ini files which may give me more of a clue as to what you are asking... Your FSUIPC6.log and FSUIPC6.ini files are located in your FSUIPC6 installation folder. If you do not know where that is (you should do - you installed it and chose or accepted the default installation location...) then use the Open Folder button in the FSUIPC6 logging tab. This will open a windows explorer panel showing the FSUIPC6 installation folder. If you cannot see the .log and/or .ini files, you have explorer configured to hide known file types. Change your explorer options so that you can see the correct file extensions (consult the appendix in the installation manual if you do not know how to do this). No idea what this means! What 'signature'? John