No. apt.dat continues to be in scenery packs. Nav data can be replaced -only once- and in its entirity via custom data.

Thanks Ben, that’s not good. I use XPLMSpeakString in all my scripts with Samatha as my default system voice. I don’t know who this dude is talking now, but he sounds like he smoked one joint to many. Put those heads together and come up with somethin different, please, I almost went back to beta 7, then I just disabled everything. Ain’t no dude tellin me I’m off course……

Cheers
tomcat

Probably?!? 🙂 Hopefully not?

I think the main risks are that if authors are modeling _to a specific DSF_ (e.g. cutting their buildings to match a particular mesh or putting exclusion zones down only for PARTICULAR autogen) then a recut can change the underlying DSF and break the “match”. I encourage authors to use techniques that do not depend on the particular DSF (e.g. build a “basement” on buildings and exclude EVERYTHING that might exist) … otherwise the pack can look good with base scenery and bad with HD scenery, for example.

Thanks Greg, but please do file bugs or contact Austin or myself directly…I am really, really, really trying to stop users from filing bug reports on the blog!

No, because there are only two cases:

1. You have a newer install (started at 10.25) – scenery added after global airports will ALWAYS be put higher in the .ini file or
2. You have an older install (custom scenery added before 10.25) – your ini file is wrong and will stay wrong.

The priority scenery packs are added is the ORDER OF DISCOVERY! NOT alphabetical!

I don’t know. The reported bug was that when the system default voice wasn’t an English speaker, the ATIS sounded crazy. So “system default voice is ATIS” isn’t a great design idea. We can’t require non-native-English speakers to use an English-speaking default voice just for the ATIS.

I’ve been away from the internet for about a month, so it is nice to see the progress that has been made. Will the recut DSF’s cause any issues with custom scenery?

Great news! I have been waiting for this since I got the DK1 last year. Let us know if you need testers! I have both a DK1 and a DK2.

2) Played with cloud deck and breakout on an ILS. Better than before, but pluging in cloud base MSL does not agree with visual of approach lights, and if you press “CAT-I” you get different MSL base (near field elevation), but proper visual of approach lights. More playing around required to check out and file bug report.

3) Observation: At Dusk, flying into low level status cloud deck, the earth is nearly black, occasional ground contact, and when subsequently descending on glidepath, go into solid clouds where the “light” level increases to daylight levels rather than remain nearly dark(black). Again, I’ll play around some more and then file bug report.

4) Observation: At initial takeoff roll, surface “roughness” of a smooth runway (KBUR Rwy 08) makes the wings rock +/- 5 degrees until airspeed above 10-20 kts. Not sure if this is modeling the thickness of the paint markings or not enough “gooeyness” the tires. As this rocking motion is near 3-5 Hz, the three external computer/screen visuals don’t remain aligned.