John Dowson

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.

No, sorry. I'm not that familiar with c#. To use the API in c#, you would need to rebuild the API as a dll project (rather than a static library), and the public functions would need to be exported. You could then call them using P/Invoke, or write a managed wrapper facade. I could re-build as a dynamic library project at some stage if someone wants to look into this.

Ok, yes that is an issue. I will correct this - I will use new though, rather than a global buffer. It doesn't matter if the allocated memory for this isn't released. No problem leaving it as it is for me, although I'll add a comment as to why I did that change, for future reference - otherwise I may reverse it! Yes, although I don't get that warning on my compiler. I'm a but lazy and tend to ignore those type of warnings anyway when I know the implicit cast won't be an issue...the number of lvars certainly will never exceed the max value held by an int! Probably a better fix is to change the printf code from '%03d' to '%03llu', I can do that... Thanks, John Later: I have made those changes and pushed to github if you would like to try.

In your original ini (i.e. not the default generated one)? If so, how strange....

Where are you looking? Its usual to assign to the Pan View control in the axis assignments tab as 'Send to FS as normal axis'. Did you try that? Its certainly there... Its also in the button assignment drop-down: That should be the first entry in the menu (unless using custom event files): John

First, you posted in the FAQ section, where it explicitly states NOT for support requests. I have moved your post, but please try to post in the correct forum for support. I see you have also posted in the User Contributions section for the Stream-Deck plugin, so I'll let your question be answered there. John

Yes. They reveal a few things. First, you have some registry issues with you X-56 Rhino Stick: This may nor be an issue, but if you are having issues best to resolve that to take it out of the equation....more on that later. You scanner and joyscan logs show that the stick has no axis: you scanner log shows: which is strange - one axis with a hex value - not sure why this is, but should show the axis letters if found, e.g. for your rudder: Are you running additional software for the X56? If so, please remove that and try again. Also, if you have installed any saitek drivers, uninstall those and let windows install the default drivers, and try again. I have just noticed the images in your original post - those are not from the windows game controller panel (or not that I recognise). Please try to see if your axis is recognised by the windows game controller application. If those images are from some sort of saitek config program, you need to remove that.

You have too much going on in that test. Please try wit the default ini but with the PMDG737offsets ini parameter set to No. This will tell us if your problem exists when FSUIPC is installed but doing nothing (except populating its offset area). Also, did you try without the Honeycomb config tool? You could also try logging offset 0x3224 (altimeter reading) to see if that is correct, although I don't know what value is driving this in your displays. I don't have the PMDG aircraft, so I cannot test this here. Ok, I'm not sure we have updated to that. However, we only update when the headers have changed and someone has had an issue and asked us to look into it... The last update we did for the PMDG areas was for the PMDG 747 and the 737 NGXu around 20th April last year. What is this? Is this related? What are you doing with that source file?

Ok. Try with FSUIPC6 first. I will release this in the next day or two. Would also be good to know if the >32 button lua worked for you in FSUIPC6. I would presume not, with the lua interface + script being the same....

Ok. I was planning on releasing this first in FSUIPC6. Do you have or use that (i.e. with P3Dv4 or v5)? If not, its not an issue. I can make a provate release of this with FSUIPC7 for you to try (i.e. before I release as a beta).

i am not sure why you are showing us documentation from another product... As Pete has said, they look like control numbers, and not offsets. I don't know what they mean by 'must be sent to the simulator as a normal axis' though. You can see if thats the case by assigning a button or key (in FSUIPC) to the <custom Control> menu item (in the FSUIPC assignments dialog, giving the control number that you want to use. Why don't you first try this to see if they work? Then, of you want to send them from your vb.net application, which is presumably an FSUIPC client (otherwise why ask here!), you can use the general control offset at 0x3110. I see Pete has also replied....