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

FSXA Vector line acting up (Solved)

Heretic

Resource contributor
Messages
6,830
Country
germany
So I've got two vector lines in two different places. Let's call them line 1 and line 2.

- Both were made from exactly the same source data
- Both were processed with SBuilderX 3.13. I've absolutely, definitely and surely selected both lines before I've compiled the .bgl.

- Line 1 uses texture A with vector line autogen
- Line 1 shows up fine in every aspect

- Line 2 uses texture B without vector line autogen
- Line 2 showed up in FSX exactly once and then never again

- Textures A and B are in the exact same format (DXT5 .bmp), both possess the same features (all-white alpha, mipmaps) and are in Scenery\World\Scenery

- The terrain.cfg entries for lines 1 and 2 are identical twins, save for texture assignment, StripWidth and GUIDs

Things I've tried:
- Rebooting to flush the page file
- Triple checking the textures for a black alpha channel
- Creating and recreating the terrain.cfg entries again and again
- Assigning texture A to line 2

Nothing worked.

Texture.cfg entries:
Code:
//Border Strip narrow
[Texture.488]
Name=Border Narrow
guid={d9894c0a-97d2-4638-8f9f-2a7285f27179}
Textures=Z_Border.bmp,Z_Border.bmp,Z_Border.bmp,Z_Border.bmp,Z_Border.bmp,Z_Border_LM.bmp
Layout=3_PLUS_1
StripWidthMeters=75
LandClassRemapType=none
VectorAutogen={09b0b994-ad86-4dcc-b6c0-f5b30d5d1eba} (Berlin border Objects)
ExcludeAutogen=Yes
FlattenMode=none
FlattenPriority=flat
RenderToTexture=yes
RenderPriority=110000
Water=No

//Border Strip wide
[Texture.489]
Name=Border Wide
guid={b036b318-7b42-4265-ac9a-daf30049a16a}
Textures=Z_Border_Big.bmp,Z_Border_Big.bmp,Z_Border_Big.bmp,Z_Border_Big.bmp,Z_Border_Big.bmp,Z_Border_Big_LM.bmp
Layout=3_PLUS_1
StripWidthMeters=250
LandClassRemapType=none
ExcludeAutogen=Yes
FlattenMode=none
FlattenPriority=flat
RenderToTexture=yes
RenderPriority=110000
Water=No

This is making me angry. Effin' piece of-



- Edit:

- Rechecked the vector line assignment in SBuilderX and temporarily assigned line 1's terrain.cfg entry to line 2. This works and shows that the source data isn't at fault.

- Shortened the texture name for line 2. No joy.

- Reordered the entries for both vector lines in lines.txt in SBuilderX' "Tools" folder to reflect the same numbering as in the terrain.cfg. Reexported the .bgl and my line 2 now shows up.

*Groan*
 
Last edited:
Back
Top