Planetside Software Forums

Well, now that we have the final 2.0 release, what more do you want to see?  Here are my current top 5 wanted inclusions:

• Georeferenced Image Maps
• True transparency for all materials/shaders without having to fight with the water shader
• Wireframe options for all imported objects
• A "Save As" package option to create a save file that includes all image maps, objects, object materials etc.
• Bring back a working "Variations" option for imported vegetation.  (This is obviously a very long shot and would probably involve working with Xfrog to make it work).

-Ryan

um yeah wire frame is a must maybe even open gl preview or preview objects like you preview the default sphere etc

Another thing I would like is to merge the tgo obj and lwo import function into just object import the amount of times I have clicked tgo import instead of obj navigated to the object and found out its an obj and having to quite out and use the tgo importer ::)

also I separate search path memory for each import and export function right now I open a file in my tg2 projects file then i go to open a terrain which i store in a terrain folder so then i have to navigate to the terrain folder
so separate search memory for
save file and open file
open terrain
open model
save render

and as ryan said transparency options for all imported objects
so a glass shader

also I wouldn't mind seeing more terrain modifiers like the twist and shear etc

I've actually goten used to having no wire frame preview.
I'm after proper transparancy, ie greyscale based
Stormingly good animation module
Unique variations would be sooo cool, but as you say that would need some Very close work with Xfrog or the development of an entirely new "Tree Growth" program
cant think of two more

Free Coffee and fags ...

:)

richard

• Yeah. A save archive option would be really handy.
• Unique variations.
• I also can't wait for SSS.
• Rolling Waves (even if not animateable).
• Support for animated, imported objects.

- Terje

Quote from: RArcher on April 27, 2009, 10:58:27 AM

• Bring back a working "Variations" option for imported vegetation.  (This is obviously a very long shot and would probably involve working with Xfrog to make it work).

-Ryan

Something else related to this would be to allow multiple objects to be imported into populations. With xfrog for instance you may have 2 or 3 variations of the same tree, maybe of different ages. If you could plug all 3 into 1 population, preferably with options to allow for biased towards 1 or other of the objects, you would have some nice variations. If you could also randomly vary the colour of the leaves, maybe via saturation along with the currently implemented random size and rotation options you would get some nice varied forests etc.

This isn't as nice as what your asking for and I also hope for the return of the variation option as well but if its simpler to add there is more chance of getting it in.

My nr.1 request is still fractal erosion. There _is_ a way and someone have already found it.

Also a build-in Macro creation system would be great, such as worldmachine has.

Edit: to proof heres a link http://dmytry.pandromeda.com/mojoworld/erosion_fractal/home.html (http://dmytry.pandromeda.com/mojoworld/erosion_fractal/home.html)
also check out this video done with it: http://dmytry.pandromeda.com/mojoworld/erosion_fractal/erosion_movie2.html (http://dmytry.pandromeda.com/mojoworld/erosion_fractal/erosion_movie2.html)

Maybe Matt should talk to this amazing genius :D

Goms do you mean erosion on a global basis because you can already create erosion on hightfields?

If I remember correctly creating fractal erosion on a planetary basis is to processor intensive at the moment. Look at how slow the alpine shader is, although it is usable you just need a bit more patience.

Edit: oops posted to quickly, just seen your links to the erosion video, very nice. Would be great to see this in TG2.

right, as Dmytry Lavrov, the creator of this example above, wrote to me, it uses a lot of memory to run "reasonable time".
But also if it is slow, it would be great to have it. As the CPUs are getting faster every half year, it should be considered to start with this.

But you coul always plug the Alpine shader to a heightfield.
When you then have generated it. It is pretty fast :)

- Terje

Quote from: sjefen on April 27, 2009, 11:46:58 AM
But you coul always plug the Alpine shader to a heightfield.
When you then have generated it. It is pretty fast :)

- Terje

But if you don't need it on a planetary basis why not just use a standard heightield and use the erosion tool on it? This way you get some control on the erosion. Then when you are happy with it save the terrain out and then you just need to load it each time without having to run the erosion tool each time.

Hi

• Remember every window position
• Water wave/surf
• spin/turn around xyz for everything
• size varitation for fake stones
• Stabil, stabil, stabil...

And thanks for all the programming till now :-)


ciao
Naoo

Displacements that are shown on mirrors:
http://forums.planetside.co.uk/index.php?topic=5178.msg53528#msg53528

I think the greatest time saver would be the proposed wire frame preview for tgo/obj viewing.  I waste so much time running multiple previews to find the placement and relationship values of my object entities. I think that this function would probably be the most easily realized of any of the additional features that have been suggested here.

A very important thing for me: resolve the problem about very big heightfields:
http://forums.planetside.co.uk/index.php?topic=5564.0
Even with "flatten terrain first", displacement is on y axis...would be better to be follow the normal of the planet!

Erwan

Quote from: elegac on April 27, 2009, 03:20:22 PM
A very important thing for me: resolve the problem about very big heightfields:
http://forums.planetside.co.uk/index.php?topic=5564.0
Even with "flatten terrain first", displacement is on y axis...would be better to be follow the normal of the planet!

Erwan

Is this a Problem? There is a way to solve this, but i dont see why anyone should use such big heightfields....

For me it would be:

* a way of storing rendered images in the render viewer (alla Houdini, Maya,....) so u can compare quick renders and changes quickly right there

* proper animation module (i.e. create animation paths straight in TG2 without needing to go through a third party app)

* fix render errors (i.e timelabs water motion still causes "black spots")

* YES wireframe preview so u can actually navigate through ur scene with a workable speed

* Fix CopyNPaste issues (sometimes - and only sometimes - copy/pasting nodes between scripts only works once a node is selected and by using "Edit->Copy/Paste")

Otherwise I'm still amazed by TG2 :)

Quote from: rodpacker1 on April 27, 2009, 11:55:06 PM
For me it would be:

* a way of storing rendered images in the render viewer (alla Houdini, Maya,....) so u can compare quick renders and changes quickly right there

* proper animation module (i.e. create animation paths straight in TG2 without needing to go through a third party app)

* fix render errors (i.e timelabs water motion still causes "black spots")

* YES wireframe preview so u can actually navigate through ur scene with a workable speed

* Fix CopyNPaste issues (sometimes - and only sometimes - copy/pasting nodes between scripts only works once a node is selected and by using "Edit->Copy/Paste")

Otherwise I'm still amazed by TG2 :)

* Storing rendered images for comparison has been requested a few times in the past, it would be a nice thing to have. The render window could have a back/forward button so you can move between the different renders.

*Animation has taken a back seat so far but I believe that will be the focus along with 64bit support over the coming year.

