I’m currently working on a scattering plug-in for in-house use, based on the VrayInstancer code in the SDK samples (think poor man’s Forest Pack). Everything is working surprisingly well. My only question is if there is some way to inhibit the logging of the following messages: [2015/Apr/26|18:17:…

Unfortunately there is no flag to prevent that message right now; I will see what can be done about it. Actually I do have a version of the instancer that generates the instances using multithreading - I can post it here if you are interested. Best regards, Vlado

Interested would be an understatement. Thanks a lot!

So I added an experimental multithreaded option to the instancer in the latest builds; I had to make some modifications to V-Ray itself as well in order to get it working. I also took the opportunity to disable the logging of these messages for each instance. If you don’t have access to the nightly…

Thank you for that excellent, well-commented code. I copied your multi-threading method, and so far it seems to be purring like a cat! On a particular scene with 500k instances, setup time went from 34.4s to 5.3s. This is on a machine with 6 cores + HT, so I’d say that it scales quite well. You …

Well, I haven’t tested it will all possible geometry types - only with regular meshes and proxies. There might be some code in other geometry types (displacement, hair) that might not be thread-safe; I will have to go through them all and check. Best regards, Vlado

Yup, makes sense. So far displacement works fine for me, haven’t tested other types of objects. I have a question regarding a related matter. Let’s suppose I would like my instanced objects to inherit UVW channel data from the surface they are scattered on. I understand that since they all referen…

The data member is internal to the class and you shouldn’t change it. I very hacky way would be to store the UVW’s into the “name” member f.e. make name[0] to make sure it’s still a valid string and then add the UVWs as binary data right after that. Then you can read that from your shader. For the …

That’s quite a hack, but it seems to work very well. I also had to add a magic header to the data so the texture map could determine if the VRenderInstance is loaded with my custom data or not. I haven’t tried your suggestion regarding multithreading yet, I will update when I do. Thanks for your s…

VrayInstancer over-logging

V-Ray for 3ds Max V-Ray for 3ds Max :: SDK

RotemS May 12, 2015, 1:43pm 9

In regard to multi-threading, it does seem to create issues when I enable random animation offset for the instances (sampling them at more than one time per frame). Without it, it seems to be working fine.

3.5 beta 2 unhandled exception preparing objects

Topic		Replies	Views
Vray instancer very slow with lots of particle V-Ray for 3ds Max :: Issues	2	249	September 22, 2015
SDK for 3dsMax: VRenderInstance best practices? V-Ray for 3ds Max :: SDK	52	2141	November 6, 2019
V-Ray 3.10.01 available for download V-Ray for 3ds Max :: Announcements	56	4503	March 2, 2015
Duplicate-->Instance meshes are rendered really slowly V-Ray for Maya :: Issues	4	187	December 10, 2014
Instanciate problem V-Ray for 3ds Max :: General	7	276	May 30, 2003

VrayInstancer over-logging

Related topics