John Dowson

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.

Ok - sounds like its something we've missed. I'll take a look - but next week now. John

Did you do/try this? If not, please do. If so, also show me your WideClient.ini. And please always post your server log with the client log.

Registration comes at the end of the installation process, after you have installed. If you have previously registered, the registration form details will be filled-in and you can skip registration - you only need to do this once to generate the FSUIPC7.key file. John

Yes, I release 7.0.7 this morning to get a few minor updates out of the way so I could release the the beta as 7.0.8a with support for128 buttons, then released that!

That is quite old now. Latest official version is 7.0.7 (released this morning). I have also released 7.0.8a, a beta release with native support for up to 128 buttons - see Announcements if interested in that. John

Yes, there is/was an issue closing down lua com scripts. I released v7.0.7 this morning with a correction for that. Please download and try it. If you still get an issue, please show me your FSUIPC7.log file. John

Yes, it seems that way. I presume its working for other Bravo users, or at least I have not heard of any other reports like yours. It does sound like its defective. Sorry, but I don't think there is anything else I can advise... My contact at Honeycomb has gone silent as well for some reason... they had said they were going to send me a Bravo last year, but nothing so far has arrived.... Btw, I have also just released FSUIPC7 with support for up to 128 buttons, but I don't think this will help you... John

I have released a beta version of FSUIPC7 with native support for HID joystick type devices with up to 128 buttons. Please see Please use this topic to report any issues. John

Will be a while coming...I'm going to take the weekend off (bar support) and start on this next week...

Then it is the wrong log file.... Check you don't have multiple installations of the WideClient. The log you posted shows WideClient connected ok and was working until the FS closed.

A final update from VoiceAttack: Sorry, can't attach the image, but you need to select 'Send Command to this target' and then select to enter in the text box (not Active Window) and enter +AceApp - which is the windows class name of MSFS. I think the issue may be that the lua Wnd window has the focus when being updated, and as it is updating several times a second, your input is going to the lua window. Explicitly stating that it should go to the FS window should resolve your issue (although i have not tested, sorry!).

Also please also check your network config as advised in the WideFS user manual section Configure your Network. You can specify the protocol and server names or ip addresses if having issues.

Sorry, I don't understand. Your WideServer log shows a wideclient connection. And you still have not showed me any WideClient log files, either Sandpiper or others.

I'm not sure what affect that has on the WideServer / WideC;ient coummication... Well of course - WideFS uses TCP and UDP as communication protocols... What other computers? The WideServer log you attached showed one WideClient connection: If you have issues for other clients, I need to see the WideClient.log files. To see if that netsh command is causing the issue (although I don't see why), you can always try resetting with netsh int tcp set global autotuninglevel=normal John

Those offsets are read-only.

I've also checked the exec calc code functionality with lvars, and this also works - this is a test to hide/show/hide the yoke via lvars (in the King Air) using set lvar and then execute calculator code twice:

Sadly, I get no effect. I also tried "(>H:A320_Neo_CDU_MODE_SELECTED_SPEED)" that has no effect, whereas Set Hvar 24 works. There was an issue with the loading of hvars that has now been corrected (and released as v0.4.2). Only one hvar CDA was being created. I'm not sure this has anything to do with this though. However, if I set a hvar or execute calculator code, the same code is executed in the WASM: So, please try again with the latest version and let me know if you have any issues. John

Ok. Then - disconnect your X56 throttle and stick - remove any additional saitek drivers and software if you have any installed - reboot (leavung devices disconnected) - start regedit, and make a back-up of your registry - create a ,reg file (e.g. removeDevs.reg) with the following content: - run the regedit file (i.e. double click it in windows explorer) - connect your devices and r-install anything you removed in the second step above - start MSFS/FSUIPC7 This may change the device letters, so once you've done that, show me your FSUIPC7.log and FSUIPC.ini files again.

I've fixed this and released as 0.4.1.

The 'Create aircraft LVARs file' facility is a hangover from an earlier version of the WASM where I loaded lvars from files. When this is called, lvars are re-scanned to create the files and so may not necessarily correspond to the lvars currently loaded (lvars can be created during the lifetime of the aircraft. You log shows that the initial scan found 616 lvars: And the scan performed when generating the files found 618 - so 2 were added in the 10 hours that it as running: You can 'Reload' to scan and update the internal lvar/hvar lists. The list created is shorter to a minor bug in the client where the display buffer is still restricted to 16300 characters - I will remove that.

A single left click seems to not work in some browsers. If it doesn't. try a right-click and select 'Save as...'.