Posts by Sheik

    Hi, I quote myself: "I tried unchecking the "Save Enscape sun position" option in creating the view, but it does not remove the issue"

    I'll see when I'm rendering next time to send the some logs.


    After the recent update, a small but very annoying glitch appeared into my workflow:

    Yes, you can adjust sun position in Enscape, which is great, but:

    1) I have a Revit 3D view with accurate GEO location and also my project has been oriented according to true north

    2) I open Enscape, and the sun is in the right spot; with only U and I, it changes the time of day, in the right manner

    3) I create a static 3D view in Enscape, I don't adjust the sun position since I have GEO location and True North set correct, so I only adjust it prior making the view with U and I

    After 3), the sun location entirely "resets" in Enscape. It kinda forgets where the north is, and it kinda forgets what the GEO location is, so U and I only moves sun's location in one straight line.

    This is fixed by "reloading" the original 3D view that had the correct geo location settings and proceeding into creating new views one by one, always reloading one. I tried unchecking the "Save Enscape sun position" option in creating the view, but it does not remove the issue, as I would have expected, so I guess the actual bug is right here.

    A small but meaningful thing.

    Keep up the good work and thank you for a fantastic product.

    Heyo, I'm gonna walk you through a memory leak -looking issue.

    PC specs: I9900K, 32gb of 2666Mhz RAM, SSD and a RTX 2070S

    Set and workflow: Revit, custom assets with loads of polygons (definitely not optimized), approximately 30 different views, 5-6 panoramas, RTX on, a lot of light sources in form of LED strips etc.

    Goal: to render all images and panoramas

    When I open Enscape for rendering purposes, memory usage is 9-10GB. If I try batch rendering everything, memory usage jumps quickly to 100%, and the whole rig crashes. SSD runs at 100%. CPU and GPU are at 0-10%. Batch rendering 2-3 images at time works, but is extremely slow, and can only be done like 2 times before all the softwares have to be shut down. When rendering single images, every rendering makes RAM usage rise by 500-1000MB. When the usage hits 14-15GB, it quickly jumps up to 32GB, freezing everything.

    I eventually managed to render everything by rendering as many images as I could until the RAM usage was at ~13GB, at which point I restarted everything and started over.

    Oddly, with panoramas, RAM usage does NOT rise at ALL, and you can render as many panoramas in row as you wish.

    I was contemplating whether this is a hardware issue, or could it be that Enscape isn't built for scenes this heavy - or could it even be that there actually is some sort of memory leak in the software?

    I am asking this under circumstances where I am looking to upgrade the rig, and I'm trying to decide whether a 3090 is worth the buck or not. At rendering usage, 2070S CPU usage at it's worst only around 60-70%, althought it's memory is often almost full, and rendering becomes often very laggy and difficult to adjust sun and well anything due to rendering glitches and freezing.

    I'm rendering with 2070S and I feel like 3.1 has increased render speed slightly, but I still struggle with crashes on more polygon dense projects. Which why my 3D modeler has started to do even more low polygon modeling so that we can achieve better results - since polygons don't often make the good stuff, textures and lights do.

    Funnily, if I batch render 20 HD images from very heavy project, it crashes often at 5th-8th rendering, but if I render only 4-5 images at a run, it does not crash. I wonder why batch rendering does this, as if it cumulates the burden on itself?

    Sheik , it would be really interesting to know if other applications give you the same results via Virtual Desktop - perhaps you have something like a game installed to test it? Also, how fast is your internet connection?

    I play with it all the time via VD, and it works perfectly. The modem using WLAN is very fast, so there's no issues with that either - in fast paced games, I would notice if it had anything to do with WLAN speed.

    But worry not, I just heard Quest 2 is going to get a major update (I assume yall know it already, ofc, but just to put it out for others too); the new update is apparently going to enable 120Hz, but the major thing is, they'll go PCVR-support natively, so stuff like Virtual Desktop will no longer be needed. I'm pretty sure that the problems like I described disappear, so maybe going further in investigating that, wouldn't be worth the trouble?

    Asking because I'm currently using a Rift S and am looking into acquiring a Quest too.

    I switched from Rift S to Q2. Doing things wirelessly now.

    Enscape has some movement bugs etc. when using it via Virtual Desktop. Not sure if it's a problem on Enscape's end or VD's end, but nevertheless, the experience is so buggy I wouldn't hand over a Q2 for a client with this setup. With tethered Rift S it worked fluently.

    I'm curious to see if things get fixed, because after Covid calms down, I might start a service to let my clients VR walk the designs, and with Q2 it is not currently plausible due to too buggy experience.

    We'll investigate Sheik . That should not be by design. Just to make sure, you only tried/experienced that with Revit, correct?

    Yes, Revit only for me.

    More information on the issue:

    This is still seemingly random. I tried to troubleshoot, and figured out something:

    -The VIEW seems to remember SOME sun data, but not all of it, and visual presets seem to remember NONE. I created two views, and in between, I changed sun orientation. Both views have same preset. At first, they remembered their sun orientation. I created new views for batch rendering, and later returned to these two. They still have same preset. The sun orientation is still DIFFERENT in both, but now it is all messed up and way different from the original. This happened when I wasn't watching. I'm not sure which sun parameters the views remember, but they seem to remember SOME and SOMETIMES.

    Hope this gets resolved soon. It makes batch rendering a very difficult at times, especially for me since I often visualise whole buildings from all angles, so I must get sun to shine from different angles.

    I used TM a lot, but eventually returned to Enscape.

    Why I used TM earlier?

    -Possiblity to edit terrain


    And why I returned to Enscape:

    -Lost a lot of work with continous crashes, althought TM21 has apparently fixed this

    -Mastering terrain editing in BIM turns out to be a better and more accurate way of visualising real world things than doing it "by hand" in TM

    -Enscape introduced Assets: now I can model my own things

    -Way better render quality, especially indoors

    -No need to play around with mirror boxes or whatever, althought the mirror rendering is pretty horrible

    -Live updated workflow with Revit is superb: being able to see what you model or sketch in real time is a must

    So for me, Enscape is a no brainer.

    But still, Enscape's devs mustn't get too comfy, because the business is blooming; VRAY 5 with it's real time rendering, TM21 and TM22 and UE, and so on..

    Am I experiencing a bug, or is this a feature? Presets don't seem to "remember" sun orientation, whenever I change it in one view with one preset and switch to some other preset, the sun orientation has changed.

    It's odd because I'm pretty sure that at some point, the sun did change it's orientation due to the picked preset, but it's now a bit confusing.. how is it meant to be by the devs?

    I would disagree at 3.0 being a disappointment for "most of us", I definitely want to publicly inform I'm not amongst disappointed users. It's a good big overhaul, and feels very natural that it had to be an X.0 update.

    Keep up the good work.

    Be aware, you can also always right-click and duplicate any of your existing settings. This means you can create your own default settings so to speak which you can duplicate whenever you like. If that isn't a sufficient workaround for you I'll forward your feedback. :)

    I only learnt this after the post, and it fixes the issue 80%. I've now implemented duplicating and also saving as a file, into my workflow and it's again, a great advance.

    This may also be related to the size of the object. (rather small objects can get simplified in terms of geometry) Can you try to create a large object using the revolve tool? If that still shows the same behavior, no matter the size, we'll have to look into this. Thanks! :)

    Yes, it is size related, only bugs with small geometry, I mostly "struggle" with this with various knobs. Some small wires etc also do weird stuff, such as turn into a needle instead of a line with symmetrical thickness.

    try it, if as you describe, you’re crashing when rendering anything above potato resolution and it works then that’s a 100% improvement.

    As for quality ... have you tried rendering with RTX off? I don’t see many users with 10xx cards screaming about the poor quality of their renders.

    I’ll more than admit that my lighting skills need improvement but I don’t see much wrong otherwise here:

    I sent you a pm about the virtual tour - but about rendering, I do spot things that RTX would have done better, but then again, there are some things RTX does way worse.. in fact, only one; a sink that is. RTX messes it up badly. But I do like more the RTX rendering quality, althought it propably is a question of taste.

    So far I haven't faced projects that would have stalled because of this issue - just slows down the workflow and makes things generally annoying, but nothing too serious. But if I face a serious issue, I will do try it out without RTX..

    Interesting, I have exactly the same specs, only I have 2070S. My RAM is 2666.

    Perhaps the difference is in our scenes. My scenes have been heavy and are only getting heavier and heavier.

    If I render a heavy scene at 4K with this setup, it will often crash. But oddly, it's completely OK to render panoramas - of course, this must be because panorama is rendered of multiple pretty small images, so it propably is kinda same as batch rendering.

    Batch rendering has been a great thing, I love it. Enscape is an amazing software as it is.

    My GPU runs at 70-80 C , and when VRAM usage goes over 7gb (out of 8gb), things get very unstable. And that's happening more and more often all the time, so I'm honestly starting to consider updating. Resolution of the images isn't a big problem for me, I rarely do larger renders. But that AI scaling does seem like a nice thing to know, if I ever have to make a bigger rendering and my hardware is unable to do it.

    I'd love if you could adjust ONE set of settings that would be the default settings. Enscape's own default settings are dark and saturated, and I always have to do same adjustments to every project.

    When models from Revit come on Enscape, things that are made with "revolve" -tool, will have only 6 corners, making them, well, not round, when they should be round. But if you do a circle as an "extrusion", it is perfectly round, so I'd assume it has like 32 or 64 corners.

    An image attached shows this spesific situation.

    ok, so i was under the impression that a workstation graphics card would be the better way to go, i have a Quadro RTX 4000....

    is this not true? if not i WAAAY over payed for a suitable card... does it matter?

    As far as I know, workstation cards can have some features "customer" cards lack, and they might have some sertificates and other stuff, but from my perspective (I live on doing 3D), that's all just nonsense, and I would be as bold to say that yes, you did overpay a lot. But there's propably someone who disagrees - and honestly, I am very keen to hear opinions too.

    Currently I'm struggling whether to do a larger investment and go for 3090, or do a smaller incremental leap to 6800, which also almost doubles the power, compared to my 2070S, and has a lot of memory.