Nav Data

[Guest prichards]

Will the new 767 use the same Nav Airacs as the older 767pic and PMDG737?

[Tabs]

It doesn't look like it - the manual describes a new XML based method for the navdata that's all contained in one file.

[Guest Agamemnon]

HiXML eh.I do hope LDS is talking to Navdata.Troy

[Guest Mark McG]

XML Is the format that the Procedures are saved in.

[B777ER]

Hmm...I wonder if Richard would be able to set something up so we could have regular AIRAC updates with the LDS767? I hope the developers are talking with him?

[wchafe]

Yes he will, we are in contact :-)As it stands now the navdata is the same, with the exception that I strip out runways and airports that can't support the 767.Wade

[Tabs]

Wade,Would it be possible for you to release the procedure XML spec and an example file early for those of us who like to code them?

[Guest Agamemnon]

WadeSounds good.Just a followup please.Will you be providing any sort of editor in regards to procedures?Troy

[Guest ielchitz]

Wade,Hi there.1) I'd also like to see any XSD's you have regarding the procedures if at all possible. Like Ryan, and certainly Lee as well, I enjoy perfecting procedures for a few specific areas/airports.2) Will the route files that the LDS loads be the same spec as the file used in the PIC 767? I'm in the middle of coding a navlog that creates on-the-fly flightplan files for a number of popular formats (SB, FSNAV, PSS, PMDG, etc.) from my flightplanner at http://www.eleventhstreet.com/fb2 - the LDS files are using the 767PIC specs. If they have changed, then being able to code according to the specs would help out.Thanks,Ian.

[wchafe]

There will be no seperate editor but they can be entered using the FMC (I know, very unrealistic ;))Wade

[wchafe]

Ryan/Ian.It's not finalized yet so I don't want to release it. We'll make it available when we can.Wade

[teropa]

I for one think that this part of "unrealism" is a step ahead from the others because being able to enter and create the waypoints straight from the FMC makes it 1) easy and 2) quick. The fact that one can create a SID "in the cockpit" and save it gives great advantage. If you're, for example, flying from an airport you don't usually fly from, you don't have to anticipate the given departure and do them all in an editor beforehand, but instead you can just create the departure when you get it from the ATC (talking VATSIM here :)).As for it being unrealistic compared to the workings of the real FMC, then that's really not an issue at all. The real aircraft don't have a departure editor program either. Since we're talking sims and we have to create our own procedures anyway, it's perfect this way :).Tero

[Guest mmcevilley]

>There will be no seperate editor but they can be entered>using the FMC (I know, very unrealistic ;))>>Wade... but simple to use, very effective, and most of all - when you are done creating a procedure you know the procedure works. ;-) ;-) ;-)-michael

[Guest ielchitz]

Understood - thanks for responding Wade.

[B777ER]

I wonder then if you say create a full DP for say JFK. I imagine you then save it by using one of the LSK keys. So I would assume that the next time you where to leave out of JFK, would that DP be listed under the DEP/ARR button?