Planetside Software Forums

General => Terragen Discussion => Topic started by: rolland1013 on October 03, 2018, 03:03:29 pm

Title: FEATURE REQUESTS
Post by: rolland1013 on October 03, 2018, 03:03:29 pm
Is there a general feature request discussion on the forum?  If not I'd like to start one.  Here's my wishes for future versions of Terragen:

1. An interactive sculpt tool for shaping terrain.
2. Erosion controls - similar to World Machine.
3. FBX and/or Alembic import ability.
4. Import ROTATION offset for importing animated cameras.
5. V-Ray shader support.
6. Realistic water animation
7. More water types; i.e. ocean, lake, stream, river, rapids, waterfall, etc.

Thanks
Title: Re: FEATURE REQUESTS
Post by: rolland1013 on October 03, 2018, 03:17:19 pm
I remembered another one, I think it would be great if you could sculpt the shape and size of clouds.
Title: Re: FEATURE REQUESTS
Post by: Oshyan on October 03, 2018, 08:33:04 pm
Yep, lots of good ideas here. Many already suggested, which we keep in a private issue tracker. We're listening and will implement as much as we can over time. I can tell you we are almost certainly never going to support Vray shaders though. Other than that it's all probably fair game.

- Oshyan
Title: Re: FEATURE REQUESTS
Post by: René on October 04, 2018, 04:04:33 am
Sculpting is at the top of my list too.
Title: Re: FEATURE REQUESTS
Post by: digitalguru on October 04, 2018, 07:53:39 am
QuoteErosion controls - similar to World Machine.


Danniis Classic Erosion plugin is great - check it out if you haven't already.

QuoteFBX and/or Alembic import ability.


Definitely Alembic - not so much FBX

and Deep Exr, the missing link for seamless compositing with other renderers!

Title: Re: FEATURE REQUESTS
Post by: rolland1013 on October 04, 2018, 12:32:03 pm
I know I mentioned this somewhere else, but image planes!!!
Title: Re: FEATURE REQUESTS
Post by: SILENCER on October 04, 2018, 02:05:01 pm
Alembic/MDD, whatever it takes to get displacement caches into Terragen. Think wind displacement for SpeedTree. Complete with instancing and offset capability.

Multiple objects in single population, randomizing their distribution


VDB in/out (I know Boss Fairclough is working on this)

Graph Editor could use an upgrade. It's kind of painful in there.

Are there any render functions that could be offloaded to the GPU?

Be nice to have render rez previews rendered out of the RTP for shot placeholders in the edit.

Alpha channels are sometimes not pure white. Comp gets fussy about that.
Title: Re: FEATURE REQUESTS
Post by: Yanik on October 04, 2018, 03:41:00 pm


My personal opinion regarding Terragen: I find Terragen artist unfriendly. You often repeat yourself, can quickly create a big spaghetti mess and must have deep technical knowledge.
You need more developers. The pace of development is quite slow. You're lucky E-on software does such a poor job, but nowadays I see many people switching to Clarisse from Vue. These could have been Terragen users.

I do love that VDB import/export is underway and can't wait to use it in other applications such as Clarisse.
Title: Re: FEATURE REQUESTS
Post by: WAS on October 04, 2018, 03:44:04 pm
I always wondered how sculpting would ever work in Terragen. I don't really see it being workable without a huuuuuuge overhaul of the preview system. I mean, think of working with just the painted shader.

In general it's addition would put the system requirements into the flagship hardware realm.
Title: Re: FEATURE REQUESTS
Post by: digitalguru on October 04, 2018, 03:47:05 pm
add:

being able to translate the little preview window somewhere other than the world origin...
Title: Re: FEATURE REQUESTS
Post by: ajcgi on October 05, 2018, 09:44:38 am
Quote from: digitalguru on October 04, 2018, 03:47:05 pm
add:

being able to translate the little preview window somewhere other than the world origin...


That is a fair point. This is something I've never requested yet bitched about to colleagues regularly.

That being said, you say it's artist unfriendly... this year has been my introduction to Houdini. You go learn that now without swearing. Go on. Off you pop.
Title: Re: FEATURE REQUESTS
Post by: Tangled-Universe on October 05, 2018, 10:15:09 am
Quote from: Yanik on October 04, 2018, 03:41:00 pm

Load a heightfield and specify the dimensions in meters. Now it guesses the size by looking at the pixel resolution. Not sure if this is already possible.



This is likely an error in the file itself. Heightfields in .ter format, as well as GeoTIFF .img files contain metadata with heightfield dimensions.
Title: Re: FEATURE REQUESTS
Post by: Yanik on October 05, 2018, 12:38:23 pm
Quote from: ajcgi on October 05, 2018, 09:44:38 am
That being said, you say it's artist unfriendly... this year has been my introduction to Houdini. You go learn that now without swearing. Go on. Off you pop.


I also have been learning and using Houdini the past year and Houdini gives you many ways to debug your scene. Houdini's network view is a joy to use compared to other node based applications. If you feel it being too complex I highly recommend you to learn some basic development skills to understand how data is stored and how it flows.
That said I agree with it not being artist friendly.

I don't think it's fair to compare a complex application that is mostly TD/VFX oriented with a simple terrain design tool. In my feature request list I posted a few ideas on how to make Terragen easier to use. Value remapping is a very important feature which is used in many terrain design tools. It allows you to artistically remap values and allows you to create new shapes quite easily.

