Hi Micha,
Thank you for your message, it is this kind of valuable feedback that helps us improving Enscape.
Below the answers to your questions:
When can be seen the new Enscape material editor at Rhino?
We are forecasting to integrate the Enscape material editor into Rhino along with V 2.4 which is planned in about 3 to 5 months. But we are still at the very beginning of the preparation phase which makes it difficult to confirm at this stage.
Is the old important material ID color bugs fixed? (Rhino API still reports different materials with different IDs)
We are currently working to use the new Rhino6-API in the Rhino6-Plugin. The material/ID color bug should be solved in Rhino 6.
When are Enscape setups saved to Rhino? The global setup list is growing and more unuseable from week to week.
We are aware of the inconvenience caused by this problem. Unfortunately, at this stage, we cannot say when it is going to be solved.
At long distance the interior lighting is destroyed, if clipping planes are used. Is there a chance to get it working? (https://forum.enscape3d.com/index.php?thread/1707-view-distance-is-changing-light-calculation-only-wide-angle-lens-works/)
Thank you, Micha for letting us know about this.
It’s cumbersome to adjust the camera target for each view (for DOF) - could it be possible to link the Enscape camera to the Rhino camera?
Technically it should be possible, if more users express this need we could think of linking both cameras.
Are the Rhino lens length used for batch render and standalone export now? Without using the lens length per view the batch render function isn’t so useful.
This is currently not implemented but it sounds interesting. Thank you for letting us know.