Itoo Software Forum

Author Topic: Modifier on Railclone  (Read 282 times)

krostiv

  • Newbie
  • *
  • Posts: 2
Modifier on Railclone
« on: July 15, 2018, 09:25:56 PM »
hi,
i am a newbie. Is it recommendable to use modifier i.e Capholes, uvmap in the modifier stack over railclone? Is there disadvantages?

greets krostiv

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1407
    • iToo
Re: Modifier on Railclone
« Reply #1 on: July 16, 2018, 08:36:47 AM »
I took following info from documentation Feel free to browse around to learn more about RailClone.

Quote
RailClone is able to create complex parametric structures by cloning and adapting mesh objects (called Segments) along one or more reference objects (such as spline). According to the spline's direction, elevation or other parameters, some Segments must be deformed and other simply cloned.

In the supported engines, it's possible to render thousands of instances of the same object using minimal resources. RailClone uses this feature, identifying which Segments may be cloned, and creating native render instances of them. This process is automatic and invisible to the user, but you can optimize your renderings by paying attention to the following rules:

    If you are certain that a type of Segment should never be deformed (such as pillars or joints), turn off 'Bend' in the Segments parameters. The same is applicable for 'Slice'.
    It is possible to use meshes or proxies as Segments, but it is not necessary to convert high-poly objects to proxies to get better performance. The plugin converts all objects to native render instances internally, so there are no significant differences (on render time and memory used) between using meshes or proxies.
    Proxies cannot be deformed, so RailClone always creates instances from them, but obviously they cannot be bent or sliced.

Some features are not available when using the native render mode:

    Vertex welding is disabled.
    Operator->Material and Segment->Deform->Mapping work only with V-Ray.
    RailClone objects cannot have any modifier applied.

You can switch to the standard render mode turning by off Display->Render->Use Instancing Engine. When this is used the plugin creates a single mesh containing all the geometry.

In any case, you can use RailClone Tools to generate the instanced geometry manually. This procedure is compatible with all render engines.
Rokas
iToo Software

krostiv

  • Newbie
  • *
  • Posts: 2
Re: Modifier on Railclone
« Reply #2 on: July 16, 2018, 11:00:20 AM »
hi,
ok generally I understand. But what happens if I do it anyway? Changed railclone to single mesh?
I tested a bit. And for the filesize it doesnt matter if I use modifier over railclone or not?

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1407
    • iToo
Re: Modifier on Railclone
« Reply #3 on: July 16, 2018, 01:01:35 PM »
If instancing is braked all geometry is treated as single mesh in rendertime. If Your RailClone has many millions of polygons- You would need a lot of ram.
If instancing is fully working You can render with a lot less RAM for that style.
Rokas
iToo Software