![]() when copying a Vray material from one file to another we have experienced everything from files crushing, to materials not importing correctly, to materials becoming Rhino materials, to renaming of imported materials as (imported1, imported2,…) making and endless list of same materials. Vray assets importing: There seem to be several bugs related to importing of the Vray assets such as materials and lights. Sometimes the assets will also not render the same. Once the files is exported it is also impossible to change any of its settings. However this requires us to have a vray for 3ds max license, open each file separately and export it out for Rhino to understand it. We are sometimes exporting 3ds max assets as a vrayscene objects to use them in Rhino. ![]() This makes it difficult to achieve the same level of the final output. Using those assets in Rhino is not very well addressed, needs a ton of manual setup and adjustments. Interoperability: Vray community has build high-quality collections of materials and models for its most used software 3ds max and Maya. ![]() Most issues probably originate with the Vray developers, however I think both software should do a step further in making it work. I know similar is true for many other offices. ![]() This often forces us into a workflow where the Rhino model has to be exported and then rendered in another software which is both time-consuming and costly. Unfortunately, we are disappointed that the rendering, material/texture handling and in particular Vray plugin are still far from what 3ds max version offers. We are an architecture office that uses Rhino in its everyday workflow more and more and finds the program very useful. I thought of starting a new thread where several bugs we have been experiencing with Vray for Rhino plugin will be pointed out in a hope that they will be resolved at some point in the future. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |