Posts by wilschroter

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.

    This is the second time this has happened to me where I load up a SU/Enscape model that has 50+ proxy references that all get "lost" when I move from one CPU to another (upgrading).

    Now I know if the directory paths change that would throw things off. But I keep a very strict 1:1 directory structure when I upgrade for just this reason.

    Is there something else in the way that Enscape recognizes file paths that I should be aware of? Other than a typical C:\folder\file reference?

    Kaj Burival I'm talking about from the moment I click the Enscape Render button in Sketchup until the moment my render shows up in Enscape.

    Right now I see my GPU at 100% (RTX 4090) which I expect, but my RAM slowly grows from around 10gb to about 30gb in Sketchup, so I'm wondering how much my RAM latency is holding up the render. Or perhaps it has zero effect, and really just the GPU @ 100% is the only bottleneck.

    Took me a while to figure this out, but when working with a 42mb file in SU 2022 Pro the model itself works lightning fast with edits.

    However, the moment I run an Enscape render, the SU model itself crawls during any kind of edits. To the point where when I make a single action - no matter what the action - I have to wait about 2-3 seconds before it will execute. It's a massive problem when trying to edit, especially when you're doing really basic actions like opening and closing groups.

    I've got the Live Updates feature turned off of course. What else could Enscape be doing to actively drag down the SU model itself?

    The SU file is 40mb but the total render (I use lots of proxies) includes about 1gb of assets. From the time I hit "render" to the time the render is complete is about 11 minutes. Prior to the render I'm using about 5gb or less of memory. By the time the render completes it sometimes eats up as much as 30gb or more.

    Spec is RTX 4090, 64gb RAM, i9-13900k

    Whenever I run my render Enscape seems to be chewing through gobs of memory. I'm typically at 70% or more of 64gb of memory by the time I get to my single render.

    Would increasing my memory to 128gb or getting significantly faster memory (I'm DDR5 2700mhz) improve Enscape's performance at all (time to render) or is my RTX 4090 doing all the work there? Feels like when I'm waiting for renders I'm just watching the memory slowly get consumed.

    When I'm working in my rendered view in Enscape, and I make a change to a proxy model within the project I'm working on, what can I do to "force" Enscape to check for an update to the proxies I'm using in the model and thereby update the Enscape rendered window?

    Sometimes I'll see a little spinning arrow in the bottom left that indicates it has recognized an updated proxy and is making changes, but I'd like to know how to make that happen intentionally.

    I'm curious - if I use a fairly big object in my model as an external proxy (like a car, that's a heavy model) if I use it 50x does Enscape run slower at render than if I were to use 50 totally different versions of the same file size model? I noticed that for things like Skatter it handles tons of trees, so I wondered if I repeat large models if there is a similar benefit in keeping the speed and load of a render faster.

    What's the workflow that the Enscape team (or anyone else) uses to create these placeholder assets? I'd like to build matching assets that look identical but can't figure out how to create/export a placeholder that has this same "wrapped sheet around the object" look.

    cornetjr Would you be able to think of any reason why Enscape would have a problem with an Enscape Custom Asset versus a Proxy? It seems they are both just calling an external model. I ask because external proxies very commonly have more than 20k polys. I'm just wondering if there is any code around the Enscape Custom Assets that present some unique challenge. Could be nothing, just curious.

    When I import custom assets into Enscape, I keep losing the material settings. I've done quite a few imports but just started noticing this happening. I'm exporting the models in Simlab GLTF, as well as native export for OBJ/FBX in SU and the same results keep happening.

    Below is a screen shot of what my original material settings were, and the second is a screen shot of how they are changed in the Enscape Material Editor.

    It's worth noting that the settings that SU keeps defaulting to are the original settings that were applied when I first downloaded the model. I tried saving and re-opening the file just to make sure it wasn't some saved/version issue.

    Any idea what's causing this? It's not just images, but other settings like if I set a material name to "chrome", etc.