John Dowson

Sorry, but why would you want to run WideClient in a VM on the same machine as FSUIPC? You can just run it in the same OS as FSUIPC (by using the ClassInstance ini parameter - see the WideFS Technical guide for details). Anyway, have you tried setting the Protocol And ServerName (or ServerAddress) ini parameters? Btw, for future reference, attaching files is preferable to screenshots of their contents.

What sim & version of FSUIPC are you using?

Yes, its the time FSUIPC has been running in milliseconds. Yes, its defined in SimConnect and is the string name of an event. Not sure where the FSX SimConnect documentation is (maybe installed with FSX?), but the P3Dv3 documentation ids here and it should be pretty similar: http://www.prepar3d.com/SDKv3/LearningCenter/utilities/variables/event_ids.html Yes, they are the same. However, note that not all controls are from the FS. Some are added by FSUIPC and may operate using simulator variables rather than controls. Yes, that is the usual way to find out what a UI control uses which you can then assign to a button, switch or keypress. John

Sorry, forgot to update the last entry, which should be: 7=PA,19,C66704,0 -{APU_STARTER}-

There is something wrong with your WideFS registration details. Make sure that you haven't included the '<' & '>' characters - there are there only to indicate the parameter that needs to be replaced. Check your details are correct, but if you cannot get this to work please PM me your FSUIPC7.key file and WideFS7 order details (date and order number) and I'll check them. Please DO NOT post them publicly. Make sure this is also a WideFS7 registration - you cannot use a WideFS6 registration with FSUIPC7. Well, you can add them but there are only 7 assignments, like I said. You also have no profiles yet created. To keep your assignments, add the following to your [Buttons] section: 1=RA,28,K113,8 -{Key press: F2}- 2=UA,28,K113,8 -{Key press: F2}- 3=RA,30,C1061,0 -{engine 1 autostart}- 4=UA,30,C1062,0 -{engine 2 autostart}- 5=RA,31,C1063,0 -{engine 3 autostart}- 6=UA,31,C1064,0 -{engine 4 autostart}- 7=P2,19,C66704,0 -{APU_STARTER}- I'm not sure why your previous log didn't like the engine autostart assignments (the comment for these assignments was empty). I've checked and those are still available (or should be) in FSUIPC7. Try them, and let me know if they are working still please, and if they are recognised in your ini (i.e. the correct comment is still there when the ini is re-written). Thanks, John

Hi Kenji, you say But also: So you assignments are still in the ini file but are not working? If so, could it be that new ids have been assigned to your joystick devices? Are you using the 'JoyLetters' facility (which will prevent assignments being lost if your joystick ids change for any reason, such as re-connecting a device to a different USB port). Maybe you can post you .ini and .log files and I'll take a look. Also make sure that you have power management turned off in your USB hubs, as otherwise windows may be putting your devices to sleep. John

Ok, good - glad it's now working. John

Yes, sorry - I shouldn't have removed that!

You only have 6 button assignments (4 of which look to be to controls that no longer exist) and no axis assignments, all to your 'C' device, which is your "Throttle - HOTAS Warthog" and is missing (i.e. not connected). Looks like this may be due to a GUID change. There is also an extra rudder device 'TPR T.Pendular Rudder' which is not connected. I think you would be better off removing your current assignments and starting again.To do this, replace your current [JoyNames] section with: [JoyNames] AutoAssignLetters=Yes and your [Buttons] section with: [Buttons] PollInterval=25 ButtonRepeat=20,10 Then start MSFS/FSUIPC7 and see if you can see all your devices. If you can't, then send me the new FSUIPC7.ini, FSUIPC7,log and FSUIPC7.JoyScan.csv files. If you would like to use your old settings from your FSUIPC4 installation, first do the above to check all your devices are recognised and assignable, and send me those files, but also send me your old FSUIPC4.ini file and I'll let you know what you can do to copy your assignments across. John

