as lighting fixtures seemed to have too much you had to do to get the desired effect. This is something that frustrated me endlessly with the native Revit rendering engines, VRay, etc. My favorite feature of Enscape is the ability to quickly change the time of day in the Viewer and how well Enscape engages artificial lighting in the model. It is also far more affordable than Lumion, and the real-time updating in the model reflected in the Enscape window are invaluable to making minor changes prior to spending the time to output an image. I'm really enjoying it and looking forward to the expanded asset library. I also found the multiple reflection options to be unnecessary and agree with the "everything should look as good as possible by default", as I am now a sole practitioner and do not really have time to fiddle with settings that do not yield outcomes worth the time it takes to achieve them.Ī former colleague who spent many hours working in Lumion put me onto Enscape. I worked in Lumion some at an office where I interned and while I appreciate that the placement of entourage and control of environment was user friendly and kept our Revit Models less cluttered with those features, it was aggravating to have to update the Revit model, save, re-link, etc. I had the VRay plug in which was fine then, and is what I use now, but I don't like the time I spend in post-render photoshopping the image. I never used Lumion in school as I wasn't a fan of the overall output aesthetic. My hope is, if the needed quality can't be reached by additional reflection types, that the mysterious RTX will help in the future. So, the result could be nearly perfect looking without to bother the not advanced user.
In this situation the advanced user should be able dive in advanced options and enable special reflection mapping types. At the moment we have the "looks like cartoon" effect for reflections in some situations without a workaround.
We will continue to improve the completeness and quality of our reflections, so we're convinced that this is the right path to go.Īs long as the final client don't ask why something looks totally wrong it can be a question of philosophy. It is " everything should look as good a possible by default" vs " By default, it looks like a cartoon but you can tune it with a bunch of options". The reflection difference is more a question of usability philosophy: We do not want to bother users with the choice of which reflection algorithm to choose per surface.
0 kommentar(er)
