John Dowson

Once you have one assignment to the buttons - all three (left rotate to decrease, right rotate to increase, push to select), you comment-out those assignment lines in your FSUIPC6.ini file. You do this by inserting a semi-colon (;) after the index number of the assignment. After doing this, reload your assignments for this to take affect. This will then allow you to assign for the second function, HDG/TRK. Once you have assigned for that, again comment out those assignment lines in your ini file, reload your assignments, and assign the third function, ALTITUDE. Once all are assigned, go back to editing your ini and uncomment the previous assignments (i.e. remove the semi-colons you previously added). Your buttons are then programmed for all three functions. However, as you have multiple assignments on the same buttons, all will be sent at the same time. You then need to add a compound button condition, so that only the correct control is sent depending on the position of the selector switch. This is what is described in the Advanced User manual under Compound Button Conditions. Basically you add a C to the beginning of the assignment (to indicate that it is a compound assignment), then you need to add details of which button the assignment depends on, in the format (+j2,b2) which means that button b2 on joystick j2 must be "on" for the assignment to take effect. Your selector knob will have three buttons associated to it, with only one being active/on at any time. John

There are also some log settings you could try which may help to see what is happening with the missing inputs. Try setting the Log -> Custom value to x2044. This will probably generate a lot of information. Try setting this just before you do your tests, then clear afterwards. If there is too much logged that makes it difficult to see what is happening, you could also try the individual log flags, which are: #define LOG_VRICOM 0x0040 // 4 #define LOG_COMDATA 0x0400 // 64 #define DEBUG_COM 0x20000 // 8192 John

I've talked to Pete about this. The read/write sleeps are set to 10ms, so the poll rate is around 100 times per second. The code for this is identical in FSUIPC6 and DSUIPC7, so any differences will be to do this FSUIPC6 being an embedded dll and FSUIPC7 being a separate executable. He also says: Maybe you can show me a log file showing this, although I don't think there will be much I can do about this... John

Ok - I have moved your post to the sub-forum for FSUIPC7 / MSFS support. I've checked the code and there was also a maximum limit of 1024 events loaded from event files. I have increased this to 2048 in the attached version. I will also update the documentation to include this limit. John FSUIPC7.exe

As the documentation states, you should be able to have up to 128 event files. Can you please attach your event files (all 5) and I will take a look. John P.S. What FS and FSUIPC version are you using?

Ok, thats interesting - thanks for the info. John

I don't know why this is, but if it isn't being recognised, it cannot be assigned. Are you using the latest version of FSUIPC7, v7.2.15? If not, please update. Also, try without running SPAD.next, to see if that is interfering somehow. Also, if you using any saitek drivers or running any saitek software, please uninstall these and let windows install default windows drivers. But if you are assigning in SPAD and not FSUIPC, which it sounds like, why are you not talking to SPAD support?

Possibly. Please leave it with me. I currently am getting no time for such changes as I am getting too many support requests, which always take priority over new development... John

For PMDG aircraft, you need to use PMDG custom controls and offsets for many things. Please see . No, sorry that is not possible. I provide user manuals so I do not have to do this. I do not have your hardware or any PMDG aircraft. FSUIPC is a tool and we provide instructions and help using this tool. I just dont have the time to provide step-by-step instructions for every FSUIPC user and for aircraft and controls, especially those that I do not have. I am currently spending all my time answering support questions, many of which have been either asked before or whose answers can be found in the provided manuals. This is currently preventing me from doing development in these products (i.e. keeping up with new FS releases, adding new features and improving the documentation). I really need to reduce the time I am spending in support, and cannot provide such detailed support for an individual user - if I did this there would be no end of requests and I would be spending all of my time setting-up other peoples systems. John

Please do not attach pictures - they tell me nothing - I cannot really see anything in that image die to the resolution. ALWAYS attach files, not screenshots of files. Your log file is very short, again. The ini file you attached is empty and is for an unregistered version, however the log file you attached shows that your FSUIPC version is registered. Are these files both from the same folder? Then you either did not install the auto-start component, or your EXE.xml file is corrupt. Check your InstallFSUIPC7.log file - that should tell you the issue. I think that may be included in the creenshot but there is no way I can read that - why didn't you just attach the file? I have really no idea what you are doing and why you are getting into such a mess. Did you previously have assignments in FSUIPC? If so, locate the ini file with the assignments and copy it to your new installation folder. If you are changing installation folders, you need to move certain files across (.ini. .key, .lua, .macro, .dll) otherwise you will lose your settings. I suggest that you uninstall FSUIPC7 again, using the provided uninstaller or using the Windows app management panel. Then locate your FSUIPC7.ini, FSUIPC7.key and any other files you are using (.lua, .macro or .dll) and place them in a folder where you would like to install FSUIPC7. Remove all other FSUIPC7 folders - you only need one and I think you are getting confused as to where things are installed. Run the FSUIPC7 installer, and select that folder (the only FSUIPC7 folder with your .key and .ini inside it) for you installation folder. This should hopefully give just one copy of FSUIPC7, so we can get rid if that confusion. If FSUIOC7 doesn't then autostart, check your Installation log and EXE.xml (the location of this will be logging in the installation log). If the EXE.xml is corrupt, you can delete/rename it and re-run the installer and a new one will be created. Then, if you still get any issues, show me your files again. Please make sure that You have exited/quit FSUIPC7 before attaching your files. John

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