John Dowson

Blimey, don't know how that happened....! Corrected, please try again... John

So AppPath exists under HKCU Software\Lockheed Martin\Prepar3D v5. I have no idea why the installation is failing for you then. It doesn't matter what the value is, it just checks to see if that exists to make sure P3Dv5 is installed. Very strange... Did you try the updated installer I posted?

Please try the attached version, v7.2.16b. In this version you can set the ini parameter MaxNumberOfCustomEvents in the [General] section of your FSUIPC7.ini. The default value is 2048, minimum allowed is 1024 and current maximum is 8192 (I can increase this if/when needed). John FSUIPC7.exe

Please also try that link again - I have updated the installer with the same change as I previously made - you will get the same message but the installation will/should continue. John

Can you tell me what registry entries you can see? The installer is looking under: HKCU Software\Lockheed Martin\Prepar3D v5 for entries AppPath or SetupPath. Thanks, John

But if this is not an issue in P3D / FSUIPC6. then it must be related to the timing differences between when FSUIPC is an embedded dll and when it is a standalone executable. Have you tried similar tests with FSUIPC6? If not, can you also do that to see how the logging differs. This is an area of the code that I am not currently familiar with, and it is difficult for me to investigate not having any VRI (or com) devices. I will take a look at this, but I am afraid it will have to wait for a while as I am busy with other things at the moment. I will take a look at this in more detail when time permits, most probably after the next FSUIPC7 release, hopefully ready in a coupe of weeks. John

Maybe, I haven't checked, but you can handle this in one of two ways: 1. If you are calibrating the axis in FSIOPC, just reverse the axis 2. If you are not calibrating, you can reverse the axis by adding an axis scaling parameter of -1 to your axis assignment entry in the FSUIPC7.ini file. See the section Additional parameters to scale input axis values on P40 of the Advanced User guide. John

I think I will leave this as 2048, by default. I will look into adding an ini parameter to allow this to be configured on a per user basis. I am also looking into other ways to provide access to certain custom events (e.g. Mobiflight) directly via calculator code, and allowing the user to define their own events based upon parameterized calculator code. John

I have now got a spad.next license and will take a proper look at this issue in the coming days and let you know. John

Just copy the FSUIPC6.key file to your new installation folder. No need to re-register. Registration just creates that key file. Also copy you FSUIPC6.ini file (and any .mcro, .lua or .dll files that you may use) if you have any previous assignments in FSUIPC - that is where they are stored. John

I have validated your details and they are fine. Please follow the provided instructions. Most probably you need to install the combined VC++ redistributable package.

That is for FSUIPC7...I have moved your post to the FSIOPC7 sub-forum. Please post in this sub-forum for any issue relating to FSUIPC7. Did you follow the advice I previously posted: ?

I removed this as it contained your registration details. NEVER post your registration details. This violates the license agreement and if you do this again I will invalidate your registration. What version of FSUIPC are you using? If using FSUIPC7 (then you also posted in the wrong forum!), did you read the section on Invalid Key Problems in the provided Installing and Registering FSUIPC7 pdf? If not, please do that and follow the instructions there. Otherwise, please let me know your order number and I will check them here. John

I have just pulled out my old saitek switch panel to take a look. It is not recongised natively by FSIOPC so you do need to use SPAD or SPAD.next (NOT the saitek drivers though - I remember there were always issues with those, unless they have been updated....). I just tried SPAD and that no longer works (crashes with a subscript error). I did have SPAD.next which I used with these panels several years ago, when I used this with P3Dv4, but I don't have a license to check SPAD.next with MSFS / FSUIPC7. You should really talk to the SPAD.next developer. If you continue to have issues, I can see if I can get a SPAD.next license for MSFS and take a look. John

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