Below you can see some simple examples on 2 basic noises that got remapped with a bezier curve editor:
(https://imgur.com/ME2UDPS.jpg)
(https://imgur.com/t0iv6uN.jpg)

Now have fun doing the same thing with blue nodes.

"Go on. Off you pop."

Quote from: Tangled-Universe on October 05, 2018, 10:15:09 am
This is likely an error in the file itself. Heightfields in .ter format, as well as GeoTIFF .img files contain metadata with heightfield dimensions.


I still think size information in files that don't follow the metadata standard should not be derived from the resolution. Let the user decide what the size is. World Creator currently has some issues exporting out large files with many file types and because of that I have to use PNG16.
Title: Re: FEATURE REQUESTS
Post by: rolland1013 on October 06, 2018, 12:23:47 pm
Scale maps:  Controlling the scale of .obj populations with a painted shader or image map.  An even better version of this would allow you to also use the min-max scale function within the population's parameters.  So your populations would still have a random scale, but also would allow you to control areas of smaller and larger scaled objects within the same population.
Title: Re: FEATURE REQUESTS
Post by: Matt on October 06, 2018, 10:10:34 pm
Quote from: Yanik on October 05, 2018, 12:38:23 pm
I still think size information in files that don't follow the metadata standard should not be derived from the resolution. Let the user decide what the size is. World Creator currently has some issues exporting out large files with many file types and because of that I have to use PNG16.


You can resize the heightfield with a Heightfield Resize operator, but we should probably duplicate that function on the heightfield load itself.
Title: Re: FEATURE REQUESTS
Post by: Matt on October 06, 2018, 10:16:44 pm
Quote from: rolland1013 on October 06, 2018, 12:23:47 pm
Scale maps:  Controlling the scale of .obj populations with a painted shader or image map.  An even better version of this would allow you to also use the min-max scale function within the population's parameters.  So your populations would still have a random scale, but also would allow you to control areas of smaller and larger scaled objects within the same population.


This is in our 2018 Plan (https://planetside.co.uk/forums/index.php/topic,24058.0.html), but might slip to early 2019. The same for rotation control.
Title: Re: FEATURE REQUESTS
Post by: rolland1013 on October 09, 2018, 06:56:57 pm
EXCELLENT!! 
Title: Re: FEATURE REQUESTS
Post by: WAS on October 09, 2018, 07:05:17 pm
Been anticipating that scale modulator. Smaller populations on slopes ftw!
Title: Re: FEATURE REQUESTS
Post by: digitalguru on October 15, 2018, 03:55:35 pm
another thought (they keep coming :-) )

a dedicated color adjust node (or addition to the existing) with RGB controls

I know you can put something together with the Build HSV node but often times you just want to subtract a bit of red out of a stack of PFs for example...
Title: Re: FEATURE REQUESTS
Post by: Tangled-Universe on October 15, 2018, 05:47:57 pm
Quote from: digitalguru on October 15, 2018, 03:55:35 pm
another thought (they keep coming :-) )

a dedicated color adjust node (or addition to the existing) with RGB controls

I know you can put something together with the Build HSV node but often times you just want to subtract a bit of red out of a stack of PFs for example...


You can do this with an "adjust saturation colour" node or multiply it with another colour, although that may cause some loss in brightness I suppose.
Title: Re: FEATURE REQUESTS
Post by: digitalguru on October 17, 2018, 05:45:27 pm
I made one myself and it works ok:- just seems strange there isn't a built-in node that can do this kind of color correction
[attachimg=1]
Title: Re: FEATURE REQUESTS
Post by: digitalguru on November 02, 2018, 12:03:50 pm
one more (maybe not  :) )

add "clamp black" and "clamp white" to blue nodes like add, subtract, multiply scalars etc. I know a separate node can be added (does adding lots of blue nodes add to calculation time?) but with lots of math blue node will help to clean up the node graph
Title: Re: FEATURE REQUESTS
Post by: WAS on November 02, 2018, 06:28:21 pm
Quote from: digitalguru on October 17, 2018, 05:45:27 pm
I made one myself and it works ok:- just seems strange there isn't a built-in node that can do this kind of color correction
[attachimg=1]


Haven't tried RGB adjustments this way, I'm going to give it a shot, see if it works. I ended up using scalar values and just fighting with the weird scale range.
Title: Re: FEATURE REQUESTS
Post by: sboerner on November 03, 2018, 10:43:11 am
Quoteadd "clamp black" and "clamp white" to blue nodes like add, subtract, multiply scalars etc. I know a separate node can be added (does adding lots of blue nodes add to calculation time?) but with lots of math blue node will help to clean up the node graph


+1

Title: Re: FEATURE REQUESTS
Post by: Hetzen on November 03, 2018, 10:49:24 am
Quote from: digitalguru on November 02, 2018, 12:03:50 pm
one more (maybe not  :) )

add "clamp black" and "clamp white" to blue nodes like add, subtract, multiply scalars etc. I know a separate node can be added (does adding lots of blue nodes add to calculation time?) but with lots of math blue node will help to clean up the node graph


What's stopping you using Clamp 0 1 or  Clamp ?
Title: Re: FEATURE REQUESTS
Post by: digitalguru on November 03, 2018, 12:35:24 pm
That's what I'm doing at the moment.

But I'm using a lot of masks and folding the clamps into additive, subtract (etc) blue nodes might reduce the clutter in scenes. Adding, multiplying and particularly subtracting overlaying mask nearly always results in out of range values you don't want

if I have a lot of nodes in a group they go off list like this :-)
[attachimg=1]
Title: Re: FEATURE REQUESTS
Post by: Hetzen on November 03, 2018, 01:48:42 pm
I see. Wouldn't something like a 'Mask Bar' be a better thing, where you have say 5 inputs, each with an internal math drop down with +,-,*,/ as options for each input, and a single output with your clamp range as an internal min and max value?
Title: Re: FEATURE REQUESTS
Post by: digitalguru on November 03, 2018, 01:52:41 pm
Probably not, that would suppose all those masks pipe into a single stream? I have lots of separate mask trees and the cumulative effect is many nodes.
Title: Re: FEATURE REQUESTS
Post by: Hetzen on November 03, 2018, 02:01:00 pm
You wouldn't need to use all inputs, it would combine at least 2 nodes into one if you were combining two inputs. When I do pop masks I'm always subtracting/adding one from another. It would be the same as your add/clamp node, just instead of two inputs you have up to five.
Title: Re: FEATURE REQUESTS
Post by: digitalguru on November 03, 2018, 02:11:17 pm
Might be ok as an alternative - -still like the idea of clamps on the math modes though
Title: Re: FEATURE REQUESTS
Post by: rolland1013 on January 09, 2019, 07:14:34 pm
I just thought of another one, well actually I've brought this one up before somewhere else in the forums.  But I thought here was a good place to request is again.  SHADOW MAPS.  Render layers/Render Elements/Extra Output Images would be the perfect place for this feature to live.
Title: Re: FEATURE REQUESTS
Post by: sjefen on January 10, 2019, 12:56:02 pm
Would be nice to be able to make the previews in the library bigger.
Also to get email notifications when a render is done.
I also think the shaders could be reworked or have more options similar to other software's. It's not easy to get the results I want on with imported objects when it comes to the shaders


