Noob question

[monks]

When I generate a set of filters on a terrain- is GC using the original terrain I imported- or the terrain from the last generation?

monks

[cajomi]

Most important when working with imported terrains is the protection slider. There you set, up to which level GeoControl takes the original imported terrain.
But if you have made a generation with a protection up to 64 and then change it to 256, GeoControl will take up to 64 the original, and from 128-256 the modified terrain.

[monks]

Now I understand.
I 've been tooling about with GC a fair bit and I'm feeling a bit of a weakness when
dealing with imported terrains. The main problem for me is that GC is very much all or
nothing- in that the whole Generation process happens at once- so everything goes through that one point of operations. I'd say that's generally a strength.
But as you said above, GC is using the previously generated terrains (up to a point). That
makes it more difficult to revise changes. OK, we have the Save terrain Settings- that's
something which I've finally gotten around to using bleh :) ! But this does not include the
original terrain so I have to constantly reimport the original terrain. Is there any chance
of having an option to include the original terrain in the Load Terrain Settings or is this
already included with Projects? (I've not used them much).

I've got a bit of a question forming and it's related to this whole Generation workflow and
Terrain Protection feature. I think it would super awesome if we could control terrain
protection on a per selection basis. I could not live without Terrain Protection with the
way I work (often imported terrains) but it's becoming something of a blunt instrument if
you want to use lots of filters over lots of Selections- which I do- and which GC 2.0 now
encourages.

Would it be possible to have an extra Terrain Protection slider for each Selection which if
activated overrides the Terrain Proetection in the General Tab? This would mean that we could have lots of control when working with both imported terrains and random ones- especially the imported ones. At the moment for ime it's like saying "here you have all of these selections and filters to place here and there but everything has to be put through this one filter of Terrain Protection at the back-end" which kind of robs you of a lot of that front-end control.
I think this would be doubly useful once tiling and procedural zoom is implemented- ie
larger terrains if EVERYTHING has to go through the one Terrain Protection filter.

monks

[cajomi]

How about more serious feature requests, that are possible in the given time?

[monks]

How about more serious feature requests, that are possible in the given time?

What!? You think I sat there at the computer in the midst of my day teaching clients and typed that for the fun of it?

You've just been complaining about lack of tester feedback. Now you're getting some (lots) and you insult me with a reply like that!


The Terrain Protection by Selection is a serious suggestion. I hesitate to call it a request (note I referred to it as a question, not a request and hey look where it's posted: -> 'discussion') because I realised that it might require some work to restructure GC to do that.
Such as response is completely unwarranted and unfair as we have no real idea of how much time you have, or what business plan you are working to. WM for instance has been in beta for a year now, so these things can be rather protracted.

monks

[cajomi]

Well you are right, I did not realized it, that is was in the discussion section.

I did not mean, a better work with imported terrains. They should load always automatically at the start level from the original file, and that I will implement.

You must have missed, that the release is planned for summer. I am doing this as full time job, so I need releases to get payed for my work.

It might sound silly to you: But reading and answering or discussing such requests, really takes time. So, make ten of such requests, and they cost one feature (smaller one) in the final release.
With serious I mean requests, that are more common, not to specialized for your needs. I think you know, that your approach is really not typical for others.
I am definintly not the typ of developer, who simply does not answer and read to concentrate on the coding.
But sometimes I feel this impulse, to make it like other developers.

So you would do me a favour, if you try to request what you basically need.
The project panel will open again and what you are describing can be realized with different layers.

[monks]

I did not mean, a better work with imported terrains. They should load always automatically at the start level from the original file, and that I will implement.

Thanks!

You must have missed, that the release is planned for summer. I am doing this as full time job, so I need releases to get payed for my work.

Ah, OK. I missed that.

It might sound silly to you: But reading and answering or discussing such requests, really takes time.

Not at all, actually, you are very responsive in the forums. I would rather have a heated discussion than no discussion. ;)


But sometimes I feel this impulse, to make it like other developers.

Yes, I think no more discussion of other apps is a good idea.


So you would do me a favour, if you try to request what you basically need.

Sure. :)

The project panel will open again and what you are describing can be realized with different layers.

OK, I'll definitely look into that.



monks