simplychen

some extra steps in there, but I commented out what each line does for you Hope this helps. ( r = maxOps.GetCurRenderElementMgr() -- get current render element r.AddRenderElement (VRayExtraTex elementname:"VRayDirt") -- add vray extra text and name it VRayDirt elementCount = r.NumRenderElements() -- count how many render elements there are k = r.GetRenderElement (elementCount-1) -- set k as the last element created (VRayExtraTex) k.texture = VRayDirt() -- add VRayDirt to texture ) After adding the texture, you can probably set a specific setting for it, but that was not part of the question, but it should be script-able.

are you collapsing the mesh down WIHLE the meshsmooth/turbosmooth display is on as isoline? if that's the case, you'll want to make sure it is only turned on (in case if you want to keep the mesh/turbosmooth modifier) once you have attached the meshes OR make sure you tick off 'display as isoline' option before collapsing. Otherwise, your mesh will get pretty jacked and basically break the mesh. Not sure if this is what's happening, but since you mentioned that you are new to max, this could easily happen without knowing it beforehand. image below to illustrate: [ATTACH=CONFIG]45584[/ATTACH]

can try rendering out the reflection in another pass along with a matte for the curtain wall. and comp the reflection in during post work. it will save you time if you turn everything besides the glass to invisible to camera (but you need to leave them visible in reflection/refraction) to speed up rendering

for every proxies you create, max will need to allocate memories for them. there are mainly two types of 'memory' dedicated just for proxies in Vray (system tab). they are 'dynamic' and 'static'. dynamic uses resources during render time meaning that they don't have a designated memory size for them. static, however, uses the amount of memories you tell it to (right above the pull down for type of memory). when i use onyx, i set it as static and approximate how many trees i have and times that number by the file size for each vray meshes. what that will do is give you a number of how much you will need to give it to vray/max to hold those proxies. try switching to static and set your memory size according to amount of proxies in your scene. so vray can pull it out of it instead of competing with other resources at play. if the log tells you the memory is too low at that point, try upping the memory sizes. as always...i could be wrong

vrlserver.exe only appears in your processes after you launched the floating license. 1. if you have a work machine, what you can try to do is to have your dongle on your local machine and have the four nodes ping to your workstation. 2. on the other hand, if you have a server holding the license, you need to make sure to have vrlserver.exe activated when windows boot up so the other comps can ping to it. you can do that by setting the vrlserver.exe as a service (...\Programs\Chaos Group\V-Ray\Licensing\Administration\Register License Server) 3. on render nodes, go to the above directory and select 'Change V-Ray client license settings' in this field, add in the IP address of the one computer withholding the dongle. (start > run > type in 'cmd' > then 'ipconfig' to figure out the ip address) 4. once you have done that, make sure the one holding the dongle/floating license have firewall turned off for vrlserver.exe to allow render nodes have direct access to the dongle file. 5. in any case, make sure you have spawners open (can also register as a service) so you can use DR