- Terje
Title: Re: FEATURE REQUESTS
Post by: rolland1013 on January 22, 2019, 05:34:11 pm
Ok this feature request is a big one for me (aren't they all?), but I keep running into the need for this.  In Maya we use a feature called "Play Blast" to output a shaded view sequence of an animation.  It's not rendered, but it allows us a quick look at the overall shot.  This would be massively helpful in Terragen.  I've run into situations were I've rendered a TG scene with a tracked 3D camera I've gotten from PF Track (or another tracking package) only to find out that the track is off.  This just happened to me with a shot that was 453 frames at 2K. 

Niel
Title: Re: FEATURE REQUESTS
Post by: digitalguru on January 23, 2019, 03:56:43 pm
QuoteIt's not rendered, but it allows us a quick look at the overall shot


Matt can correct me if this isn't right, but I assume Terragen has to render via a micro-polygon render to get the terrain displacement in the preview - looks like a progressive version of the main renderer capped at a certain level of detail, it's obviously not an Open GL preview that you can scrub or render quickly to a playblast.

Maybe an idea would be to add a "terrain only" mode to the render node, so the render would behave like the preview does when the Terrain tab is selected - i.e. no atmos, gi,  terrain shading etc. That would be quicker to render for a test. Would also be great when using the render node to save out a Micro exporter as that's all you need to save an obj or fbx.

Have you tried my script for Maya? -
https://www.highend3d.com/maya/script/terraman-for-maya

I use it all the time to render out animation playblasts, and using tiling for the terrain can get very detailed geo into Maya for a playblast, plus you can use Maya to add useful screen ornaments like frame numbers and camera names burnt in.

QuoteI've run into situations where I've rendered a TG scene with a tracked 3D camera I've gotten from PF Track (or another tracking package) only to find out that the track is off.


I've scripted custom camera rigs to ensure cameras get exported to Terragen quickly and accurately and use .chan data for the export.I  haven't had to deal with a tracked camera from something like PF track, but that's something I definitely want to add soon - just need to write a conversion tool to make sure the FOV, film backs etc translate correctly to Terragen.
Title: Re: FEATURE REQUESTS
Post by: rolland1013 on January 30, 2019, 06:22:14 pm
Yep we use Terraman for import/export of terrain, cameras and such.  While we have gone that route of exporting TG geo into Maya for playblasting, it does add several steps to the workflow.  In tight deadline situations that can be frustrating.
Title: Re: FEATURE REQUESTS
Post by: digitalguru on January 30, 2019, 07:16:14 pm
QuoteYep we use Terraman for import/export of terrain, cameras and such.


Good to know!

Quoteit does add several steps to the workflow.


It does, unfortunately, if you think of anything that could improve that, let me know.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on January 30, 2019, 09:46:28 pm
Quote from: rolland1013 on January 22, 2019, 05:34:11 pm
Ok this feature request is a big one for me (aren't they all?), but I keep running into the need for this.  In Maya we use a feature called "Play Blast" to output a shaded view sequence of an animation.  It's not rendered, but it allows us a quick look at the overall shot.  This would be massively helpful in Terragen.  I've run into situations were I've rendered a TG scene with a tracked 3D camera I've gotten from PF Track (or another tracking package) only to find out that the track is off.  This just happened to me with a shot that was 453 frames at 2K. 

Niel


I suggested to Matt awhile back that it would be nice to be able to render out animations from the RTP (ray traced preview) by having an option to set the maximum refinement time (per frame), and then rendering out the animation. 

Maybe now that Terragen 4 has the Path tracing Render Engine as an alternative to the original, a third alternative render engine could be added as seen in the attached image.

[attachimg=1]
NOTE:  I meant "ray traced preview" not real-time preview.

Derek
Title: Re: FEATURE REQUESTS
Post by: Dune on January 31, 2019, 02:25:11 am
I think the problem being that the ground isn't updated in RTP.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on January 31, 2019, 10:03:29 am
Quote from: Dune on January 31, 2019, 02:25:11 am
I think the problem being that the ground isn't updated in RTP.


Yes, but it still would be useful for doing cloud animations.  ;)
Title: Re: FEATURE REQUESTS - Isn't it Time to Seed Beyond 256?
Post by: D.A. Bentley on February 01, 2019, 04:08:16 pm
Matt,

You said a long time ago:

QuoteThe Power Fractal Shader only has 256 unique seeds. After that the seeds repeat. I wasn't aware of that limitation when I made the Random Seed button generate values between 0 and 65535. The Alpine Fractal Shader and Fake Stones Shader have this limitation too, and probably other shaders that use noise functions. But other nodes in Terragen might have a larger number of seeds.


But isn't it possible to leave the current seeding code in place and fix the bug to allow for the full number of seeds (65535) using a radio button option for backwards compatibility?   Anywhere there is a seed option there would be two radio buttons (One for 8-Bit, and another for 16-Bit).  For backwards compatibility the default would stay on "8-Bit/256", but by switching to "16-Bit/65535" we could explore the much greater range of seeds.  Mainly I want this for clouds and Density fractals.  Pretty Please?

Derek
Title: Re: FEATURE REQUESTS
Post by: Dune on February 02, 2019, 02:09:58 am
More seed variation would indeed be awesome. I've come across limitations too, which had to be circumvented.
Title: Re: FEATURE REQUESTS
Post by: cyphyr on February 02, 2019, 03:26:03 am
In no way am I a coder but couldn't a solution be to multiple two seeds together.
If two random seeds are generated within the 256 limit and are multiplied together that would give a total of 65536 seed possibilities.

ps: I have for a long time wanted a seed node with a corresponding input override on all nodes that have a seed value.
Actually a seed node would just be a Constant scalar (could have a randomise button on it as well), the issue is to have it input and override the random seed generated by PF's, Cloud fractals and FSS.

Very often I have MANY node networks have multiple duplicates of the same noise functions all of which have to be changed to the same new seed value. This is a slow and tedious process that a seed input on  PF's, Cloud fractals and FSS would solve.
Title: Re: FEATURE REQUESTS
Post by: Dune on February 02, 2019, 04:44:50 am
Seed input, brilliant idea!
Title: Re: FEATURE REQUESTS
Post by: mhaze on February 02, 2019, 05:20:11 am
I have a wish list as long as your arm but the thing that bugs me the most is .obj input.  Many .objs I make and use have anything up to 50 part shaders.  When TG loads colour correctly but not displacements I have to manually input them.  Poseray reads the.mtl s correctly but exporting from poseray to TG makes no difference.
Title: Re: FEATURE REQUESTS
Post by: Dune on February 02, 2019, 06:29:35 am
50 is a lot. Can't you combine them (if they can use same texture or color of course)? Like the DAZ figures have 20+ parts, but when combined to the same texture, that can be reduced to maybe 7.
Title: Re: FEATURE REQUESTS
Post by: cyphyr on February 02, 2019, 07:38:57 am
Is the combing something you can do in Poseray?
Title: Re: FEATURE REQUESTS
Post by: Dune on February 02, 2019, 07:45:36 am
Yes, Poseray has a lot more in in than you'd think. Also combining objects by selecting a number of objects that should be combined and giving it a name. I often later make extra parts for an object (say a hairpiece or shovel, as lwo or obj), and just copy the path and name in the input window whilst the original object is already open, and merge them.

With DAZ figures I always set all groups to invisible, make the ones visible to combine, merge them, until all are in new combined groups, then go to materials tab and do groups to materials. You loose original textures, but they can easily be relinked by clicking on the image window.
Title: Re: FEATURE REQUESTS
Post by: DannyG on February 02, 2019, 07:57:02 am
Quote from: Dune on February 02, 2019, 07:45:36 am
Yes, Poseray has a lot more in in than you'd think. Also combining objects by selecting a number of objects that should be combined and giving it a name. I often later make extra parts for an object (say a hairpiece or shovel, as lwo or obj), and just copy the path and name in the input window whilst the original object is already open, and merge them.

With DAZ figures I always set all groups to invisible, make the ones visible to combine, merge them, until all are in new combined groups, then go to materials tab and do groups to materials. You loose original textures, but they can easily be relinked by clicking on the image window.


Extremely helpful Ulco, Thks
Title: Re: FEATURE REQUESTS
Post by: cyphyr on February 02, 2019, 08:37:30 am
Quote from: Dune on February 02, 2019, 07:45:36 am
Yes, Poseray has a lot more in in than you'd think. Also combining objects by selecting a number of objects that should be combined and giving it a name. I often later make extra parts for an object (say a hairpiece or shovel, as lwo or obj), and just copy the path and name in the input window whilst the original object is already open, and merge them.

With DAZ figures I always set all groups to invisible, make the ones visible to combine, merge them, until all are in new combined groups, then go to materials tab and do groups to materials. You loose original textures, but they can easily be relinked by clicking on the image window.


Brilliant. Very useful info and workflow.
Thankyou
Title: Re: FEATURE REQUESTS
Post by: Hannes on February 02, 2019, 10:05:53 am
Very informative, Ulco! Thanks a lot. I'll have to take a closer look at Poseray. So far I only used it for recalculating normals.
Title: Re: FEATURE REQUESTS
Post by: Dune on February 02, 2019, 11:32:29 am
I also use it to make a left-looking cow out of a right-looking cow  ;)
Title: Re: FEATURE REQUESTS
Post by: mhaze on February 02, 2019, 02:57:52 pm
Great idea to explore. Thanks, Ulco
Title: Re: FEATURE REQUESTS
Post by: Matt on February 02, 2019, 06:30:42 pm
Quote from: mhaze on February 02, 2019, 05:20:11 am
I have a wish list as long as your arm but the thing that bugs me the most is .obj input.  Many .objs I make and use have anything up to 50 part shaders.  When TG loads colour correctly but not displacements I have to manually input them.  Poseray reads the.mtl s correctly but exporting from poseray to TG makes no difference.


