Author Topic: SIDs at KORD.  (Read 6417 times)

alexzar14

  • Jr. Member
  • **
  • Posts: 50
SIDs at KORD.
« on: January 25, 2015, 09:23:03 pm »
Must be a known problem, please review:
no SIDs available for any runway at KORD, the SIDs fiels in FMSes of various different aircraft is empty. Flying out without SIDs... Please advise.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50700
    • VIRTUALI Sagl
Re: SIDs at KORD.
« Reply #1 on: January 25, 2015, 10:04:06 pm »
That's doesn't have anything to do with the scenery.

SID/Stars are NOT part of a scenery, they are entirely unknown to FSX, that doesn't support them, and are only an internal database that is known and used only to the FMC of the airplane you use so, whatever problem you have with them, it's related to the airplane and its database configuration.

alexzar14

  • Jr. Member
  • **
  • Posts: 50
Re: SIDs at KORD.
« Reply #2 on: January 25, 2015, 10:52:20 pm »
ok thanks, will address to aircraft support.

JSilva

  • Jr. Member
  • **
  • Posts: 62
Re: SIDs at KORD.
« Reply #3 on: January 26, 2015, 04:38:43 pm »
In KORD, there is only one SID, O'Hare Eight (ORD8).
PC Specs: Intel Core i7 4790K @ 4.4GHz, ASUS Z97 PRO Wi-Fi AC, G.Skill Trident X 2x8GB RAM DDR3 2400MHz CL10, Nvidia GTX 1080 Ti 11GB EVGA SC2, Corsair RM750

klimchuk

  • Newbie
  • *
  • Posts: 8
Re: SIDs at KORD.
« Reply #4 on: January 28, 2015, 04:23:31 am »
That's doesn't have anything to do with the scenery.

It has a lot to do with AFCAD which doesn't have runway defined in AIRAC.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50700
    • VIRTUALI Sagl
Re: SIDs at KORD.
« Reply #5 on: January 28, 2015, 02:03:54 pm »
It has a lot to do with AFCAD which doesn't have runway defined in AIRAC.

It doesn't have anything to do with the AFCAD, because the concept of a SID or Star doesn't exists in the AFCAD. It's something entirely internal to the database used by the FMC, which has its own internal database of runways too, and that one is supposed to associate a runway of its internal database, with a SID/Star in the internal database. It's a relationship entirely internal to that database.

The user is not reporting a disagreement between the runways displayed in the scenery (defined in the AFCAD) and the runways displayed in the FMC database. He's reporting ALL runways in the FMC database have EMPTY SIDs.

So, regardless if the runways in the FMC match the ones in the scenery or not, the problem is they are empty.