Any comments from Enscape, please?
Posts by L.S
-
-
I've requested on the forum and also submitted through the portal, but nothing happened yet.
-
I am using the latest Rhino, so it sounds like it happens both current and previous Rhino versions. I think it happens more often when there are a lot of lights. Is that the same for you guys?
-
I remember seeing the same post before, and I'm glad this is posted again. This fix would be awesome.
-
I have been using this script. I modified it a little bit to make the name simpler, but it's been very helpful.
I want to thank robotopera again. It was a huge pain without your script to use linked files in Photoshop and InDesign.
Needed a way to integrate things with our work flow so here is a powershell script that renames files
-
Any comments from Enscape? This is especially bad, when the PNGs are all the same rectangles. No way to see which is which.
-
This happens quite often with images especially. Explode the image first, then you can correct the image texture accordingly.
-
Any comments from Enscape? This gets very tiring with so many saved views needing different focal lengths.
-
I also noticed with Rhino with large file size quite often. The only way to fix it is to turn off and on Enscape. The same issue doesn't happen with SKP even when the file is large (with large file size SKP, Enscape just crashes SKP - I guess it's different symptom to the same cause).
-
I can certainly understand the frustration here, though the status is that we've made further progress with 3DConnexion. The fix seems to be working.
But now they have added further requirements that we have to meet in order for them to roll out the fix. And that includes hotkey support.
We are now currently working on that and said fix is planned to roll it out in release 3.5.
I will of course also notify everyone in this thread once 3.5 is out or once the fix is generally added.
It still doesn't work in 3.5 preview 11 (both SKP and Rhino). Is it still planned to include 3dconnexion fix in the final 3.5?
-
Please stop making 'self-illuminated' PNG completely white in Rhino rendered view. As soon as PNG becomes Enscape self-illuminated, it becomes completely white in Rhino's 'rendered' view. It doesn't happen when PNG is Rhino's own 'self-illuminated.'
When there are several illuminated PNGs in the model, it becomes very hard to see which is which in Rhino's view.
-
Even though it's not "auto exposure" light level goes up drastically once the view is moved from entry to interior. Turning on/off "auto exposure" won't help.
Is this expected behavior?
-
I posted a similar request. I didn't realize there's already a post about it. Demian Gutberlet, is Enscape at least acknowledging Preset is not really in good shape? and this needs to be updated? or is this being ignored because Enscape team is thinking this is one of those requests only a few users are complaining about?
-
When we select an image file as the Albedo map in the Enscape Material Editor, it overwrites the texture in the SketchUp material. And vice-versa, when we select an image file as a texture in a SketchUp material, it overwrites the Albedo map in the Enscape material.
Is it possible to decouple the two? The use case would be to use a low-resolution image in SketchUp, while having its high-resolution counterpart in Enscape. Storing high-resolution images in the SketchUp file can quickly make it several hundreds megabytes.
I think I remember that it was possible in previous version. That when we chose an image file in Enscape, it was decoupled from the SketchUp material texture.
It is also possible in V-Ray by disabled "Bind".
We actually want to do this via attributes by using <Source>TEXTURE_PATH_ABSOLUTE</Source> and specifying the path, but it doesn't seem to have any effect anymore.
A great idea. I always try to make texture size down well below 1mb because SKP file size will be unmanageable very quickly otherwise.
-
It's extra frustrating because it worked just fine before. The new changes did nothing but broke functions of the video editor.
-
An option for Camera setting to be saved per each scene is needed.
When you create a lot of scenes, it's inevitable to change field of view / depth of field / focal point. All these are tied to a preset. You have to create so many presets and link a scene to a new preset only for the camera length.
-
I have urge to spam the forum with Video editor and proper Rhino support, but Enscape clearly doesn't care about these two.
-
I have just submitted the feedback with log file. Automation Update Nvidia driver - Enscape Renderer Error / 01134458 / [ ref:_00D0Y1IeF9._5001n1tkpZo:ref ]
The issue couldn't be replicated with a new simple file when I tried.
When the shutdown happens, it doesn't help even if the computer is rebooted. I had thought clearing up memory would help, but no.
-
I remember this working fine before, but now if a HDR skybox file is linked from the network server, instead of the local computer, Enscape won't open. It loads to 99%, then it crashes.
The problem is, you cannot update Visual Setting to change HDR file path to the local computer unless Enscape opens.
-
Hey thank you for the input! Yes, that is the result that I’m aiming at, perhaps a bit more gloomy/moody. Your comment makes me think that my problem is in the trees themselves perhaps? The “glowy” ones in my scene are Maple trees. Maybe there’s something wrong with them? I will check tomorrow again.
Your scene looks very beautiful. Did you use HDRI in your render or is it the default clouds/sky? Also I may be wrong, but it seems your day time is either early morning or evening, correct?
I usually use HDRI, but this one is just default sky with shadow sharpness 0% and low sun brightness (definitely lower than 10%).
Probably the time was somewhere it doesn't cast direct sunlight into the scene.
There are some spot lights used in the scene, but it was to emulate reflectors in photography rather than actual light source.
This is why I wish Enscape to offer a way to hide Enscape light in reflection, like you can with Vray.
Don't remember which tree I used, but it's surely worth checking if it's the tree itself is the culprit.