Can you send me an object like this? I'll get TG to import the displacement.
Title: Re: FEATURE REQUESTS
Post by: bobbystahr on February 02, 2019, 09:55:24 pm
Quote from: Dune on February 02, 2019, 11:32:29 am
I also use it to make a left-looking cow out of a right-looking cow  ;)


yeah that works but I also do that right in TG
Title: Re: FEATURE REQUESTS
Post by: Dune on February 03, 2019, 02:21:38 am
How do you do that then? I'm not aware of the possibility to mirror objects in TG.....
Title: Re: FEATURE REQUESTS
Post by: cyphyr on February 03, 2019, 04:12:19 am
Quote from: Dune on February 03, 2019, 02:21:38 am
How do you do that then? I'm not aware of the possibility to mirror objects in TG.....


You can mirror by scaling -1 in which ever axis you want to mirror in.
Title: Re: FEATURE REQUESTS
Post by: mhaze on February 03, 2019, 05:32:59 am
Cheers Matt, I've sent a file to support.
Title: Re: FEATURE REQUESTS
Post by: Hannes on February 03, 2019, 08:16:25 am
Quote from: cyphyr on February 03, 2019, 04:12:19 am

You can mirror by scaling -1 in which ever axis you want to mirror in.


Hah!!!! That's clever! It's always amazing if someone finds solutions for things that seemed to be impossible in TG.
Title: Re: FEATURE REQUESTS
Post by: Dune on February 03, 2019, 09:05:52 am
Ah, thanks Richard. Never thought of that.
Title: Re: FEATURE REQUESTS
Post by: bobbystahr on February 03, 2019, 10:52:19 am
Quote from: Dune on February 03, 2019, 02:21:38 am
How do you do that then? I'm not aware of the possibility to mirror objects in TG.....

Scale -X ... -Z rotates 180
Title: Re: FEATURE REQUESTS
Post by: Dune on February 04, 2019, 02:24:12 am
Yes, but that just rotates. The scale=-1 is the trick, and it's good to know for pops of say cows.
Title: Re: FEATURE REQUESTS
Post by: René on February 05, 2019, 04:32:28 am
Besides sculpting, which is number 1 on my wish list, the possibility to load two TG documents at the same time. I know, you can load a second document into an older version of TG and I do that a lot, but it doesn't always work properly because some functions are missing in the older version and the nodes often become detached. This would be a real time saver, at least for me, because I often copy nodes from older iterations to the new one.

As far as sculpting is concerned: that' s already possible with the painted shader but it's so complicated that it doesn't pay off.
Title: Re: FEATURE REQUESTS
Post by: icarus51 on February 05, 2019, 09:44:16 am
Hi.

Quote from: rolland1013 on October 03, 2018, 03:03:29 pm

Is there a general feature request discussion on the forum?  If not I'd like to start one.  Here's my wishes for future versions of Terragen:

1. An interactive sculpt tool for shaping terrain.
2. Erosion controls - similar to World Machine.
3. FBX and/or Alembic import ability.
4. Import ROTATION offset for importing animated cameras.
5. V-Ray shader support.
6. Realistic water animation
7. More water types; i.e. ocean, lake, stream, river, rapids, waterfall, etc.

Thanks


I add these: atmospheric optics effects - rainbows, halos, iridescence, corona, sun pillars, distorsion/mirage sun and moon near horizon.
Greetings to all.
Title: Re: FEATURE REQUESTS
Post by: Matt on February 06, 2019, 01:46:26 am
Quote from: René on February 05, 2019, 04:32:28 am
the possibility to load two TG documents at the same time. I know, you can load a second document into an older version of TG and I do that a lot, but it doesn't always work properly because some functions are missing in the older version and the nodes often become detached. This would be a real time saver, at least for me, because I often copy nodes from older iterations to the new one.


On Windows you can open multiple instances of the same application, and on Mac OS you can too, I believe, but there's some trick which I don't remember as I'm not really a Mac user.
Title: Re: FEATURE REQUESTS
Post by: penboack on February 06, 2019, 08:25:22 pm
On MacOS the following Terminal Command may be used to open multiple instances of Terragen, in this example Terragen 4.

open -n "/Applications/Terragen 4/Terragen 4.app"
Title: Re: FEATURE REQUESTS
Post by: bobbystahr on February 07, 2019, 10:13:18 am
Quote from: René on February 05, 2019, 04:32:28 am
Besides sculpting, which is number 1 on my wish list, the possibility to load two TG documents at the same time. I know, you can load a second document into an older version of TG and I do that a lot, but it doesn't always work properly because some functions are missing in the older version and the nodes often become detached. This would be a real time saver, at least for me, because I often copy nodes from older iterations to the new one.

As far as sculpting is concerned: that' s already possible with the painted shader but it's so complicated that it doesn't pay off.


Still, though clunky, you get amazing results..I'd like a tutorial on "Sculpting With Painted Shaders" myself....
Title: Re: FEATURE REQUESTS
Post by: sboerner on February 07, 2019, 12:28:22 pm
OK, since we're blue-skying this . . . my request would be for true object references.

