- Messages
- 783
- Country
I am responsible for 35 freeware airports, afcad and flatten made with ADE. In other words, I always get two files when exporting, the afcad, and the CVX.
Now other people uses ADE to open my airports (open from bgl), in order to make their own version. Fine. Until they export directly to my scenery folder. Then I get lotsa mails about bugs in my scenery, trees all over the airport, etc. Not fine. Try to tell people to NOT export directly to the scenery folder. Doesn't work...
This is the problem with ADE: Even if no terrain polys are drawn in the project opened from my bgl's, when exporting, ADE overwrites my existing CVX file. The CVX bgl is gone! So people end up with NO CVX file in my airport package, and I get a lot of buggering.
Why does ADE do so? There is no sense in this. I hope it is possible to do something about it. When no terrain info is listed in ADE after opening from a bgl, ADE should not erase the existing CVX
Cheers,
Now other people uses ADE to open my airports (open from bgl), in order to make their own version. Fine. Until they export directly to my scenery folder. Then I get lotsa mails about bugs in my scenery, trees all over the airport, etc. Not fine. Try to tell people to NOT export directly to the scenery folder. Doesn't work...
This is the problem with ADE: Even if no terrain polys are drawn in the project opened from my bgl's, when exporting, ADE overwrites my existing CVX file. The CVX bgl is gone! So people end up with NO CVX file in my airport package, and I get a lot of buggering.
Why does ADE do so? There is no sense in this. I hope it is possible to do something about it. When no terrain info is listed in ADE after opening from a bgl, ADE should not erase the existing CVX
Cheers,
Last edited: