Chaos Corona for 3ds Max > [Max] Resolved Feature Requests

Bitmap Transform_source(FStorm) or Mapping_source(VRay) feature

<< < (2/3) > >>

piotrus3333:
use controllers for that:

Juraj:
Controllers like above aren't solution, I've been using them for 2-3 years and it's great hassle.
First, it takes a lot of time to make them for single big node (like Trip or Randomizer), but you can save them as preset into your library.
Instancing them is only easy the first time you do it, after every reload of 3dsMax, controllers get hidden and need to get unhidded. Can be scripted to avoid but another step of busy-work.
Lastly, after being used on two nodes at least (like Trip&Rand at same time), it creates horrible mess of layout to the shader that affects readability. Or hide them and then you can't instance them.

It just sucks. Mapping node is simple and elegant solution.

piotrus3333:
not the right connection on my screenshot - uvw scale and not tiling. one bezier color controler, even cleaner.

when controller is hidden you can adjust one of uvw scale spinners, all maps will update.

piotrus3333:
and this should I guess fix the "disappearing" controllers issue:

Juraj:
I really want to post a screenshot of my uber-shader which utilizes like 500 (Float, Bezier, Etc,.) Controllers to really drive home the idea Controllers are not meant for this :- ). And I use that for 80perc. of my material library.

So in more complex answer:

1) Obviously controllers work as well when hidden, what would be their point otherwise :- )? But when they are hidden, they can't be instanced properly. This may be current Slate limitation, haven't tried 2024 if the new one is constantly aware of hidden parameters.
2) When they are unhidden though, they created absolute mess, simple 5 texture Shader takes full-screen page. That's the whole point of hidding additional parameters. You don't want them to be unhidden all the time.

That means constant back n forth hassle between manipulating shader, and manipulating controller instancing when extending their use.

It's not in way whatsover replacement for proper Mapping Source or Master Controller. It's not just Vray and F-Storm has it, Blender, Maya, Unreal Engine and countless others utilize the same approach.

Just because some existing workaround exists doesn't mean new and much superior feature shouldn't be implemented.

Navigation

[0] Message Index

[#] Next page

[*] Previous page