When you place a tgo, the mesh is referenced but the shading network is incorporated into the tgd. Which is nice if you want to tweak the shaders in the main scene. But if you make any substantial changes to the tgo's shading group names or network, the links get broken and you have to delete and replace the tgo in the main file. Sometimes you can manually edit the shading network, but either way with multiple tgos and populations it can get a little tedious.

Referenced objects would encapsulate the mesh, shading groups, and their internal shading networks. Any changes would be made to the original tgo and would appear by explicitly refreshing the tgo or by reloading the main scene.

Perhaps a new file type could be specified ("tgr"?) so that these objects could be used alongside regular tgos.
Title: Re: FEATURE REQUESTS
Post by: RichTwo on February 08, 2019, 05:50:22 pm
Maybe only the oldtimer Terragen Classic users remember a feature of the Animation / Scripts feature which sadly was dropped with T2 and subsequent releases: Button 9.
It just hasn't been the same without it...
Title: Re: FEATURE REQUESTS
Post by: Dune on February 09, 2019, 02:16:00 am
 ;D
Title: Re: FEATURE REQUESTS
Post by: bobbystahr on February 09, 2019, 07:29:23 am
ha ha ha,,,tanks fer da mem'ry
Title: Re: FEATURE REQUESTS
Post by: René on February 09, 2019, 11:19:41 am
Quote from: Matt on February 06, 2019, 01:46:26 am
On Windows you can open multiple instances of the same application, and on Mac OS you can too, I believe, but there's some trick which I don't remember as I'm not really a Mac user.

I was not aware of that. I'm going to try it. Thanks for the tip!
Title: Re: FEATURE REQUESTS
Post by: René on February 09, 2019, 11:26:27 am
Quote from: bobbystahr on February 07, 2019, 10:13:18 am
Still, though clunky, you get amazing results..I'd like a tutorial on "Sculpting With Painted Shaders" myself....


Here you go!
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on February 09, 2019, 04:12:33 pm
Quote from: René on February 09, 2019, 11:26:27 am
Quote from: bobbystahr on February 07, 2019, 10:13:18 am
Still, though clunky, you get amazing results..I'd like a tutorial on "Sculpting With Painted Shaders" myself....


Here you go!


Painted shader 01 under the Terrain group shows a little hump, but why are the Painted Shaders 02 03 and 04 in the Shaders group just all black?  I zoom way in and can't find any sign of something painted.  I find this to be the case a lot in Terragen (no visual feedback).  Especially with Blue Nodes.

So how can an all black Painted shader being used as a mask produce the additional extruded bumps on the main terrain bump?

Derek
Title: Re: FEATURE REQUESTS
Post by: René on February 10, 2019, 01:41:20 am
I renamed some of the nodes so hopefully it will be a bit clearer. Once you displaced a painted shader, it may not be visible anymore. Projection is set to 3D.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on February 10, 2019, 05:18:42 am
Thanks René!  Now I see what you are doing.  I hadn't used the Painted shader in a long time and forgot you could directly paint in the 3D viewport on the terrain, so I was looking for signs of painting in the shader preview pop-up window.  It is odd to me that nothing shows up in the shader preview, and hence this brings us back to a Feature Request!  I would like a Shader Preview window that lets you Pan and Zoom so your not just stuck zooming into the origin.  There have been many instances where I have needed to zoom into something in the shader preview but I couldn't get close enough because as you zoom in the area I wanted to see gets cut off by the edges of the preview and you can't pan on over or pick a different zoom in point.

Derek
Title: Re: FEATURE REQUESTS
Post by: sboerner on February 10, 2019, 11:54:40 am
QuoteI would like a Shader Preview window that lets you Pan and Zoom so your not just stuck zooming into the origin.  There have been many instances where I have needed to zoom into something in the shader preview but I couldn't get close enough because as you zoom in the area I wanted to see gets cut off by the edges of the preview and you can't pan on over or pick a different zoom in point.


Echo this. I know this has been requested elsewhere in the forum. It would be a huge timesaver.
Title: Re: FEATURE REQUESTS
Post by: Dune on February 11, 2019, 02:19:29 am
Indeed, handy to have that possibility sometimes.
Title: Re: FEATURE REQUESTS
Post by: mhaze on February 11, 2019, 04:37:04 am
Ditto :D
Title: Re: FEATURE REQUESTS
Post by: ajcgi on February 25, 2019, 10:34:45 am
Quote from: Yanik on October 05, 2018, 12:38:23 pm
I also have been learning and using Houdini the past year and Houdini gives you many ways to debug your scene. Houdini's network view is a joy to use compared to other node based applications. If you feel it being too complex I highly recommend you to learn some basic development skills to understand how data is stored and how it flows.
That said I agree with it not being artist friendly.


Absolutely agree. I have had to up the anti on understanding how data moves around VFX scenes. That being said I come from a Softimage background and ICE simulation necessitated understanding some of that at any level. Going from that to Houdini was a challenge workflow-wise in some ways, but at least it wasn't like going to Maya which to me was like arguing with a petulant child every time I did anything.
Node network in Houdini is now my best friend. Every time I'm in Terragen I long for differently coloured nodes, ones of a different shape and so on.

Quote from: Yanik on October 05, 2018, 12:38:23 pm
I don't think it's fair to compare a complex application that is mostly TD/VFX oriented with a simple terrain design tool. In my feature request list I posted a few ideas on how to make Terragen easier to use. Value remapping is a very important feature which is used in many terrain design tools. It allows you to artistically remap values and allows you to create new shapes quite easily.


Houdini has excellent terrain tools that both I and my colleagues have had great success with, especially in tandem with Terragen.

Lastly, many sincere apologies for saying 'off you pop'. Reading that back made me cringe. It was very sarcastic, arrogant and doesn't help anyone. I must have been having a shitty week for some reason.
Title: Re: FEATURE REQUESTS
Post by: Dune on February 26, 2019, 02:15:14 am
I have one; sometimes you can't easily get rid of the manipulation stuff of an object or simple shape or something, once selected. I usually click somehwere outside the preview window, but yesterday it constantly selected another simple shape. Turning off all objects (in the window) turned them all off, but the crosshairs remained.
So maybe an extra line in the popup where you can select an object should be needed: 'selection off' ?
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on February 26, 2019, 04:59:55 pm
I also have another small request.  When resizing Group windows it seems you can only resize to the left, right, or down, but not up.  I often times need to expand my Atmosphere group, so I have to drag the whole thing up first and then resize it from the bottom edge instead of simply just dragging the upper edge up to make more room.  Very minor, but thought I would ask.  ;)

-Derek
Title: Re: FEATURE REQUESTS
Post by: Matt on February 26, 2019, 05:04:23 pm
You can resize the group by the top edge, but you have to be zoomed in quite far. I'll try to improve this. Some more info here: https://planetside.co.uk/forums/index.php/topic,25674.0.html
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on February 28, 2019, 06:12:16 pm
Thanks Matt!  Now I know why I could sometimes move the top edge of the group container.  ;) 

