Suggestion

[monks]

Hello- I've got a suggestion regarding the 3D preview. The way I've been working is to keep the 3D prev minimised and use the 3D button to pull up the prev and go straight into rendering. The problem is, it doesn't remember the previous settings (when minimised), so I have to keep turning off shadows, and reorienting, etc. I prefer to have the window minimised to conserve screen space.

Also, I've noticed, when importing a 1024 .ter and folowing your instructions, Johannes, that one cannot really put protect terrain up to the max (in this case 512) because vertical straight line artifacts appear. I have to turn protect terrain down to 256, which introduces a bit of blur to the terrain. It just so happens that in this case that is the first thing I was going to apply anyway :lol: so it's not troubled me, but I guess I'm interested to know, why these lines appear? Would it be possible in any way to avoid these lines and get 512 protect terrain?

monks

[imported_cajomi]

Hello Monks,

well I will have a look at these lines and what they are caused by, of course it should not be.

To the 3D view:
If you use the "3D" button above the main view, all settings are resetted, if you maximize the 3D view window and then use the "Render" buttom, the settings for the 3D view keep.

Johannes

[monks]

The lines are only vertical, not horizontal, so that suggested to me that it wasn't a 'tiling' problem: if GC even uses that concept (?)

If you use the "3D" button above the main view, all settings are resetted, if you maximize the 3D view window and then use the "Render" buttom, the settings for the 3D view keep.

I know, but that is one extra mouse click, so two in all (maximise, render). I would go one step further and suggest a hot key, which does both: maximise:render (with settings remembered).
I really like to streamline my working if I can, right down to the minimum steps, because I tend to do a lot of experimenting and double checking, so two mouse clicks at opposite ends of the screen, starts to wear after 50 times (well about 10 for me actually :lol: ).

So far though I've had good terrain results :D

monks

[imported_cajomi]

Hello monks,

I have not found the lines here. May be it depends on which software created the terrain.
Which software was it in your case?
Or may be it was the filter.

Johannes

[monks]

Hi Johannes, the terrain was first exported from Wilbur's Tess as a .bt. Then imported to Leveller and exported from there as a Terragen. Then imported to GC.

The terrain does not show any of the lines when imported back into Wilbur or Leveller as a .bt. It also opens fine as a Terragen in Wilbur and Leveller.

It sounds like it might be GC's import of the TG file.

monks

[imported_cajomi]

was it an even or odd size?

[monks]

It was even: 1000 px square.
I've sent you an email with a couple of comparative shots.

monks

[imported_cajomi]

GeoControl is not build to import such free sizes: Only the 16er row and 16er row+1.
I am wondering, that it does work without an error message.

I will look, whether I can widen up the import, but it will be not trivial.

Johannes

[monks]

I finally got a little time to have another look at the demo. Yes, I think 1024 will be fine for our use, so that's not really a problem now. I now understand why this is happening- it's the powers of 2 thing isn't it? Hence why the protection = 256 is OK with a 1K terrain, but 512 is not OK.
I'll just use 1024 terrains. :)


//EDIT
I tried 1024 terrains in TG format: Geoncontrol doesn't open them properly: tried two exported from Leveller and Wilbur. The 1025 terrain size works fine.

Cheers,
monks

[imported_cajomi]

I will have a look to fix that.

Johannes