I've not noticed much dev time being pushed into the RW module in recent years. Maybe there's a reason they gave it away to everyone a few years ago. If RW could utilise the GPU then that would be a good step forward. I've a file that takes 25 minutes/frame on CPU, but 45 second/frame on GPU. RW rendering is a CPU process at the moment, so when I put Vray through a twin GPU they're both in a different class.
I stayed with what I was accustomed to at the time but I've not seen anything making me want to give RW a second go. That being said, I have seen some people's RW renders and they look very good. There's an awful lot that these packages offer that RW does not. I think it would take an amazing engineering feat, or a ground up rewrite to get RW to compete with these other packages. Occasionally I'll have an openGL viewport here and there, but generally I'll render in 3DS+Vray. I got an upgrade to Designer w/Renderworks, and played with RW only a couple of times, but abandoned it pretty quickly. I must admit, I began visualising in 3DS and Vray, when I only had a fundamentals licence. Swift action is required from Vectorworks to help Vectorworks-based companies, and the Vectorworks package itself, to stay competitive.įollowing is a link from August last year, and I wonder if anyone can provide some update on conversations with Chaosgroup? Or if the engineering department has made progresses and inroads for integration with other rendering packages? When can VW get direct Synchronisation with TwinMotion? Would Vectorworks get integration with ENScape? How quickly can all this happen? Our industry is quickly evolving, and as operators, we don't have time to wait for Vectorworks to take years to implement integrations (when others have working integrations already). In conclusion, if I was to apply the conversation about being 'left behind by the industry' based on speed and quality of visualisations, Vectorworks (and to a lesser degree, Mac) is becoming a hinderance for us to compete against the companies that uses Revit, ArchiCAD or even the basic sketchup program. (5) Vectorworks (Renderworks): Quality of render simply is nowhere like the packages above
(4) Vray > Works with Revit, ArchiCAD and Sketchup, but not work Vectorworks. (2) Twinmotion > Works with Vectorworks, but NO direct synchronisation like it does for Revit and ArchiCAD (1) ENScape > Works with ArchiCAD, Revit and Sketchup, but NOT Vectorworks The packages that are widely used now are ENScape, Twinmotion, Lumion and Vray.įor a VW company like ours, who uses Vectorworks on Mac, these are the limitations: Over dinner with industry friends last night, I was reliably informed by a senior partner of an international firm that if our firms don't 'adopt the new ways of generating fast high-quality renders for our clients', we'd be left behind.
0 kommentar(er)