*I've noticed a few black spots over the last couple of versions which i've never had before so a fix would be good.

*Yes everyone wants wireframe  ;D

*I've been running into the copy/paste bug a lot recently, I was going to make a post myself. It seems to work ok from the menus but ctrl+C and ctrl-V just don't seem to work sometimes.

I don't know if discussion topics like that are having any effect, but it's still interesting to see what everyone else is looking for next. For me it would be different to from what I read from you guys...

* yes, the wireframes would be useful
* a cloud layer v4... I really want better light scattering and more control over cloud shapes
* more noise functions for the powerfractal
* macro support... I would like to be able to package complex networks into an easy to use dialog with custom sliders and such
* multiple objects per population

That's it.

Frank

I'd like to have populations working similar to shaders - with the kind of shader tree and child layers. This way it would be easier to set variations of only grass or similar trees but with different ages for example.

Wireframe would also be nice.

"Drop on terrain" for objects. We have it  for populations so why not for single instances.

Ability to close Terragen and resume render after next launch.

64 bit version for those large scale renders full of vegetation.

Quote from: Goms on April 27, 2009, 03:53:19 PM
Is this a Problem? There is a way to solve this, but i dont see why anyone should use such big heightfields....

Never heard about orbital views? ::)
And for now I haven't succeeded...

Erwan

*Wireframe (obviously)

*For people who are lazy like me, a throwback to the old TG09 "Shadow lightness" setting, when you realy can't be bothered to faff about with the GI and Enviro Light settings

*Child populations for mixing variations in populations

*Water that actually sits at the height that you stated in the water level box, please, please, please

*Most importantly of all... Button 9

And as Cyphyr said... Free Coffee and Fags.... in abundance  ;D

Miles

Yeah!! Button 9 for everyone!
However here are my dreams! ::)

* SSS (materials such as marble could incredibly benefit from it)
* Transparency and reflections with caustics ( ;D I'm a really big dreamer, I know!)
* Xfrog plugin (and everything it could bring: unique variations, trees editor, a new populator with more parameters)
* Realtime navigation over the terrain (something like the terrain preview in the 0.9)
* Wireframe for objects

Quote from: elegac on April 28, 2009, 06:01:27 AM

Quote from: Goms on April 27, 2009, 03:53:19 PM
Is this a Problem? There is a way to solve this, but i dont see why anyone should use such big heightfields....

Never heard about orbital views? ::)
And for now I haven't succeeded...

Erwan

Right, but for this huge scales a power fractal is much better in my opinion.
However, you can convert the heightfield into a .tiff file and use the imagemap shader.
Heres an article about that: http://en.tgblog.de/?p=40 (http://en.tgblog.de/?p=40)

