John Dowson

Thanks for the feedback. These changes will be incorporated into the next official FSUIPC7 release. Regards, John

If you do have SPAD working with MSFS / FSUIPC7, then the gear lever offset is 0BE8, with value 0 for Gear Up and 16383 for gear down. John

Ah, but from your image I see that you are using SPAD and not SPAD.next... I don't think the orifgnal SPAD works with MSFS - I did try this but couldn't get it to run. The development on SPAD stopped in 2012, over 10 years ago. I suggest you try SPAD.next if using Saitek devices such as the multi-switch panel or radio panels. These will not be recognised by FSUIPC. You will have to pay for a license, but it does also come with presets for many aircraft, and I would consider it essential if using Saitek devices (other than the throttle and joysticks, X52, X56 etc, as these can be handled by FSUIPC). John

I have also switched the assignments to use the sim events directly rather than FSUIPC offsets, and this also works without issues: John

So, I installed SPAD.next. Configured it to use FSUIPC, loaded a default profile for the C172 then tried this in the JF Piper Arrow and the landing gear lever on the saitek multi-switch panel works as expected. Here's the SPAD.next configuration for this lever: John

What does this mean? Alt + F just displays and hides the FSIIOPC main window. You can see the FSUIPC7 main window can't you? The image you posted above shows it is displayed. What exactly is your issue? Is it that - FSUIPC7 doesn't auto-start with MSFS? If this is the case, show me this file: C:\Users\Admin\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml - there is no Assignments menu? Your log shows that your copy is FSUIPC7 is registered, even though your folder listing doesn't show am FSUIPC7.key file. However, it MUST be there as your lof states it has found these details: - FSUIPC7 exits/quits while MSFS is still running? If so, add this to the [General] section of your FSUIPC7.ini: DisableMSFSMonitor=Enum (see point 5. under Problems running FSUIPC7 in the provided README.txt). In fact, you should do this anyway as running under Windows 11. If you are experiencing strange issues, I also suggest that you install the latest combined VC++ redistributable package from Microsoft. Uninstall any individual packages first an then install the combined package - again, see the README.txt, item 1 under Problems running FSUIPC7. John

Great! Glad that issue is sorted. Cheers, John

I just disabled the abort when no P3Dv5 installation was found and set the flag that it was actually found (i.e. a hack!) If you re-installed windows, did you also install the latest combined VC++ redistributable package? If not, please do that - that may be the issue. John

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