Posts by landrvr1

    Okay, rolled back to Enscape version 3.2.0+65063 and the problem was fixed.

    I've now cross-checked on two other computers running vastly different graphics cards/drivers/versions and this appears to be a bug.

    Adam, find anything interesting?

    EDIT: Just reinstalled the latest NVIDIA driver (516.59) and everything still works.

    Attaching the SketchUp File. Thanks Adam.

    Just tried the latest version 3.3.2+82281. Same problem.

    Tested on a basic Dell laptop that's running Enscape version: 3.3.1 +75071 and a standard, NON-RTX card. Same problem.

    Rolling back the NVIDIA driver did nothing.

    Testing previous Enscape versions now.

    Experiencing an issue lately in which certain self-illuminated materials are becoming highly pixelated.

    The problem seems to be with jpg textures that have fairly strong RGB values.

    Images that are more muted or 100% desaturated aren't exhibiting the problem.

    Textures are RGB 8-bit jpgs.

    Using png files does not help.

    Changing to CMYK does reduce the severity, but there's still issues.

    I'm running an RTX8000

    NVIDIA driver up to date: 516.59
    Enscape version: 3.3.1 +75071

    I'm probably going to roll-back my NVIDIA driver to see if that helps.

    Anyone else having any issues?

    The problem is that if items are stored on the C drive of the student's computer, the path will always incorporate their unique username in Windows 10!
    With other drives that's not a problem.

    I created a different login account on my new computer that had the same username as the computer I had with my former employer. This solution worked great, you just have to make sure that you set access permissions properly across multiple users when setting up the new account. Of course, depending on IT policy, it may not be possible for a student to set up their own username on a school machine.

    That's clearly a serious of individual panels, raised from the substrate material at different heights. I'd make a flat substrate panel and give it a brass material, then quickly model those squares and rectangles in SketchUp and lay them on top. Would take no time at all!

    After seeing a recent thread I finally did a test using the excellent Keyframe Animation extension. Works pretty well and it's easy to use. I'd actually tried this a few Enscape versions back, but could never get it to work!

    Watch Video

    243 frames of animation, at 30 frames per second. 8 seconds of animation.

    Rendertime with my RTX8000 was about 25 seconds per frame - much longer than simply rendering a single frame without animation - but still pretty quick. Total time to render the sequence was around 101 minutes.

    I should mention that this is a pretty large scene. Tons of polygons, lots of textures, and loads of Enscape proxies. The film only shows a fraction of what's there, so this was a pretty good test in terms of a big pull on the GPU.

    The best workflow I've found so far is to first create your Scenes within the Enscape View Manager. My test had 9 initial scenes, and for each one I'd move the camera forward just a bit, then make a new scene. Move forward, make a new scene. Best to have the Sync View on in the Enscape menu. (watch the Keyframe Animation tutorials for a better understanding of what 'initial Scenes' are...)

    Once I had my 9 initial scenes, I opened each scene one at a time in SketchUp, moved an object, then recorded that movement in Keyframe Animation.

    There's some important things to keep in mind, and they took me a bit to figure out:

    Every scene, regardless of whether your camera is moving or stationary, will need the Camera Location box checked in SketchUp. If you have a scene in which that cam data isn't captured, the rendered output will be ALL BLACK.

    Also, just as important: every SketchUp scene that you initially create (before the Tween Scene creation step) MUST have an object moving and that movement needs to be recorded by Keyframe Animation. I had two Scenes where the cam continues to move forward but I didn't want any animation. When you go to create all your Tween Scenes, they won't be generated for any sequence that doesn't have an object moving because - technically - nothing is happening. I got around this by animated a simple box out of the camera view for those two Scenes.

    I did this very quickly just as a proof of concept, so it's a bit rough. I'd like to get a softer landing (easy ease) for each chair, so I'll try going into my original file (again, 9 scenes) and add an additional scene for each object just before it touches the ground (12 inches or so). You can then set the duration of the animated movement for that scene, and start to get a sense of ease in/ease out. For instance, if each chair takes about 1 second to drop, the last 12 inches could be set to take 2 seconds or so. Nothing crazy, because real ease in/ease out isn't possible. The timing settings in the Extension look to be pretty great.

    There's real potential for this extension, but it will take a bit of patience and practice.

    Link to extension:

    There's some must-watch tutorials on the site, and a nice user guide as well. I definitely plan on buying the license.

    You could also make 3 or 4 different short clips - each with a different color but the same camera movement. Each clip would stack directly on top of one another, and you'd keyframe a fade effect from one clip/color to the next. You could also then use a colored spot light to cast more color under your skywalk...

    Auto updating proxies is a pretty inconsistent feature. I've noticed that the larger the scene, the less likely the auto update will work. The only consist pattern I've seen is that auto updating will sometimes work for a short time after recently opening the file and firing-up Enscape. The longer I work in the file, the more likely auto update will not function!

    Having a new update button would be super handy. Relaunching Enscape from scratch, with large scenes, is a hassle for sure.

    Okay, new development/discovery:

    I previously thought that I had to have the Enscape render window running in order to get the error but that's not the case. It just happened without the render window being open...

    Seems at this point this should be pretty easy error to replicate. Any info, Rick?

    Hey Rick, that's going to be an enormous challenge and just not possible because at this point I have dozens upon dozens of proxy files referenced into my main project. However, I made an interesting discovery which may be of help (or not, lol).

    First, a recap:

    This error seems to happen after I've been doing work in other instances of SketchUp that I have open, or perhaps if I've been doing heavy FBX importing or work in my main SketchUp file. When I close the file and restart, I can once again import proxy objects into the scene without issue.

    Today, however, I discovered that IT'S ONLY SKETCHUP 2021 FILES that will give me the error. When I import something that was saved ages ago with a previous version, it comes in just fine. Even when I save a 2021 file as 2020, I can bring that in without an error.

    So.... I'm not sure what this really tells us but at least it's some new info.

    I just started experiencing this problem last week. I'll be working (on a very light scene, low polys, etc) and my screen will go black and the GPU fan kicks into high gear. I then have to do a force shut down. It's happened 4 times just today....

    Reading this brief thread, I'm not convinced Enscape is the problem - but I do believe it's the trigger.

    I've owned my new Boxx for about 45 days, and everything has performed flawlessly. I've not added any new software, updated drivers, etc. My spec has remained exactly the same. There's been no Windows10 updates for at least several weeks.

    (2) Xeon Gold 6226R 2.9GHz

    128GB RAM


    With that kind of horsepower we can eliminate the GPU or any part of the system becoming overburdened. Everything points to a hardware failure of some kind - most likely in the GPU itself. Software doesn't just magically start causing crashes if absolutely nothing gets updated or changed. However, Enscape has always been running during the black outs, but that doesn't mean Enscape is at fault. Enscape, more than any other process, is going to heat up the GPU. If there's any kind of failure (like eroding or not enough thermal paste), that increased heat will likely trigger the crash.

    I'm working the rest of the day on stuff that doesn't require Enscape. Let's see if I have another crash. I'll report back what I find out for anyone else in the future that might experience the same issue.

    By the way, Boxx customer service has been excellent. They are ready to replace my RTX8000 immediately to eliminate that as a possible cause....