• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Search results

  1. A

    MSFS Autopilot Altitude Hold Problem - Help Please

    Thanks for your insight. I've managed to identify the actual problem template: ASOBO_AUTOPILOT_Push_Altitude_Template I fail to comprehend why a default template would be created by ASOBO that creates such unrealistic autopilot behaviour. Anna
  2. A

    MSFS Autopilot Altitude Hold Problem - Help Please

    I'm hoping that some of the experts here can provide some much needed advice and assistance. I'm trying to program a standard autopilot that has a flight director, standby button, altitude hold, altitude select, vertical speed button, IAS button etc. According to the info I have, the normal...
  3. A

    MSFS A model behavior to shortcut "CTRL+E" event

    Hi Anthony, Many thanks for showing this code. If I had several engines on a drone and wanted to sync these all to whatever ENGINE_Throttle_1 is at from your above templates, how would I go about that? I was thinking of: <UseTemplate Name="ASOBO_ENGINE_Throttle_Template">...
  4. A

    MSFS XML Event Trigger

    Thanks for your input, for some reason it just won't work, not sure why, I'm baffled. I have now tried to link the XML event logic to a switch with the following: <Template Name="Drone_Lights_Switch_Light_Template"> <Parameters Type="Default">...
  5. A

    MSFS Write random value 0 or 1 in xml

    Hello, Maybe you could try this: <UseTemplate Name="ASOBO_GT_Anim_Code" Node="ASCRJ_MAIN_DOOR"> <ANIM_NAME>ASCRJ_MAIN_DOOR</ANIM_NAME> <ANIM_LENGTH>1</ANIM_LENGTH> <ANIM_CODE> rand 0.5 > </ANIM_CODE> <ANIM_LAG>80</ANIM_LAG> <Code>(E:LOCAL TIME, Seconds) 30400 &gt;=...
  6. A

    MSFS XML Event Trigger

    Yes thanks, all of that is correct, as in my amended post, I just messed up copy and pasting, tired eyes. Do you have any idea why the event is not being triggered at all? Is there anything missing, should I be using some sort of Asobo XML template for all of this to work correctly?
  7. A

    MSFS XML Event Trigger

    Thanks and my bad, that was just a typo here, my actual code does have that, corrected the above accordingly.
  8. A

    MSFS XML Event Trigger

    Hello, I'm stuck and cannot get an event to trigger. I have a drone with multiple engines and want the drone to go into a sort of safe mode if one engine fails, safe mode being a hover at first. This is the code I tried and nothing happens when engine 1's RPM falls below 100 RPM: <!--...
  9. A

    Combining 4 Magnetos to 1 Master

    I'm not sure if this is possible, but I think it should be and so I thought I'd ask here for some guidance. If an aircraft has 4 engines with 4 separate and individual magneto switches, 1 switch per engine, would it be possible to code a so-called master switch, one master switch that has an On...
  10. A

    MSFS Visibility

    Thank you Mamu, that's splendid! The 36000 > and 41400 < threw up an error, I changed it to the following and got it working: <Code>(E:LOCAL TIME, Seconds) 36000 &gt;= (E:LOCAL TIME, Seconds) 41400 &lt;= and (E:LOCAL TIME, Seconds) 54000 &gt;= (E:LOCAL TIME, Seconds) 63900 &lt;= and or if{ 1 }...
  11. A

    MSFS Visibility

    As per the above example, let's say I wanted an object to be visible only during the morning between 10h and 11:30h and then again in the afternoon between 15h and 17:45h, I tried the following code: <Visibility> <Parameter> <Code>(E:LOCAL TIME, Seconds) 36000 &gt;= (E:LOCAL TIME, Seconds)...
  12. A

    MSFS MSFS Toolkit by Nool Aerosystems

    Hello Paavo, Thank you for the update. While v0.51 works fine and without any errors, v0.52 is unusable, there are a bunch of error messages that appear and it tells me that GDAL cannot be found. I'm not sure what might be causing this, I've tried to troubleshoot this, and yet these error...
  13. A

    MSFS MSFS - Unable to build package using fspackagetool, after using patch 1.16.2.0 (SOLVED)

    Well that's exactly what Umberto had written - I assure you it works if there are no spaces anywhere in the path that contains the master XML project file. If you still had spaces even after this advice, then it's no wonder it still didn't work.
  14. A

    MSFS MSFS - Unable to build package using fspackagetool, after using patch 1.16.2.0 (SOLVED)

    Copy the fspackagetool.exe into the SimpleScenery folder inside the provided SDK sample folders, then Drag & Drop the SceneryProject.xml onto that fspackagetool.exe there. If that works then you know that your issue is elsewhere, perhaps with your dashes as you mentioned.
  15. A

    MSFS MSFS - Unable to build package using fspackagetool, after using patch 1.16.2.0 (SOLVED)

    Further to Umberto's advice, here is the solution that works: Backup your work and do a full uninstall of the SDK. Reinstall the SDK and click on Options and modify the path from C:\MSFS SDK to C:\MSFSSDK Let the installer finish. Drag & Drop using the fspackagetool.exe will now work again...
  16. A

    MSFS MSFS - Unable to build package using fspackagetool, after using patch 1.16.2.0 (SOLVED)

    I have tested this with the default samples provided with the new SDK 13 and the ability compile via Drag & Drop using the fspackagetool.exe and dropping the XML onto it seems broken, the default sample project names do not have any spaces either and do not compile via Drag & Drop. This is...
Back
Top