- SSS
- Better object preview
- Directional light
- More powerfractal flavour
- Possibilty to stop a render and get back to it later (Hey I know it's a dream...)

Quote from: Seth on April 28, 2009, 11:17:27 AM
- SSS
- Better object preview
- Directional light
- More powerfractal flavour
- Possibilty to stop a render and get back to it later (Hey I know it's a dream...)

DITTO!

Here are mine:

1. Camera/object animation paths
2. Better object handling (wireframe view, drop-on-floor, local/global axis, material tweaking and preview)
3. Better/more export/import options for lo-res terrain meshes, camera paths, etc. with ability to "talk" to a larger number of apps (would open up TG2 to the matte-painting market).
4. More sophisticated population handling system with proper pre-vizualisation.
5. Some presets for clouds, atmos, mats...

1.  Great Animation Tools.
2.  Great Animation Tools.
3.  Great Animation Tools.
4.  Great Animation Tools.
5.  Great Animation Tools.

1. save render progress.
2. Wireframe for imported objects
3. Animation module
4. Subsurface scattering
5. Terrain carve tool in preview

• Full greyscale opacity function for shaders
• populations of internal sphere/planet/lightsources
• Working rock object displacements
• Wireframe objects
• TG3

Linear animation curves (cloud movement doesn't ease in and out, and having to make and import linear .chans from other apps is actually a nutache).
Expanding the inputs of nodes so other nodes can drive features (e.g., a power fractal controlling the placement and intensity of warp).
Allowing image maps to drive the intensity of reflection on models.
Colour variation in populations, especially individual materials (i.e., foliage).
The choice of smoother waves in the Water Shader.

edit:
Is that 5? If not, here's another  ;)

When saving a scene, the render preview window is grabbed and saved as an icon image for the file itself. So, when you go to load a scene, you can have at least an idea of what the file is through a little piccy.

That's 5, isn't it?.......

Most of what I want has been mentioned, however I would love "insert clip file" as an option in node network context menu.

1. ability to rotate a heightfield
2. diff X,Y edge values for heightfield edge blending
3. multiple ROI sectors for rendering preview
4. for populations - select from an arbitrary large number of preloaded objects
5. multiple floors - to allow heightfields to be on top of each other. To create interior elements....
   - where range where a given heightfield is used is set by simple height rules including similar to underlying intersection mechanism

Quote from: dandelO on April 29, 2009, 11:44:50 AM

• TG3

lol completely disagreed ... we only get free upgrades within TG2 ... so as far as i am concerned i am happy to work with TG2.9.9.9.9.9.99999999 in 2100 :)


However what I completely forgot in my wishlist:

- Renderpasses !!!!!
- proper export for procedurally generated objects (including shading - basic colormapping for navigation would be fine) as obj to work 
  accurately with e.g. FX tools like Houdini (i know this isn't easy, btu this is a wishlist, right?!)

cheers
rodpacker

Here's mine: in no special order:

The ability to insert a clip file from the right click context menu in the node network with the inserted nodes translated to approximately the click from location.  Would need to work at any level so that clips could be inserted directly into an object's Parts Shader.

An array population:  i.e. I would like 20 rows separated by this distance each containing 100 instances of the object separated by that distance. It would still need to be possible to apply random scaling and rotation to the individual instances as with normal populations, local random position variation would also be useful as would stepped rotation. 

Get Instance Variable: I'm not sure what to call this one but here's how it would work:  Each instance within a population would have a random number between zero and one assigned to it which could be accessed via a Get Instance Variable node, this could then be passed to a conditional or blend shader.  This would allow per instance colour variation and a whole host or related effects.  This would also have the potential to control the object loaded at each instance which may be a more flexible way of implementing Unique Variations.

Variable transparency for both the default shader and image maps containing the appropriate alpha channel.

Sub Surface Scattering: Even if it takes ages to render, we used to have to wait days for big fluffy clouds and after all you don't have to use it.

I'm fairly happy with the power this program has. I still consider myself a beginner.
I would like to be able to stop a render at any time, then re-start the render from that point.
My computer has a Pentium 4 hyperthread cpu. A decent render can take 8 to 20 hours (1 thread). I would love to get a newer computer, but I can't afford it.

Quote from: kaisersuzuki on April 30, 2009, 12:21:54 AM
Most of what I want has been mentioned, however I would love "insert clip file" as an option in node network context menu.

I second this!!!!  I've been wanting this for a while.

1. As I really like sky/clouds, it would be nice to apply virtual filters to the camera - e.g. a polarising filter - that would make them really pop.

2. Similarly, DOF through the camera - virtual focus + virtual f-stops

3. Oh, and of course, ability to stop renders and re-start after program closure.

Quote from: JimB on April 29, 2009, 12:07:31 PM
When saving a scene, the render preview window is grabbed and saved as an icon image for the file itself. So, when you go to load a scene, you can have at least an idea of what the file is through a little piccy.

That would be a magnificent.

- Terje

Like Bryce do, sipmle save and reload the preview as image-file.

A manual
(x5)

.......

Planet rotation

Three I can think of...

1) User customizable menus with the option to add new menu branches.  Maybe something like Lightwave Modeler.

2) A blinking "copy this view to the current render camera" icon when the camera position has moved.  Just a better indicator of something should be done before starting a render. 

3) A render view stacking system.  You do several renders and can simply look at each image via a drop-down menu (on the viewer) to compare them (and save one's you want to keep.)  Oh, and a clear image stack option if it gets too much of a memory hog or you're just done with them.

I just had a thought -- maybe there's already a way to do this -- but referring to #2, maybe a "always update render camera" option?

1.  Multiproc support in the 3d preview
2.  More documentation
2.  64-bit support
3.  Wireframes

I would really like to see the 3Dconnexion's SpaceNavigator/3d mouse work with Terragen 2 for 3D navigation. This would make it easier to fly around and look for interesting areas on the planet for setting up shots or animation paths. That's assuming Planetside can improve the speed in the perspective view in Terragen nearer to real time. ;D

http://www.3dconnexion.com

- Object Wireframes in Preview
- drop single imported Objects on Ground and where the Camera is, not at Position 0,0,0
- 64 bit Support
- more Perspectives on one Screen ( front - top - side ) - with Movie-Paths in all views
- an installable Network-Rendernode for Movie-Renderings  and also for big single Pictures(or first a detailed workthrough how to set up a free 3rd Party Renderer - I haven't managed to do this yet. And it seems there is no officially Support of one of them to TG2)

Oh I forgot one - unfortunately that are six now - more Import-Formats: with Poser-Senes and Objects

Hi

I agree with rkphelps!


ciao
Naoo

Most of these have been mentioned already.

1/ 64 bit. Excellent to hear this is top priority.

2/ A conditional render output node. It would be great to isolate certain parts of a render for compositing, within the one scene. So if I want to isolate say the clouds, or set up a DOF pass, I could have the possibility to say to the node network, that this set of conditions only work for another output channel and have internal layers within the render node to set up what ever channel those conditions apply to. So say a scene camera is linked to a render output node, I would have within the internal network of that render node a set of user defined channel outputs (read seperate image renders and directory paths, with channel asigned numbers) which your conditional branches have directected to.

3/ Collate assets for a TGD. To make multi-machine rendering, and archiving completely painless.

4/ Multi object populations, which you generate to a cache file (also part of the collate project) saving on having to generate per frame or preview render, unless un-checked.

5/ Access to internal node settings from external node outputs. I'm thinking linear phasing to modulate those settings, ie sine functions to modulate noise position, or frame time to shift noise in y, would be good for wave animations, especialy if you could get loop'able noise functions. Got to say I love the noise effect in After Effects, it's a really powerful function, especially when you can link other instances to it. But, and edited to add, it would be bloody useful to have a distance shader control the sample quality within atmosphere and clouds, etc.

There you go, my five.

Cheers

Jon

I am running a render now which has been going for 11 hours. (My computer is about 4 years old) Anyway, I forgot to adjust the fake darkness in the atmosphere tab. The image is looking fantastic, but a darker sky would have been better.

What would be nice is if the sun's angle tangent to the camera's horizon would adjust the sky darkness. Maybe a check box so it could be turned on or off. The only times I have been able to get a dark sky, is when the sun light is at or below the horizon. I look at the sunrise/sunsets and the sky is quite dark even when the sun is 4 or 5 degrees above the horizon.

1: full 8+ core support
2: 360 Panorama renders for using it as reflection maps (in Maya)
3: when i do a render and close the render view window, it should keep the last image, so if I click the render view panel again, it's still there... also an option to store there the  rendered pictures, and swap through them (like in Maya).
4: WIREFRAMe on imported obj's in the 3d preview.

Thanks :)

(in no peticular order)

a preset camera at 0,0,0 pointing toward the rest of the render 6' above the ground.

a library of default skies, vegetation populations, fake stones, surfaces, times of day, Ect...  (like TG .9x)

Depth of field, f-stop and other setings on the camera that emulate real cameras.

Waves and other water efects. (light waves through water) generaly treating water as a solid instead of a surface.

having the camera, view, an the other buttons drasticly change collor when they are presses (or or off)

"having the camera, view, an the other buttons drasticly change collor when they are presses (or or off)"


Oops I see that you allready did this one.  ;D
-Thanks

Quote from: N810 on May 19, 2009, 10:15:54 AM
"having the camera, view, an the other buttons drasticly change collor when they are presses (or or off)"


Oops I see that you allready did this one.  ;D
-Thanks

Must be down to your graphic card driver specifics ... I still see almost no change under my "old" GForce 7900
Richard

Ditto Mr. Lamppost's suggestions
Auto fill the obj name when you save as tgo.
bring back the ability to adjust the terrain map size.
put a cursor point at 0,0 in the terrain map so you can move the terrain from there, instead of just the camera.
More Coffee!
A 64 bit version.

• Ability to rotate heightfields.
• Ability to rotate plane objects
• Water surf/foam
• True transparency with all shaders/materials
• Separate search/store memory

Hope these are humble enough to see them fulfilled in the near future. ;)

This may sound petty, but can we have an option to automatically adjust the render camera every time we move the preview camera? I can't count the number of times I've forgotten to hit that little button and started a render with the old camera view.

Just an option to toggle, if people wanna use it. That's all I ask. Thanks.

Oh yeah! And a "wet surface" surface layer that basically halves the brightness of underlying colours and adds shine (reflectivity). That would be sweet.

Quote from: kevnar on May 21, 2009, 06:58:31 PM
Oh yeah! And a "wet surface" surface layer that basically halves the brightness of underlying colours and adds shine (reflectivity). That would be sweet.

How about:
Copy surface shader, decrease colour, create reflective shader, plug in as child layer, decrease reflectivity.