-Derek
Title: Re: FEATURE REQUESTS
Post by: Ethrieltd on March 02, 2019, 02:55:06 pm
Quote from: icarus51 on February 05, 2019, 09:44:16 amI add these: atmospheric optics effects - rainbows, halos, iridescence, corona, sun pillars, distorsion/mirage sun and moon near horizon.


I've used Halosim for Sun Dogs from https://www.atoptics.co.uk/halo/halfeat.htm but it'd be great to see the ability built in. There's also IRIS from the same site that is for Rainbows, etc. Which I haven't tried.

This is an example of a HaloSim generated effect composited into a Terragen scene.
Title: Re: FEATURE REQUESTS
Post by: bobbystahr on March 02, 2019, 03:27:24 pm
Quote from: Ethrieltd on March 02, 2019, 02:55:06 pm
Quote from: icarus51 on February 05, 2019, 09:44:16 amI add these: atmospheric optics effects - rainbows, halos, iridescence, corona, sun pillars, distorsion/mirage sun and moon near horizon.


I've used Halosim for Sun Dogs from https://www.atoptics.co.uk/halo/halfeat.htm but it'd be great to see the ability built in. There's also IRIS from the same site that is for Rainbows, etc. Which I haven't tried.

This is an example of a HaloSim generated effect composited into a Terragen scene.


Indeed that would be a handy thing to have
Title: Re: FEATURE REQUESTS
Post by: sjefen on March 06, 2019, 12:02:01 pm
Would also be cool with a population that can handle more objects at the same time and control how much % each one gets populated. Would make it a lot faster to grow a forest with more variations. Combined with random scale and rotations (with controls) and I would be very happy  :)


- Terje
Title: Re: FEATURE REQUESTS
Post by: digitalguru on March 06, 2019, 05:49:39 pm
QuoteWould also be cool with a population that can handle more objects at the same time and control how much % each one gets populated.


I've been using MASH in Maya to create some ecosystems: https://vimeo.com/205891678

Has some very cool ideas, like seeding the start points for an ecosystem, then having it "grow" out from the seed points based on wind distribution of the seeds of each plant/tree.

Mostly though it stores an array of objects to randomly populate in one node, which can be biased to favour selected elements. Would love to see this in Terragen.
Title: Re: FEATURE REQUESTS
Post by: icarus51 on June 21, 2019, 06:50:27 am
Quote from: Oshyan on October 03, 2018, 08:33:04 pm
Yep, lots of good ideas here. Many already suggested, which we keep in a private issue tracker. We're listening and will implement as much as we can over time. I can tell you we are almost certainly never going to support Vray shaders though. Other than that it's all probably fair game.

- Oshyan


Hy.

I remember when, many years ago, ask for optics effects in Terragen (eg. rainbows, halos, light pillar, mirages and iridescence in clouds). Many years have passed but these features i don't see in the current software. I know these effects can be made after render (post production) by graphic editor but  these effects will not be embodied and calculated in the software with the result of a unrealistic and displaced vision.
A plugin (or feature) for these effects would be fantastic for this feature or few new parameters in Atmosphere and/or Clouds.
Sculpting Tool could be the most precious thing, naturally. Now in the current 2019 seems to me that the time for these things is arrived, or am i wrong and missed something? In case, excuse me for my enthusiasm and my impatience.  :-[
Greetings.
Title: Re: FEATURE REQUESTS
Post by: icarus51 on June 21, 2019, 07:04:31 am
Quote from: Ethrieltd on March 02, 2019, 02:55:06 pm
Quote from: icarus51 on February 05, 2019, 09:44:16 amI add these: atmospheric optics effects - rainbows, halos, iridescence, corona, sun pillars, distorsion/mirage sun and moon near horizon.


I've used Halosim for Sun Dogs from https://www.atoptics.co.uk/halo/halfeat.htm but it'd be great to see the ability built in. There's also IRIS from the same site that is for Rainbows, etc. Which I haven't tried.

This is an example of a HaloSim generated effect composited into a Terragen scene.


I also have tried this but if this feature could be  built in Terragen  this is better, i hope you understand me.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on June 21, 2019, 09:01:29 am
I have a NEW feature request, but not sure if it has already been asked.

Can we get a check box to turn on "Save GI Cache (for single frame renders"

Because I don't do a whole lot of animation I often times turn my GI Cache Quality up, and it takes a long time to process just the GI, so after rendering a single frame I would like to keep that GI cache file wherever it may be.  I know you can render just the GI cache, and then use the Load GI Cache file that way, but it would be nice to kick off a render and have it save the GI Cache automatically without doing a 2-Step process.

-Derek
Title: Re: FEATURE REQUESTS
Post by: jaf on June 21, 2019, 12:05:31 pm
I'm going to repeat a request I made long ago.  Never did hear why it wouldn't be useful or very hard to implement.  A simple "do not clear render output" checkbox.  One would do a crop and with that checkbox checked, make a change like to a surface shader and then do another crop near or next to the first one and then render again.  And then, if desired, do a third, fourth, etc. Much quicker and easier than saving off crops and comparing each in an editor.
Title: Re: FEATURE REQUESTS
Post by: digitalguru on June 21, 2019, 12:30:03 pm
I would imagine that's quite easy to do, all it would need is some way to step through/read any renders output to the Automatic Render Output files folder.

It's something I do on every Terragen session (and all users of Terragen I'd imagine) It would be a very useful feature.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on June 21, 2019, 02:41:38 pm
Quote from: jaf on June 21, 2019, 12:05:31 pm
I'm going to repeat a request I made long ago.  Never did hear why it wouldn't be useful or very hard to implement.  A simple "do not clear render output" checkbox.  One would do a crop and with that checkbox checked, make a change like to a surface shader and then do another crop near or next to the first one and then render again.  And then, if desired, do a third, fourth, etc. Much quicker and easier than saving off crops and comparing each in an editor.


I have been dreaming of that feature as well!  Great Idea, since render iteration in Terragen is what we all do over and over.  I hate how the frame buffer clears to black ever render.
Title: Re: FEATURE REQUESTS
Post by: kentm on June 21, 2019, 03:44:22 pm
This is one thing I'd love as well, for my 2 cents.

Personally I'd love it if new features could be put on hold for a little bit and have the dev team focus on UX & workflow enhancements. Terragen, in my opinion is at an AMAZING state as far as toolsets go and its the perfect time to focus instead on ways to refine the UI and streamline the workflows.

I'm new again to the program and am just getting back into it, though I was briefly a part of the original beta years (I forget but I'm going to say v 0.5?), and do want to say that I really am blown away by what its possible to do with Terragen and the functions that have been added to the program, so I'd love to see the UI and workflow getting some real attention.
Title: Re: FEATURE REQUESTS
Post by: Oshyan on June 21, 2019, 03:50:36 pm
Improvements to the render view are planned for the future and would incorporate some similar functionality to what you're referring to ("don't clear the previous render").

