There are the features, that need your feedback:
Enscape uses the lights you can place natively in Rhino. There is no way to select an IES file, so we would have to provide a solution similar to SketchUp - lots of work for such a small gain.
Placing sound sources like in SketchUp might be an option. Still have to prioritize that feature.
from a point of view of a long term rhino user it would make the most sense to have the active viewport synchronized.
Top, Back, left and right should than be excluded to allow the life adaptions to the plan layout.
Other approach could be that you read out the list of viewports into the UI and you have to pre-select the viewport before you export the scene which is linked.
Yes View Sync is a must and the active View should be the starting point.
Would love to see a head-up display of available camera positions to choose from and teleport to.
I have been reliably informed by our Rhino Wranglers that āLinked blocksā are an absolute must have.
@nvizeon How does the view synchronization in 2.0.2.605 work for you?
@snowyweston Preview version 2.0.2.605 new supports linked blocks and attached files (worksession). Is everything working alright for you?
view sync works really well with switching the cameras in rhino.
HUD would be very good to be implement so the client could change the views on there own during presentations (exe)
bump and alpha works very well with rhino native materials.
if you use vray materials with refraction than the maps are not recognized.
For the bump map is there a possibility for adding a intensity value (multiplier)?
Sorry been busy with work lately Iāll try to come back and continue the conversation about Enscape and Rhino.
@GRAFT_1 Bump map intensity can be configured in Rhino natively and we read that value.
Canāt say anything about VRay materials. We do not explicitly parse anything VRay related, but probably VRay tries to fill the native Rhino material as best as possible and we do read that.
I did try a little bit to get to the VRay material data, but it seems impossible.
the problem is that the 100% are limiting - in advanced engines you have multiplier values from e.g 0-10
is there a way to override this values with enscape ? this leads to the discussion of an material interface
is there a way to have the outlining activated also for transparent objects ?
is there āEmissiveā support already - would be really great
@GRAFT_1 Just use the Emission Color you find in rhino materials. It does something different in Rhino and has only a default brightness - but itās more than nothing.
Found a new version of Enscape and emissive effect works. 
But ā¦ I load a new material āwhite reflectiveā and it glows white. Only if I set emissive color 1,1,1 instead 0,0,0 than the glow is off.
Wrong Clipping for small objects also at the latest release. (Could be a problem for jewelry design.)
Could be nice to get global document/general plugin options (for example like Bongo is using it - see screenshot). There could be placed multipliers for lights, bump ā¦ . So, the user could adjust the multiplier ranges for a scene. Also Octane has global options there can be found options for Rhino material conversion (see screenshot).
But instead to use global multipliers I would prefer the way of other render plugins - own option UI for lights (for example Vray for Rhino), own materials at the material editor (like Octane). Itās more plugin code work now but for the long run it will be help to make an advanced pro render plugin. Rhino basic material UI is to much limited, same for lights.
Or the render plugin AIR - it doesnāt use the Rhino materials, there is added a parallel universe of options. Attached some screenshots.
I hope Enscape will leave the limited Rhino UI and grow to an own UI. I think itās the only chance to bring Enscape at Pro level.
I donāt understand the part with ākind of ambient colorā. I think reflectivity should be used as reflection intensity multiplier. Glossiness is something like Roughness. Could be nice if the IOR parameter could be used.
Currently there is a bug in the preview versions where objects glow white when switched from emissive to non-emissive. Try restarting Enscape in this case.
Since the 2.0.2.832 preview we increased the maximum light intensity. We have thought about mapping 100% in Rhino to the new maximum to support the full range, but we didnāt want scenes that are not optimized for Enscape to look overly bright - so we decided against it. A global or per-project multiplier might be a solution, thank you for the suggestions. We will evaluate what to do and are open for more feedback in the meanwhile.
