Posts by ShynnSup

REMINDER! If you encounter any issues with Enscape (e.g. crashes, installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Support button as detailed HERE! Thank you for your understanding.

    The issue with that is, that we need to stop shipping Service Packs for the old technology at some point. Otherwise, it will be more or less 'wasted' effort

    I don't follow the logic here. It seems feasible to have developed a version compatible with Rhino 8 months ago, especially given your indication that it could have been accomplished within 2-4 weeks.

    I fail to comprehend why facilitating a significant portion of your user base to seamlessly transition to the latest Rhino release is considered "wasted effort." You could have done this first and then have all the time in the world to develop 4.0 release.


    (which you will probably not even notice

    Your first priority should be the convenience of your user base, not yours.

    Experiencing same issue with


    2023.08.31 19:55:00.163 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:00.199 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:00.231 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:00.267 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:02.233 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.283 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.316 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.350 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.382 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.414 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.449 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.483 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.515 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.551 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.582 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.620 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.651 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.684 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.715 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.747 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.781 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.814 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.847 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.878 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.910 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.945 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.980 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.013 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.047 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.078 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.109 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.142 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.172 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.207 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.237 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.272 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.304 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.338 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.369 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.404 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.435 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.464 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.497 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.523 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.559 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.591 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.628 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.659 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.694 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.725 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.760 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.791 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.825 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.860 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.893 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.927 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.959 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.994 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.028 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.062 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.095 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.131 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.164 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.200 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.231 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.266 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.299 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.330 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.363 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.393 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.425 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.455 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.492 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.526 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.561 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.592 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.624 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.656 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.684 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.718 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.748 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.782 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.813 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.845 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.866 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.899 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.921 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.965 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.


    Fix this.

    I appreciate your feedback - Right away, please also try to make use of our latest service pack 3.5.2 which resolves an issue that could at least be related to this behavior as well. If that makes no difference what so ever (which it may not), please let me know and I'll discuss it further internally.


    We'll investigate that further accordingly, you'll hear back from me soon, and meanwhile please also submit a report with logs as detailed here (ideally after updating to 3.5.2) just so we have that information available if required. Here in this case it would be great to know once you've submitted it too.

    Hi Demian. I tried, but the issue persists.

    Specifically what I did was copy about 200 trees around an empty scene, have Live Update on and turn off and then back on the layer where the trees are.


    When I turned the layer off, all trees disappeared in the render window in a second or two, which is ok.


    But when I turned it back on Enscape and Rhino freeze until all trees are rendered, but I can see render window updating one tree at a time.

    There were threads discussing Live Update not working. It won't show change of materials. Enscape has to be turned off and on to get Live Update working.


    Enscape for Rhino not updating in real time


    Enscape hasn't acknowledged the issue despite other users reporting the same issue.

    Yes, there are also those issues, but those are not exactly performance issues. That's for another thread.


    I am talking about how live update works, by iterating through every object and refreshing render, hence making calculations for every object instead of calculating all at once after changes are made. Moving a group should not result in your enscape freezing for minutes. It should stop live update under the hood, move the objects, make one single calculation accounting for the new position of objects and after that refresh the render window.


    Right now its moving one object at a time, calculating, updating render window

    Move second object calculate, update,

    Move third object, calculate, update.

    etc, etc per every object in the group.

    Live Update is a pain to work with. For instance, Undo operations in Rhino take forever, even when Live Update is turned off. I When I move multiple objects at once, I noticed how Enscape is trying to update the window after each object iteratively.


    Turning layers off and on is the same story: I had a single layer full of Enscape vegetation blocks, turned it off. When I turned it back on, it froze my computer for about 10 minutes, rendering every single block one by one and refreshing everytime, instead of waiting to calculate all together at once.


    This is basic developing people. I don't know what the heck you guys are thinking but this is not the way.

    I was going to post this together with the other thread but the amount of inconsistencies lead me to conclude it was better to just divide it in two separate issues.


    Replicate:

    -Save a view in Rhino. (call it Camera A)

    -Save that same view in Enscape. (call it Camera B)

    Realize these two views match in Rhino viewport correctly. All good so far.

    -Watching Enscape render window, while in Rhino set Camera A from the 'Named View' panel in Rhino.

    -Watching Enscape render window, while in Rhino set Camera B from the 'Named View' panel in Rhino.

    Realize these two views match in Enscape window correctly when set from Rhino's interface.

    -Watching Enscape render window, while in Enscape set Camera B (which has a sun saved) from Enscape 'view management' panel.

    Realize it is different from the same Camera B set from the 'named view' panel in Rhino.


    So the same Camera (Camera B), is actually different if you select it from Rhino's interface or Enscape's interface.

    This is a major problem because if you have a sun saved in Enscape, you take your first Render and all is fine, then you set the camera again from Enscape interface to match the sun and you realize the Camera is now different. The only way to get around this is to go back to Rhino viewport, move around and choose Camera B but from Rhinos interface.


    Additional comments:

    I am tired of experiencing this focal length issue across different degrees. It is extremely frustrating and counter intuitive. Render engine should not have a life on its own, it should replicate what I am looking in my freaking viewport. EXACTLY.

    Problems:

    Every time I hit 'screenshot" to export my view the sun position resets to a random one.


    Expected:

    Last used sun should stay so that I can take all my renders with the same sun. It should not reset back to Rhino sun after I have selected a view. Sometimes I need to take various renders from same view with same sun and every time I take a screenshot it resets, I need it to stay put.


    Replicate:

    -Save a Enscape view with Sun.

    -Hit Render.

    -Sun resets back to Rhino sun even though I haven't changed the view.

    View Synchronization is fundamentally different to selecting a render camera, that is the whole point.


    So summed up, as long as you have Live Updates on and View Synchronization off, the live render viewport of Enscape should basically behave like it does in the example video using Octane

    This is not true. Switching View Synchronization off often changes the camera settings such as focal point, etc, no longer matching the camera when View Synchronization is on:



    Moreover, the advantage of choosing a render camera instead of having the silly View Synchronization button is that you can manipulate camera widgets and see live changes on that. You can't do this with View Synchronization workflow.


    With choosing render camera I can then manipulate the chosen camera from another viewport and see those changes live on my render window.

    In Enscape I can't because the moment I turn View Syncronization off, to be able to jump into another viewport (say Top View), when I move the camera widgets, the view is no longer updating because its off.




    The whole point of this thread is that View Synchronization is not analogous to choosing a render camera. It is far worse. Not only is it different from industry standard for no good reason, it actually offers less flexibility.


    I would appreciate it if you would stop being so condescending now. I don't need you to explain me how Enscape works, nor do I need to engage in a discussion on whether Enscape already offers the features I am requesting. I know what I am talking about and I know it doesn't. Thank you.

    Hi Demian.


    That is not what I am talking about.


    Check this timelapse.

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    Most renderers let you fix a camera position, independent of viewport camera. This means you can orbit around on the viewport, modelling and making changes, but the render camera stays fixed.


    For instance here, I have chosen a perspective camera for render, but I on viewport I am working from Top view.


    That's just terrible and incoherent. Materials export just fine. So if I model a cube and add an Enscape material to it, it will export fine and work on Sketchup.


    Hell, I can even import a Quixel model into Rhino, export it to Sketcuhp and it will work! How much more should this work with a specifically curated library by Enscape itself!!


    The only assets that do not work are the specific Enscape library?!?


    Year 2023 btw. No wonder humanity is lost.


    Bet Chat Gpt can develop better than whoever came up with this.

    Hi everyone,


    I have been working on some models adding vegetation on Rhino and then I exported said model to Sketchup to work keep working there and I found out all of my assets stopping being properly visualized, they turned pure white instead of their usual green shader.


    Is this a know issue? Rhino and Sketchup Assets are not interchangeable? That would be a really really bad things specially for someone who depends on Rhino - Sketchup workflow for a living.


    Thanks for any insight. A very concern user.