John Dowson

Yes indeed... Do you also use a mod for the TBM930, of so, which? Not at the moment - seems strange that the _1.. version works for some, and the one without for others. I can only think that it must be different mods or versions. It makes sense having _1... and _2.. versions for 2 PFDs, as also indicated by @hiddencreative, but I don't understand why this is different for different people unless the mods used are different... I haven't installed the WT G3000 yet, I'll take a look sometime. Maybe the difference is using this with or without the GTC 580 (the touch-screen controller)...

Yes, you can do this using lua. However, don't use the Tripleyse.lua, as that is to distinguish between short, long and double presses based upon the timings of the press events received. What you want is to use a lua that uses event.button, but maintain a global variable so that you know if this is the first press or the second press, and then perform the required actions accordingly.

Nice lua scripts you have written there! There are sometimes issues closing/killing luas that use the com library. First, could you please try the dll posted recently in this topic, which has a few improvements in this area: Also, check the value of your ini paramater TimeForLuaClosing and maybe increase to 4 or 5. If you still have issues with that, you could add an event.terminate function where you can explicitly close your com connection (com.close).

Yes, sorry. You have to put the ';' after the entry number, not at the start of the line - you can then just remove it afterwards - from the Advanced User Guide:

Could be several things....1st, make sure that you don't have things assigned both in FSUIPC and in MSFS. If assigning in FSUIPC7, best to start with an empty profile for that device in MSFS. Then activate logging for Events as well as Buttons & Keys in FSUIPC7. Produce a short log file showing your issue, i.e. load an aircraft, take off and then try and retract the gear. Then exit, and show me your FSUIPC7.log and FSUIPC7.ini files.

save the following as a .reg file (e.g. removeDevices.reg) and use this (take a backup first!): Windows Registry Editor Version 5.00 [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_25BB&PID_008B] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_25BB&PID_008B] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0402] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_044F&PID_0402] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0404] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_044F&PID_0404] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_068E&PID_00F2] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_25BB&PID_008B] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_25BB&PID_008B] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0402] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_044F&PID_0402] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0404] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_044F&PID_0404] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_068E&PID_00F2] Before you edit the registry, do as before - disconnect all your devices, uninstall all drivers/software and reboot. And best to reboot again after the registry update, then connect your devices. Maybe run FSUIPC after doing this, and before installing any specific software or drivers first, to see if they are recognised by the windows default drivers. if not, you can then install any drivers/software that you use for these devices. Your GUIDs and joy letters will probably have changed again, but we can sort that out once all your devices are recognised. May be better to rename your current FSUIPC7.ini file (e.g. FSUIPC7.ini.original) so that a new one is created. If you post that + your FSUIPC7.log file after doing this, I'll take a look to see what changes need to be made to your original ini to re-instate your original settings.

Can you show me this file please: C:\Users\BD3B484275CE462B\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml

And I've just checked the MF events and those hvars don't exist! Should they be: H:AS3000_TSC_Horizontal_BottomKnob_Small_DEC H:AS3000_PFD_SOFTKEYS_1 ? Maybe try with those instead - first via Execute Calculator code to see if they are available and work, and if so you can add them to your hvar file and assign.

First, check you have those hvars listed in the FSUIPC hvar file for your aircraft. You can check this by using the Add-ons->WASM-> List Hvars menu option. If they are not there, then you need to add them to the hvar file and then Add-ons->WASM->Reload. Once you have confirmed the hvars are available, create a macro file to use them. Note hvars do not have an associated value/parameter. Your macro file should look something like this: And then assign your buttons (or keys) to the hvar name. You can also try to execute the hvar (before adding it) using the Add-ons->WASM->Execute Calculator Code function, using, for example, the following: (>H:AS3000_TSC_Horizontal_1_BottomKnob_Small_DEC)

Yes they are using the same ID. Looks like your registry is in a bit of a mess and will need cleaning. Well, this is what I would advise you to try first! To be clear, you should: - disconnect all your devices - uninstall all devices + drivers from those devices from the Windows device manager, AND any supporting software for those devices - reboot and re-connect your devices to see what you get If that is what you have done, then the next stage is to remove some of your registry entries. Before doing this, I need some more information given by additional logging, so please go to the FSUIPC7 Log -> Custom... menu option and enter x200000. Then close down FSUIPC7 and restart it (with all your devices connected), and then close down again, and show me the latest .log and .ini files.

Looking at the image you posted earlier, it shows the list of offsets to be used for effects 21-30 (excepting effect 25), e.g. Effect 26: offset address 3060 Doesn't it give you the offsets for the other effects that you are missing? If not, I really think you should try X-sim or 6D0F support, or try to determine the data you need from the documentation. Note that there was a similar question from the 6D0F development team posted a year and a half ago: I think you need to ask 6D0F or X-sim, or maybe post in that topic to see if @E Automates can help you.

As I said, check the offset document. I still don't know what those are - what are the units? Maybe try these offsets:

