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

George's ADE-GP 0.0.45

GHD

GHD

Messages
12,244
Country
england
If not brilliant Don, it's almost perfect :D

I wasn't quite sure about the Lines_Def parameters, but I think they are:

Code: 
Parking Single Row | gp_Patterns | V=944 | 75 | 1024
Parking Double Row | gp_Patterns | V=806 | 130 | 1024
                                     |      |      |
                                     |      |      |
                                     |      |      |
                                     |      |      |--- Width of texture
                                     |      |
                                     |      |
                                     |      |--- Delta height
                                     |
                                     |
                                     |--- No of pixels from bottom of texture

It is unusual to measure bit maps from the lower-left, it is normal for the origin to be at the upper-left.

Only one problem. Having defined a line, it is not possible to edit it:



The results, using width 12 metres for the double row and 8 metres for the single:










Edit. Oops, sorry, I posted in the wrong thread :o

Perhaps Jon could move it?
 
Last edited:
Which thread do you want it in George?
 
Thanks Jon :)

Don,

I have a problem with 0.0.45 in that when I select a texture, the preview bitmap covers the vertical scroll handle so I cannot scroll down.

 
Oh bother - do I need to put them together?
 
No, as long as Don knows about both of them, which was my goal in posting. :)
 
when I select a texture, the preview bitmap covers the vertical scroll handle so I cannot scroll down
Click to expand...
Other than the exception reported in the other thread, if we're down to this level, we're almost there.

Don
 
when I select a texture, the preview bitmap covers the vertical scroll handle so I cannot scroll down
Click to expand...
Other than the exception reported in the other thread, if we're down to this level, we're almost there.

Don

Edit:
I wasn't quite sure about the Lines_Def parameters, but I think they are:


Code:
Parking Single Row | gp_Patterns | V=944 | 75 | 1024
Parking Double Row | gp_Patterns | V=806 | 130 | 1024
| | |
| | |
| | |
| | |--- Width of texture
| |
| |
| |--- Delta height
|
|
|--- No of pixels from bottom of textureIt is unusual to measure bit maps from the lower-left, it is normal for the origin to be at the upper-left.
Click to expand...
Your assumptions about those three fields are correct. As for pixel numbering orientation, texture U/Vs are specified from the bottom left hand corner. While I appreciate graphics are generally specified top to bottom, changing this could have a destabilizing effect. I will, however, make a note in the User Manual.
 
George, you'll be happy to know that your observation about pattern offsets being specified from bottom-to-top rather than top-to-bottom was the clue I needed to fix the display of horizontally-oriented patterns.

Incidentally, when I refer to horizontzlly- or vertically-oriented patterns, I'm referring to the orientation of the patterns on the texture, not the orientation of the texture sheet itself. In the case of gp_Patterns.bmp being used by George in the example below, I would refer to that as horizontally-oriented patterns, even thought the major axis of the texture sheet itself is vertical.

Don
 
Right - in fact, most textures used for horizontal lines would logically be vertical textures, while the opposite would be true for vertical line textures. That way you can pack in more line styles. :)
 
Only one problem. Having defined a line, it is not possible to edit it:
Click to expand...
George, do you still have the file that caused this problem? If so, please send it to me.

Don
 
I have a problem with 0.0.45 in that when I select a texture, the preview bitmap covers the vertical scroll handle so I cannot scroll down.
Click to expand...
George, the texture is displayed as a tooltip. While you can alter the size of a tooltip, I can find no way to alter it's position.

Don
 
gadgets said:
George, do you still have the file that caused this problem? If so, please send it to me.

Don
Click to expand...

Hmm, whilst preparing to send you the file, I edited one of the new single segment polyline and got the error. I then edited a multi-segment polyline and it worked fine. I then edited the new single segment line and I no longer got the error :confused:
 
George, I've just discovered a typo in last night's update that would result in an exception being thrown for single segment line using a verically-oriented texture. (It's now fixed.) Horizonal orientation is OK.

The error to which I was referring in my earlier request, however, was the "start-up" error you reported.

Don
 
gadgets said:
The error to which I was referring in my earlier request, however, was the "start-up" error you reported.

Don
Click to expand...

Try the attached Don. If you edit the line indicated, the error is displayed and the vertices in the editor window are incorrect.

You will also need to add:

Parking Single Row | gp_Patterns | V=944 | 75 | 1024
Parking Double Row | gp_Patterns | V=806 | 130 | 1024
Parking Slant | gp_Patterns | V=560 | 130 | 1024

to Lines_Def.txt.

 
Last edited:
You must log in or register to reply here.
Back
Top