Posts by Paul Russam

Please cast your votes in our two ongoing feedback polls here and here!

    In Windows, have a look in C:\Program Files\Enscape\Renderer\SystemData\Textures\Horizons (I don't know about MacOS location)

    You'll find all the std ones that ship with Enscape.

    I don't know if you can add a new one or if you'll have to replace an existing one but as long as you match the size/format etc it 'should' work.


    You'll be doing this at your own risk, we users are not meant to modify stuff in the Program Files folders

    Any Enscape update will almost definitely overwrite any changes you make with the std ones so backup!

    if Enscape could apply a different proxy "shape" instead of the clear wire frame to these proxies via "linked models."

    I have a bucket load of bed, sofa etc and like you the simple wireframe cube isn’t good enough, what I do is create as simple a shape as possible that represents the bed/sofa with the correct length/width/height/shape and then edit the wireframe component replacing the wires with the simple shape.

    I then save this simple poly to the same folder as the original hi-poly one.

    My usual naming structure would be something like:

    • Bed01-mat01-fullgeometry.skp (the original hi-poly model)
    • Bed01-mat01.skp (the simple proxy model)

    Material variations of the same bed will get mat02, mat03 etc

    And a new bed will get Bed02, Bed03 etc.

    Essentially the process is “I like that bed but can it have green pillows” at which point I copy the fullgeometry model, rename it next in the mat sequence, edit it, save it and then in a new SU model; insert a previous version’s proxy, re-link the proxy to the new bed edit it to have the simple geometry and right-click/save as to create the new simple proxy. (Sounds long/complex but isn’t, if anything it’s tedious)

    I mentioned it in the survey but one of the 1st q's is "Do you use custom asset categories" (or similar). The 1st q should have been "Do you use custom assets"

    I don't use custom assets as I already have a large library of models I use via proxies, I'd have to go through the process of finding them as obj's (not all were), reprocessing their poly's/materials etc only to have exactly what I have now WITHOUT the flexibility to quickly make another version with different materials.

    I've seen this before in surveys Enscape has put out .... you assume we all use all features ... we don't.

    Well, there’s me put in my place :)

    When you put it like that you’re quite right.

    I suppose the question is ‘how do we establish/apply the initial setting(s) from which we can then deviate(if needed) per scene?’

    Let’s say I’ve setup 20 panos with 1 setting and now I want to setup 20stills with a new one.

    Currently I have 2 settings called ‘panos’ and ‘stills’, in the future how do you picture the process of applying the stills setting whilst simultaneously modifying it per scene WITHOUT upsetting the already setup panos?

    This isn’t a challenge by the way, it’s something Enscape is going to have to work out and we’re going to use so thinking about it now ‘may’ influence their methodology.

    This is an older thread but very relevant RE: Duplicate views, select/change preset of multiple views & other QoL features

    In the recent poll as to how much of the visual settings should be in the individual views I chose the 2nd option (partial). If you produce 1 or 2 views from a model I can see the attraction of the 3rd option (full) but I usually knock out 20 or 30 views and I need a consistent look to all of them, if I want a slightly lower/higher exposure I can currently; and with the 2nd option make that change once. With the 3rd option; with the exposure (and other relevant settings) in the views I have to make it for every scene.

    Something I’d like to see is the visual settings being accessible from outside of the Enscape window.


    I’m working on a model and I want to use the settings I used in a past model and they weren’t saved as external files at the time.

    I have to close my current model, open the old model, fire up Enscape, wait, wait, wait, save the settings, close the model, reopen the one I’m working on, fire up Enscape, wait wait wait, and finally import the settings.

    I don’t need to edit them, just import them from one model into the current one.

    a dead simple checkbox in the settings menu

    I’m perfectly happy to have that but the current setup (ie compressed) should be the default. If you want to have uncompressed/full fat textures you should be the one(s) burdened to change the checkbox.

    This forum is only visited by a small % of users and an even a smaller % ever comment, this thread has only 8 users (me included), I just don’t think it’s something the vast vast majority of Enscape users care about.

    0.9mm .. whist it’s nice to have real world accuracy it’s unnecessary for a lot of stuff.

    It’s important that the wall is the correct height/width etc but an exact replication of its thickness and profile isn’t. I see this (and catch myself doing it) a lot.

    I build models of buildings, not real ones (I leave that to builders) and as such I can simplify or even omit a lot of stuff, as a grossly simplified example it’s totally unnecessary to model the wires between a switch and a ceiling light even though they will exist in the real building BUT I will model something that looks like the switch and light.

    what's the point or correct use of 'auto exposure'?

    I'm not the best to ask as I tend to throw settings at things and stop when it looks ok.

    You're very close to the doors in that view, you may want to try turning AE back on and back up a bit so there's more of the room (less of the sky) in the shot, the exposure will be better/more balanced and you can always crop the rendered still after.

    When I'm setting up shots for my DTP colleagues I set up what 'I' think is a good shot and then back up a bit before saving the scene, this way they can crop the resulting render down in Indesign to what they 'need' for their compositions.

    It’s auto exposing, there’s more light coming from the outside without the roof so it’s automatically lowered the exposure ‘for the whole scene’ to compensate.

    You could try turning off auto exposure in the settings and adjusting the value to suit both setups.

    Yea, I’ve tried using Blender but it does ‘me ed in’.

    I’ve done some simple tests with models in 3DVista but I’ve been unimpressed with what I’ve seen so far from myself and others.

    If there was a way to export what I ‘see’ in Enscape as a GLTF it would be amazing.

    DGD-Duane How about this for an idea, I’ve only just thought of it so it may be a bit …. Poo.

    Make/find a sundial model and place it in your model aligned north but have it off camera.

    Make a second video using the same time settings looking straight down on the dial.

    Composite the 2 videos in Premiere.

    Without Enscape introducing updates to the video editor (ha!) you’re not going to get timestamps any time soon so it might be worth giving the above a go.

    Enscape is a real-time renderer whereas VRay is an offline renderer.

    From Wiki:

    Rendering can be split into two main categories: real-time rendering (also known as online rendering), and pre-rendering (also called offline rendering). Real-time rendering is used to interactively render a scene, like in 3D computer games, and generally each frame must be rendered in a few milliseconds. Offline rendering is used to create realistic images and movies, where each frame can take hours or days to complete.…%20a%20few%20milliseconds.

    As such Enscape will always require a meaty graphics card.

    Each major SketchUp version is a completely separate install, as such you’ll have to reinstall all your extensions.

    It’s a pita but it’s always been like that.

    You still have 2022 installed if you’d prefer to carry on as before, 2023 is very buggy and a lot of us are sticking with it until they fix things.