Ohw wait, we already have that...  ;)

Quote from: Mohawk20 on May 21, 2009, 07:16:05 PM

How about:
Copy surface shader, decrease colour, create reflective shader, plug in as child layer, decrease reflectivity.

Ohw wait, we already have that...  ;)

Yes, but if we could have it as one of the shaders already installed so we could set it up with one click and a couple tweaks, quick and easy.

My top wanted features.

I manage a render farm, and these would be invaluable.

1. More command line options.  ie ability to change render size, render camera etc
2. Report render progress back to console.  It would be nice to tell how far along a render is when there is no window.
3. Archive function.  Where it copies all the files used in a project into a zip.

Lens controls. Setting the render camera lens greater than 60 degrees causes a fisheye effect. This is most noticeable in the clouds.

A better palette control. Microsoft has not improved their color chooser since Windows 95. It would be great if colors could be tabbed. Greens and Yellows for grasses, greys in a stone tab, sky colors tab... Also maybe 32 user defined colors for each tab, so the user can build a library of their favorite colors. HSL sliders, and a palette mixer.

Thought of another one:

Solo population preview instances.

This would be so you don't have to turn off the preview for a large group of populations just to see the one you are working on.

New one. animation of colours. You can kinda change the colour of the atmosphere in an animation by putting animation keys on the bluesky and redsky additive but not things like cloud colour, scattering colour, etc.

my top feature request is for new camera types, for easy HDR image output which can be used as backdrop in other apps. suggested types: spherical (the most urgently needed), cylindrical, cubical mappings and HDR lightprobe format.

cheers

markus

I've only been using terragen for a few weeks so forgive me if some of these things are possible and I've simply not found them, and some of these things have been mentioned already but I'll just add my +1...
and to give you an idea of where I'm coming from, I'm a character TD for a studio in Toronto using Houdini, so I'd love to be able to integrate Terragen into some of our VFX projects -

1 - real cameras (focal, aperture etc etc)
2 - AOVs (rendering elements in separate passes), or even just a phantom shader...
3 - animated geometry (read file sequence 001.obj, 002.obj etc, you can hack this now with multiple terragen files but...  :-\ )
4 - export of terrain using a bounding box - create a BBOX, set scale, move to position, export as obj etc, this would allow for exporting of overhangs etc)
5 - import point cloud as population source, and possibly as seed points for clouds (this would add the awesomeness of importing animated points = particle system!)
***@Mr_Lamppost***

QuoteAn array population:  i.e. I would like 20 rows separated by this distance each containing 100 instances of the object separated by that distance. It would still need to be possible to apply random scaling and rotation to the individual instances as with normal populations, local random position variation would also be useful as would stepped rotation.

Get Instance Variable: I'm not sure what to call this one but here's how it would work:  Each instance within a population would have a random number between zero and one assigned to it which could be accessed via a Get Instance Variable node, this could then be passed to a conditional or blend shader.  This would allow per instance colour variation and a whole host or related effects.  This would also have the potential to control the object loaded at each instance which may be a more flexible way of implementing Unique Variations.

what you're describing are some of the features of Houdini's Copy SOP ( http://www.sidefx.com/docs/houdini10.0/nodes/sop/copy ), even just a few of these features would be amazing to have in Terragen.


6 - bounding box view for clouds - based on density(?), so you'd have a rough idea of where your clouds are in 3D space
7 - optional lock camera to view


thanks

Agree with goldfarb...
Bounding box for clouds would be nice too... :)

QuoteBounding box for clouds

You could already have this if you were to use my TG2 Metaclouds, or a system like it... http://forums.planetside.co.uk/index.php?topic=3691.msg50573#msg50573

Each single cloud has its own bounding box, just like Vue, only better because it's called Terragen. ;)
Still waiting on a 'group objects' function, mind, that would take this to the next level, to group a clump of clouds and move them as one object...

I was thinking about that, dandelO.  dandelO made some very cool clouds that are extremely useful and, as far as I can see, these have been under exploited.  We could do a lot more with his great ideas.

@dandelO
thanks...very interesting :)

A couple of things:

1. Mixed populations (variations would be a bonus)
2. Drawing out population areas - DigiElement World Builder used to have this. You would draw the area you wanted to populate as a closed polygonal shape on the ground. It remained editable - ie each vertex was a moveable node. Much better than the current "box only", and far easier than image masks. (Unless I am missing something!).
3. Real Camera Lenses

I will reserve 4. & 5. in case I think of something else later!

pbelchamber: for population masking, create your population, on the Distribution tab click Use Density Shader then click the green + button to the right and select Create New Shader -> Colour Shader -> Painted Shader. Now go to the 3D Preview, click the Paint button and select Star Painting Shader -> Painted Shader 01. Now you can easily paint the area for your population. You can also use this in Blend Shader inputs to control the distribution of almost any node.

- Oshyan

Just wondering...
Will the Planetside staff do anything with the suggestions in this thread?

It would be nice to see some kind of reply in which some requested features are listed in order of priority or something. Not with a time estimate or anything, but just an indication of stuff that will be added, and what will be added sooner than other stuff.

Quite honestly there is such an overwhelming array of desired features in this thread, it would be hard to craft a fair response that would address even part of it. We've made our plans for the next development priorities fairly clear - animation, 64bit support, and import/export. Those are the broad areas. Details beyond that will have to wait until we have something to release and, as recent convention has established, we will not be publishing release dates prior to finishing the actual development.

- Oshyan

Not sure if this has been suggested yet, but for planetary renders, could we have a filter for surface layers based on latitude of the globe? In other words, set it up so that you could also constrain a "Snow & Ice" layer to have a minimum latitude of 60 degrees on the globe, or a "desert" layer with a maximum latitude of 30 degrees.

Quote from: kevnar on June 09, 2009, 12:58:18 PM
Not sure if this has been suggested yet, but for planetary renders, could we have a filter for surface layers based on latitude of the globe? In other words, set it up so that you could also constrain a "Snow & Ice" layer to have a minimum latitude of 60 degrees on the globe, or a "desert" layer with a maximum latitude of 30 degrees.

That would be fairly easy to do at the moment.
Just position a camera at the pole and connect it to a distance shader (spherical). Then use that combination as a blendshader for your snowcap.

You could do something similar with a desert layer around the equator.
Then use the same technique but create 2 cameras and distanceshaders set to Z-depth and let the camera look/point toward each pole.

Using 'Y for slope/altitude' would achieve this aswell for snowcaps on the poles of an entire planet. I've done this before.

i got another one x and z axis translation control for the crater shader through the render preview like you get when you import models im sick of trying to move crater shaders via the centre.
also a second option not only to move an object via the xy and z but also to rotate and scale through the render preview.

