Sceneries; Condor1 to Condor2… 'problems' on the edge of the map!

[Xanix]

Hello. I don’t know, if the members that made my favorite Condor 1 sceneries, are going to upgrade them, for Condor 2.

I’ve already converted Portugal, AA and California...

Everything is perfect on the middle of the scenery… on the edge, I get this strange vertical lines!
Does anyone know what is causing this? Is there a solution?

I get these ‘artifacts’ in all converted sceneries, (near the ‘water’ I think).

Ambri; everything is perfect!

Venezia; strange vertical lines!

[arneh]

If you've converted the terrain height with TrnToTr3, then you've probably run into this bug in the converter:
viewtopic.php?f=37&t=17724

You can fix it by setting all the too high altitude values to 0 with the flatten tool, although that may be a lot of work.

[Xanix]

If you've converted the terrain height with TrnToTr3, then you've probably run into this bug in the converter:
viewtopic.php?f=37&t=17724

You can fix it by setting all the too high altitude values to 0 with the flatten tool, although that may be a lot of work.

Thank you for the explanation. So, the problem is during the terrain conversion.
Can you tell me where is that ‘flatten tool’? I can’t find it on the ‘LandscapeEditor’ application.

[JBr]

In LandscapeEditor activate the height map layer, FLATTEN button will appear in the toolbar. If you zoom in enough, the button will become active and you may use the flatten tool.

[arneh]

Select the height checkbox on the left of the landscape editor, then zoom in a lot in a problem area until you see the elevation numbers on the map, like in the last picture in viewtopic.php?f=37&t=17724

Then select the "flatten tool" on the left side of the landscape editor, set elevation to 0 and start "painting in" the areas which have 65000-something values.

[Xanix]

Hi. Thank you all, for the details. ‘Flatten’ is easy to use, when zoomed in. My only problem; there are lots and lots of incorrect ‘points’, near the coast! «arneh» was right; is better to wait for an update, of the converter…

[Jan Oorthuijsen]

You have to re-process your 30 meter srtm data files in Qgis with ( fill with no data ) and one by one.

[arneh]

You have to re-process your 30 meter srtm data files in Qgis with ( fill with no data ) and one by one.

Which srtm files? This is when converting a Condor 1 trn to Condor 2.
The original srtm files were 90 m, and didn't have these errors, and neither did the Condor 1 trn-file. The errors only occurred on converting to Condor 2 .
And I don't think Qgis can work with the tr3 files Condor 2 creates.

[Andy1248]

I do not understand why anyone would convert a Condor 1 90 metre terrain into the 30 metre for Condor 2. The negatives of this process are clearly highlighted in the new scenery guide.
Creating a new 30m terrain from new Srtm data is easy, very straight forward and clearly explained in the new guide. In addition if the coordinates of your V1 scenery are known then it is very easy to clip your new 30 m terrain in QGIS to exactly the same size as your old V1 scenery.
Then your existing Condor V1 bmp tiles can then be processed through the Landscape Editor or by just using Nvdxt.

Creating Condor 2 scenery with a modified 90 M terrain is pointless and misses one of the best features of V2, improved terrain.

[NickB]

For converting a 'flat-land' scenery with a few hills, using the 90m tiles is OK. Using 30m resolution will provide no extra improvement. For mountainous areas, it is best to use 30m, and start from scratch.
Converting from the .trn file to .tr3 files can be simple, but the .tr3 files are 193 x 193, not the expected 192 x 192 size (64 *3 x 64 *3). Is there an overlap of some kind ?

[JBr]

People, stop hacking internal formats...

[arneh]

People, stop hacking internal formats...

Might be the fastest way to fix the buggy altitude values

[JBr]

The fastest way to solve the buggy values is to do a proper terrain from 30m data. As I wrote in the guide -- the best answer to "how to convert v1 scenery" is "don't do it."

[arneh]

The fastest way to solve the buggy values is to do a proper terrain from 30m data. As I wrote in the guide -- the best answer to "how to convert v1 scenery" is "don't do it."

No, making a 30m terrain is not the fastest, but it will give better results eventually.

I spent a lot of time on my Condor 1 scenery to flatten areas, and tweaking height values, work which I have to redo now. In addition, I have to use a different source for the 30m data than the 90m data I used for Condor 1, which means the terrain doesn't match the alignment of the textures completely anymore. For the most part it doesn't make that much of a difference, but it does look weird with water or lakes running up hills, so I also have to spend time adjusting water/lakes to the new terrain position. So my 30m terrain will be a lot more work than just converting the 90m terrain from Condor 1 would have been, and I had to seriously consider if I wanted to spend that much time on it when the difference isn't that big.