• 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.

Ade_gp 0.0.96

Floda, please see the post previous to yours. It warns that such errors may occur in that release.

You can either wait for the next release (<24 hrs) or simplify the poly.

Don
 
Gp.

gadgets said:
Floda, please see the post previous to yours. It warns that such errors may occur in that release.

You can either wait for the next release (<24 hrs) or simplify the poly.

Don
Click to expand...

Hi. I read it and I,ll stay foot the next 24 hrs. Good luck.

Chico
 
Beta version 0.0.96(n) attached.

The problem was in the 100m partitioning for FSX. So long as each partition line crossed only two edges of a large poly, all was well. However, if a partitioning line crossed more than 2 edges (say a VB-shaped poly more than 100 high - for which there would be at least four crossings in total), the partitioning was not performed properly, resulting in missing or extraneous triangles which may or may not have resulted in a triangulation error message.

But I think I've got it right this time. This version properly processes my (CYYJ) complex "V" and several other large, complex polys. I've also tested it on Jacques LSFT without apparent difficulty. And, Gary, it seems to do yours KTOL as well.

As often happens, this exercise resulted in simpler code.

Please give it a good workout.

Don
 

Attachments

Gp

Hi Don !

I have installed the latest version 96.n. and still got compiling problems. I send
you two pics. so you can see what I did. The result is not wright either .
Do I cross any edges? Do you want my ADE3 file? I'll give you everything just
to make it work :))

Thank's in advance:

Chico
 

Attachments

  • 1.jpg
    1.jpg
    263.5 KB · Views: 569
  • 2.jpg
    2.jpg
    324.4 KB · Views: 527
I doubt it's a line style issue.

Yes, please send me your ad3 file, Floda.

Don
 
Gp

Hi Don !
I feel miserable to spoil your victory on this GP stuff. I would be happy if you could go on inventing new eye candies for this family of desk pilots and scenery builders. But one day you will lit on the big cigar.
Tom I'll soon come back to you!

Best regards:

Chico
 

Attachments

Chico, just edit that line and save without making any changes and the problem will go away.

It appears at some point after creating the line you "tweaked" the position of one or more vertices in ADE without going to the ADE_GP editor. Doing so necessitates an entry to the editor and the compiler should have told you so. My job now it to find out why it didn't.

Don
 
Version 0.0.96(o) attached.

It adds a fix for Floda's issue - i.e., now both lines and polys are examined prior to compile to determine whether they require editing in order to be compiled and a warning message issued when that is the case.

From the surrounding code, it appears I previously omitted the check on lines simply because I felt it wasn't necessary. I am concerned, however, that now including it may prompt editing in situations when not required (as well as when it is). Please test on a variety of lines - patterned and non-patterned.

Don
 

Attachments

Gp

Don, sorry the same result (attachment). Could you see if I made some mistake?

Best regards:

Chico
 

Attachments

Were you "invited" to edit the line? If so, did you edit and save without making any changes, or did you cancel?

Don
 
Gp

Hi again Don !

Yes I did click "yes"when invited to edit, but did not make any change after that and compiled. A lot of clicking !!
Hope this information will help. B.t.w. it does compile now.

Thank you again.

Regards:

Chico
 

Attachments

  • Q.jpg
    Q.jpg
    84.8 KB · Views: 603
gp

Hi, yes it does compile but will I have those questions in the future "Do you want to edit it now ? and after that clicking "yes" ? Or will you make some
hokus pokus to get rid of it. I have made most of my ground polygons so I can
live with it. To answer your question, this problem is solved. Thank you Don.

I will take a look at the Twyshoulder.

Best regardes:

Chico
 
"Do you want to edit it now ? and after that clicking "yes" ? Or will you make some hokus pokus to get rid of it.
Click to expand...
The hokus pokus is already there.

Generally, when you edit a GP object other than a simple move of the entire object, you should call the GP editor. This is so the GP data can be updated. But, you are not forced to go to the GP editor at the time. And, so long as you don't attempt to compile, no harm is done.

However, there is a check performed prior to compiling an each object. If you've changed a GP object and you haven't opened it in the GP editor you are invited to do so then. If you accept, the editor opens. You can make any changes or just close it. This only has to be done once. If you decline, the object will be compiled with possible errors - but you'll be asked again at the next compile. You also have the choice of abandoning the compile operation altogether, but at the moment, this is awaiting Jon's "return" so he can add the associated code in ADE.

Incidentally, this is described on page 10 of the user manual.

Don
 
gp

OK, Don the Wizard ;),I roger that. Thank's for explaining it and I hope it won't bother you any more.

Best regards:

Chico
 
Version 0.0.96(q) attached.

It fixes the potential problem when compiling very small groups (=< 100m). As well, the scroll bars during compile (likely seen only at airports with complex GP arrangements) now work properly.

Don
 

Attachments

Don,
I was having the same problem. During compile I was also getting the edit window (mentioned in previous post) on all my GP objects. I would click yes to edit, click OK in the edit window, then moved on to the next object. I downloaded your lastest version and still having the problem. I does compile however.

I am also having trouble with ILS hold short lines. I can't get them to show up. The black backing shows.

Thanks,
Supernova48
 
I was having the same problem. During compile I was also getting the edit window (mentioned in previous post) on all my GP objects. I would click yes to edit, click OK in the edit window, then moved on to the next object.
Click to expand...
This is not a problem! You must edit a GP object after moving/adding/deleting vertices in order for it to compile. You should do so when you make the edits, but you are not forced to. If you don't, then the compiler reminds you and makes it convenient to do so at the time.

I downloaded your lastest version and still having the problem. I does compile however.
Click to expand...
Did you save the AD3 file after compiling to preserve the edits?

I am also having trouble with ILS hold short lines. I can't get them to show up. The black backing shows.
Click to expand...
Did you copy the taxiway_Mark.bmp as instructed in the manual?

Don
 
You must log in or register to reply here.
Back
Top