John Dowson

Your offset conditions are not correct: 14=DA000&200 49,8,66502,1 ;vor flag&setting flag 1 -{1: Press=AP_NAV_SELECT_SET }- You need to add the condition. To check the bit is set, use: 14=DA000&200!0 49,8,66502,1 i.e. check the flag is set: And here: 14=D66C0 49,8,66502,1 ;vor flag&setting flag 1 -{1: Press=AP_NAV_SELECT_SET }- As documented, the format is: You have the '<size><offset>', but not the '<mask><condition>'

Sorry, was confused by this in my previous response (with another support request...). Yes. that offset should be working. I'll check your ini.... Could you also supply a log file please, with only buttons & keys + Events logged.

Sorry, I wasn't going to, but I would also like to comment on this: I think that is far too strong. We provide documentation to hopefully reduce the time spent on support, which takes away from development, bug-fixing, and other activities that are more productive and useful (and also more interesting) than repeating things said many times and also documented. We don't expect a *thorough* reading (who has time for that with all the software/hardware you need to install these days!), but a quick look to know what's available and a review of the user' manual is always a good idea. Then, use then as needed to help you, depending on your knowledge of flight sims and maybe earlier versions of FSUIPC. And if you have an issue or need more specific information, you should consult the Advanced guide or the specific guides for using lua, PMDG aircraft or offset use. If you can't find anything there, then try a quick search of the forums, and maybe look in the FAQ section, or User Contributions if something extra thats not provided. All we ask is that you try to help yourself first, using the provided resources, before asking. The answer may be deep in the documentation somewhere and not easily found - it is far from perfect I'm afraid....! I have no preference whatsoever on the technical understanding level of the people who post for help. Many people who post here have a far better and deeper understanding of aircraft and aircraft subsytems than I do (or probably ever will), and there are far better lua programmers/experts on here as well. I would certainly never judge a persons technical understanding on what they post, as they are often posting to learn anyway, regardless of ability or previous experience, and am not interested in any qualifications, technical or not, of any poster. John

Hi Peter, sorry, but I think you tried the wrong dll - you used 6.1.1a (22nd April), whereas I would like you to try the latest added to that thread, which was 6.1.1f (2nd May). So before I look in detail at your scripts, could you first try that version, and any issues show me your FSUIPC6.log file again please. Just be be sure, here it is again: FSUIPC6.dll No, as they are not running then.... But if you remove them from the [Auto] section, they aren't running! You should really add them to your [Auto.A2AC172] section - or whatever your A2A profile is called, assuming you have one. If not you should create one and use this. They would then only be started when you load the aorcraft that uses them. Try that dll, but I think there could be various threading/timing issues when starting the lua threads (which then start the coms) then you switch straight away, killing everything to restart. Of course, this is not to say that it shouldn't cause issues killing the scripts and restarting. I will look into this further if needed. John

Yes, but that is for reading. If you check the FSUIPC Offset status document (and column L of the spreadsheet), you will see these offsets are read only and cannot be written to (No in last column): 03C0 64 The current state of the buttons on actively scanned joysticks (local ones, 0 to 15). Each of the 16 DWORDS contain the 32-bit state of the joystick 0-15, in order. Button 0 is the least significant bit (bit 0) in each DWORD. Ok-Intl No So if you want to do that, user a free user offset. Note also that those offsets are only populated for a joystick if/when there is at least one assignment to that joystick, If you mean the G1000, it has/was reported as mostly not working using standard events/controls, although some things may be working now via lvars/hvars. For full functionality, you should look at the Working Title mod for the G1000 (see https://msfsaddons.com/2020/12/06/the-working-title-g1000-mod-greatly-improves-the-glass-cockpit-in-flight-simulator/) Yes, you should use that. Not just for the 128 buttons, but also for the lvar/functionality. It is pretty much complete - I just need to update the documentation (and add a minor fix to event.button for buttons > 32) and will release this officially soon, hopefully at the weekend. You can use the mobiflight events if you like. The events may work in the stock G1000, but still probably better when using the WT mod. Note also that all MF events are based upon activating hvars or setting lvars, which you can do now directly in FSUIPC7 with the FSUIPC WASM module installed. You can install both WASMs (MF + FSUIPC WASMs) if you like and try both methods to see which works for you. You should have a WASM entry under the Add-ons menu, where you first need to activate the WASM functionality (you do this once). Did you select to install the WASM during installation? If so and its not there, please show me your InstallFSUIPC7.log file. Also check your MSFS community folder. FSUIPC7 only adds the Add-ons ->WASM entry if it can see the FSUIPC WASM folder fsuipc-lvar-module in your MSFS Community folder. Update: No OBS at the moment in the WT G1000, and so some people prefer the stock one. See this thread: https://forums.flightsimulator.com/t/release-working-title-g1000-v0-3-updated-to-v0-3-5-on-14-apr/288944/626

No, not yet. I'll take a look at the weekend.

Yes, and that kind of makes sense...I just don't know why it isn't working for some....

Interesting. Did you try using H:AS3000_TSC_Horizontal_BottomKnob_Small_DEC to see if that also works? You can try this using the Add-ons->WASM->Execute Calculator Code function (if its not in your hvar file), using: (>H:AS3000_TSC_Horizontal_BottomKnob_Small_DEC) Strange that it doesn't work for @guit33. I'll take a look but probably not until the weekend. Trying to get the garden in shape this week (as it it has been abandoned the last 6-12 months or so!) so am only covering basic support until next week...

Ok, thanks. Would be useful to know what those are and if they can account for the differences...

But what mods are you using, besides the WT G3000?

You can turn on logging for IPC writes - this will log anything written to offsets via external programs.

If its the MobiFlight commands that are not being executed (i.e. you are assigning in MobiFlight, not FSUIPC), I think you should try the MobiFlight support (or Discord channel) first. Sorry, but I don't use MobiFlight (except the WASM) so cannot advise on this.

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.