Visual Settings presets and Two-Point Perspective render issue in Rhino

Enscape Announcements
,
1

Hi everyone,

I’ve just installed the latest Enscape update today, and since updating I’m having two major problems that I did not have before the update.

1. My Visual Settings/presets are no longer being retained.

Previously, I had my HDRI, Sun Brightness, exposure, etc. set up and saved, so I could work through different views without having to constantly redo my lighting.

Since installing the new version, these settings seem to reset everytime I render. For example, I have to reload my HDRI and readjust the Sun Brightness every time I render. This is becoming extremely time-consuming and is not how my setup behaved before updating.

2. Two-Point Perspective is not being kept when I render an image.

I am working in Rhino 7 and have my view set up as Two-Point Perspective. The Enscape live viewport shows the correct view, I have used the sync button.

However, when I actually click Render Image, the resulting render does NOT match the Enscape viewport. The perspective changes and the lines converge in different directions, no longer straight lines, so the final image is effectively a completely different perspective from the one I set up.

To be clear, I have already checked the usual things:

  • Rhino viewport is set correctly
  • Enscape is showing the correct camera/view
  • View synchronisation is enabled
  • The Enscape viewport itself looks correct

This only started happening after installing the latest Enscape update today. Everything was working correctly yesterday with the previous version.

Has anyone else experienced either of these issues with the latest version, particularly when using Enscape with Rhino and Two-Point Perspective?

At this point I’m wondering whether this is a bug/regression in the new version, because I’m losing a significant amount of time having to recreate lighting presets and then having the final render ignore the camera/projection that is clearly correct in the Enscape viewport.

Any help would be massively appreciated, particularly if there is a known workaround or a way to roll back to the previous version.

Thanks!

2

Hi @Tilda_Heron,

Thank you for reporting these issues, and welcome to our forum.

We haven’t heard of the first issue before, so we would need some additional information and log files to look into this further.

Please send us a feedback report, including the log files as seen in our article here, and add a link to this Forum post in the description as well, so we may connect the provided data to it.

Regarding your second issue, we are aware of this, and our team is looking into resolving it in a next release. For now, we can recommend rolling back to our 4.18.1 release found here.

Kind regards.

3

WE are having the same issue with this last release of Enscape for archicad 29. It seems that the problem is the visual setting presets because Archicad cannot force its perspective settings like 2 or 3 point perspective when sync view is active because it’s grayed out on visual setting. WE have to unsync it and force the same FOV. Then, with both FOV used, you can sync again and it will get the same perspective. This means that if you are using visual settings presets for several renders and batch them, you will get unwanted perspectives.

This leads me to another issue that WE have mentioned in another post, that camera settings should be set ti each render and not on the visual setting preset just like DOF and other camera settings. Visual settings are preferences used for several renders, like render frame size, render type and many other.

Lets think as a photographer, whats in the camera is unique for that photo, but whats outside the camera is controlled not by the photographer but by the reality or project.

WE would love to use View settings from Enscape to have all render settings ready… with its visual and light settings presets and a separate camera setting also, and be able to render loads of renders in a few hours, since render times now are less than a minute. Why does this make sense? Because with BIM projets you are not design one perspective, but a full project with any views you need from it.

Please take this extra step for BIM users in order for us to take our projects with enscape to the next step. With ai in the rise, WE want full control of a project and being able to render with ease lots of perspectives, all of them making sense because it’s in the BIM model. Ai can enter before to generate ideas and iterate options, then WE model to document with renders also, then WE elevate the rendered images once again with Ai. For it seems the way to go…

Cheers