John Dowson

https://hubhop.mobiflight.com/presets/ I have given you instructions (several times now)...it really isn't that difficult. To be clear: 1. Open your Community\aircraft-tbm930-improvement\SimObjects\Airplanes\Asobo_TBM930\model\TBM930_interior.xml file in an editor. Scroll to the bottom 2. Add the code so it looks like this ... <Component ID="Seatbelt_R" Node="Seatbelt_R"> <UseTemplate Name="ASOBO_GT_Visibility_Code"> <VISIBILITY_CODE>(L:XMLVAR_TBM930_HideCoPilot) (A:PAYLOAD STATION WEIGHT:2, pound) 100 &lt; or</VISIBILITY_CODE> </UseTemplate> </Component> </Component> <!-- ############################################### --> <Component ID="MobiFlight_External_Control"> <UseTemplate Name="ASOBO_GT_Update"> <UPDATE_CODE> (L:MF_TBM930_ENGINE_Ignition_1_Set, Number) s0 0 &gt; if{ l0 1 - (&gt;B:ENGINE_Ignition_1_Set) 0 (&gt;L:MF_TBM930_ENGINE_Ignition_1_Set) } </UPDATE_CODE> <FREQUENCY>1</FREQUENCY> </UseTemplate> </Component> </Behaviors> </ModelInfo> i.e. insert this code only in the correct position: <!-- ############################################### --> <Component ID="MobiFlight_External_Control"> <UseTemplate Name="ASOBO_GT_Update"> <UPDATE_CODE> (L:MF_TBM930_ENGINE_Ignition_1_Set, Number) s0 0 &gt; if{ l0 1 - (&gt;B:ENGINE_Ignition_1_Set) 0 (&gt;L:MF_TBM930_ENGINE_Ignition_1_Set) } </UPDATE_CODE> <FREQUENCY>1</FREQUENCY> </UseTemplate> </Component> 3. Create a myevents.txt file in your FSUIPC7 installation folder and add the following: My_TBM930_Ignition_On#2 (>L:MF_TBM930_ENGINE_Ignition_1_Set) My_TBM930_Ignition_Off#3 (>L:MF_TBM930_ENGINE_Ignition_1_Set) My_TBM930_Ignition_Auto#1 (>L:MF_TBM930_ENGINE_Ignition_1_Set) 4. Start MSFS/FSUIPC7, load the TBM930, and assign your buttons/switch to My TBM930 Ignition On My TBM930 Ignition Off My TBM930 Ignition Auto It really isn't that difficult. If you have any issues, try re-reading this thread again before posting. Everything you need to know is in this topic. John

This sounds like you have controllers (and assignments) activated in FSX. Please check that controllers are disabled in FSX. Just install over your current installation - no need to uninstall or remove anythung. You ini shows that you only have one device (SideWinder Precision 2 Joystick), but you also have assignments to another device (with id 1) which is no longer corected. You should change the following in your [JoyNames] section to prevent issues when device ids change: AutoAssignLetters=Yes As you are using separate file for profiles, I also need to see the profile file of the aircraft you are using (which you don't say). So, please update, make those changes, and then show me your .ini and .log files. John

No. This is the code you need to insert (the code specified in the preset description, which I also showed you a few comments ago): <!-- ############################################### --> <Component ID="MobiFlight_External_Control"> <UseTemplate Name="ASOBO_GT_Update"> <UPDATE_CODE> (L:MF_TBM930_ENGINE_Ignition_1_Set, Number) s0 0 &gt; if{ l0 1 - (&gt;B:ENGINE_Ignition_1_Set) 0 (&gt;L:MF_TBM930_ENGINE_Ignition_1_Set) } </UPDATE_CODE> <FREQUENCY>1</FREQUENCY> </UseTemplate> </Component> Then, after you have that code inserted, you can then use the lvar L:MF_TBM930_ENGINE_Ignition_1_Set as I have already specified, or create those presets and use them. John

Ok... Have those TransmitClientEvent errors gone from your log? I see you have a lot of assignments to Custom controls - were they for the PMDG 737? Note the P3D/FSX version used custom controls, but the MSFS version uses the Rotor Brake control with the parameter specifying the switch/button and mouse action - see John

You are using a very old version of FSUIPC7, v 7.0.8. Please update and try there latest version, which is v7.3.7 (with v7.3.8 to be released in the coming days). Only the latest version is supported. John

And I have the same response: John

Can you please turn off logging for IPC read/writes - this is not needed and generates a large log file if used. You have lots of TransmitClientEvent errors which shouldn't be happening. This usually indicates an issue with Simconnect in the MSFS installation. To check, can you just run MSFS with FSUIPC7 and nothing else. Just load the PMDG 737, wait a few minutes until its fully loaded, and then exit, and show me both your FSUIPC7.log and FSUIPC7.ini files. Thanks, John

Ok - adding that code to the Community\aircraft-tbm930-improvement\SimObjects\Airplanes\Asobo_TBM930\model\TBM930_interior.xml file, and the ignition switch works as advertised: On: 2 (>L:MF_TBM930_ENGINE_Ignition_1_Set) Off: 3 (>L:MF_TBM930_ENGINE_Ignition_1_Set) Auto: 1 (>L:MF_TBM930_ENGINE_Ignition_1_Set) So, to use, first add that additional component section to the xml file (path given above - insert within the <Behaviors>...</Behaviors> section ), then create or add the following to a myevents.txt file (located in your FSUIPC7 installation folder) My_TBM930_Ignition_On#2 (>L:MF_TBM930_ENGINE_Ignition_1_Set) My_TBM930_Ignition_Off#3 (>L:MF_TBM930_ENGINE_Ignition_1_Set) My_TBM930_Ignition_Auto#1 (>L:MF_TBM930_ENGINE_Ignition_1_Set) You can then assign using those new presets. John

I can only check your assignments in FSUIPC, but additional logging may help. Try activating logging for Buttons & Keys as well as Events. Load your aircraft and press the two buttons on you alpha in turn. Then exit GSUIPC7 and show me your FSUIPC7.ini and FSUIPC7.log files. John

Can you please supply more details. Where is that message coming from? Sounds like a message from an FSUIPC 3rd part client. Do you have FSUIPC7 installed and running? You posted in the main support forum. I will move your post to the FSUIPC7/MSFS support forum, where it belongs. Also note, if using the PMDG 737 with MSFS, there is a beta version of FSUIPC7 available with the additional PMDG FSUIPC offsets enabled - see John

Ok - I didn't trad that far! I will install from github and let you know. Did you apply the fix detailed in the preset description to get this to work? If not, maybe try that (I will also take a look) - this is the description of the TBM930_IGNITION_ON preset: I'm not sure if this applies when using the improvement mod, but worth a try... John

No, it isn't. FYI, I will add this simvar to offset 0x0590 (4 bytes). If you update to use that offset, you can just remove the line that adds that once I have released. If you like, you can test this already in the attached version (which I haven't tested yet!): FSUIPC7.exe John

