John Dowson

A new version has been released that contains: - a fix for the compound button issue mentioned above - a correction to an offset monitoring panel issue - a fix for a bug that prevented axes working when FSUIPC7 started when MSFS already running with a flight loaded I have also changed the version number for this release, and the beta release for 128 button support is now version 7.1.0a. Please see the announcement to download the latest version.

v6.0.14b has been released with - support for compound buttons - correction to offset monitoring issue

You can just re-install in the same folder (that will be the default), and then everything should work.

All looks good now. You can just delete that missing joystick in your ini.

👍🙂

Its an attached file. You should be able to download by just clicking, but if that doesn't work then right-click and select 'Save link as...'. If you still have issues, disable any antivirus software or add an exception.

Yes, I don't see why not. Depending on the app, but if it uses offsets then you can use the general control offset at 0x3110 with control number 68536. For the control numbers for each event, there should be an automatically generated document in your FSUIPC7 documentation called Controls List for MSFS Build 999.txt, which shows the control/event numbers, i.e. 68536 TOGGLE_AIRCRAFT_EXIT_FAST John

@jaxx Please try the attached version, although I haven't tested a plane switch. Its still v7.0.7 unfortunately, but with a build date of 19/03/2021, as I released the 128 button support update as v7.0.8a. I'll revise this tomorrow and release this as v7.0.8, and merge these changes into the 128 button support release and re-release that as 7.1.0a, but tomorrow or Sunday now. If you could test this before then, that would be good, Thanks, John FSUIPC7.exe

Please try with the latest version - Its still v7.0.7 unfortunately, but with a build date of 19/03/2021: FSUIPC7.exe I'll probably release this officially as 7.0.8 tomorrow...

Martin, events issued by MSFS are pretty mixed-up and difficult to use to determine that actual state, and this changes with each release. And FSUIPC7 has to try to determine the correct state in ALL situations, from having FSUIPC7 running before starting MSFS, having MSFS auto-start FSUIPC7, or starting FSUIPC7 when MSFS is already running, either in a menu, a flight, or in some other state. And when the WideServer component is started is also dependent on these things. So, if you have an issue, I need to : - know when and how you are starting FSUIPC7 - know the state of MSFS (in menu, flight, or elsewhere) when you try to connect - see your log files, especially your FSUIPC7.log file Also note that there is currently an issue with the latest 7.0.7 release where things are not being started correctly if FSUIPC7 is started when MSFS is already running and a flight is loaded. This probably also affects WideServer, although i haven't checked. So, please wait for further tests until i have released an update for this, either later this evening or more likely tomorrow now. If you are not using that version, then you should really update, but may as well wait now until I have released the update. John

Ok, thanks for the update.

Your GUIDs have changed, and as a result your ini ids are in a mess. You really need to enabler "JoyLetters" BEFORE you do these sort if changes. I can sort out this mess for you, but, as Pete said, we also need to see your latest FSUIPC6.log files, as well as the inis. We need to see them together (ie. generated/uploaded at the same time - they change each time you run FSUIPC or the FS). So, please upload your log and maybe also a new ini and I will take a look, However, I am very busy, so I may not get a chance to look into this now until next week. John

Sorry, but it really helps if you can be clear if you need assistance. I don't know what you mean by 'loaded', sorry. As I have explained. it should enable automatically when both the following are true: - it is set to be enabled automatically, or if it was enabled when you last shut-down - when you have a flight loaded and ready-to-fly If that is not the case, THEN let me know. So, if you are ready-to-fly and WideServer is not enabled, then enable. Then close everything down and start again, and get a a/c ready-to fly. Then it should enable automatically. If it doesn't do that, I will look into it. To summarize: - if for some reason you have set to 'Disable', it will never automatically 'Enable'. You need to manualy 'Enable' at some point. - when 'enabled', it will only actually be started once you have a plane loaded and are 'ready to fly'. If this is not the case, let me know. John

You didn't attach your inis, but did you delete this one as recommended: Also, search for any other assignments to your 'D' device and remove them, and then you should be ok. John

