Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,278
  • Joined

  • Last visited

  • Days Won

    271

Everything posted by John Dowson

  1. No, re-installing just updates the files that have changed, it won't affect your settings/assignments. Also you can skip the registration stage as you have already registered and have a valid FSUIPC4.key file. John
  2. It will be under your FSUIPC7 installation folder, i.e. C:\FSUIPC7\FSUIPC7.log If it is crashing, do you see any errors? Is there a crash event in the windows logs (accessible using Event Viewer)? If FSUIPC7 is not starting correctly (or crashing on start-up) this is usually due to your system not having the required VC++ redistributables installed - check the provided README.txt for details. John
  3. You could try with a lua script, which would send the TOGGLE_LOGO_LIGHTS event and then set a timer to set/toggle XMLVAR_LandingGearLightBlink between 1 and 0 every second or so. I'm a but busy to try this at the moment, but should be relatively straight forward - if familiar with lua! Otherwise, maybe try asking about this in the MobiFlight discord channel - they maintain and help with presets. Otherwise, I can take a more detailed look towards the end of the week. John
  4. You have a button assigned to send a keypress (Del), and a key assignment on Del for WideFS KeySend. So, how are you sending the key to wideFS? If you press Del, does that work? The key Del key sent when pressing the button will be ignored when received again by FSUIPC (it does not act in key presses/release it sends). So, if you want the key sent on the button press, assign the button press (and maybe release) directly to the WideFS KeySend control. Any further issues, also be show me your FSUIPC7.log and WideServer.log files, with logging activated for Buttons & keys as well as Events. John
  5. Why do you think this? When FSUIPC7 starts, it shows a splash screen and is iconised to your system tray, from where you can open it, or use the default hot-key Alt+F to open the FSUIPC7 main window. Please read the provided documentation, and if you have any issues show me your FSUIPC7.log file, not your installation log - that looks fine. John
  6. What is changing? Something must be changing if it sometimes connects and other times not. Make sure you have an aircraft loaded and ready-to-flu before trying to connect. And uf you have issues, I always need to see your FSUIPC7.log file, and maybe also your FSUIPC7.ini. John
  7. Note you could also just create one preset: My_TBM930_Ignition# $Param (>L:MF_TBM930_ENGINE_Ignition_1_Set) and then provide the parameter value in your assignment, Up to you how you want to do this. John
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. And I have the same response: John
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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.
  24. 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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.