ADE gp 0.0.90

[robystar]

Hi,

As the line.def does not seem to work for what I am trying to do, I deleted the line.def entry and made a ground poly instead.
I used the rectangle helpershape to make a 21 x 1375m ground poly textured with my 256 x 1024 texture.
And this is what happens when I try to resize:

I sent the error report.

I close the error report and continue, this time renewing the texture entry and this is what happens: (note the texture size mentioned this time is correct but the vertices are not)

So I try to resize horizontally and this is what happens:

Just for the sake of testing (I gave up on the other) I rotated the texture only to notice that one of the vertices is gone AWOL:

Roby

PS Every time I open the texture editor to check on the line.def properties of a texture and click OK, a new line .def is inserted in the line.def.txt, something which is rather awkward as you then get two of the same in the lines.def.

 

[gadgets]

As the line.def does not seem to work for what I am trying to do, I deleted the line.def entry and made a ground poly instead.
I used the rectangle helpershape to make a 21 x 1375m ground poly textured with my 256 x 1024 texture.

As you've discovered, handling a ground poly of this size and aspect ratio with such a tiny (coverage-wise) texture is rather difficult. You should continue to use a line - which others have used quite successfully in a similar application (runway/taxiway edge-stripes).

It would seem there's still a problem with resize - which I'll investigate. However, once the exception occurred, any following issues are likely related to what did or did not happen when the exception occurred. The option to continue after an exception is a built-in feature of NET/Framework. The fact that you could continue (often you can't) doesn't mean your data is intact.

Object cannot be resized any smaller

In order to be able to recover from resizing and maintain the original shape, there is a lower limit (3 pixels) to the horizontal and vertical distance between adjacent pixels. If you want to resize smaller, you must zoom in first

I rotated the texture only to notice that one of the vertices is gone AWOL:

It is clear from the earlier screenshots that the shape is not rectangular. Whether this is due to two vertices being superimposed on one another or a missing vertex is impossible to determine from the screenshots.

Every time I open the texture editor to check on the line.def properties of a texture and click OK, a new line .def is inserted in the line.def.txt, something which is rather awkward as you then get two of the same in the lines.def.

There is no OK button on the Texture Editor dialog.

Don

 

[gadgets]

And this is what happens when I try to resize:

How did you "try to resize". While I can't say for certain, it would seem that no vertices were in view. That being the case, how did you select the vertices (some of which must have been selected in order for the resize buttons to be enabled)?

Don

 

[gadgets]

What are you trying to tell us, George?

Don

 

[robystar]

Hi Don,

Replying to your comments:

- " What are you trying to tell us, George?" I'd say: ???
- All vertices were in view but as you can see there was already one missing in the third screenshot.
- I double clicked all vertices so as to be able to resize and drag.
- Windows Update updated the dotnet yesterday. Do not know if that could have some influence on things?
- zooming did not help at all and the 4th vertex was already gone at that time.
- As you can see from the first screenshot the shape was clearly a rectangle i.e. a shape with 4 vertices.
- As you can see in all the screenshots there is definitely an OK button in the gp texture editor.
- True, I could also make lines with this texture as you could see in previous screenshots but they were made with the 0.0.62 or something and I am not able to do that anymore with the 0.0.90.
All in all, I think I have to go back to that earlier version and see if I can get it right in there and if I can then it means that something fundamental has been changed in my two weeks of absence.
Sorry Don, I wish I would have been able to tell you everything is fine now
(Could be my own lack of experience but so will it be for others that have not tried it yet or are just starting to use the gp_poly addon).

Roby

Update: forget about the George thing. I found out what thread you were referring to (I think).

 

[gadgets]

All vertices were in view but as you can see there was already one missing in the third screenshot.

If you check the first screenshot, you can see a slight slant in the left-hand (almost) vertical line, suggesting the vertex is already missing. I suspect the missing vertex is the cause of the exception, but I'm having no luck at all in finding when it disappeared. Did you do anything unusual immediately upon the GP Editor being opened? Can you confirm that the four vertices were there initially?

Windows Update updated the dotnet yesterday. Do not know if that could have some influence on things?

I doubt it.

As you can see from the first screenshot the shape was clearly a rectangle i.e. a shape with 4 vertices.

There are no vertices shown in the first screenshot and, as noted above, the 4th vertex seems to be missing already.

As you can see in all the screenshots there is definitely an OK button in the gp texture editor.

The GP texture editor is not shown in any of the screenshots - at least not in any I can access. Neither the Lines_Def.txt nor Texture_Def.txt files are written by the GP Editor dialog, which is the one you are looking at. So, I have no idea where this new entry is coming from.

I could also make lines with this texture as you could see in previous screenshots but they were made with the 0.0.62 or something and I am not able to do that anymore with the 0.0.90.

Why? What's stopping you?

All in all, I think I have to go back to that earlier version and see if I can get it right in there and if I can then it means that something fundamental has been changed in my two weeks of absence.

Nothing has (intentionally) changed that would cause the difficulties you now seem to be experiencing. It shouldn't matter what version of the GP editor was used when a line or poly was created. The only change I recall to the data held by ADE was the addition of a texture scale. (I don't recall in which version that was added, but it certainly was more than two weeks ago. In any case, at worst, that would result in incorrect texture scaling which, once corrected, would stay corrected.)

 