Quoteto rotate and scale through the render preview

Yup, a multitool for transform/scale/rotate would be nice. Good one.

For the free version (which I'm stuck using), can you make it so that the render limits are 480,000 pixels maximum instead of straight 800x600 limits? Sometimes I wanna do panoramic pics, of like 800 tall by 400 wide, or 1024 wide by 468 tall, etc., but it doesn't let me. I respect your decision to limit the render size on the free version. All I'm asking is to base it on the total pixels, as opposed to hard-coded dimension limits. Thanks for your consideration.

A cool feature on the Amiga was the 'HELP' key. Some programs used this. You could hover over something with the mouse pointer, press the 'HELP' key, and a hypertext window would appear. This gave, usually a simple, explanation of the feature.
It would be a lot of work to set this up. But today, links to the forum posts, wiki, and various tutorials could pop up.

Definitely
- 64bit support
- 360 Panorama renders for using it as IBL source and reflection maps

Vue and Carrara already support spherical cameras for a while, but Terragen would really be an awesome source for such HDR images.

Quote from: Singular3D on June 22, 2009, 08:49:52 AM
- 360 Panorama renders for using it as IBL source and reflection maps

Vue and Carrara already support spherical cameras for a while, but Terragen would really be an awesome source for such HDR images.

HearHear!!

-To save the render progress that you can shout down, or do anything else and then continue render
-Shoutdown after finished render progress
-64 Bit Version

3.  full animation feature set
2.  full animation feature set
1.  full animation feature set

But, not necessarily in this order.   ;D

I am entirely sure that you already had you vote, calico!
It's too late now for that wish ;)

Frank

Rats.  You caught me.

I just needed to hear it again.   :P

One that recently occurred to me: the ability to make multiple crops of a scene in one render pass, so that two or more 'problem' areas can be examined/compared at once.

OK, here's one I posted in the open discussion forum...

http://forums.planetside.co.uk/index.php?topic=6628.0

Quote from: dandelO on June 03, 2009, 06:42:00 PM
Maybe Matt should re-enable the fake internal scattering to the cloud's GI again. Or have a checkbox to enable/disable scattering in GI areas. They look like the pre-release TG2 clouds, that oily look. Cool.

I also used extreme FIS values for the volumetric fire and explosion .tgd's that I made before for the Public Library, I'm not sure these work anymore, either. I must check...

FrankB: Seth said you'd like this in the other thread, lets see if it'll come back at some point, I liked the clouds the way they were before, too... :(

Can't see this in here but could we have an option for multi-region crops? By that I mean rendering more than one area of a scene in a crop (e.g. an image cropped into vertical thirds, render the left and right crop at the same time, leaving out the centre crop.) I always get a couple of things that I don't like the look of and at the minute I have to either render the whole thing again or render loads of little crops.

I'd like to see the GUI become dark grey and the node's more like "Particle Flow". That would be awesome :P

- Terje

Yeah and maybe use Windows 7's multi touch to sculpt terrain and clouds. ;D

Quote from: Singular3D on June 22, 2009, 08:49:52 AM
Definitely
- 64bit support
- 360 Panorama renders for using it as IBL source and reflection maps

Vue and Carrara already support spherical cameras for a while, but Terragen would really be an awesome source for such HDR images.

Use http://forums.planetside.co.uk/index.php?topic=6931.0 and a 90° camera, then your favourite panorama tool (I use hugin) to merge them.

Yes, it would be easier to get this right out of TG2, but with just two minutes of extra work, it is doable today. I've got a bunch of HDR panoramas for sale on http://skies.lemuria.org/Panoramas/Panoramas.html that were generated this way.

a method to return a parameter to it's default would be nice...

Quote from: goldfarb on August 01, 2009, 03:12:16 PM
a method to return a parameter to it's default would be nice...

Memory buttons, like bryce/poser (I didn't say that ...;o)
Richard

64 bits version, and the animation module of course !  :D

Did anyone mention collision detection? When flying the camera around, would be nice if it stops when it hits the ground, or an instanced object.

Quote from: kevnar on August 02, 2009, 01:05:01 PM
Did anyone mention collision detection? When flying the camera around, would be nice if it stops when it hits the ground, or an instanced object.

a much simpiler feature would be to set altitude limits on the camera...but you'll end up with very choppy camera movement.

Here are mine. At least what I presently think are my top priorities. I haven't read through all this thread so I don't know what other people have suggested:

1.

Linux version. This is always my top priority. Even a Linux renderer but I guess this wish may be a long way off.

2.

Navigation that works on longitude, latitude and altitude. It seems to me that this makes obvious sense in an app that is actually creating an entire planet. X,Y and Z become meaningless once you start moving around. In fact I largely ignore those read outs. The measuring tool comes in handy though.

3.

Colour gradient. These provide extremely rich ways of getting colours for procedural landscaping. I did hack one together and I think there is a file on the forum somewhere but it is a work around.

4.

Voronoi basis fractal. Next to Perlin this is the most useful fractal for landscape work. Convolution would also be cool for craters and towers.

5.

Curve graph. Another important feature that is in other landscape apps to sculpt the functions.

I'm going to add another:

6.

A new colour picker to replace the dire Windows one.

A color gradient similar to Photoshops would do well. Also the ability to select colors imported from an image and the creation of color swatches. Swatches would be helpful say a user needed a selection of colors that represented a particular terrain or climate.

The color picker should have preset samples based off of real earth colors to have a good start. X-Frog has something similar for plant colors.

Sounds like the old 0.9 color picker...  ;)

Quote from: CCC on August 04, 2009, 12:45:18 AM
Also the ability to select colors imported from an image and the creation of color swatches. Swatches would be helpful say a user needed a selection of colors that represented a particular terrain or climate.

The color picker should have preset samples based off of real earth colors to have a good start. X-Frog has something similar for plant colors.

Tell me about this. So few apps have this capability. It is especially obvious with landscape apps to be able to easily select colours from images and build up swatches.

Of course if operating systems (especially Windows) had anything like decent design then we would use their colour applets to do all this work and between different apps as well.

Here is the colour picker from 3D coat. It's not even the latest 3D Coat which is a now a volumetric sculpting app. There are two basic pickers here due to this being a kind of in flux version of 3D Coat but I can't be bothered doing a new screen capture. This picker does everything you want - even bringing an image in to pick from. Then of course you have the swatches. Even apps like ZBrush do not have all this capability. Ludicrous since they are essentially "painting apps".

(http://img528.imageshack.us/img528/530/colorpickerii7.jpg)

Also having a gradient dialog very much like that of photoshops would be nice. Imagine creating complex color combinations for terrains and being able to save custom gradients as well.

Hi

1. Crop-Render whitout clear Screen
2. 2 or more Renderbuffers (like Blender)
3. One Renderslider to downscale the Quality for realy quick-Renders
4. Remember TG-Windows Positions
5. Wave-Surfes at the Beach


ciao
Naoo

Not sure if this has been requested, so please excuse me if it has? 

Would it be possible to have a "Crop Area Tool" that could be set to "Free Transform" ?  Many times We re-render select areas of Our Scene, and many times it's an area that is diagonal across the Scene. With the square/rectangle that We have now, We are forced to render areas that We really don't want to re-rendered. This would save wasted render time and energy.  Hope I'm explaining this clearly?

Quote from: buzzzzz1 on August 07, 2009, 11:41:51 AM
Not sure if this has been requested, so please excuse me if it has? 

Would it be possible to have a "Crop Area Tool" that could be set to "Free Transform" ?  Many times We re-render select areas of Our Scene, and many times it's an area that is diagonal across the Scene. With the square/rectangle that We have now, We are forced to render areas that We really don't want to re-rendered. This would save wasted render time and energy.  Hope I'm explaining this clearly?

I've never seen this in any application....I doubt it would be easy to do, and at best you'd get a blocky diagonal...perhaps a better feature would be to be able to select multiple crops...?

Quoteto be able to select multiple crops...?

Now, that sounds cool, and do-able.
I'd like to transform the crop area, aswell, but I've never seen anything that does that either.

been thinking about clouds today...

it might be good to be able to control Cloud Density and Edge Sharpness with altitude via a shader and/or a ramp...
the tops of clouds are almost always different than the middle and bottom.

Hi dandelO,

Quote from: dandelO on August 07, 2009, 05:50:33 PM
I'd like to transform the crop area, aswell, but I've never seen anything that does that either.

Do you mean rotate the crop area? That's the only standard transformation which can't be done.

Regards,

Jo

OK, I seriously think that being able to save a renders progress should be the #1 priority, moreso than 64bit. I can't tell you how many renders I've lost after hours of waiting because it crashed or my PC froze or there was a bluescreen or a power cut or whatever. I know it's only a 32bit application and will crash when it hits the 2GB barrier but you can set a LARGEADDRESSAWARE flag for an application so that it uses 4GB in 64bit. It's just bloody annoying losing 15 hour renders. To partially resolve my problem, at least for the current render, I've used NTCore's 4GB Patch (http://www.ntcore.com/4gb_patch.php) which can add the flag to any executable. So far I'm at 5 hours with non of the 'mini-freezes' I was having before

Hi PG,

TG2 already has the LARGEADDRESSAWARE flag set - you shouldn't need to use another program to set this with TG2.

Matt

I would like to adress any (!) value inside the node-networks with a function (i.e. stone scale and density, Powerfractal values ...)

1: Complete Procedural Erosion of all types, the missing magic shaders!!!       ;D
2: River networks (Large scale).
3: Glacial erosion and glaciers.
4: More render speed, why is Modo so fast?
5: Internal flora creation system.

Quote from: Volker Harun on August 17, 2009, 07:10:39 PM
I would like to adress any (!) value inside the node-networks with a function (i.e. stone scale and density, Powerfractal values ...)

That would be nice. But the mosts important, which prevents making 1 node functions, is that you cannot from the inside access
an input node. E.g it is not possible to make a a node (using one the alreadyy existing nodes) that takes twot vectors as input, and delivers
a vector as output.

1.a rendering compare system à la maya or nuke.i mean store a render without saving it and  put the old render on the new render, to see the difference after changing a value.
2.expressions or simple code to animate values without keyframes..here i think to Houdini and is "$F fonction"....with it it will be possible to create some animation assets for cloud and water.
3.A black/white masks render system to get only the clouds, only the light rays, only one population kind, etc....
4.An asset management tool to create a clean .tgc library...maybe with a internet sharing system.
5.call nodes faster in the network view. maybe by pressing a key and typing the first node name letter.
   

Sorry if this has been mentioned, I should have put this on the list at day one.
Global Object control on at least this setting, what a pain in the butt. ;)

Just a mini feature really, someone's probably already thought of. I'd quite like a bias feature on things like minimum and maximum scale of populations. There's currently no way to control how many rocks in a population are small and how many are large, other than seperate layers.

hello everyone
these are my top 5

-64bits
-linux , at least for the standalone renderer.
-the ability to work with very large texture maps without the need to have them in memory (like .rat in houdini or .map in mental ray)
-more documentation
-more presets

I've been working with 3D for 20 years. Presets usually mean 'limited'. There are very many terrain files in the file sharing part of the forum. Often you can find something there which will give a good start to a project.

re-using of images.

ender view tools, starting with a past-render buffer with right and left select buttons.  A pair of A/B assign buttons so that I can do a simple toggle between any two pictures.  Also add a magnify button so I can do a quick A/B check between two arbitrary ZOOMED images in the buffer queue.  And of course delete keys to clean up the buffer.  Oh yeah, an auto-crop button so I don't have to live with the huge black zone in my crop renders.

-Rotate handles on everything in the 3D view.

-More noise functions in the shaders. (at least voronoi)

-Node macros (keep clips trees inside a single box)

-Full 3D preview, ie an option button to render the view in all directions.  It would take longer of course and I wouldn't be able to move but I WOULD be able to spin in any direction immediately.  I'm mostly doing skybox work so checking my entire pano view is a very common function.

Still. Object grouping. :) To combine items/objects and move them about under one 'group' parameter, which would obviously hotpoint at the centre of the group. That's a dream I've had for a long time.

Quote from: shadowphile on September 19, 2009, 07:33:35 PM
-More noise functions in the shaders. (at least voronoi)

We have Voronoi noise but it's available in a slightly funny way. Several types of Voronoi noise are available from the Noise part of the Functions menu. To see anything useful from the noise functions there you need to connect something like one of the Get position function nodes to Voronoi nodes first input. I'm not really sure why these aren't available through something like the Power fractal node to be honest!

Quote-Node macros (keep clips trees inside a single box)

Although it isn't the same as a full macro system you can put nodes inside other nodes to keep node trees organised. We call these "internal networks". Right now it works best if you put the nodes inside group nodes, but the next release has a bunch of fixes and improvements which make this more versatile. To see the internal network of a node either click the Internal Network button next to the node name in the param view ( the icon shows 3 little connected nodes ). You can also context click a node in the node network and choose Internal Network from the context menu. You can connect node inputs and outputs to nodes which are inside or outside an internal network in various ways.

Regards,

Jo

How about an Iterator node?

With a hardcoded Maxiteration limit (to avoid endless loops)

Inputs would be:
IterationCountToDo
Anything from another node

Outputs would be:
Output result at current Iteration count (feed this to the input of another node whose output is connected to the input of the Iterator)
Output current Iteration count (for monitoring or other control?)
Output final result when IterationCountToDo has been reached - this to be fed to the next node in the chain.

This would enable all sorts of recursive functions/features.

...or am I dreaming ..or does a similar function already exist in TG2 ?

I think i had requested that as well. This would be good for canyon lands and other certain geological features. Something like a iterated rigid marble noise would probably look best for certain types of canyon networks like what is seen in places like Arizona, Utah etc.

It would make more sense to have all available noises, both current and up-coming to be present in the drop down list in the power fractal shader.

Only thing I would really like is 64bit.  I have 12gb in my desktop now, i7 920.  I can only imagine how much render improvement I'd see if TG2 could take advantage of the available RAM.

Rich

My top 5 most important items, and I'll be as clear about it as I can be.
1)  64 bit
2)  64 bit
3)  64 bit
4)  64 bit
5)  64 bit

