Hi,
I'm doing some tests with your scene, but got some strange results both using Forest and RailClone.
Could i ask why each model have an Edit Poly modifier applied ? Had you some problem using the alembic objects ?
I noticed most of models have a 'armature' object as parent. I'm not sure what is their purpose, but unlinking them seems to solve some problems.
Anyway, to use them with RailClone are required some changes:
- Since each model must be distributed along the spline without deforming, you should enable Segment->Deform->'Force Instance'.
If not RailClone will try to bend the object along the spline, slice it, etc. That requires much more effort to compute, and may cause artifacts with these models.
- I suggest to unlink the 'armature' objects, if they are not really needed.
Also you would convert all RC objects to standalone items using
RailClone Tools, checking the 'Force Instances' option (in RailClone Tools).
That will have the same effect than setting it at Segment->Deform, and let you to make a render test with the alembic models natively.
Alternatively you would use Forest Pack instead RailClone for this scene (using the 'Path' distribution mode). It has some advantages:
- Forest can instance the alembic objects at render. Instead, RailClone convert everything to a mesh, which requires more effort.
- Forest handles animated models more efficiently. For this scene, i suggest to use Animation->'Follow Geometry', disabled on Viewport.
- You could use ForestSet to collect all models, and assign them to Forest in a single step. This is quicker than randomizing all segments in the RailClone editor.
Topic: Bug railclone objects jump from point to point (Read 3286 times)
