• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Crash While Clicking Taxiway

Messages
108
Country
us-pennsylvania
Error when clicking on a taxiway I had just made.
Repeatable.
Normal Blue Taxiway.
Select and turns light yellow
Double click on center line and the error in the first picture

Also, the taxiways do not appear in FSX after a compile. The other ADE created elements appear as expected.

Windows XP/SP2 DualCore 2.5ghz 2gb memory 8600/256mb video card


Dick Boley
 
Last edited:
Dick

Can't replicate Can you please repeat the problem and then attach or email me ade_200806.log
 
Dick

Can't replicate Can you please repeat the problem and then attach or email me ade_200806.log

ADE 1.30 would not load anymore - refer to other error regarding transparency message. So I un-installed 1.30 and reinstalled 1.20 to start over. I tried the Taxiway problem in 1.20 and it occurred. The log is attached. The error message was the same as the original message.

Dick Boley
 
Last edited:
Dick - that log finishes before there is any Error reported - looks like you are working on an airport called 1LA - would you mind sending me the bgl file so that I can repeat your steps? jon AT scruffyduck.co.uk
 
The first thing to note is that there is only an exclusion polygon in the cvx file, not an airport background.

The other thing is that there is only one taxiway link together with a few orphan nodes in the bgl.



Perhaps you could attach your ADE file.

George
 
Last edited:
I see the same as George - there are some orphan nodes. I assume that the single taxilink is where your problem arises. I have selected and double clikced that a number of times without incident. I have tried adding another link and double clicking that. Again I can't replicate although clearly there is a problem that I can see in the log when opening the property dialog. I agree with George - we need the ADE file. As best I can tell from the error log this problem relates to an invalid taxi designator but unfortunately from the bgl I cannot identify the exact link since compiling re-numbers nodes and I am seeing 37 > 38 although those numbers do not exist in the bgl file any more. If we could find the offending link then deleting and recreating it would probably solve the problem. It is just possible id this airport originated as a bgl file from another utility that a designator problem transferred but it could be a problem in ADE. Having said that we have not had a problem reported on links since the early beta days.
 
Last edited:
While not identifying the specific problem, I was thinking about what was common when I had actually reverted to 1.20 with an error as well. As was suspected, I believe that the original project file was the common source since I always used that instead of trying to reconstruct the various in-place elements. Unfortunately that file was erased and now ADE 1.30 is working just fine with a fresh start.

There remains the possibility that the whole thing stems from mixing activities amongst different airport design programs (AFX).

I do not think that any more time need be spent on this, or the other problem I reported. All is well on all fronts right now!!

Thanks,
Dick Boley
Near Pittsburgh
 
Last edited:
While not identifying the specific problem, I was thinking about what was common when I had actually reverted to 1.20 with an error as well. As was suspected, I believe that the original project file was the common source since I always used that instead of trying to reconstruct the various in-place elements. Unfortunately that file was erased and now ADE 1.30 is working just fine with a fresh start.

There remains the possibility that the whole thing stems from mixing activities amongst different airport design programs (AFX).

I do not think that any more time need be spent on this, or the other problem I reported. All is well on all fronts right now!!

Thanks,
Dick Boley
Near Pittsburgh

Hi Dick

Many thanks for letting us know. While all utilities create something that FSX can read unfortunately some of the differences cause unexpected problems. AFX has a lot going for it but (like AFCAD) it uses it's own compiler rather than BglComp. We have always stuck with BglComp because we know that this is the standard set by MS and if we can pass something safely through that then we have a fighting chance (does not always work however :rolleyes:)
 
Back
Top