Everything else pales.... erm I mean color adjust gamma white.

1) Linux 32-bit
2) Linux 64-bit
3) New native version to be tested and 100% working on ubuntu,
4) Fedora and
5) openSUSE

Wouldn't it be nice to just get a native linux version of terragen?

Sign in this petition, I'm sure it'll help!

http://petitiononline.com/sxiii/

I'd like:
1. Animation in the free version but restricted to 300 frames.
2. Rotating planets/image maps.
3. Wireframe previews of all objects except planets and populations.
4. Displacement on rocks.
5. Some fractal shader that gives the same results as the Alpine Fractal but on a planetary scale with no Y distortion/symmetry.
5.5: Some kind of Easter egg. ;)

It would also be nice to have a Home version that isn't as expensive as Deep and has some of the same restrictions on rendering:
800x600>1024x768
3 rendered populations>5 rendered populations
All the other restrictions would be the same.

A small but usefull preset library like we had in TG 0.9  ;)
things like grass, sand, snow, dirt, trees, types of clouds and skys, ect...

Quote from: N810 on July 14, 2010, 08:52:56 AM
Hmmm... wonder what this button does....

NO! DON'T TOUCH THAT! *Earth explodes* ;D

But I was only pushing button number 9...  ;)

Quote from: melmartinez01 on July 16, 2010, 12:47:17 PM
I'm after proper transparancy, ie greyscale based