We don't plan to support unusual atmospheric and optical effects at this time, however.

- Oshyan
Title: Re: FEATURE REQUESTS
Post by: WAS on June 25, 2019, 12:59:31 pm
Quote from: Oshyan on June 21, 2019, 03:50:36 pm
We don't plan to support unusual atmospheric and optical effects at this time, however.

- Oshyan


I believe he's trying to descibr ice particles in the air when it's below freezing point. Not unusual, actually very common globally, and would be a nice effect with TG's atmosphere tab. A "Temperature" slider even that creates halo around light sources. Colder it is, I believer the further the halo is seen from the source, and more dense it's effect. This is commonly seen with the sun because most people are indoors during dawn, and not in northern or southern hemispheres, but this phenomenon is very common at night with the moon.

Rainbow effect isn't as common and comes down to where you are in relation to lighting. More a post-processing thing.

But having a halo effect from ice particles would add a level of realism for light sources and sun/moons.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on July 08, 2019, 02:06:31 pm
Another render related feature request here.  Wouldn't it be nice if we could render a particular set of chosen frames, and frame ranges like you can do by command line rendering right in Terragen.

We can render a sequence by a certain interval, but why not have the option to render Frames "1-100, 115, 116, 128, 132-134, 150-255" right within Terragen?

This would be very helpful for me, so if it's easy to implement please do so Master Matt.  ;)

-Derek
Title: Re: FEATURE REQUESTS
Post by: WAS on July 09, 2019, 03:39:54 pm
Quote from: D.A. Bentley on July 08, 2019, 02:06:31 pm
Another render related feature request here.  Wouldn't it be nice if we could render a particular set of chosen frames, and frame ranges like you can do by command line rendering right in Terragen.

We can render a sequence by a certain interval, but why not have the option to render Frames "1-100, 115, 116, 128, 132-134, 150-255" right within Terragen?

This would be very helpful for me, so if it's easy to implement please do so Master Matt.  ;)

-Derek



That's a pretty good idea actually and doesn't seem like too much would need to altered by targeted frames.
Title: Re: FEATURE REQUESTS
Post by: kentm on July 16, 2019, 06:47:02 pm
I'd like to cast a vote for having a render/RTP window open at the same time as a 3d Preview window.

...I'm trying to punch a hole into a cloud in a specific spot and am having to jump back and forth between the two states/view styles in the one pane to adjust the position of the SSShader and its a bit frustrating. I CAN do it numerically of course but it sure would be a lot easier if I could drag the handle around in one window and have the immediate feedback from the RTP preview.
Title: Re: FEATURE REQUESTS
Post by: Oshyan on July 16, 2019, 07:29:59 pm
RTP will have drag handles in upcoming version 4.4. Multiple simultaneous preview windows should be a possibility in the future.

- Oshyan
Title: Re: FEATURE REQUESTS
Post by: Dune on July 17, 2019, 01:38:36 am
I've written it several times, but it's easier to punch a hole in skies with a projected white circle (inverted of course), instead of laborously moving around SSS's.
Title: Re: FEATURE REQUESTS
Post by: bobbystahr on July 17, 2019, 10:48:50 am
Quote from: Dune on July 17, 2019, 01:38:36 am
I've written it several times, but it's easier to punch a hole in skies with a projected white circle (inverted of course), instead of laborously moving around SSS's.


And many thanks for that Ulco...a most useful suggestion then and now.
Title: Re: FEATURE REQUESTS
Post by: rnasielerge on August 04, 2019, 02:25:45 pm
Is there a general feature request discussion on the forum?
Title: Re: FEATURE REQUESTS
Post by: WAS on August 04, 2019, 02:35:59 pm
Quote from: rnasielerge on August 04, 2019, 02:25:45 pmIs there a general feature request discussion on the forum?

This has sorta become the informal request thread, I guess. There is no formal request discussion.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on September 23, 2019, 09:35:48 pm
I would like to have the ability to render an animation sequence and have the resulting frames be saved at the size that was specified by the crop frame instead of including the empty black space.  Mostly I would find this useful because I render lots of seed animations of clouds to search for interesting cloud formations, so I am ending up with thousands of frames with "Black Bottoms" since I am mostly only concerned with the sky above the horizon.  Sometimes I render "Above The Clouds" cloud seed animations though so in these cases I would have a black upper area in the image.

If this "Crop Save" option was a feature it would save me some disk space, since even black space in an image takes up bytes, and also my preview thumbnails would be more useful    ;)

-Derek
Title: Re: FEATURE REQUESTS
Post by: Oshyan on September 23, 2019, 09:50:55 pm
Quote from: D.A. Bentley on September 23, 2019, 09:35:48 pmI would like to have the ability to render an animation sequence and have the resulting frames be saved at the size that was specified by the crop frame instead of including the empty black space. 
You can already do this from the command line. Reference docs are in the /Docs directory of your Terragen install and can also be found in the Wiki: http://planetside.co.uk/wiki/index.php?title=Command_Line_Reference

What you want is -cropoutput

- Oshyan
Title: Re: FEATURE REQUESTS
Post by: René on September 24, 2019, 04:23:34 am
I make and store a lot of test renders, with the result that my folders get full of Tif files with crop renders. That takes up a lot of space so I cut off the black part and save it as a jpg. It would be great if there was an option to save only the rendered part (not the black part) as a jpg. It would save me a lot of time.
Title: Re: FEATURE REQUESTS
Post by: bobbystahr on September 24, 2019, 10:51:48 am
Quote from: René on September 24, 2019, 04:23:34 amI make and store a lot of test renders, with the result that my folders get full of Tif files with crop renders. That takes up a lot of space so I cut off the black part and save it as a jpg. It would be great if there was an option to save only the rendered part (not the black part) as a jpg. It would save me a lot of time.
I echo this request and thanks to René for posting it!
Title: Re: FEATURE REQUESTS
Post by: Matt on September 24, 2019, 02:38:44 pm
Quote from: René on September 24, 2019, 04:23:34 amI make and store a lot of test renders, with the result that my folders get full of Tif files with crop renders. That takes up a lot of space so I cut off the black part and save it as a jpg. It would be great if there was an option to save only the rendered part (not the black part) as a jpg. It would save me a lot of time.

I'm echoing what Oshyan just said, that Terragen will do this if you run it with "-cropoutput" somewhere in the command line (without the quotes). But what's rarely mentioned is that this works with the GUI too. On Windows you can set this up with a custom shortcut. Create a shortcut to Terragen with -cropoutput in the command line arguments, and then every cropped render you do will exclude the black border.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on September 24, 2019, 07:40:24 pm
Quote from: Matt on September 24, 2019, 02:38:44 pm
Quote from: René on September 24, 2019, 04:23:34 amI make and store a lot of test renders, with the result that my folders get full of Tif files with crop renders. That takes up a lot of space so I cut off the black part and save it as a jpg. It would be great if there was an option to save only the rendered part (not the black part) as a jpg. It would save me a lot of time.

