Re: WS3.0 Philosophy and Status

Wayne Bragg <[email protected]> Thu, 28 May 2026 17:48:49 -0500
Newsgroups gmane.games.flightgear.devel
Message-ID <CANM4b0La4fRLE+abYaYPT62xayBqaJCcetWNZQ7f_zvaST32_Q@mail.gmail.com>
"I would not recommend using it for testing purposes as it is quite far
behind "next" in terms of development."

FYI,

I have been using 2024.1.x to display some of the WS3.0 tooling output. As
Stuart stated, there are issues when trying to do this, OSM roads, and even
buildings to some extent, are not working correctly, the line data
generated with genVPB.py won't display properly. It requires some
unorthodox procedures to get it to work at all and be able to see OSM data
with 2024.1.x and WS3.0 scenery. Even with that, buildings and road
elevations are off because they are the resources provided for WS2.0
terrasync being hacked to show up in WS3.0 scenery. I have been showcasing
some of the scenery generated with the newest NLCD rasters I am writing
smoothing processes for. I'm temporarily  using it to compare WS2.0 stock
scenery against WS3.0 scenery to demonstrate the superiority of the WS3.0
tool chain. It is a temporary use case for convenience.
Wayne

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel