Recent Posts
1
RailClone Pro (*) / Re: Preserve Mapping size for random segment size
« Last post by Michal Karmazín on Today at 09:59:18 AM »Hi,
I highly recommend using tileable textures. With tileable textures, you can utilize the Apply Box Mapping feature along with the Random > Offset feature of the UVW XForm Operator to achieve the desired look.
The link you can add by using the url tag in the following way:
I hope this helps.
Best regards,
I highly recommend using tileable textures. With tileable textures, you can utilize the Apply Box Mapping feature along with the Random > Offset feature of the UVW XForm Operator to achieve the desired look.
The link you can add by using the url tag in the following way:
Code: [Select]
[url=https://forum.itoosoft.com/]text[/url]I hope this helps.
Best regards,
2
Tutorials / Re: Creating randomised books
« Last post by Michal Karmazín on Today at 09:20:14 AM »Hi Charly,
Since this tutorial was recorded, the behavior of the Transform operator has changed slightly. Initially, rotating using the fixed transform controls did not alter the size of the bounding box used to calculate adjacent segments. However, in recent versions, to match the behavior of the Segment node, the bounding box does change when using the fixed transform controls, causing the segments to be pushed apart.
To address this, instead of entering the angle in the Fixed Rotation settings, set identical values in both the minimum and maximum fields in the Random Transform section. Ensure that the "Transform affects size" option is disabled. This will rotate the objects without altering the bounding box size.
Please note that you may experience slight overlapping since the segments are rotating in their original positions. For greater accuracy, you can use expressions to calculate the exact position of adjacent segments based on the bounding box's width, height, and angle, along with some trigonometry. I've attached an example of this technique for your reference.
I hope this helps.
Best regards,
Since this tutorial was recorded, the behavior of the Transform operator has changed slightly. Initially, rotating using the fixed transform controls did not alter the size of the bounding box used to calculate adjacent segments. However, in recent versions, to match the behavior of the Segment node, the bounding box does change when using the fixed transform controls, causing the segments to be pushed apart.
To address this, instead of entering the angle in the Fixed Rotation settings, set identical values in both the minimum and maximum fields in the Random Transform section. Ensure that the "Transform affects size" option is disabled. This will rotate the objects without altering the bounding box size.
Please note that you may experience slight overlapping since the segments are rotating in their original positions. For greater accuracy, you can use expressions to calculate the exact position of adjacent segments based on the bounding box's width, height, and angle, along with some trigonometry. I've attached an example of this technique for your reference.
I hope this helps.
Best regards,
3
Forest Pro (*) / Re: Pinestraw
« Last post by Michal Karmazín on Today at 08:43:39 AM »Hi Bobby,
I'm sorry to hear you're facing these troubles. It might be that you're using the Forest Color map and currently, the Forest Color map is only partially supported by V-Ray GPU - using the Get Color from Map feature with Random values or As a texture on the Surface is not supported at the moment.
Thanks in advance for any further comments on this issue that you can share with us or our user community (in case some users encounter similar troubles).
Best regards,
I'm sorry to hear you're facing these troubles. It might be that you're using the Forest Color map and currently, the Forest Color map is only partially supported by V-Ray GPU - using the Get Color from Map feature with Random values or As a texture on the Surface is not supported at the moment.
Thanks in advance for any further comments on this issue that you can share with us or our user community (in case some users encounter similar troubles).
Best regards,
4
Forest Pro (*) / Re: ETA Forest Pro 9 Beta and 3ds Max 2025
« Last post by iToo on Today at 08:43:32 AM »Yes, we are very close.
We only need to make some adjustments to the Ivy samples, and prepare the Update Manager packages.
We only need to make some adjustments to the Ivy samples, and prepare the Update Manager packages.
5
RailClone Pro (*) / Preserve Mapping size for random segment size
« Last post by CharlyRT on Today at 02:03:48 AM »Hi
I want to create a stone wall with segments that has random sizes
The problem is that the mapping its being scaled with the segment size
How can I preserve the mapping size? just like its being preserved in Floor Generator for example
I attach the file and images from my ressult in RC and Floor Gen
maps are from this tutorial
https://www.itoosoft.com/tutorials/macros-mirror-variations-and-stepped-rotation?back=page%3D6%26sortby%3Dcreated%26tag%3Drailclone
question about the forum
how can I insert hyperlink in a word? I cannot figure it out 
I want to create a stone wall with segments that has random sizes
The problem is that the mapping its being scaled with the segment size
How can I preserve the mapping size? just like its being preserved in Floor Generator for example
I attach the file and images from my ressult in RC and Floor Gen
maps are from this tutorial
https://www.itoosoft.com/tutorials/macros-mirror-variations-and-stepped-rotation?back=page%3D6%26sortby%3Dcreated%26tag%3Drailclone
question about the forum
how can I insert hyperlink in a word? I cannot figure it out 6
Forest Pro (*) / Pinestraw
« Last post by Bobby Parker on May 20, 2024, 11:35:05 PM »My pine straw is rendering white. I have the texture, but it doesn't seem to be applying it. I have had this issue with other things, but stopping and starting a render fixes it. With the pine straw, that isn't the case. I am using V-Ray GPU.
7
Forest Pro (*) / Re: ETA Forest Pro 9 Beta and 3ds Max 2025
« Last post by Bobby Parker on May 20, 2024, 08:19:30 PM »Days have turned into a week. Are we getting close? Of course, it is better to wait for a working copy them to rush it.
8
Tutorials / Re: Creating randomised books
« Last post by CharlyRT on May 20, 2024, 06:37:18 PM »Hi I havent use RC in a while, so, I was following this tutorial and I cannot reproduce the leaning of the books, this is an old method and even with the updated files I cannot reproduce it, its strange coz the file its showing exactly the same as I have but my ressults are different, I have deleted the object in the file and when reproduce it exactly the "error" appears.
I could play with rotation angles but its not the same
The only "solution" was to use Padding and fixed rotation
It ssems that the old solution was practically perfect, I know things have changed, but I was wondering why the updated file seems ok but when reproducing its not the same ressult
Also Im not getting any random ressults with Nest option, using Random seed doesnt seem to work, what I have done is export custom seed from each
I could play with rotation angles but its not the same
The only "solution" was to use Padding and fixed rotation
It ssems that the old solution was practically perfect, I know things have changed, but I was wondering why the updated file seems ok but when reproducing its not the same ressult
Also Im not getting any random ressults with Nest option, using Random seed doesnt seem to work, what I have done is export custom seed from each
9
RailClone Pro (*) / Re: Vray IPR changes
« Last post by CharlyRT on May 20, 2024, 05:16:00 PM »Woah, havent thought that it was complicated to use it, thanks for the explanation Ill try to use what Michal said hope this could help a bit
10
RailClone Pro (*) / Re: Vray IPR changes
« Last post by iToo on May 20, 2024, 09:14:13 AM »This is a limitation with all interactive renders, including IPR:
RailClone generate and keeps on memory a complex set of data, including instances and custom meshes.
Usually data for viewport is different from render, due to the Display setttings.
But when using IPR, there are multiple render and display threads running simultaneously, requesting each one their own data. For this reason, we disable the viewport visualization.
The only solution for this, is to generate two separate data sets (one for viewport, and other for render). This is the way that Forest Pack works.
We tried same approach with RailClone, but it caused a lot of side effects, because code is more complex that Forest. Besides this technique have a significative performance hit (object must be rebuilt two times).
To make things even worse, there is not a standard defined in 3DS Max for interactive renders. Each render engine (V-Ray, Corona, etc.) use their own method, which force us to implement multiple workarounds in the code.
RailClone generate and keeps on memory a complex set of data, including instances and custom meshes.
Usually data for viewport is different from render, due to the Display setttings.
But when using IPR, there are multiple render and display threads running simultaneously, requesting each one their own data. For this reason, we disable the viewport visualization.
The only solution for this, is to generate two separate data sets (one for viewport, and other for render). This is the way that Forest Pack works.
We tried same approach with RailClone, but it caused a lot of side effects, because code is more complex that Forest. Besides this technique have a significative performance hit (object must be rebuilt two times).
To make things even worse, there is not a standard defined in 3DS Max for interactive renders. Each render engine (V-Ray, Corona, etc.) use their own method, which force us to implement multiple workarounds in the code.
