![]() ![]() set the angle in Enscape (NOT on sketchup).Prior to 2.6 update it still possible to match with the following workaround: In Vray Skp it still possible to pan after put the view on 2pts mode but it wont match if you then scroll the mouse to play with fov. There's no renderer that can match exactly with Sketchup view when you put it on 2 pts then pan, specially zoom (changing the fov). I hope that this item ranks high on the development agenda, because I can hardly expect to use Enscape This means workflow and all this is finally the reason why we still may not use Enscape for our real production but only in a parallel "test run". No matter who presses the render button, no matter under which viewport setup, no matter on which computer, no matter if PC or MAC - everybody produces an identical result. Render or Shaderlight) master this task confidently. We successfully use many different renderers - even the simplest and cheapest renderers (e.g. This is the reason why many other renderers refer only to SU´s viewport height while the desired render width remains variable - unfortunately Enscape opted for the width though. No matter under which viewport conditions a SkUp model is opened, SkUp always displays the height proportion. Hi VStudio yes, you're absolutely right - but: This makes it hard to maintain the same exact export when using the Use Viewport Aspect option in Capture. But this is not our job reality.ġ SketchUp's viewport proportions are different on virtually every workstation due to tool bars, etc. Sure, as long as I render a singular project and know that the customer only wants 3 nice pictures and done, all this doesn't matter. You could, just for fun, render your own example on another machine with it´s own setup - you wouldn't get the same results out of the box! This is a real money killer Or imagine any prefabricated house supplier - he would like to present his house type X uniformly in the internet with always new design variants etc. It is absolutely necessary to rely on workflow rules here. I hope, my example below shows what I mean.Īll these many graphics are absolutely identical, although these have been made by different people, in different places, on different computers. Enscape is not able to allow this basic requirement of a workflow so far. So he or she just has to open the model and select the appropriate scene to be sure that he or she will produce exactly the same result I produced the day before. ![]() This must be the case, because the next day a colleague might be obliged to render the same scene again. įor this reason the mapping of a rendering content is determined exclusively by the CAD scene. the exact matching is for example necessary where you combine graphics from the CAD and from any renderer - this happens daily in almost every architecture company - within any layout tool these graphics match then without any further stupid fumbling or scaling - just for a simple and fast workflow. Hi jan1 - the main reasons are workflow and reproducibility, because it's a lot of money ![]()
0 Comments
Leave a Reply. |