Itoo Software Forum

Author Topic: variable size, but equal chamfer  (Read 2768 times)

Rokas

  • Hero Member
  • *****
  • Posts: 3324
variable size, but equal chamfer
« on: August 30, 2014, 12:51:11 PM »
Hi,

how can we create a style with variable size sgments, but equal chamfer`s ?


I can create a segment with RailClone and randomize segment size the way i want, and then feed it to master RC, but this way segments random values are randomized once, and repeated in master RC.
Rokas

Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2991
Re: variable size, but equal chamfer
« Reply #1 on: August 30, 2014, 05:34:05 PM »
Hi Rokas,

Are you able to split your tile so that the end chamfers are separate segments and then piece them back together using a compose operator, scaling only the mid section:



Alternatively if you want to use a RailClone object as a segment and maintain randomisation, turning on the Nest option from the Segment's properties should do the trick.



Cheers,

Paul
Paul Roberts
iToo Software

Rokas

  • Hero Member
  • *****
  • Posts: 3324
Re: variable size, but equal chamfer
« Reply #2 on: August 30, 2014, 08:29:21 PM »
Thank You Paul for taking interest in this problem.
I attach a max file, so we could be on the same page...

Your first suggestion is interesting- I almost managed to make what I have in mind, except chamfer on Y axis- as I scale segment in Y direction- chamfer scales as well.

Your second suggestion- which I would prefer, doesn't work for me- please see attached file and tell my what am i doing wrong?
Rokas

Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2991
Re: variable size, but equal chamfer
« Reply #3 on: August 31, 2014, 10:49:12 AM »
Hi Rokas,

Thanks for sending the style. It looks as though there is a fixed random seed value in a Randomise operator. The Nest option changes the global random seed of the RailClone object (found in the general rollout) to create the variations so this explains why it isn't working. I sometimes find adjusting the global seed is a useful test when nesting files, if adjusting this value doesn't change the style then it won't change when nested either.



If I turn off the seed override option in the Random operator the style appears to work as intended.



Hope that helps,

Cheers,

Paul.
« Last Edit: August 31, 2014, 10:50:57 AM by Paul Roberts »
Paul Roberts
iToo Software

Rokas

  • Hero Member
  • *****
  • Posts: 3324
Re: variable size, but equal chamfer
« Reply #4 on: August 31, 2014, 12:32:20 PM »
OMG, thank You a lot,- that is huge revelation for me...
Rokas

TL1895

  • Sr. Member
  • ****
  • Posts: 396
Re: variable size, but equal chamfer
« Reply #5 on: September 08, 2014, 06:14:59 PM »
Hello.  Interesting topic, and I have a question about this, too.
In attached picture, how would I fix the area in red, please?

Thanks a lot!
TL1895

Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2991
Re: variable size, but equal chamfer
« Reply #6 on: September 08, 2014, 06:55:04 PM »
Hi,

Rokas' file isn't producing random lengths from an infinite range, but is instead picking from up to 10 possible tile lengths. and in this example it just so happens that the random selection has produced some repetition, but changing the seed value from the General rollout will yield different results. In fact I couldn't actually repeat that screen grab :)



Many thanks,

Paul.
Paul Roberts
iToo Software

TL1895

  • Sr. Member
  • ****
  • Posts: 396
Re: variable size, but equal chamfer
« Reply #7 on: September 08, 2014, 07:01:41 PM »
Hi,

Rokas' file isn't producing random lengths from an infinite range, but is instead picking from up to 10 possible tile lengths. and in this example it just so happens that the random selection has produced some repetition, but changing the seed value from the General rollout will yield different results. In fact I couldn't actually repeat that screen grab :)



Many thanks,

Paul.

Hi Paul,

Okay, thank you for the explanation :)

Yuriy Bochkaryov

  • Jr. Member
  • **
  • Posts: 62
  • CG Artist
    • https://ybochkaryov.com
Re: variable size, but equal chamfer
« Reply #8 on: August 10, 2016, 05:03:45 PM »
Hi,
Thanks for cool example. Very usefull feature!
I'm trying to add some changes and have issue with material IDs. The problem is - railclone generates ID for each segment, and does not behave 1 stone as single object. As result - 1 stone could have 3 different IDs.
I guess same thing with UVW Xform.
Is it possible to fix it, maybe add some additinal math functions?
Thanks.
Mail:     info@ybochkaryov.com
Skype:  Hunter-3d
https://ybochkaryov.com
https://www.instagram.com/yuriy_bochkaryov/

Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2991
Re: variable size, but equal chamfer
« Reply #9 on: August 10, 2016, 05:25:19 PM »
Hi!

Thanks for the question.

You are correct that the material operator randomises the IDs for segments if if they're inside a compose operator. However, there is a workaround. Export the From and To parameters and wire them both to a Random Number node set to Segment. This node will only create one new random value per compose operator and the colours will all be the same!



I've attached a sample file. I hope that helps but please let me know if you have any further questions.

Many thanks!

Paul.
Paul Roberts
iToo Software

Yuriy Bochkaryov

  • Jr. Member
  • **
  • Posts: 62
  • CG Artist
    • https://ybochkaryov.com
Re: variable size, but equal chamfer
« Reply #10 on: August 10, 2016, 07:48:58 PM »
Hi Paul.
Thanks for quick answer.
Could you please help to deal with random UVW Xform. I tried assign it and it's not working for compose objects.
Thanks.
Mail:     info@ybochkaryov.com
Skype:  Hunter-3d
https://ybochkaryov.com
https://www.instagram.com/yuriy_bochkaryov/

Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2991
Re: variable size, but equal chamfer
« Reply #11 on: August 11, 2016, 11:35:02 AM »
Hi,

You can randomise UVWs in the same way. Just export the U and V fixed properties and wire them to random nodes set to segment.



This should apply the same values to all segments in the compose operator.

Cheers!

Paul
Paul Roberts
iToo Software