Jump to content

Jo Erlend

Developer
  • Posts

    525
  • Joined

  • Last visited

  • Days Won

    29

Jo Erlend last won the day on November 29 2021

Jo Erlend had the most liked content!

About Jo Erlend

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jo Erlend's Achievements

Contributor

Contributor (5/14)

  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare
  • Reacting Well Rare
  • Dedicated Rare

Recent Badges

1.5k

Reputation

  1. Hello, I was able to recreate this and here's some updated files that should sort this out. Replace the old files according to the folder structure in the attached zip file. Let me know if you still have issues! Trondheim - v1.08 - P3Dv5.zip
  2. Just a small update on this issue, the jetway animations have been fixed and are going to be included in the next scenery update along with support for the new aerosoft VDGS module.
  3. There is an bug in the sim that can cause lights to spawn at the incorrect altitude, so I would suspect that this is the issue. Personally I've seen it more if I overfly an airport or get close to it during approach. Flickering and partially disappearing airport/runway lights
  4. The flight info seen on the VDGS display is indeed dynamic! The module has an interface where Destination and TOBT can be added, while the flight number is what's assigned in the Aircraft -> Customization menu.
  5. Here's some screenshots from last week, with the way it's shaping up and unless a lot of things goes sideways testing should start for full next month.
  6. The APIS Benjamin posted a screenshot of is still being developed and not yet implemented at EDDK. Support for the new VDGS module will be added in an update to EDDK at a later date. (There is a basic VDGS system already implemented at EDDK, this one is based on the default marshaller system and not as advanced as the standalone module.)
  7. I'll check with Stairport Sceneries if this is something they plan on adding, the cone bug is unrelated to the scenery though as this happens on default airports as well.
  8. On those screenshots it still looks like you have some extra floodlights being placed next to the terminal. There's also quite a lot of models missing from the MA Oslo scenery (Hangars in the background of the first image and the tunnel objects in both images) so I suspect you still have some leftover BGL files from another Oslo scenery that's excluding those and adding the extra floodlights.
  9. Hi, this is a known issue with T-type jetways at the moment. How jetway animations are handled changed in SU5 and we're still waiting on some updated documentation, but this issue is actively being looked into.
  10. You can choose which of the stand docking systems are activated through a menu, so the VDGS works just as well for online flying on VATSIM as it does for offline. As this is an external module it's not reliant on the default ATC in any way.
  11. What you see in that gif is actually a "ghosting" graphics artifact that happens when using TAA as Anti-Aliasing, so it's not something that's related to the VDGS itself.
  12. Another new feature is that the VDGS are running on an external module created by Aerosoft. This allows for a highly functional VDGS with airport specific custom stopping points based on aircraft types. It is still in active development, currently 3 different system types has been created and the module is highly flexible and expandable. Activation or changing which VDGS is active is done through a UI menu. This feature is not only limited to Brussels, but is also planed for upcoming Aerosoft airports.
  13. A while ago there was a question regarding hangar interiors, how many that's gonna be included is still not decided, but here's a preview of one of them. Hangar doors automatically open when you approach (and close when you leave), these hangars are also scripted to "wake up" and trigger animations at random, helping to bring some more life and busyness to the airport.
  14. Missing textures would indeed be due to an incorrect "fallback" path in the texture.cfg, verify that it's pointing towards the correct location of the Texture folder inside the Mega Airport Oslo 2.0 folder. By default it should be and this should not need to be changed unless the scenery has been moved / installed to a different location than the default FSX/Aerosoft folder. fallback.1=..\..\..\..\Aerosoft\Mega Airport Oslo 2.0\Texture
×
×
  • Create New...