If you ask me so Demian Gutberlet ... please implement at full working material editor with all typical functions or better use the Rhino material editor and Enscape materials like Octane do it. The current workflow is really disappointing.
A bit off topic, but would there be any news on implementing gif animated texture? I know we discussed that a while ago..
Micha - this is the first iteration of the material editor for Rhino, and I am sure that we will be seeing some improvements to this feature over time. We know it's not perfect yet, so any feedback we get from users is, of course, helpful. You have to remember, Enscape in comparison to Octane and VRay, is the new kid on the block, so to speak, so we are playing catch-up in some regards. Please offer your constructive feedback though, it is valued.
gautier - this is still in our developer agenda, so has not, as of yet, been worked on further.
Maybe the McNeel team could help to get the Enscape materials working direct in the Rhino material editor. It would enhance the workflow a lot.
I'm glad to hear that there are chances to see improvements. Only I afraid we talk about a very long term since there are some old Rhino shortcomings waiting for improvement too. Maybe it help to recall some of this issues:
* target points of the Rhino camera and saved views not used for Enscape, so that the use needs to manual adjust the DOF distance every time he change the view
* Enscape options not saved to Rhino file that can cause lost setups
* not working material ID output (randomized colors for the same material)
* batch rendering ignores the lens length of the recalled views (and don't use the target for DOF)
* Enscape output window doesn't stay at top without installing extra tools that the user need to search at the web
* the nice Rhino soft edgening is not used for the Enscape output
This are standard functions of any Rhino render plugin and without this functions the integrations looks quite weak. I understand if the core developers have to much work, but couldn't more developer power added to the plugin and non-core functions development? I ask this since my impression is we have this slow plugin progress problem since more than one year now. Please surprise your users and release a well implement plugin at the next official release and not over the time.
Note: some(/most) of these issues are not Rhino specific but are just current limitations to the Enscape program across all platforms.
Editor needs to be floating, not locking rhino when opened. Ottherwise workflow is to disrupted to bother in my opinion.
IIf there is a problem with sync I suggest you introduce a manual refresh shortcut option, it is needed anyway.
jpedstrand - I am led to believe that this is a problem due to the limitations that the API Rhino offers.
There is no workaround for this at the present time, and the developers have tried to implement the best possible solution available to them.
Rhino 7, when it becomes available, may or may not resolve this issue.