Comments on: Scenery Packs – the New Rules https:/2012/09/scenery-packs-the-new-rules/ Developer resources for the X-Plane flight simulator Thu, 27 Sep 2012 01:36:23 +0000 hourly 1 https://wordpress.org/?v=6.6.1 By: Brian Godwin https:/2012/09/scenery-packs-the-new-rules/#comment-5963 Thu, 27 Sep 2012 01:36:23 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5963 Awesome! Thank you sir! Importing an old .dat into a newer version did duplicate the airport, but I was able to group my work, drag it into the new airport list and delete the remainder of the old.

You rock, and saved me a ton of work!

]]> By: Ben Supnik https:/2012/09/scenery-packs-the-new-rules/#comment-5962 Wed, 26 Sep 2012 23:46:32 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5962 In reply to Brian Godwin.

In WED 1.2 you need to _explicitly_ import elements in your scenery pack to see it in the XML.

]]> By: Brian Godwin https:/2012/09/scenery-packs-the-new-rules/#comment-5952 Wed, 26 Sep 2012 20:01:09 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5952 Ben (or Chris S.), “slightly” off topic here. I am trying to collaborate with another scenery designer. He is doing the graphical and I am providing the ATC taxi routing. He was finished with changes to apt.dat and only working with Overlay Editor, while I started with his apt.dat and did the ATC. When I replaced the apt.dat with mine in his finished package, WED will not read my information, but XP reads it fine (I assume the issue lies with the XML file being out of sync)? Unfortunately, I am not finished with the route creation. Is there a way to get my apt.dat data to sync with the XML file or am I SOL and need to start over?

Thanks!

Brian

]]> By: Robert https:/2012/09/scenery-packs-the-new-rules/#comment-5925 Tue, 25 Sep 2012 18:13:28 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5925 In reply to Jomni.

This is a great tool doing exactly that….

http://code.google.com/p/xaddonmanager/

]]> By: Robert https:/2012/09/scenery-packs-the-new-rules/#comment-5924 Tue, 25 Sep 2012 18:11:05 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5924 In reply to Tom Knudsen.

+1

]]> By: SqrtOfNegOne https:/2012/09/scenery-packs-the-new-rules/#comment-5918 Tue, 25 Sep 2012 02:36:48 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5918 In reply to Ben Supnik.

Thanks.

]]> By: Jomni https:/2012/09/scenery-packs-the-new-rules/#comment-5916 Mon, 24 Sep 2012 14:59:28 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5916 In reply to Ben Supnik.

That great! Looking forward to more improvement. At least we now have control.

]]> By: SqrtOfNegOne https:/2012/09/scenery-packs-the-new-rules/#comment-5914 Mon, 24 Sep 2012 13:48:09 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5914 In reply to Ben Supnik.

Fair enough. Thanks.

]]> By: Ben Supnik https:/2012/09/scenery-packs-the-new-rules/#comment-5913 Mon, 24 Sep 2012 12:44:25 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5913 In reply to SqrtOfNegOne.

I don’t think the in file is documented beyond this blog post. But also I am not sure that what you are looking for is a function of the sim – if any scenery pack has a requirement on something else (and hopefully most do not) then the scenery pack needs installation instructions.

The only other rule is: overlays should be higher on the list than orthophotos/meshes. (This replaces the old rule “overlays should be earlier in the alphabet than orthophotos/meshes.)

]]> By: Ben Supnik https:/2012/09/scenery-packs-the-new-rules/#comment-5912 Mon, 24 Sep 2012 12:42:02 +0000 http://xplanedev.wpengine.com/?p=4513#comment-5912 In reply to Jomni.

Agreed – the .ini file is meant as a foundation on top of which a GUI will (someday) be built. But for now it solves the problem of installation/update thrash.

]]>