Itoo Software Forum
RailClone => RailClone Pro (*) => Topic started by: Rokas on September 08, 2014, 03:47:20 PM
-
Hi, i can`t understand why this happens:
(http://i.imgur.com/drSpJVb.gif)
I use the same method for X and Y scaling, but X seems buggy, dont't know why
I attach max file
-
Hi Rokas,
Not sure exactly what's causing this, X and Y are handled differently (an A2S array is essentially a stack of L1S generators) so it's possible they're not behaving identically. Setting the default mode to scale fixes the problem.
Thanks,
Paul
-
That fixes the problem for the time being, thank You.
But, I have another one: why measurements of RailClone object are not the ones I specify in X and Y ?
(http://i.imgur.com/XuHBP2Q.gif)
-
Hi Rokas,
We've taken a look at this and it's actually a problem with the Measure tool. It uses the bounding box returned by the object, which in the case of RailClone is a bit larger (5%... because of other reasons). If you measure it using another technique, i.e. using a snapped rectangle, everything should be correct.
Many thanks,
Paul
-
good to hear, thank You for explaining...
-
From time to time I keep getting the same bug as described in 1st post. And sometimes workaround mentioned is not applicable.
-
Hi Rokas,
I'm not sure, but my suspicion is that the algorithm used to calculate the scale factor required to set the new size of the segment is limited in accuracy by the number of floating points max uses. Therefore adding an additional (whole) segment at certain measurements. A quick fix for this is to turn on Slice for that segment. I'll look into it and see if I can get to the bottom of the cause.
Thanks for reporting!
Paul