I'm having this issue as well. Yesterday the file was fine now its crashing every time I run Enscape on one particular model.
When I am prompted to send runtime error information Enscape freezes and doesnt process the command to send error data.
I'm having this issue as well. Yesterday the file was fine now its crashing every time I run Enscape on one particular model.
When I am prompted to send runtime error information Enscape freezes and doesnt process the command to send error data.
I just got an error as well that crashed the program.
It also changes the sun position after rendering... ignoring the saved scene sun position.
This happens every time i go to render the scene. Even when resetting the sun position.
Check that your surfaces are closed and that no minute gaps are present. Up the rendering lever to high or better.
Thanks for the explanation Adam really useful information!
I agree the "standard" displacement map is black, white, and grey. However the pebble materials Enscape provides uses what looks like a normal map.
So I decided to copy that logic since its their software.
Anyways, I guess to improve it I should make it black, white, and grey.
Hi Demian Gutberlet perhaps so if you turn on Enscape match camera.
Generally, I set my camera location with SketchUp but once I turn on Enscape I edit the scene and save a new one within Enscape.
From there I work solely within Enscape to edit the camera position and capture the scene, exposure, artificial lighting, atmosphere, FOV, saturation, aspect ration, etc...
After all isn't that the point of live render
Can sun position - adjusted with shift+u/i or ctrl+u/i be saved in a scene by enscape?
When making an other camera view, with other sun position, in the first view the shadow settings are also changed. Very frustrating!
I agree it's frustrating!
Live render is great but wasting time to re-calibrate settings seems pointless when I should be able to save all settings and lighting to the scene.
Likewise when doing different camera ratios I have to write down what scene has what Ratio and Field of View
and then input that number every time I have to re-render. Otherwise I would be SOL trying to recreate the scene.
I generally use Encscape to play around with the time of day. Once the daylighting and shadows are what I want them to be there is no way for saving the time of day to a scene.
Am I supposed to create a preset for every scene that uses a different time of day and month? This seems like overkill, is there a way to save time of day/month etc within Enscape?
Thanks Paul, it looks like it worked out fine in your example.
I am seeing some rendering differences between 2.7 and 3.1 particularly day lighting as well as shadows.
1) Day lighting is significantly impacted from the "Sky" clouds settings "Density" and "Variety". Much more than in previous versions.
2) Shadows and reflections of vegetation/geometry are reading much thinner than before.
Has anyone else dealt with these issues? I Personally prefer the look on 2.7 (Left Image)
2.7 Left and 3.1 on the Right
I use a desktop with an AMD Ryzen Threadripper 2920X 12-Core processor. Hasn't failed me yet in 2 years!