Thanks. Fixed.

“One of my concerns about the public beta has been the number of aircraft I have seen that were developed or updated in the last year or two and yet use authoring techniques that were in the “obsolete but supported” bucket for X-Plane 10. The window of compatibility where we provide support for old and new features doesn’t help if people don’t migrate.”

Thats a pretty good reason why not budging on the change, may be a good thing, past practice shows it to be detrimental.

Yes, I get my airspaces from soaringweb. Just a correction, their URL is soaringweb.org.

Ehm, I just don’t get the point – maybe I missed something here. But I use the Flight Factor Boeing 767-300ER Pro every day in XP 11. The current version still uses the GNS430 folder.

All user action required to make the 767 work fine again is to create the now missing folder manually: “X-Plane 11\Custom Data\GNS430”

Then just edit the AIRAC data update tool to the new path and you are all set to go flying. It is even possible to simply copy that folder of XP10 to that path and all add-on birds depending on the GNS430 folder should run fine.

So what is it that LR should do to XP11?
Creating a folder is a 5 seconds job only and can easily be done by the user.

Just my 2 cents.

Regards,
Marc

Since you have now opened the parallel email discussion, I will not comment on this in public.

Philipp – You’re just being inexplicably stubborn. Adding the GNS430 folder back to X-Plane 11 has zero impact on LR, and on the rest of your brilliant new navigation efforts.

The fact is that if you don’t add the GNS430 folder back, you are basically showing that you do not care about the add-on developers that have to work around this deletion, and the hundreds, if not thousands of users that will now need to either deploy a questionable work-around themselves or seek an update to their product, which may or may not be available. I’ve already had to spend significant time with a client this morning, solving his installation issues that are a result of this very situation. If the human cost in time and aggravation are unimportant to you, then continue to resist. You’ve presented no good reason not to include the GNS430 folder, only a determination to not yield to simple logic and a zero cost correction.

Skewering my analogies is also not constructive. You know what I mean. Is the GNS430 navdata solution perfect? No! But it’s been out there for the better part of the X-Plane 10 run, and you have an ethical obligation to maintain it for a reasonable period of time. Give developers a chance to migrate away from using the GNS430 folder over a period of years, not months. What you’re basically doing is to suggest that it’s okay to pull the rug out from devs and customers. X-Plane 11 will be great, but it doesn’t need to be a significant hassle to developers and customers at the same time. Right now, it is just that.

Custom airspaces in openair format can be installed into Custom Data/airspaces/ You can get them for example from soaringweb.org
We have no plans to introduce a different file format for airspaces.

The ARINCDecoder program is just a suggestion, there exist other tools in the industry to work with ARINC424 files for sure. Generating a user waypoint through the map is currently not implemented in XP11. You can however use the XP11 default FMC to generate user waypoints, that also causes a valid user_fix.dat to be generated that you can then work with.

What I noticed is that there is no mention about airspaces. There is a airspaces folder under Default Data with USA airspaces, and I added an airspaces folder to Custom Data with airspaces data for Canada, etc..

Can you comment about what the correct way is to maintain airspaces, and what LR has in mind for that in the long run?

Thanks a lot for feedback Philipp. So user_fix.dat is created when a fix is edited using the map GUI in X-plane…to add other VRP I just have to use the ArincDocoder v4.4 then convert in X-Plane format using the convert 424toxp11 tool? I’m asking because in previous X-Plane version I worte a PHP parser to read data from official ENAV AIP to add the 417 VRP to the X-Plane dataset….adding those VRP manually one by one into the ArincDecoder should be a pain. Thanks again for feedback