As many of you may have heard ASGVIS, LLC is working together with the Chaos Group on a product called Rhino2Vray. Soon we will be anouncing details about those exporters and other products. What we are in need of right now is about five licensed V-Ray for 3ds Max and also Rhino users for development purposes. Please provide information at our website Chaos: Industry-leading design and visualization software .
Requirements:
Registered Vray User
Registered Rhino User
Dxdiag
Best samples of your vray rendered images (2Mb max)
Although the beta has a lot of really nice additions its still a beta and is bound to have atleast a few bugs. ASGVis’s aim here is probably to do some local bug testing before they decide to sell to the public. In that situation it would be best to keep RhinoToVRay seperate from the beta version of Rhino v4 seeing as Rhino v3 is going to be more stable.
For all Rhino users, I’d really recommend Rhino2Max from nPower Software. The new version fixes many of the drawbacks from the previous version (Importing layer names, etc.), plus you get all the nice stuff supported in Max.
We’ve used it a couple years now and it’s a dead simple workflow now.
I believe the latest version supports the Rhino 4 Beta.
Well I got nPower PowerNURBS 1.1 . . . Rhino 4 wip/beta files are not supported. Convert to Rh3 - and import is impossibly slow (never got it finished)
P.S. PowerNURBS - it’s all they have for Rhino and Max.
What’s amazing is that if you import your model in .iges/.igs format into Maya you’ll have no problems at all.
In max you get ugly seams and the normals on some surfaces are reversed for unknown reasons. I do admit that .3ds export from rhino is messed up, you get seems in no matter what program you export too - that means there must be something wrong within either the format or the way rhino writes its .3ds files.
I honestly don’t know why the guys at Autodesk never seem to put the time in to fix the problem with .iges import in to Max. Max is severely lacking in the NURBS department, they should at least make it so that people can import NURBS from other packages.
I am curious as to how this RhinoToVray connection is going to work. Are you guys connecting directly to a standalone VRay from within Maya, or are you exporting model data to max for setup and rendering?
Normals - just try Dir command inside the Rhino to see the direction of normals.
By default u can’t easily know the direction of normals (u need to use Dir all the time - abs. uncomfortable )… so use AdvancedDisplay command and click ColorBackfaces. From now you’ll see flipped normals colored in Red
When you’re ready to fix flipped normals just type Flip on every flipped surf!
BTW - I wish there’ll be connector to Alias StudioTools
Power NURBS contains all of the functionality of Power Solids 2.0 and Power Translators 2.0. The following chart shows the differences between PS and PT 2.0.
Actually you don’t even need PowerTranslators either. You can just use Power Rhino to Max and save about $200.00. PT is $495 and RtoM is $295.00. Visit the nPower store to see how the packages are broken up.
On a different note, I really like the idea of having V-Ray for Rhino but the problem I would have with it is instances. Not having instances would kill me in Rhino if that was were I did my final renderings.
