Array 2S - corner problem

[REDVERTEX]

Hi,

I'm struggling with an issue and can not figure out any workaround.
While preparing an preset for rotating facade shaders, I've come to a point that everything is working perfect except the corner element in one of the two options.
I'm making the corners with the default and start segments in composite operator.

Option 1 is interrupted and is made of start segment  and a null segment with exported X fixed size:


Option 2 is continuous and is made of start segment and default segment with exported X fixed size:


For option 1 everything is working fine.
Unfortunately in option 2, when i change the degrees of rotation, the size of the corner element changes as well. See examples:




I've attached the file.
Do you have any idea what is the reason for this?

In addition,  I'm making the distance between the Y rolls via padding.
This is making an absolute padding, which depends from the angle of opening.
Please share if you have any suggestions for approach that will make the y rolls static without taking the rotated elements in the padding evaluation.

Looking forward to some ideas.

Best regards,
Kiril Alexandrov, RedVertex Team.

[Rokas]

Hi, I am still trying to understand the style.
I can't still understand Your description, what is this "Option 1" that is working as expected.
Is it ShaderType = 1 and rotation?

It does not work for me. As I undertand Increasing Corners size is the problem, right ?

[REDVERTEX]

Hi Rokas,

Thank you for the prompt response!


The two options are for "Corner_Type".


Check the fixtures that should be on the mullion. They are moving when you change the angle.




Here is simple explanation of the parameters:

Shader_Rotation - rotation of the panels (degrees) /Y fixed rotation
Shader_Type - 3 different types of segments
Shader_Z_Distance - the distance between the Y rows (via padding)
Corner_Type - 2 types of corners (first one is interrupted and the second one is continuous)
Corner_Adjustment - manipulating the distance between the corner mullions+handles and the edge
Mullion_X_Distance - mullions+handles on X Evenly
Mullion_Z_Size - Height of the facade (Y size of the generator)
Bottom_Adjustment - adjusting the distance between the first Y row and the lowest point. (Generator's bottom padding)

Check the difference between "Corner_Type" 1 and 2 while changing the "Shaders_Rotation" and i believe that you'll get my point.

Please let me know if you need additional clarifications.

Best regards,
Kiril Alexandrov, RedVertex Team.

[Paul Roberts]

Hi,

Please take a look at the attached file. The confusion arises because of the way that RailClone deals with sliced corners. To ensure the mitres meet correctly, the segment must be moved toward's/away from the corner depending on its depth.

To alleviate this I have removed the need to have corner geometry at all by moving the shades to a separate generator. I've also changed the hinged brackets used in the evenly inputs so that they are independent from the shade geometry. In this way I can allow the shades to carry on uninterrupted around the corner. Changing the Corner type changes the bevel mode to allow you to turn this on or off.

I've also moved the shade geometry to the Y Evenly inputs to that the vertical spacing is no longer dependent on the padding.

I hope this helps, please let me know if you have any questions.

All the best,

Paul

[Dragan]

Hi Paul.
I don't consider myself a beginner but I have never used `SegmentY(x)Role` and as I can see from your Style it makes a quite impact at Translation position .
Just one active input for Selector so assumed the Output will be the same if I Remove/override Macro (Selector with Segment_Role).
I cant find some simplified example for this Expression Attribute so I will be grateful if you can put some light on this 
My apologies to Kiril for intrusion on the topic.
Best Regards
 

[REDVERTEX]

Hi Paul,

Thank you for your time and the perfect assistance!
I really did not thought about dividing the shaders from the support in different generator. Great approach!
As for the "SegmentY(x)Role", i was not aware of these functions as we were using 3.3 until January.
We had a major update and finally got to experience the new features, which are quite flexible.
Thank you!

I've tried to implement this approach for the start and end element, even tried it with SegmentXRole in YEvenly, but did not manage to make it work. Is there any limits that it wokrs only in the evenly segments?


Best regards,
Kiril Alexandrov

@Dragan, it divides the evenly array and you can control the different sections. (bottom, top, default, evenly SegmentYRole[X Evenly] and start, end, default , etc for the SegmentXRole[Y Evenly]). In simple words, in this example he is distributing XEvenly elements in the YEvenly Array. I hope this explains it for you.
You can open the macro and see the Expression.

[Paul Roberts]

Hi,

Glad we could help out. It's most useful in rows rather than columns, so to target the start and end you would use it in the Y Evenly input. Another important thing is that Y Evenly > Extend to Side should be disabled.



I've attached another version in case it helps out.

All the best,

Paul

[REDVERTEX]

Hi Paul,

It works just as it should be.
I've already launched the Style into use, but this will definitely be included in the update. After the optimization and visual arrange, this solution will simplify the structure for better understanding from the ordinary user.
I'm still a bit confused with the workflow for the Segment(Y/X)Role, but this will be smoothed out with the practice.

Thank you for the great support as always! 

Best regards,
Kiril Alexandrov, RedVertex Team

[Paul Roberts]

Glad it all works. I'll record a little tutorial about that macro at some point so as to make it clearer for everyone.

All the best.

Paul

[Dragan]

Tnx Paul,
eventually, I have got it when I take a closer look into it but it is always nice to watch any tutorial made by Itoo.
Best Regards