Jump to content

Recoil16

ED Beta Testers
 View Profile  See their activity

  • Posts

    1294

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by Recoil16

  1. Recoil16
    And it's quite a number more than just those, these are just the ones I remember seeing fixed off the top of my head.
  2. Recoil16
    fixed in 2.7.4.9632
  3. Recoil16
    Approach lighting was adjusted in 2.7.4.9632. Still not quite there yet though.
  4. Recoil16
    Fixed in 2.7.4.9632
  5. Recoil16
    Fixed in 2.7.4.9632
  6. Recoil16
    Fixed in 2.7.4.9632
  7. Recoil16
    Fixed in 2.7.4.9632
  8. Recoil16
    Fixed in 2.7.4.9632
  9. Recoil16
    Fixed in 2.7.4.9632
  10. Recoil16
    Fixed in 2.7.4.9632
  11. Recoil16
    Akrotiri fixed in 2.7.4.9632. Kingsfield still incorrect.
  12. Recoil16
    Fixed in 2.7.4.9632. But of course now the other NDB at Damascus is broken. But that's reported.
  13. Recoil16
    Fixed in 2.7.4.9632
  14. Recoil16
    So it has been. Good catch, forgot about those. Especially since one of them is in the Wishlist for no apparent reason.
  15. Recoil16
    That Antenna Tower is the Saipan NDB ("SN"), whether it should be this tall is a good question. It certainly seems suspect considering that this is an instrument runway. If you have any good pictures showing the antenna (irl i mean) that would go a long way in improving the situation.
  16. Recoil16
    Yes. That's what you're trying to install Marianas to after all.
  17. Recoil16
    Open a command line in your bin folder in the install directory and run "dcs_updater install MARIANAISLANDS_terrain".
  18. Recoil16
    The F10 info box in general only works for single runway airfields either way. As soon as you introduce a second or (god forbid) a third runway, information gets lost. But I reckon we're departing from Marianas bugs here and getting more into DCS Core wishlist territory.
  19. Recoil16
    All I'm saying is that to me this appears to not contribute anything to the actual discussion of the bug (or not bug as it appears to be). I appreciate that you share these documents, but as far as I know that was already accomplished in another thread. I'm very clear on the IRL ILS freqs, but as I just pointed out, the ones in DCS deviate from that, so in fact these charts will only contribute to the confusion in this specific instance imho.
  20. Recoil16
    What's the harm in modelling the hook? For all we know, there could be working barrier arresting systems introduced to DCS in the future.
  21. Recoil16
    How does this contribute to this?
  22. Recoil16
    Not so much a code problem in regards to duplicate freqs probably as the fact that all localizers in DCS (to my knowledge) have a back course, unlike many modern systems (like the ones presumably installed at Andersen). IRL you probably wouldn't have been able to pick up the localizer back course at Andersen. But yes, maybe also a code problem. Bottom line though, this latest issue is also not really a bug. Edit: And that kids is why you check the ident of the station you're tuning
  23. Recoil16
    You were flying the 06R localizer back course, not the 24L ILS. There's your issue. Due to (afaik) DCS game limitations, the ILS for 24L is 110.15, not 110.1 as it is IRL. IRL the 06L and 24R ILS and the 06R and 24L ILS use the same frequencies, respectively, but in DCS the 24L/R localizers have .05 MHz added on.
  24. Recoil16
    Airport beacons are currently not a thing in DCS in general, would be great to see them introduced!
  25. Recoil16
    That is a good point. Although that brings up the question of what is really part of an airport's name and what isn't.
×
×
  • Create New...