You can try this which should just register buttons 32-39. Don't forget to update the Vendor & Product variables. I've not tested this (no time, sorry!). John HidButtons32-39.lua

Can you attach your .ini, .log and .Joyscan.csv files and I'll take a look - they will be in your FSUIPC installation folder.

Sure. You can remove the axis processing stuff (and the logging if you don't need that), and only write the buttons you need here: ipc.writeUD(0x3340 + ((i-1) * 4), buttons) However, buttons are written 32 at a time (8 x 32 but words). You can ignore the first 32 buttons by not writing there when i=0, or just write buttons 32-64 when i=1. Try modifying yourself, but if you have any problems I can take a look tomorrow for you.

You should read the release note (or the README.txt that is in the FSUIPC7.zip) which contains this: John

I'm not sure yet, but its not such a big issue now FSUIPC is an exe rather than a dll. You can just run it either before or after you start MSFS. I'm still waiting for details on how to start a program automatically when the sim starts. Once that is clear, I'll look into providing an installer. For future reference, all questions/topics on FSUIPC7/MSFS should go to the dedicated sub-forum for FSUIPC7-beta/MSFS. I'll move this post there for you. John

It should be [Auto]1=Lua HidDemo That should auto-run the script. The virtual buttons should then be assignable in the UI. John

As I have already said, your version is not supported. Please update. John

fsuipc 5.103 is no longer supported - we only support the latest version of each FSUIPC release. And the latest version of FSUIPC5 is only valid fromP3Dv4.3 and later. You can use earlier versions of FSUIPC5 that supported v4.0 (if you can find them!). but they are not supported, sorry. John

This has been corrected in the latest build, now available.

You could also add the following to the [General] section of your FSUIPC6.ini file (what there is of it!): Debug=Please LogExtras=x200000 That should show me more. Finishing now - I'll look into this further tomorrow.

Looks like its crashing on scanning your devices and registry. I'll take a closer look tomorrow, but could you tell me what joystick/usb style devices you have? I can see just a Saitek Pro Flight Yoke, but it looks like there is problems retrieving its details from the registry. Did you install Saitek software and/or drivers? If so, please uninstall them, disconnect your yoke and then reboot. Connect the yoke and try again. If you haven't got any additional drivers/software installed, it still worth disconnecting, rebooting and re-connecting, maybe in a different USB port. And if you are connected to a USB-3 port (blue), try a USB-2 one instead. I'll take a look in more detail tomorrow and see if we can add some extra logging to track down where.

Same place as your .log and .ini files.

Sorry, but could I also see your FSUIPC6.JoyScan.csv file please.

I can confirm this behavior: - FSUIPC offsets and the Fuel Pump control act as toggles between off/low - no parameter to the Fuel Pump control - this just acts as a toggle - FSUIPC correctly updates the fuel pump offsets when in off/low - manually setting the fuel pump(s) to high does not show any events/controls, and does not update the FSUIPC offsets - once the fuel pump(s) are set to high, the FSUIPC offsets and controls no longer have any affect I will raise this with Asobo. John

SimConnect is an API which allows communication between 3rd party programs and the flight simulator. FSUIPC is one such 3rd party program which makes use of the SimConnect API. SimConnect is an API. i.e. an application programming interface. You need to write a program to use it. FSUIPC is a utility program. If you are writing a program from scratch, you would be better of using the SimConnect API. SimConnect is provided and supported by the maker of the simulator, and as such is supported by them as is the simulator. FSUIPC is build on top of SimConnect and will survive as long as is needed. Try goggle. There is plenty of information out there on both SimConnect and FSUIPC. John

For requests, you will probably get more responses in the main support forum. This forum is to hold such scripts when contributed. For the FSL A3xxx series of aircraft, you need to look into the use of the ROTOR BRAKE control, which has been re-purposed for diffferent controls based upon the parameter. You may find what you need there (but I can't check as I don't have these aircraft). Please see https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/ John