Me too, still.

And, object/item grouping, within a parent bounding box, that can translate grouped items/objects with one preview handle and/or group parent-node parameter input field.

That's all I want. Anything else is sugar coating. :)

I'd like to see the true transparency ( BW image ) as well.  ;D

Also:

Scaling info kept in TGO files... and loading of all the proper materials related to the object ( object loader)

A glass shader that is transparent to light coming through for interiors and proper shadowing.

A river shader that has water and gives you the choice of eroding the river bed. Something on the order of VistaPro but far better. It could also recognize rocks and other objects in the river bed.

A real volumetric lake and ocean.

A means of easily creating flat places for buildings or any other thing you would like.

Import of Poser and Das Studio scenes, animations, ect......   :)

Hi Marlin,

Quote from: Marlin on July 17, 2010, 05:23:21 PM
A means of easily creating flat places for buildings or any other thing you would like.

Although it doesn't help for freeform sorts of shapes, try using the Simple Shape Shader in displacement mode for that. You can create it from either the Colour shader or Displacement shader menus.

Regards,

Jo

Quote from: Mariemiller02 on July 18, 2010, 11:53:48 AM
Unique variations would be sooo cool, but as you say that would need some Very close work with Xfrog or the development of an entirely new "Tree Growth" program
cant think of two more

I think if we could just place multiple objects into a single population this would be a good first step (with the option of colour variation for the leaves).

Here's a modified list copied from another thread.

x64 bit.
Multi-threaded render preview window.
Improved multi-threaded efficiency, especially for higher thread counts.
Ability to displace ray traced objects.
Support for multiple objects and colours in one population.
"Sit on terrain" for single objects.
SSS.
Water features such as foam, waves, waterfalls.
Sky features such as rainbows and rain.
Depth of field.
Stars.
Improved erosion operators.
Controlling the look of clouds is very difficult, please make easier :)
A more stable paint shader.
Stop the sun from shining through the terrain without having to resort to rts.
A rock object that supports displacement.
Faster development cycle with more frequent updates, maybe let Oshyan near the source code  :o

...and then...

Full animation system.

...and then...

A vue-type Ecosystem with unique variations of realistic looking internal plants and trees that react to their surroundings and wind.

I don't think that's asking to much :)

You forgot one thing: a magic button to put everything in the right place and immediately render the greatest art ever, all in one go!

Isn't that called a camera? If you think my renders look bad, you should see the photos I have of my thumb. :D

Quote from: Dune on July 20, 2010, 02:33:07 AM
You forgot one thing: a magic button to put everything in the right place and immediately render the greatest art ever, all in one go!

Quote from: njeneb on July 20, 2010, 07:55:23 AM
Isn't that called a camera? If you think my renders look bad, you should see the photos I have of my thumb. :D

that would  be the mysterious camera 9 node ;D :D

1. Georeferenced images

Great support when masking with real world data.

2. Possibility to import position and scale for object populations.
   
Measured datasets for entire populations of trees exist in many forms today. In landscaping, trees are often plotted with use in 3D applications in mind. The widespread use of airborne lasers in geographic surveys produces huge amounts of forest data. These range from vegetation height rasters to point clouds for individual trees. Especially the last should be well suited for import.

3. Possibility to place individual objects on surface.
 

I want at least 4 more coders for Planetside !
Then we will have all of these wishes very soon ;D

Here's mine currently. Sorry if it sounds like a bitch. It's more of where I am with the program.

1/ 64 bit has to come out soon.
2/ Multi object populations with more random variance, like tilt in Y, and colour shift with fractals.
3/ A better lighting model for clouds. Even a setting for depth of shadow cast would be useful, rather than just on or off, or via how dense the shape looks. There are some magnificent layers of clouds outside my window today, with some fantastic pearl like qualities, which I know I can't model, because I know my layers will create too much shadow, and the clouds themselves will not project light.
4/ More control on cloud shape. The cloud node takes over, and has a habit of 'crunching' cloud shapes too much. I'd like to spend more time with this, but constantly get thwarted in trying to creat scale within the cloud depth restrictions, ie I'd like to set the percentage of flattening of the base of the structure, and I'd also like to control the coverage through the height of a cloud. I had an idea of just being able to modulate depth and altitude of the cloud layer, but as it is, the calculation requires a set boundry to work in. That's ok, but we really do need to be able to put more variation in easily.
5/ Caching. There has to be some sort of intelligent caching of GI AND populations. Matt has already aluded to that populations can be switched to real x,y,z co-ordinates rather than population x,y,z. This would allow for travelling population areas to be locked to the camera, and that only the newest parts of the landscape revealed to the camera are calculated, rather than having one massive area, with it's calculation baggage, per frame. I'd happily let a machine work the hours to work this out to file. It would save on render times, memory constraints, and edit time.

