If tex is not None and tex.GetMappingChannel() != 1: # change all exture channels supported to 1 # supported map channels to change the mapping type of Here is the new script, as an addition to the old one: import System I guess all these assumptions are valid, but in case they are not, you can alter the code as you please Also I change the mapping channel to a hardcoded 1. I decided not to upgrade the material, since it is assigned to the axes lines, for which V-Ray doesn’t really care.Īssuming all materials are standard custom materials (not PBR materials), then we have only 4 textures to check. (as said ArchiCAD export is far from perfect). The last material: Verf - grijs antraciet is not part of the Rhino rendering material table, but part from the Rhino legacy regular material table. The V-Ray scene transaction is necessary to speed up the process, if you don’t care, remove the line. I guess you want this, if you don’t just remove the line

(m, vrayMtlId, True)Īs you can see, first we merge all materials with the same name, because they seem identical.

('_RenderMergeIdenticalMaterials _SameNameOnly=_Yes _Enter', True)įor m in : Here is the code that you need to run: import System dwg export was a terrible back in the days, and I don’t see much changed for 22 years.

If that is what you mean by “redundant materials”įirst, just to share a personal opinion. The converted material is already assigned to whatever the previous was, while the previous is automatically removed by Rhino.once the material is converted one way or another, Rhino will change the assignment automatically.Mind that this modifies the RhinoDoc.RenderMaterials collection Also that command requires selection, which is pretty unpleasant to script. Instead of vrayMtlFromRhino you can use () The API call does more or less the same thing as the command, but avoids the overhead of the V-Ray plugin messing with the material table. In general you shall not use a command for something that is available in the API.

Vray for archicad 24