Jump to content

Marten@Stairport

Developer
  • Posts

    691
  • Joined

  • Last visited

  • Days Won

    48

Everything posted by Marten@Stairport

  1. You can check the default door position in the Authoring Tool in the Utils tab by selecting Draw help lines. In case the appearing lines don't cross at the correct door location report it again. Otherwise the jetway values are not perfect. The included templates are not always 100% correct because it depends on some factors the scenery author controls like average distance of parking to the jetway. So the author has to check the animation before and can change the measurement values accordingly.
  2. Besides the fact that you missed to say the aircraft type you can check the default door position in the Authoring Tool in the Utils tab by selecting Draw help lines. In case the appearing lines don't cross at the correct door location report it again. Otherwise inform the scenery author about the incorrect setup.
  3. That is indeed a problem in the configuration of the author. You may advise him to check if he used the correct template values for the jetway.
  4. That's a suprise indeed. Maybe the beacon override is only when loading the plane but not after finishing a flight? Never did an actual flight as I'm still waiting for VR compatibility (probably forever).
  5. Sure why not. Feel free to ask aerosoft directly or through their forum.
  6. status 1 = VDGS is activated because of an approaching aircraft status 2 = Aircraft is in the predefined position status 3 = Aircraft is parked (engine + beacon off)
  7. Hi Zak, looks like you did something wrong with the jetway configuration. I would bet you took the wrong template and therefore the measurements of your jetway are wrong. Greets Marten
  8. Hi Danny, in theory... yes. In real life... configure the doors for ALL 3rd party aircraft objects, put in another 500€ for the development and make the 3rd party plugin developer cooperative to give us access to the aircraft placement. Same to you! Greets Marten
  9. Hello sir, if your intention was to obtain help with your issue the following things would be necessary: a post in the Bug Section adress of welcome in your post your name all files noted here Greets Marten
  10. The reason is more an old relict of the SAM range in general. It is limited to 10km which is sometimes necessary if you have animated objects far off the airport like windturbines or other stuff. For jetway objects this is a bit too far indeed.
  11. Weird things happend during last export. Will fix it for next update.
  12. Hi Patrick, Can't check if right now but if that's the case we will fix it in the next update.
  13. Hey guys, SAM has been updated to 1.0.2. Here is the changelog: ⦁ Fixed Animation Error in FMT 4.0m pole ⦁ Fixed CRJ200 config ⦁ Added AN24 config ⦁ Added JS31 config ⦁ Added EMB110 config ⦁ Added Dash8 config
  14. Hi Florent, You don't need SAM to do that. There is a dataref indicating the month sim/cockpit2/clock_timer/current month (1-12) and the temperature sim/weather/temperature_sealevel_c (degrees Celsius). You can animate your objects with Anim_hide depending on these datarefs to appear or disappear. Greets Marten
×
×
  • Create New...

Important Information

Please read the Terms of Use