RailClone > RailClone Pro (*)

Transform vs Randomize/Selector

(1/2) > >>

Dragan:
Just a quick question to avoid testing on a large scale.

eg. I have a segment that has to be rotated by 90deg through various nested generators.
What will be the faster/efficient way to do it regarding RC programming code (how it works under the hood):
- use Transform_rotate>Random Calculated on Segments for the original segment or
- use pre-prepared segments (original and rotated ones) and go via Randomize / Selector>Random on Segments Operator

Sometimes I can solve some difficult tasks with some smart Expressions and just Transform Nodes that look elegant and nite in the Style editor but maybe it is not build-time efficient than the approach in some other more complex way in the Style.
The bottom line is whether there is any preference for using Transform_rotate>Random on Segments VS Prepared segment>Randomize/Selector?
I`m just interested in the build time ;)

Tnx.

Paul Roberts:
That's an interesting question. I've just used the basic scene attached to do a quick test and overall the expression won



Digging into the detailed stats though, the generator build time is actually slightly longer for the expressions at 5ms vs the geometry version at 3ms. The bulk of the time difference is due to the Geometry Setup phase



Hope that helps,
Paul

Dragan:
Hm, I'm surprised that the geometry setup is so long. Is this related to geometry polycount, segments count, or something else?
This will be quite a value looking on a large+nested scale. We should dig more about this.
Thank you

Paul Roberts:
In my tests. geometry setup doesn't really increase with the number of instances so the difference is really quite negligible. For example, creating 10100 instances (instead of 625 as in the previous example) only added a millisecond or two in both versions.

Best,
Paul

Dragan:
I was referring on number of Input Segments.
Is 4 x 90degSegments vs 1 x Segment_for_transforming has more impact on geometry setup?
Let's continue the testing with forced instancing workflow so we can exclude slicing as probably biggest impact on build and find out more about...

Navigation

[0] Message Index

[#] Next page