I don't really care about the animation module, because camera keyframes are irrelevant in this package. I can set up a landscape proxy in Max or Maya, and then ship over the camera data to render out my plate. Which is what I do at the moment. More control within the nodes via an A,B,C matrix is actually way more exciting than having a graph/dope sheet editor.

Anyway, my tupence thrown into the well.

Cheers

Jon

Hi,

If you want multi-object populations can I ask why exactly you want multi-object populations? I certainly think it's a reasonable sort of thing to have, but I'm interested in the reasons that you want this.

Regards,

Jo

Hi Jo

Multi-object populations would be useful when you have several models of the same species of tree for example, or if you want to mask up a forest with a variety of trees, in one calculation. You could have a generic grass population, which would have a variety of models in it, that you specify what the odds of each appearing are, like scattering flowers etc. Ideally, you could have a probability on clumping them, so species gravitate towards each other.

I understand you can do this already with multiple populations and a lot of mask work, but I think this sort of feature would help a lot of people get goods results quickly, especially in short time restrictions.

It would also make the node network neater, ie you place your models inside the node, and connect it to one of sixteen inputs. A bit like the old material shader.

Cheers

Jon

Just to add Jo, being able to create modulised 'eco systems' or 'species systems' I'd think would be a great after sales revenue. Rather than buying 1300 random species with young, adult and mature variants, you could set up something like 'Pine Forest' or 'High summer grass' packages, which did give you the variation, in not only models, but also shadows within those sorts of textures those models create.

Especially if you allow fractal variance in the leaf colours.

 ;D I'm on a roll.

It would also be very cool to be able to aply fractal or functional displacement on these models to give them some movement in tilt around their anchor points. It's a subtle thing to get right, but you rarely see vegitation remain still. It maybe something that needs a little more thought, but if you want this program to become the premiere package in natural realism, it is something to consider.

1)  64 bit - so more complex and larger images can be created - access to greater memory
2)  Developer written best practices manual - so that end users can learn more quickly and renders look better
3)  easier multi-view interface - need more natural user interface - TG2 not accessible enough
4)  better object integration (mainly the bmp/displacement ray tracing thing)
5)  better lighting support (IES, and different style lights)
6)  gpu rendering support (yes I know, stay reasonable)

I think Hetzen has explained pretty clearly why multi-object populations would be so useful. It seems like such an obvious thing to add and it seems to appear on quite a few peoples most wanted feature list, along 64bit support. Of course just being able to add multiple objects to one population is just the initial step being able to accomplish the other stuff Hetzen mentioned such as colour variation, specifying odds on when a specific object would appear and clumping would really be a massive upgrade to the populator and make more realistic populations a lot easier to make.

Hetzen when you say

Quote from: Hetzen on July 23, 2010, 04:36:03 PM
Just to add Jo, being able to create modulised 'eco systems' or 'species systems' I'd think would be a great after sales revenue.

I hope you're not suggesting breaking up future versions of Terragen into parts and then sell them individually. You would end up with a fragmented product similar to how vue has ended up. With Vue you could purchase one of the many core packages and then later buy a few modules. The problem is that when a new version is released, and with vue that seems to happen every few months, you not only have to buy the core package but re-purchase the new version of all the modules as well. It all ends up very messy. I think it works better just having 2 or 3 core packages, i.e. lite, deep and deep+animation and then allowing the user to update from one level to another at a later date if they wanted.

So Jo do you think multi-object populations are likely to appear in Terragen 2 any time soon?

Hi Reck, sorry I wasn't suggesting spliting TG up into modules, I was thinking more along the lines of creating bundles of plant models which have already been plugged into a node clip file. Something Greenworks would excell at.

Take a possible bundle 'Pine Forest', which may have say 8 variations of a pine model, then maybe some floor debirs along with some bracken ferns and maybe even some dead trees too. All you need do is apply a mask and plug your compute terrain in.

Hetzen, I think that sounds great.

Seriously Reck I'd pay for that. The cost of my time to get that right against a pre package.. I'm struggling to compete against Vue, V-Ray Scatter. I know this app can compete, it's a matter of open architecture against establshed out of the box.

Hi,

Quote from: reck on July 24, 2010, 10:01:34 AM
So Jo do you think multi-object populations are likely to appear in Terragen 2 any time soon?

We don't have it scheduled at the moment. We'll need to talk it over.

Regards,

Jo

Hi,

Regarding 64 bit, because it's such a common request I thought I would mention that it is on the way. We have a 64 bit Mac build that alpha testers have been using for a while and a pre-alpha Windows build. However it will be some time before the 64 bit build is available. We want to make sure it's thoroughly tested before a public release, although we may very well have a public beta period for it prior to the final release.

Regards,

Jo

These are my five:

1. All shader internal parameters able to take spherically mapped image maps/masks as inputs.
2. The arrow move keystrokes should move the current camera relative to its current orientation, not according the the absolute coordinate system.
3. Complete documentation.
4. All input fields use temporary edit buffers so that each*keystroke*does*not*cause*the*progressively*edited*field*to*be*accepted*as*a*new*value.
5. Can rotate/shift all mappable images/masks.
6. Can lock navigation controls relative to a planet. When this happens, the forward command brings about "horizontal" motion when altitude relative to the planet is constant.

1- Export Perfect Cube Map textures Button - [option] multiple files or single image

2- Render Spherical Map LDR

3- Render Spherical Map HDRI

4- Export current terrain with Xmeters Ymeters, distance from current camera location as mesh

5- Export current terrain with Xmeters Ymeters, distance from current camera location as vector displacement map at XY pixel resolution.

Perhaps motion blur not linked to camera movement would be interesting, if at all possible.
During my holidays I got this great idea (and no computer to test it) to make an avalanche (and blur grass/trees, etc) by making 2 frames where the second frame had a different set of values (smaller/less stones, or an eroded version of the same basic terrain). Rendering the first with motion blur checked would (so I thought) calculate a motion between the two frames' values, and render this.
Nope, didn't work. If it would, there would be masses of things you could use it for, like the soft transparent water in long exposure photographs, wind blurred fields of soft grass, pieces of ice falling of glaciers..................

I just had an idea...

if you get time,
how about a button to
remove all unconnected/unused  nodes

3Dconnexion