Yes, WideServer needs to be 'enabled' in FSUIPC. However, you don't need to do this manually - it should automatically start when 'ready to fly', i.e. you have to have an aircraft loaded and not in the MSFS menus to connect. Maybe this was your issue - you just hadn't loaded an aircraft/flight? John

No - your code should still work. However, as I said, if you previously registered and have a key file, you can just use that. However, if it says it is invalid, then that is usually because there is an error in one of the three fields (name, email, key) - all of them much exactly match whaty is specified in your SimMarket purchase email or account. If you are sure that your details are valid, then it could be an issue with your VC++ redistributables. However, if this is an issue, it usually also prevents FSUIPC7 from running. So, try running FSUIPC7, and if you get an error then you need to re-install the VC++ redistributables. Instructions for this can be found in the README.txt file provided. Finally, if not of that works, you can manually create a key file. To do this, create a file called FSUIPC7.key in yout FSUIPC7 installation folder, and give it the following contents: Replacing the parts in bold with your details. Also, please remember if it still doesn't work, please DO NOT POST YOUR KEY DETAILS. Thanks, John

Yes. This was a fix in FSUIPC6 that I copied across to 7, and released in a bit of a rush and didn't test. properly...Sorry about that, I will correct. Ok, I'll look into this. Is that from the dev menus? I haven't tried this... Was it previously working? I will also take a look at this.... John

There is also a standard control/event for the - Toggle Aircraft Exit Fast. Have you tried that?

You could start by explaining what you mean so that i can understand your issue. What do you mean by 'the code wouldnt work '? Are you talking about the installer? What did you try? What was the result? Also, if you have previously registered successfully and have an FSUIPC7.key file in your FSUIPC7 insstallation folder, there is no need to re-register - your details should be populated in the registration panel and you can skip registration. There is currently an issue where the installer will crash after installing the FSUIPC7.exe and when trying to update the EXE.xml. This is due to a corrupt EXE.xml file. If this is your issue, then you can de-select the 'Auto start' component when you install. Alternatively, you can remove (or better rename) your existing EXE.xml file and then re-install. Further details on this issue can be found here:

So you can see the buttons > 32 ?

Currently, you can use MSFS K: events with MobiFlight + FSUIPC. There is a tutorial explaining how to do this here. I am currently looking into adding support to access L: and H: vars directly in FSUIPC. I wasn't planning on adding K: vars at the moment, but this should also be possible. I may also supply a general method to execute user-supplied calculator code, which would also allow access to K:Vars. John

Hmm. Strange, Did you install any additional drivers or software after running the regedit file? Either the regedit entries weren't removed correctly, or additional software/drivers you are installing is creating additional registry entries. If its the latter, you can do the procedure again but this time to do not install any additional drivers or software - just try with the windows drivers. I should have advised this first, sorry. If its the former, there may be an issue with the file you created, you should check the registry to see if those entries have been removed, and if not you can manually remove them. Have you manually changed your ini? And added new assignments? You shouldn't really have touched it. Your C device is now missing, has been replaced by D, and you have new assignments to it. You can correct by changing your [JoyNames] section to the following: You can also delete this entry under [Axis]: 6=DR,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }- Or maybe replace it with this: 6=CU,256,F,66818,0,0,0 -{ TO SIM: STEERING_SET }- (which was your previous assignment to that axis). And the delta in your steering tiller assignment seems very large...to correct this, change your SteeringTiller assignemnt: 5=CR,16383,D,36,0,0,0 -{ DIRECT: SteeringTiller }- to 5=CR,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }- John

No, thats still valid. This is most probably due to a corrupt EXE.xml file and the installer is crashing. If you re-install again but deselect the auto-start component it should complete. You can also delete your existing EXE.xml file before installing and a new one will be created. For further info, see

Was it all working ok before this change? And nothing else has changed? Have you tried rebooting your system?

No, that shows your network is working for those activities. We provide documentation so that we don't have to continually repeat the same advice. Please read that document and try what is advised there, and then let me know if you have any issues, and supply all necessary files (logs + inis). When you attach files, they must all be generated from the same session. Please always supply WideServer + WideClient log files, WideClient.ini and your FSUIPC ini. BUT, before you post again, please review your network configuration as shown in the WideFS documentation, and try specifyingthe protocol and server names and/or ip addresses.