I was wondering if anybody had the change to play with it? the price tag on that thing is insane… but the car images look like photos, not photoreal actual photo…anyway anybody try it? / care to comment on it?
VRED Professional node locked: 25.000 €
Tried it. And don’t like it. Vray rt + 3dsmax = works better for me 
Also - why it cost so much…
Thats what i thought, too.
I always thought this 3D market was kind of small and now so many companys are developing those iterative renderers.
And those prices don’t make much sense,
looks like they think there is no competition to their product.
I am pretty sure they won’t sell many licenses at even a tenth of those prices.
In fact, as far as i remember, there is only one other software able to directly raytrace nurbs (VRed seems to do render-time tessellation), and that’s real3D from realsoft.
So no, they don’t have much competition in that department.
Given how laborious, and fail-prone the nurbs conversion and editing is, it’s not such a huge price tag.
Compare it to having a few clever people hired for the purpose of properly converting cad data into correct, renderable geometry, and you’ll see it’s not that far fetched.
Particularly for cars and product design, a bad normal can wreck havoc in the scene, so if that product does it all in one go (which it promises to do, i have no direct experience), i can see a few considering it as an option.
I dont know their tesselator, but these days there are pretty advanced tesselators out there. And i am afraid you’d still need the clever ppl to handle the “not working for whatever reason” files…and with data from different sources you will hit them…all tesselators/convertors/importers i know do so at least hehe. Given it is targeting CAD ppl the price tag is not that steep tho…there seems to be an unwritten law that any tool that has “CAD” somewhere in the featurelist should be 5x more expensive then tools without 
Regards,
Thorsten
Eheh, i do remember meeting a few of those clever ones over at Macke XD
That’s the thing with this software, though, it seems to be the holy grail of nurbs rendering.
I’d sure be pi**ed off if i bought one and then ran into issues when bringing in a model…
As surely this has a lot less flexibility to fix stuff than max with a Dieter, for instance
Lol indeed. The main issue with supporting many cad formats is that they are rapidly evolving (just take catia with it’s v5R18SPblah scheme) and it’s tough for 3rd party devs to keep up with that. So depending on the version-freeze duration of your client this CAN pose issues hehehe
Regards,
Thorsten
Awww, dear, i hurt already.
im confused, how is this different from mental ray tessellating with approximation?
also, render man does true nurbs.
You can also get very high quality nurbs models into max with power nurbs.
But i haven’t tried to render them with VrayRT, i don’t know if thats supported.
I sometimes work with the Power NURBs folks at nPower. Their stuff renders beautifully in RT. Of course, it is with tesselation, and theirs is pretty nice…
-Alan
Lele - there’s a timelapse video in ‘support’ section where they show what has to be done before rendering. It looks like there are normal facing problems etc…
Eh, as usual with nurbs.
The normal once nurbs get tessellated depends on the curve/surface direction.
I have used powernurbs a couple of times before for yacth design work, and have to say i loathe the thing.
Sure it works, but boy the workflow is annoying, and the bugs used to be many.
Very sorry to hear that it was so painful for you, Lele. Perhaps if you get a moment, you might tell me specifically what your problems with the workflow are, and I’ll get those to the developers right away.
Thanks,
-Alan
Don’t worry, Alan: I’m sure it was a case of pressure, coupled with my own ignorance.
They sure know NURBS better than i ever will, so i am confident they have the right approach, unlike me.
In any case most of the time i end up exporting polys from Rhino.
The pN jobs were a one(two? :P)-off.
I’m just curious LeLe…
Our workflow is Rhino to Max for rendering. Designers here use ProE and Rhino, then we use Max for rendering.
I’m curious to know your workflow. We use nPower, but I’m only semi-happy with it. It seems my viewport is much faster, and easier to understand when I have nurbs data through nPower though. The mesh is often just terrible and can be very time consuming when dealing with thousands of differently shaped objects from Rhino to Max. nPower seemed to save quite a bit of time importing for us.
Here I import the whole model into Max, then Xref that file into my scene. This keeps my file Way smaller so saves are faster and more often. I don’t really change that data much other than color and it’s easy enough to open the Xref and change tessellation if I need (which is often needed more than I would like).