Preserve Segments/Clipping Base Spline

[Dragan]

RC 5.0.7
Please check:
1. Preserving segments not working again (use Transform X/Y translation to move)
2. Try to change the Base spline to Line001 (two closed subsplines). RC crashed with the screen... Not sure if this is on my side 

[Michal Karmazín]

Hi Dragan,

Big thanks for the provided scene. With your help, we've been able to reproduce this unwanted behavior here too. We'll check what can be done to fix it - it'll need to be investigated more in deep by our main developers. Thanks for your speedy collaboration, your feedback is very important to us.

Best regards,

[iToo]

1. Preserving segments not working again (use Transform X/Y translation to move)

I cannot reproduce this one. I'm using the attached scene for testing.
Please, could you compare what's different from yours ?

[Dragan]

Hi Carlos,
Try to use it on Rectangular Base Spline.

[Dragan]

Even in your circular Base spline segments are missing.
Try the scene from promotional if you can access it.

[Dragan]

I need to check again if nested segments were preserved until all have been out of the clipping spline.
If you look at the gif image there are segments on start|end|def seams to be preserved when shutters are opened.

In the promotional scene, the shutters are a nested generator that's hung on the inside of the window reveal. That means that a bit of the hinge always remained inside of the clipping spline and thus the whole object was preserved. I can confirm that moving it entirely outside of the spline means that it disappears. This behaviour makes sense because really the change is that the composed/nested geometry was behaving as though it was a single segment when it comes to clipping. As far as I know, this behaviour was the same in all the beta versions.

Cheers,
Paul.

[iToo]

I see your logic, but as far as i can see, Clipping behaviour has not changed: segments only are preserved when are inside or intersecting with the spline, but not completely outside.
I'm a bit confuse about your statemenent, regarding this behaviour is not working again. Was it working in RC 5.0.6, and broken in 5.0.7 ?

Unfortunately i cannot verify the promotional scene. Paul has the file, and he is on vacation today. Anyway, i can check this issue with him tomorrow.

[Dragan]

 
I need to check again if nested segments were preserved until all have been out of the clipping spline.
If you look at the gif image there are segments on start|end|def seams to be preserved when shutters are opened.

However, please check what can be done to accomplish the `preserve all` workflow in the future.

[Paul Roberts]

Hi Dragan!

That's always been the behaviour during the beta. At present, the change is that nested or composed geometry is now treated as though it were a single segment in terms of clipping behaviour. The example in the video uses a nested generator to create the shutters, and the hinges are inside the window reveal so there's always a part that is within the clipping spline.

We'll think about if the behaviour can be changed to move nested geometry completely outside the clipping area.

Thanks as always for the feedback,

Paul

[Dragan]

Hi
Just think of nesting complete window frame generated with one A2S (X/Y size calculated from Master A2S) nested in the Master A2S.
Now you need to Slide out of the Clipping area. All segments in nested A2S will be removed/sliced.

Right now I do a workaround with combining L1S with height parameter via main/marker data parameters to get the Y size for A2S. But RC could preserve the whole nested generator this will give me/users the opportunity to use directly Clipping splines to acquire both X&Y sizes for the nested A2S.

Sure, I don`t know how deep this will go into coding. Thank you for taking this into consideration.
Hope all that have any sense to you guys

[Dragan]

Hi, any news about the topic?
Paul, what do you think about preserving all nested segments and how did you configure your style for the promotional scene?
As I can see vertical planks in the RC4 version are removed (one-by-one) when they go outside the clipping area but in the RC5 version vertical planks remain even though those segments are completely out of the clipping area.
It is difficult to analyze just from a gif knowing you always have a different (genius) approach to every problem 

[Paul Roberts]

Hi Dragan, it's on the wish list, but no more news at present. In my scene, the door is still just slightly inside the clipping spline (the hinges are in fact) which is why the planks are retained.

Cheers,
Paul

[Dragan]

Not sure any more 
In the RC4 vertical segments are cut out one by one and in the RC5 they remain.

I`m still voting to preserve ALL segments even they are completely out of the clipping area. After all, users now have full control of the slicing option even trough Transform Override so it will be very easy to control and evaluate through the Style.

[iToo]

Just a note: Transform > Slice doesn't affect to Clipping, only to slicing at right/bottom/corners of array rows. Basically there are two separated slicing operations.
I know it may be a bit confuse, but that option is inherited from when RC supported only linear generators.

Sorry, that was not correct.
Effectively there are two slicing operations, but 'No Slice' is considered on Clipping, specifically with the 'For No-Slice' option. I forgot it.

[Dragan]

Thank you Carlos.
No confusion on that matter but my point is if we are nesting a complete A2S Generator carrying complete geometry  (window frame, fence car door, etc), and its geometry is calculated/based on the Master A2S/Extended and we need to move this geometry out of the clipping area (sliding door frame, sliding fence car..) we need those nested segment preserved.
I can see by the questions on the forum a lot of new users getting deeply into RC Style since RC5 is released and I think it is just a matter of days when most of them will need something like this. 
I`m still ok with my workarounds, nesting my A2S to an L1S level to avoid unnecessary clipping but this just makes one or two more calculation loops.

Please if it is not a deep coding issue let us have this `preservation mode` and see if this will cause any problems in the future.
You can always go back 
Regards