hello! plan to support railclone? at the moment it is not working properly((
can you be more specific? Maybe post some images of what went wrong
what texture are you using to randomize in the first case?
The second case is a known resolved bug in railclone - it is fixed in their latest beta
ok, in that case, could you send me the scene? http://corona-renderer.com/upload
no problem,sent
book_bug.rar
Hi Pererostka,
did you try to turn off “use instancing engine / use geometry shader”? I think it could fix your book problem.
Hi all, from the looks of that it looks exactly like the problem i’ve run into sometime ago http://forum.itoosoft.com/ System units and Global Illumination
Still no solution to it - Itoo guys probably cannot fix it without Ondra’s support as from what I understood it needs some different type of material id channel (not sure what it is called exactly) which vray got (as this feature works with it) and Corona currently do not.
One thing is strange about your case Pererostka - after my post on Itoo’s forum they’ve added automatic instancing disabling and the warning about it -
quote: "In RC 2.4.0b, instancing is disabled automatically when using an unsupported feature (in this case Material in Corona), but this is not intentional.
It should work keeping the behaviour of previous releases: segments are instanced although Material is not applied. We’ll change that for the next build." end of quote.
- which made my life a little less miserable, and more predictable so it should disable instancing and show such warning to you too unless you’re using some pre 2.4b version.
Still, Corona surely needs that mat id function (probably vray is using it’s Effect ID for that but I’m not sure) as it will not only allow for better railclone support but probably for ForestPack’s Edge mode support too.
to Ondra - if you’re wondering why I still didn’t make a request about that if I want it so much, well first thing I’m not totally sure it is that function exactly and second - I’m quite chaotic myself but my attention/memory/workload are mostly even more chaotic so I’ve found some workarounds and just forgot about that until romullus poked me about it via pm
I talked to Itoo and they will be adding option for us to support this in their next release
Excellent!
moving - reason: old,
revive if needed
Hello, is this feature working in corona now??
I am trying to do a floor tile but I don’t get the material variation, I tried Max multi sub object and also Corona Multimap.
Thanks
Nice to see it’s finally works! Time to upgrade RailClone Lite.
just tried it does not work here either 
Yes, sorry for the confusion. The limitation is that instancing engine must be turned off, although sometimes it may appear that all is fine. Here are some parts of my conversation with iToo support:
I can confirm, that the Corona Multi Texmap should be working with the latest RailClone release without any troubles with the limitation mentioned below (the Use Instancing Engine should be switched-off). Attaching a quick test image.
As mentioned in one of replies in that thread and as you can double check on following Feature Compatibility table, to get the Material Operator working with Corona Renderer, it needs to be enabled by turning off the instancing engine.
Please feel free to check more detailed information about this topic and examples in the “4 - How to Control Material IDs” chapter of our “Next Steps with RailClone” guide. Also, you might find useful following How-To: Using Bercon Gradient and MultTexture article as the way how Corona Multi Texmap can be used is very similar - in the Material ID mode.
Let me add, that the RailClone object doesn’t automatically inherit any of materials used by its Segments and the user is responsible of creating a material and applying it to the Railclone object. If there are different materials applied to the source geometry, user needs to create its own multi-sub material, assigning a different material ID to each element and applying it to the whole RailClone object.
“.. it works fine with “use instancing engine” on …”
In some specific cases it may look so, because of adapting Segments to RC conditions it might result to unique parts and no instancing is used. Feel free to disable Deform - Bend & Slice options for your Segment(s), which will lead to better instancing and you’ll notice that’s not fully compatible with the Use Instancing Engine mode.
As mentioned previously, the Use Instancing Engine option should be switched-off.
Links mentioned in these messages:
http://docs.itoosoft.com/display/RAILCLONE/Requirements
http://docs.itoosoft.com/display/RAILCLONE/Display+Settings#DisplaySettings-Toenable/disabletheInstancingEngine
http://docs.itoosoft.com/display/RAILCLONE/4+-+How+to+Control+Matrial+IDs
http://docs.itoosoft.com/display/RAILCLONE/Next+Steps+with+RailClone
http://docs.itoosoft.com/display/RAILCLONE/Using+Bercon+Gradient+and+MultTexture
btw their support is really great so if you have trouble achieving something, I am sure they will help
I don’t get what’s fixed then, because with instancing engine turned off, material randomisation worked in RC Lite 2.4.x too. Having to turn off instancing engine, makes whole thing pretty much useless. I would like to know if it’s possible in the future to have full feature set support for Corona as like Vray does?
I know this topic is old, but I’ve just had the same problem and found a fix for it should people still have the same issue.
For me, turning off the instancing engine did not work, and to be honest I’d rather not turn it off since the scene I’m working on is huge. So instead, I added a MaterialByElement modifier on top of the railclone, set the random distribution to a high number and voila, it works!
Adding the modifier does prevent the point cloud display from working though, but that’s a small sacrifice since displaying as boxes work just fine.
Hope this helps.