I'm echoing what Oshyan just said, that Terragen will do this if you run it with "-cropoutput" somewhere in the command line (without the quotes). But what's rarely mentioned is that this works with the GUI too. On Windows you can set this up with a custom shortcut. Create a shortcut to Terragen with -cropoutput in the command line arguments, and then every cropped render you do will exclude the black border.
Awesome!  This is Fantastic!  Thanks Matt & Oshyan!  :)  -Derek
Title: Re: FEATURE REQUESTS
Post by: Tangled-Universe on September 26, 2019, 02:45:15 am
JPEG output support would be highly appreciated though :)
Title: Re: FEATURE REQUESTS
Post by: Hannes on September 26, 2019, 03:15:10 am
And I'd like to see TG supporting normal maps!!!
Title: Re: FEATURE REQUESTS
Post by: cyphyr on September 26, 2019, 03:54:02 am
I echo JPG support. Not just useful for sharing work on social media and forums. Also helpful for collaborating on projects.
Title: Re: FEATURE REQUESTS
Post by: Dune on September 26, 2019, 06:15:54 am
So do I. And automatic 32-bit .exr (or choice) saving instead of the bmp's. And automatic depth pass saving instead of alpha (or choice).
Title: Re: FEATURE REQUESTS
Post by: René on September 26, 2019, 09:17:01 am
Quote from: Matt on September 24, 2019, 02:38:44 pmI'm echoing what Oshyan just said, that Terragen will do this if you run it with "-cropoutput" somewhere in the command line (without the quotes). But what's rarely mentioned is that this works with the GUI too. On Windows you can set this up with a custom shortcut. Create a shortcut to Terragen with -cropoutput in the command line arguments, and then every cropped render you do will exclude the black border.
Thanks for the explanation. I am on a Mac; Mac users are in my experience less computer savvy than Windows users, moreover, I have zero experience with comand lines. I took a look at the wiki and it looks rather daunting to me. Moreover, I am lazy and expect the computer to do the work for me. ;) So it looks like I have to dive into it after all.
Title: Re: FEATURE REQUESTS
Post by: digitalguru on September 26, 2019, 09:30:41 am
+ 1 for JPEG support

also, it would be nice if there was an option to turn off the extra alpha image in the temp output
Title: Re: FEATURE REQUESTS
Post by: Matt on September 26, 2019, 02:48:38 pm
Quote from: Dune on September 26, 2019, 06:15:54 amSo do I. And automatic 32-bit .exr (or choice) saving instead of the bmp's. And automatic depth pass saving instead of alpha (or choice).

This is in Preferences > File Saving > Render save format.
Title: Re: FEATURE REQUESTS
Post by: Dune on September 27, 2019, 02:17:18 am
That's already there! Never noticed. Thanks Matt!
Title: Re: FEATURE REQUESTS
Post by: sjefen on September 27, 2019, 03:55:18 am
Quote from: Hannes on September 26, 2019, 03:15:10 amAnd I'd like to see TG supporting normal maps!!!

Yes! This would be really great  ;D


- Terje
Title: Re: FEATURE REQUESTS
Post by: WAS on September 27, 2019, 03:11:20 pm
Quote from: Hannes on September 26, 2019, 03:15:10 amAnd I'd like to see TG supporting normal maps!!!
Quote from: sjefen on September 27, 2019, 03:55:18 am
Quote from: Hannes on September 26, 2019, 03:15:10 amAnd I'd like to see TG supporting normal maps!!!

Yes! This would be really great  ;D


- Terje

In the meantime, you can use a DirectX (Or OpenGL) driven PBR Material generator (like Materialize: http://boundingboxsoftware.com/materialize/getkey.php) to convert a Normal Map into Displacement. From what I can see, it reads the Normal Map as displacement, and converts to heightmap displacement, with tunable settings on interpretation.

Programs like CrazyBump do not interpet the Normal Map as displacement, and instead grayscale and edit the normal map itself, creating very inaccurate results.

You can see my exaggerated examples on the Facebook TG community: https://www.facebook.com/groups/Terragen.Galleries/permalink/2362937713832238/
Title: Re: FEATURE REQUESTS
Post by: Hannes on September 27, 2019, 03:29:33 pm
That's good to know. Thanks, Jordan! So far I used Crazy Bump, but I'll check Materialize.
Title: Re: FEATURE REQUESTS
Post by: cyphyr on September 27, 2019, 03:35:17 pm
I have often wanted to turn a normal map into a displacement map. Of course, simply turning it into a greyscale is not the way to go.
Actually, I don't understand how a displacement map can be derived from a normal map. They are describing very different things. The normal map describes the "real" angle of a surface relative to the actual value whereas a displacement map is a perpendicular (clue is in the name!) displacement relative to the surface.
How can one derive one from the other?
(please excuse my non-technical language)
Title: Re: FEATURE REQUESTS
Post by: WAS on September 27, 2019, 03:38:37 pm
Quote from: cyphyr on September 27, 2019, 03:35:17 pmI have often wanted to turn a normal map into a displacement map. Of course, simply turning it into a greyscale is not the way to go.
Actually, I don't understand how a displacement map can be derived from a normal map. They are describing very different things. The normal map describes the "real" angle of a surface relative to the actual value whereas a displacement map is a perpendicular (clue is in the name!) displacement relative to the surface.
How can one derive one from the other?
(please excuse my non-technical language)

From what I can see in Materialize (haven't tried to decompile anything or look at source), it seem to fire light from relative off-set angles in 360 degrees, creating the microdisplacement you'd see in render engines or game engines, in a grayscale environment. The final 360 equalized passes are than editable via contrast bias settings and such.

If provided maps, it seems to read them in a 3D environment, using shaders to create maps.
Title: Re: FEATURE REQUESTS
Post by: D.A. Bentley on September 30, 2019, 10:51:22 am
Animation F-Curve Out of Range Types

Just wanted to add this to Feature Requests:  https://planetside.co.uk/forums/index.php/topic,26970.0.html (https://planetside.co.uk/forums/index.php/topic,26970.0.html)



-Derek
Title: Re: FEATURE REQUESTS
Post by: rolland1013 on October 14, 2019, 07:11:40 pm
OpenExr 2.0 with Deep output

This one just came up again here at my studio.  I think I've seen others request this feature here. 

Niel
Title: Re: FEATURE REQUESTS
Post by: Oshyan on October 15, 2019, 05:38:21 pm
Quote from: rolland1013 on October 14, 2019, 07:11:40 pmOpenExr 2.0 with Deep output

This one just came up again here at my studio.  I think I've seen others request this feature here. 

Niel
It's in the project tracker, but I'll bump it with your request.

- Oshyan