Mapping in Transform Operator

[Dragan]

I know you are close to the final release, but I still miss the Mapping functions in Transform Operator.
I have to duplicate segments if I want to have different types of mapping on the same geometry.
It will also give more freedom in Macros creation.


 

[iToo]

Added to the wishlist.
Mapping is available only in the Segment node because performance reasons, but i will see what can be done.

[Dragan]

We need some improvements for mapping.
Box mapping does not adopt scaling/translation but maps scaling or stays in world space while translating geometry.
Even mapping on the Segment level seems to not work individually on UVW but has some issues. It is very difficult to control size/orientation even for more experienced users.
If we could have mapping in Transform Operator at least we could do some mapping adjustments through Graph creation. 
 

[Dragan]

I want to bring this topic back to your attention. 
During beta testing, I found most of the new features quite useful, but I have always been missing a better way of manipulating maps.
With the new Shape & Spline operators, we have a lot of options for creating complex nested generators, but even with potential Mapping in Transform operator, I found that lots of issues can't be solved.
I would like it if we could have some easy options in the  Generator to set up the final map size and orientation, but instead to be based on Box Mapping to maintain the Segment's orientations and to fix issues when the Default-> Scale is applied.
e.g. For a simple L1S Generator, we can't set some constant Real-World Map size to maintain on Default ->Scale Type. 

[iToo]

Thanks for the feedback, Dragan.

As said above, currently mapping is limited to Segments nodes because performance reasons (it's a costly operation and also breaks instancing).
I will check if it's possible to apply mapping on Transform/Generator nodes, but that will require significative changes in the code.