Posts by icarumba

Please note: Should you experience issues with Enscape or your subscription, and in case of any urgent inquiries/questions (e.g. regarding our upcoming licensing changes) please reach out to our dedicated support team via the Help Center or Support button as detailed here.

    The merger between Enscape and Chaos will undoubtedly (and hopefully) result in some unification, integration, and streamlining of the V-Ray and/or Enscape interfaces. I would like to be proactive in asking that the new company not fall into the same "me too" mentality with regard to oversimplification of the user interface that is so common these days. The current interfaces of both pieces of software are not perfect, but they are pretty good.


    For some reason, more and more UI designers seem to harbor a delusion that hiding tools make software easier to use. Perhaps they are afraid that too many visible icons will frighten away noobs, or maybe they are just looking to create a portfolio piece for themselves, without any regard to functionality. A "kiosk-type" interface is great for, say, kiosks, but it simply does not belong on a piece of software that is going to be used daily or weekly.


    When you have to search for where a tool is hidden, it makes the software harder and more inefficient to use, not easier. Even when you know where that tool is, if you have to drill down into a nested menu to use it, it makes the software harder and more inefficient to use, not easier. I don't care how "clean" the interface is, requiring four of five clicks to activate a command is less efficient that one click. Why is this so hard for interface designers to understand?


    The absolute best current example of bad interface design is Twinmotion. Not only are pretty much all of their tools hidden, they don't even use the space for a bigger viewing window! At the bottom is a huge, mostly blank band with a couple of icons on it. It simply could not be worse, and I hope that Enscape never even gets close to going in this direction.


    I am very much in favor of a clean, well-organized interface, but not one that is oversimplified to the point where it becomes inefficient. I hope that Chaos/Enscape will choose to continue to buck this trend.

    I am having a similar problem. I only have 2 keyframes, the first set at 7am, the second is set at 9 pm. The sun stays at 7 am and does not move until 90% through the animation, and then rapidly switches to 9 pm at the very end. There is no smooth linear progression with the sun animation, but the camera animation works well. I have checked for overlapping keyframes, and there are none.

    I am having a bizarre issue with a certain material that refuses to render correctly. The first image is the texture that is being used, the second image is how Revit 2020 shows the material in Realistic Mode, and the third image is how Enscape renders it. No amount of material, Visual, or lighting adjustments will get it even close to what it is supposed to look like. I have tried creating a completely new material with no luck, and have used different versions of the texture image with the same results.


    Any help would be appreciated; this snafu is holding up the project!


    I am having the quality issues mentioned here, as well as another problem. When I am running Enscape with our HTC Vive wireless headset, I am unable to make any keyboard or mouse inputs without having it crash. This happens whether I am running an .exe or running live from Revit. With the tethered headset, I could do this without ever experiencing a crash.


    This is important, because we often have clients that are unable or unwilling to teleport by themselves (I'm still amazed that pointing and pulling a trigger is beyond the capabilities of some people). I will need to either move them through the project with the WASD keys, or select saved views for them. I cannot do either with the wireless headset due to the crashes.


    Any workarounds for this?

    We are starting to use Enscape for still renderings, and cannot figure out a way to see exactly what portion of the image will be exporting. Are there any plans to add a "Safe Frame" or something similar to the view window, for the times that the aspect ratio of the view window does not match the aspect ratio of the output? Or is there a way to do this already?