I’ve found a problem that seems to have cropped up between SU3 and the SU4 beta. I have a small GA airport scenery that uses painted lines to lay down custom textures for my taxiway centerlines. In SU3 (release), the lines auto-connect in the scenery editor where two taxiways join. Using this same scenery, which was compiled in SU3, in the SU4 beta (1.6.25.0), there are two places in the scenery where not only do the lines not auto-connect to one another, but the custom texture seems to display in full over the final vertex of the disconnected line.
I’ve attached screenshots of both disconnects, taken in SU3 and the SU4 beta.
Mabye you can install that and have a look at it in the sim. Don’t know if it helps but I thought I may as well let you know about another affected package. Maybe you can find some similarities
Hey Bill and Boris, this issue has been there for a very long time now since SU2. If you have the taxiway line or afcad line (for lights/taxiways) nodes very close to or intersects your custom painted line nodes you’re bound to see your custom taxiway painted line do what you’re seeing. Make sure to space the taxiway node away from your custom painted taxiway line node.
That is interesting. There was a similar bug in 2020 where when the nodes were too close together you could see the line either having a slight discontinuity, or the line started to twist around itself and almost looked like some sort of spiral. But it wasn’t like this where you could all of a sudden see the whole texture.
After the release of SU4 failed to fix it, I made a change in my project file (relocating the taxiway nodes slightly) that did. I’ll have to go back now and see if the latest update makes a difference.