I don't know what 'effects' are. Of course, I know what Pitch, Bank and Yaw are, and these are available from FSUIPC offsets, but I do not know what Heave, Surge or sway are. For a description of what is held in the offsets, please see the FSUIPC Offset Status document that is included. You can search the document, so, for example, searching for pitch & bank shows: 0578 4 Pitch, *360/(65536*65536) for degrees. 0=level, -ve=pitch up, +ve=pitch down 057C 4 Bank, *360/(65536*65536) for degrees. 0=level, –ve=bank right, +ve=bank left For Yaw, use the heading: 0580 4 Heading, *360/(65536*65536) for degrees TRUE.

Yes, Paul Henty's WebSocket server has been integrated into FSUIPC7 and available via the FSUIPC7 installer. Details on the server can be found here: http://fsuipcwebsockets.paulhenty.com/

This is because you have assigned your button press to Throttle2 Decrement, and the button release to the throttle 4 decrement. With repeat, it is the press control that is repeated until you release, and then the release control is sent. So it will be decreasing throttle 2 while the button is pressed, and then sending just one control to decrease throttle 4 when released. To assign multiple controls to a button, you do this by editing the ini. First, remove the throttle 4 decrement control on release and then close the assignment panel (click 'Ok'). Then open your FSUIPC ini file and find that assignment and comment it out (by putting a semi-colon character ';' in front of it). Open up the button assignment panel again and 'Reload all buttons'. Then assign the same button to the throttle4 decrement control on press with repeat (and no release) and them close the panel again. by clicking 'OK'. Open the FSUIPC ini file again and uncomment the line previous commented out, making sure the index numbers are still unique and alter of not. Once thats done and saved, you can go back to the buttons assignment panel and reload all buttons again. You will now have both controls assigned to that button on repeat. Note that you will only see one assignment in the UI panel and it will be grayed out. To alter or change it again, you need to edit the FSUIPC ini file.

You have hijacked a completely unrelated thread. Please do not do this -raise a new support topic, giving it an appropriate title. Also, if using FSUIPC, please provide more information.

6D0F is a free user offset that X-Sim is using. You will be better off trying in X-Sim support, or at least add that to the title of your post and it may attract other X-Sim users. I don't know anything about X-Sim, sorry.

Sorry. the '*' is just a wildcard, you replace that with letters that match as a substring to the aircraft title, as indicated by @SAC002

Great - thanks!

Slopes are for axes controls, not increment/decrement controls. If using inc/dec controls, it usually better not to use repeat, so you could try that. Otherwise, please activate logging for Events in FSUIPC. Then produce a log file showing your issue, i.e. load an aircraft and activate the trim showing your issue, then quit P3D and show me you FSUIPC log and ini files. Also check that you have controllers turned off in P3D, or if activated, make sure that you do not have trim controls assigned there as well.

Thanks Thomas - hadn't noticed the FSX version from the log! John

Thats your FSUIPC4.log file, not your installation log. That does show you have issues with SimConnect: 78 FATAL ERROR: FSUIPC4 cannot connect to any supported version of SimConnect but please show us your installation log file 'FSUIPC4 Install.log'.

Can you please show us your FSUIPC4 installation log. Note that you images show that you have file types for know files hidden in Windows Explorer - best to change this so that you can see the File extensions.

Yes, sorry - I still need to add the documentation for using hvars. To use hvars, you first have to let them be known by the FSUIPC WASM (and hence FSUIPC). You do this by adding a *.hvar file to the FSUIPC WASM module (under the modules folder). The current beta v7.1.0f only has 1 hvar file, for the A320, and this is quite old now and needs updating. I will do this at some point, and maybe provide some hvar files for other aircraft - I have asked users to supply these, when found, but have so far only received one for the DA40-NG, which I will add in the next release. Only one *.hvar file is loaded per aircraft, which will be the first one found on a substring match to the aircraft title. You can add hvars to the file when FSUIPC7 is running, and issue a Reload command (from the Add-ons->WASM-Reload option) which will reload hvar files and re-scan for lvars. To use hvars, you can either use macros, in the same way you would use an lvar, except only the Set command is available. Otherwise you can use the ipc.activateHvar function. I am planning to add some specific FSUIPC controls for lvars/hvars to make them easier to use, i.e. 'Lvar Set', 'Lvar Toggle', 'Lvar Increment', 'Lvar Decrement', 'Lvar Cycle', 'Hvar Activate'. There are a few complications with this (mainly that the IDs of lvars aren't consistent!) and I need to update the WASM /WAPI to enable callbacks, so this is going to take a while. I may also add a user facility to populate (user) offset with lvar values, to make them more accessible.

What 'undocked windows' are you referring to? It is nor possible to control the positioning of MSFS windows. There are also issues with the SimConnect text display facilities in MSFS. If you are using the lua Wnd library, these windows can be initially positioned and then moved/resized as needed. The size/coordinates are stored in your FSUIPC7.ini and will be re-used the next time the window is displayed.