I’ve gone through the boards here and over at iToo’s forum.
Can someone clarify what the status is on getting instancing to work with iToo’s plugins?
On their boards they say you guys have been in contact, but the ball is currently on the Corona Devs’ court. Here on the Corona forum it seems like you think the ball is on the iToo’s court?
It’s a big time waster not being able to use the instancing mode on RC and FP. Lots of extra tweaks has to be done to get the plugins and presets to work as they as they do with vray.
I don’t know if it’s related, but I’m also experiencing very large slow downs on render starts in scenes with heavy FP and RC items. “transforming vertices” “parsing scene” takes ages, but once the rendering starts, all is pretty fast.
Should have rephrased topic to Railclone only. Forgot edge mode in Forestpack has been working for some time
Railclone seems to still have limits when working in Corona (vs vray). Especially with randomization. It simply doesn’t work.
It’s nice now with the new Corona multimap and the UVW randomizer as I can now do a work around, but it still doesn’t work when enabling instancing in Railclone.
Since randomizing won’t work when enabling instancing, I had a feeling that it had a big impact on why my renders were taking so long to start in “heavy” Railclone scenes.
Just made a quick test to see if the instancing had an effect. (only with a small sample of RC object isolated, but clearly there it is causing extra parsing time). See attached.
In my full scene and at only 1800px (test render) I’m waiting over 1min for it to parse. It’s not really a problem for the final render that takes much longer anyway, but for test renders it’s a huge pain.
ForestPack: Try to avoid using object exclude areas with high resolution and also if you are using spline exclude/include areas keep those splines with smallest vertex count as possible(use normalize spline modifier for example)…then you will see speed up in transforming vertices pass.
Sadly this isn’t something I can apply to my scene as it my exclude splines are indeed very simple (4-10vertices). I’m still pretty sure it’s the missing support of “instancing”. Very noticeably in this case as I’m doing large building facades with custom tiles and wood cladding.
We have faced the same issues here. Recently we had a really huge scene to render and in this scene the randomization feature of RC was essential. Unfortunately it was impossible to render the scene with the instancing turned off, because of the memory consumption (it tk the whole available memory (64GB) and then crashed.
The only workaround was to use the Railclone Tools and instanciate the whole RC object before rendering.
Instancing on - works as expected, parsing is faster, there is an issue with randomizing.
Instancing off- works as expected
Randomizing does not work when instancing is enabled - using Corona Multi Map
Jens, could you contact us about this at support@corona-renderer.com with a very simple scene demonstrating this? It could be even a scene like in your screenshots, with some boxes scattered around.
If there are some other issues with Railclone or other iToo plugins, please also report them at support@, but one issue per one separate email please.
It’s a general problem that Corona doesn’t seem to recognize the way RC “manipulates” the instances with it’s “Instancing engine”. Neither random mat IDs or UVW offsets nodes work. Corona only sees the scattered object as the exact same instance, hence no randomization will occur. So the new Corona UVW randomizer doesn’t work either. - Unless we turn the instancing engine off, but that comes with the drawbacks listed above.
Hi guys.
Is there any chance this might be resolved in the nearest future?
I tested RailClone recently mainly with an intention to use it to create more complicated floor tiling patterns, but without Corona understanding how RC assigns IDs to its objects it doesn’t make sense to invest in it.
Thanks,
Michal
The main issue here - “When instancing is enabled in Railclone, randomizing cannot be used, for example using Corona Multi Map” - is fixed, and this should also fix some further related issues.
The fix will be included in the upcoming V6 and its daily builds.