[robystar]

Hi Don,

Show you the ADE screenshot I forgot with the rectangular helpershape and the ground poly:

I hide the helpershape and rightclick on the groundpoly to check its properties and notice that there are only three vertices shown.

Re the OK button: sorry, mixing things up. I should have said 'when clicking update definition files'. It does not update but adds another line.def entry.

Re using the polyline instead: I was unable to get the same result as I did with the previously made polylines (see the screenshot again) for one reason or another.

(Could be I get confused with the UV mapping of the texture. Could you explain once more what exactly means U=1 | 1 | 1024 for example ?)

Tks,

Roby

 

[gadgets]

and notice that there are only three vertices shown

Yes, I'm working on that now.

I should have said 'when clicking update definition files'. It does not update but adds another line.def entry.

When you click that button, ADE-GP assumes you've made some update you want to save. If you want to close without making an update, click "Close".

Could you explain once more what exactly means U=1 | 1 | 1024 for example ?)

It means the pattern starts 1 pixel from the left, is 1 pixel wide and is on a texture sheet that is 1024 pixels wide. with the texture sheet you showed in your screenshots yesterday, I would have expected something like "V=0 | 25 | 1024".

Don

 

[robystar]

Hi Don,

That is very clear and what I expexted to hear from you. Thanks a lot.
Enjoy your sunny day, I am doing the same.

Roby

 

[tgibson]

Hi Don,

I'm back from vacation.

I am having a problem editing lines with 0.0.90. When I create a line using your 40F texture (which works fine) and then try to edit it, all I see are two vertices in the editor screen - no line.

The lines in my def files are:

gp_PatternedLines_40F|0|40F|false

Dashed - Short (Yellow) | gp_PatternedLines_40F | U=92 | 8 | 512

I don't think these are the problem, since the initial line creation works fine.

 

[gadgets]

Welcome back, Tom.

0.0.90 contains an error (as you've discovered). That error is fixed in 0.0.91 which you can pick up here.

(Jon was otherwise disposed at the time, so it was released in a non-standard manner.)

Don

 

[tgibson]

Hi Don,

Thanks for that, but 0.0.91 is doing exactly the same thing...

If I move a vertex in ADE and then edit the line I do get the proper display. But if I immediately return to the editor I then get the bad display.

 

[gadgets]

I read your post very quickly and made a bad assumptions. When you said "line", I should have realized the problem fixed in 0.0.91 wasn't what you were experiencing.

Rather than me spending time trying to recreate the issue (which no one else seems to be experiencing) with one of my test airports, perhaps you could send me an AD3 file which demonstrates it.

Don

 

[robystar]

Tried to tell you that, Don.
See my previous comments on my being absent and then trying to get a line done correctly once again.

 

[tgibson]

Sure, here's one, for FS9. It happens with every line I try to edit, so far.

 

[gadgets]

Roby, I'm having difficulty seeing where you previously mentioned the problem Tom has highlighted.

Until Tom jumped in, this entire thread (including your very first post) dealt with the missing vertex issue - which was what got fixed in 0.0.91. Perhaps I missed something, but I don't recall any other input since - before Tom's - related to lines.

If you are referring to this thread, I think you'll agree it would be quite a "stretch" for me to be able to infer Tom's issue from your descriptions in it - even if it is the same issue.

If you are experiencing a similar problem, perhaps you could describe the symptoms. That should not only make my job easier but ensures your reported issue is fixed.

Don

 

[gadgets]

Tom, I can't reproduce. I've tried editing virtually every line in the airport you sent me and they all display as I would expect.

I've confirmed that my lines_def and texture_def entries are the same a yours.

Is it one particular line that gives you the problem?

I recall a similar problem several weeks ago, but it was fixed.

Jon released a new beta installer version during your absence. Is it possible you are inadvertently using an old version of ADE_GP. Does the GP Editor title bar display 0.0.91 as the version number?

Don

 

[tgibson]

Hi,

I am using 1.60.4932 (that included the 0.0.90 GP Editor), and upgraded to 0.0.91 manually. I can confirm that the menu bar says 0.0.91. Sometimes I can see the correct display as I enter the editor, but it quickly reverts to just two vertices, connected by a line.

I tried to edit several existing lines, and then tried it with 2 or 3 new lines I created, both single segment and multi-segment. All failed.

Note that I am using XP, which may cause differences?

 

[gadgets]

I would guess that the two vertices are shown side-by-side at the bottom of the texture. Please confirm

XP shouldn't make any difference. But, given that sometimes you briefly get the correct display, this suggests an internal timing/sequencing issue -which I recall was what caused the initial problem. I need to go back and try and remember how I fixed the previous issue to see if by fixing that issue in WIn 7 I caused it to fail in XP.

I presume you have NET/Framework 3.5 or later.

Nothing else comes immediately to mind.

Don

 

[tgibson]

Yes, on a vertical line texture the two vertices are at the bottom of the texture, in the correct horizontal positions (as I remember). I presume I have the correct NET Framework - it worked fine earlier.