Phantom Scatter introduction
I am the creator of Phantom Scatter, a standalone app that is designed around generating matrices used for the instancing of objects: https://scatter.phantomtechnology.nl/
The most effective use-cases are generating things like grass/forests. By keeping the instances out of your working model, it stays snappy and pleasant to work in. The scatter instances are only used in the final render, in the current case that is Octane Standalone.
Workflow looks like this:
Bringing support to LuxCoreRender
Now I'd like to bring support to LuxCoreRender.
I read that it is possible here: https://luxcorerender.org/advanced-features/
Let's imagine we want to instance around grass pieces for an exterior scene, which is a totally common use-case. I don't see instancing in the SDL page (https://wiki.luxcorerender.org/LuxCore_ ... erogeneous)Instances
When working on huge projects with multiple copies of the same object, LuxCoreRender’s support for instances will significantly save system resources, in particular memory consumption. If the same mesh is referenced by multiple objects, for example in the case of particles, it is only loaded into memory once.
A number of 100,000 grass pieces is easily reached. Am I understanding it correctly that I should now call a grass object 100,000 times inside the *.SCN file? I am hoping that if it's not yet supported, a feature can be developed where an object can reference a *.CSV file and then use those instance matrices, in the exact same format as is now requested by the scene.objects.<object name>.transformation call
Why instancing is of essential importance
Instancing tons and tons of objects makes renders truely come alive, making everything a bit different, varied, making it feel natural. Nothing in the real world is perfect, everything is a mess. By trying to create a mess in your renders, I believe it really enhances the quality and believability.
Scene in Blender:
Scene in Octane standalone + scattering:
Any thoughts?