I am surprised that you can move the starter and ignition switches at all using the improvement mod. When I have that installed, I cannot move those switches in the cockpit at all. Without the mod, the switches work but the TURBINE_IGNITION_SWITCH_SET1 event has no affect when sent externally. There are quite a few (recent) comments that these switches are not working with this mod - see comments here: https://flightsim.to/file/8288/tbm930-improvement-mod I suggest you try contacting the mod provider to see if this can be fixed. John

Hi @VBV234 You could try the attached version, the latest beta, which has presets in a separate menu with the 'Preset:' prefix removed as well as allowing a few more characters in the menu items. There are still a few preset names that don't fit completely, but you should be able to distinguish between them/ Use the attached exe to replace your current one. John FSUIPC7.exe

I will take a look at this over the weekend (no time at the moment, sorry), but a quick search indicates that this is/was a known problem with the TBM930 mod, see https://www.avsim.com/forums/topic/610542-tbm-930-wmod-start-and-ignition-switches-inop/, but this later post indicates that thus was fixed in an update: https://forums.flightsimulator.com/t/tbm930-starter-and-ignition-switches-not-work/479945/3. So, first check that you have the latest version of the mod installed. Other than that, I will check and get back you. John

What values can the L:ped_autobrake_switch1 variable take? Are you sure that this lvar is writeable (some lvars are read-only, and no way to know if its read/write or read-only)? To check, use the Add-ons->WASM->Set Lvar menu item, and try setting the lvar to different values. When you chanhe the value of the lvar, list the lvars afterwards to see if the lvar holds the value you have set. Note also that your assignment screenshot shows you are setting the lvar value to 0. The switch is already in the 'off' position, so if '0' is off, the assignment isn'y going to do anything. I can help you to assign this correctly if you confirm that setting this lvar is having the desired affect, which you should always test if you have any issues. Also try logging the lvar value when the switch is in different positions, so that you know what value corresponds to each position. John P.S. Please STOP asking for support by 'reporting content', i.e .do not use the Report option. That is NOT for support requests. Just use the reply function.

The next release will have the presets in a separate menu, available on a new checkbox. With this version, I will remove the 'Preset' prefix, so more characters are visible. I will also consider increasing the width of the menu if needed, once the 'Preset' prefix has been removed. John

No problem. I think that simvar would be useful for many people, so I will add it to a fixed offset in the next release. Let me know how it goes. John

Yes - your filename has the extension .mcro.txt when it should be just .mcro. Remove the .txt. John

Then you are doing something wrong. The correct way to do this is to assign your axis to the controls using 'Send to FS as normal axis' and then, with FSUIPC7 not running, edit your ini to remove any toe brake calibration and add the reverse scaling (',*-1') if needed. That is no solution... John

Yes - read the provided documentation! From the README.txt (the clue us un the name...): John

Make sure that you have not installed FSUIPC6 under your windows Documents folder, or in any other Windows protected folder. If you have, re-install into a different location. Any further questions, please attach your InstallFSUIPC6.log file as well as your FSUIPC6.log file. John

Then you will have to wait until someone else discovers how to control the functions you are looking for and publishes a preset for you to use. Or maybe ask on the MD82 support forum. John

Note also that there is a new(ish) MSFS simvar INDICATED ALTITUDE CALIBRATED, documented as Indicated altitude with the altimeter calibrated to current sea level pressure. You could add that simvar to a free FSUIPC offset and see if that holds the value you need. If so, you can then spoof the value of any other altitude offset using that value (using FSUIPC's spoofing facility at offset 0x0024) for 3rd party programs that need that value in a specific offset. John

Have you tried using the Pressure Altitude simvar (offset 0x34B0) instead of the Plane Altitude (offset 0x0570)? There is a long discussion on this problem here: https://forums.flightsimulator.com/t/vatsim-ivao-pilotedge-users-be-aware-of-an-important-bug/426142/451 (as well as those other links I preciously posted), the last comment being: I don't think you should be doing your own calculations to determine the correct altitude... With vPilot 3.3, they recommend using indicated altitude with the altimeter set correctly - see https://forums.vatsim.net/topic/31832-altitude/page/2/. John