Hi all This is just a small note that there is a xBDM (x instead of X) airport code in current 2012.04 xplane data cycle (2012.04). This does not affect flightgear because flightgear still works with it’s own/older apt.dat fork. But if someone (like me) is working or doing experiments with recent apt.dat this might throw some errors processing the current apt.dat, depending what tools you use. It will be corrected with next xplane data cycle coming out soon.
Another small note about my EMAS improvement: The proposal to integrate EMAS into apt.dat goes into direction of having EMAS as a new surface type "for any piece of pavement, so that the EMAS can be added as a arbitrarily-shaped chunk of pavement. This would require fewer file format and sim changes - just a new art asset and some sim changes relating to surface friction." (R. Peel). EMAS is not integrated into xplane yet and it is still discussed, but I sent my available data to Robin Peel already and maybe xplane shows up with EMAS soon? Now to integrate EMAS to flightgear I would need some help. I don’t know how to set a new material/object/friction in flightgear for such at the moment. If someone is interested in helping out here, please send me a note. Thanks a lot. Cheers, Yves ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-scenery mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-scenery
