John Dowson

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...'.

Yes, that's the next stage. There will probably be more API updates when I do this, but that will be to add in functionality not change existing functionality. Cheers, John

I don't see any reason why you can't, but you need to try it. There are various ways to configure the throttle, one of them should work... Ah, I see @jaxx has replied - thanks! As far as I'm aware, these are new controls added by MSFS. There are various "Ex1" controls, here's the full list : // Additional controls from Asobo forum: https://forums.flightsimulator.com/t/simconnect-mega-thread/116305/62 #define KEY_THROTTLE_AXIS_SET_EX1 (KEY_ID_MIN + 1560) #define KEY_THROTTLE_INCREASE_EX1 (KEY_ID_MIN + 1561) #define KEY_THROTTLE_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1562) #define KEY_THROTTLE_DECREASE_EX1 (KEY_ID_MIN + 1563) #define KEY_THROTTLE_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1564) #define KEY_THROTTLE_FULL_EX1 (KEY_ID_MIN + 1565) #define KEY_THROTTLE_CUT_EX1 (KEY_ID_MIN + 1566) #define KEY_THROTTLE1_AXIS_SET_EX1 (KEY_ID_MIN + 1567) #define KEY_THROTTLE1_INCREASE_EX1 (KEY_ID_MIN + 1568) #define KEY_THROTTLE1_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1569) #define KEY_THROTTLE1_DECREASE_EX1 (KEY_ID_MIN + 1570) #define KEY_THROTTLE1_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1571) #define KEY_THROTTLE1_FULL_EX1 (KEY_ID_MIN + 1572) #define KEY_THROTTLE1_CUT_EX1 (KEY_ID_MIN + 1573) #define KEY_THROTTLE2_AXIS_SET_EX1 (KEY_ID_MIN + 1574) #define KEY_THROTTLE2_INCREASE_EX1 (KEY_ID_MIN + 1575) #define KEY_THROTTLE2_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1576) #define KEY_THROTTLE2_DECREASE_EX1 (KEY_ID_MIN + 1577) #define KEY_THROTTLE2_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1578) #define KEY_THROTTLE2_FULL_EX1 (KEY_ID_MIN + 1579) #define KEY_THROTTLE2_CUT_EX1 (KEY_ID_MIN + 1580) #define KEY_THROTTLE3_AXIS_SET_EX1 (KEY_ID_MIN + 1581) #define KEY_THROTTLE3_INCREASE_EX1 (KEY_ID_MIN + 1582) #define KEY_THROTTLE3_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1583) #define KEY_THROTTLE3_DECREASE_EX1 (KEY_ID_MIN + 1584) #define KEY_THROTTLE3_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1585) #define KEY_THROTTLE3_FULL_EX1 (KEY_ID_MIN + 1586) #define KEY_THROTTLE3_CUT_EX1 (KEY_ID_MIN + 1587) #define KEY_THROTTLE4_AXIS_SET_EX1 (KEY_ID_MIN + 1588) #define KEY_THROTTLE4_INCREASE_EX1 (KEY_ID_MIN + 1589) #define KEY_THROTTLE4_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1590) #define KEY_THROTTLE4_DECREASE_EX1 (KEY_ID_MIN + 1591) #define KEY_THROTTLE4_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1592) #define KEY_THROTTLE4_FULL_EX1 (KEY_ID_MIN + 1593) #define KEY_THROTTLE4_CUT_EX1 (KEY_ID_MIN + 1594) #define KEY_PROP_PITCH_AXIS_SET_EX1 (KEY_ID_MIN + 1595) #define KEY_PROP_PITCH_INCREASE_EX1 (KEY_ID_MIN + 1596) #define KEY_PROP_PITCH_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1597) #define KEY_PROP_PITCH_DECREASE_EX1 (KEY_ID_MIN + 1598) #define KEY_PROP_PITCH_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1599) #define KEY_PROP_PITCH_LO_EX1 (KEY_ID_MIN + 1600) #define KEY_PROP_PITCH_HI_EX1 (KEY_ID_MIN + 1601) #define KEY_PROP_PITCH1_AXIS_SET_EX1 (KEY_ID_MIN + 1602) #define KEY_PROP_PITCH1_INCREASE_EX1 (KEY_ID_MIN + 1603) #define KEY_PROP_PITCH1_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1604) #define KEY_PROP_PITCH1_DECREASE_EX1 (KEY_ID_MIN + 1605) #define KEY_PROP_PITCH1_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1606) #define KEY_PROP_PITCH1_LO_EX1 (KEY_ID_MIN + 1607) #define KEY_PROP_PITCH1_HI_EX1 (KEY_ID_MIN + 1608) #define KEY_PROP_PITCH2_AXIS_SET_EX1 (KEY_ID_MIN + 1609) #define KEY_PROP_PITCH2_INCREASE_EX1 (KEY_ID_MIN + 1610) #define KEY_PROP_PITCH2_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1611) #define KEY_PROP_PITCH2_DECREASE_EX1 (KEY_ID_MIN + 1612) #define KEY_PROP_PITCH2_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1613) #define KEY_PROP_PITCH2_LO_EX1 (KEY_ID_MIN + 1614) #define KEY_PROP_PITCH2_HI_EX1 (KEY_ID_MIN + 1615) #define KEY_PROP_PITCH3_AXIS_SET_EX1 (KEY_ID_MIN + 1616) #define KEY_PROP_PITCH3_INCREASE_EX1 (KEY_ID_MIN + 1617) #define KEY_PROP_PITCH3_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1618) #define KEY_PROP_PITCH3_DECREASE_EX1 (KEY_ID_MIN + 1619) #define KEY_PROP_PITCH3_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1620) #define KEY_PROP_PITCH3_LO_EX1 (KEY_ID_MIN + 1621) #define KEY_PROP_PITCH3_HI_EX1 (KEY_ID_MIN + 1622) #define KEY_PROP_PITCH4_AXIS_SET_EX1 (KEY_ID_MIN + 1623) #define KEY_PROP_PITCH4_INCREASE_EX1 (KEY_ID_MIN + 1624) #define KEY_PROP_PITCH4_INCREASE_SMALL_EX1 (KEY_ID_MIN + 1625) #define KEY_PROP_PITCH4_DECREASE_EX1 (KEY_ID_MIN + 1626) #define KEY_PROP_PITCH4_DECREASE_SMALL_EX1 (KEY_ID_MIN + 1627) #define KEY_PROP_PITCH4_LO_EX1 (KEY_ID_MIN + 1628) #define KEY_PROP_PITCH4_HI_EX1 (KEY_ID_MIN + 1629) The comment from Asobo (from the link above) on these is: John

I have released a beta version of FSUIPC6 with native support for up to 128 buttons. Please see John

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

You can do that using regedit. However, if they are not causing issues, you can leave them. As you are using JoyLetters, the correct entries should be used. If you still want to remove them, then make sure you back up the registry first (you can do this from regedit). Then, disconnect the two devices that have duplicate entries, then delete all registry entries with matching product and vendor ids for thos devices, reboot and then re-connect you devices. If you still want to do this, if you show me your latest JoyScan.csv file I can provide you with a regedit file that you can use to remove the entries.