Posts by Hans-Sen Hoefer

Aw man, you're too kind. I'd show you the way to the MRT but all snack bags are MINE.

Last suggestion; consider a less detailed model for the walkthrough - most people won't notice the small details unless you point it out to them, there's too many elements to process. For the extreme details, static will always work better - the feeling of having to rush through and see everything isn't there - I mean it's called a walkthrough for a reason. You could probably present the walkthrough, point out scenes that they should take note of, then follow up with static shots depending on the client and their interest. Just a few thoughts to think about!

Hans

Herbo ; If the 1.4gb model size sounded unusually large - it was! I mentioned consolidated and largest I'd ever worked on, and that includes ALL the textures and accompanying mipmaps which were tasked between 6K-8K output, rendered via Maxwell. One off feasibility study that was conducted for a recent high-powered tech venture here in Singapore. Needless to say, individually building and texturing 85 floors with a team of 24 others was a great self-feasibility study in how to lose focus quickly and know exactly where the purge_all script button lay on your workspace.

Namrfb ; Proxies are definitely one of the top optimizations to speed up and lower overall project file size. I previously asked what kind of detail you were working towards, and if you were building as realistically as possible - like the approach a carpenter may take to building a piece of furniture. If that's the case, you're adding a lot of micro detail that you won't necessarily see, but you'd definitely feel in a very short space of time. All that detailing and texturing is increasing your polygon count, and if that's the approach you're taking - you need to be working with proxies as Herbo mentioned.

It'll change your entire workflow for the better. If you right click on any component, there's an option to save as external model for Enscape. If you want to make any changes to the object itself without reloading the component within your model, open it in another instance of SketchUp and save it under the same name. To update the changes in your master model, you can either right click on the proxy in question and choose reload component or reload all changed components. If you don't want to reload the proxy as a component, you can left click it, go to Enscape's object creator and select the proxy tab if isn't selected already and re-link the original file with the edited proxy file.

Talking about components, you need to use components whenever possible. My rule of thumb is if there's need for more than one instance of said object, it needs to be a component. Those components should all go into a group and not the other way around. Multiple instances of the same component are only instanced once, whereas non component groups are instanced whenever they're used. If you knew all this already, apologies in advance! It's something that is commonly misunderstood, and could potentially save you a lot of time and subsequent effort.

Best,
Hans

Sounds like an incredibly complex, slow performing townhouse. You may want to consider separating the ground floor from the first and saving each as different models. Essentially becoming two individual models and two separate walkthroughs, cutting the project size in half, or near there hopefully. To be honest, I've never heard of or seen a model this heavy, at least when compared to the volumetric size of an average double story townhouse. The largest model I've ever worked on was around 1.4gb consolidated, was never edited as a singular model and had 85 storeys at 200,000 sqfpf. Do you mean 90 mb?

Are you modeling everything 'fully' (as in real world realistically) and that everything be accessible in one walkthrough based on client needs?

Quote from Gadget

I get this on almost every model before I'm finished with it: sometimes turning off and on [live updates] fixes it, sometimes clicking on the [start Enscape] button to re-load works, sometimes I have to close Enscape before clicking on the same button. And sometimes I have to close and re-open SU.

On some rare occasions, the Enscape materials editor shows "Missing texture" and it has to be re-applied.

The origin of the bump channel is tied to the location of the original map (I think), but it can be scaled by clicking on the tab at the top of the enscape material editor and ticking the [Explicit texture transformation] check box. (I've asked before, but it would be really handy to position the origin and rotate the individual materials within this dialogue.)

Gadget @omiKron-arh ; Have you tried separating each bitmap file by sub-folder, i.e.; 0. Triangular_Wheel. 1.Original / 2. Bump / 3. Reflections etc. I'll give that a shot. Somewhat of a pain in the ass to implement, but well worth a few extra minutes prep time if it works.

Not really a big issue but occasionally the material editor confuses the bump / roughness maps with other materials in scene. I usually have to delete the entire texture via the editor and reload the original. This happens when I run the purge all command. It's not a big problem but it cuts into creative momentum. Anyone else experience similar?

Best,

Hans

You can right click on the proxy object and select either 'reload component' or 'reload all changed components'. That is if you edited the proxy file in aanother instance of sketchup and saved it in the same folder under the same name of the original proxy file. I hope that's what you meant. Still good to know in any case. Saved me alot of time when I figured it out.

Best,

Hans

Hey Nirmala,

1. Are you using a HDRI skybox? Or the standard lighting that comes out of the metaphorical box with Enscape?? Get a good HDRI during sunset or morning. You won't be able to change the time of the scene via the normal shift + right click hold and drag.

You'll have to adjust sunlight angle manually via the rotation option, and intensity of sun / stars and moon. I find starting at a low sun intensity or even at 0 and then working up to desired effect is most useful.

However, don't depend solely on this to light your scene, just use it to set the ambiance. Utilize the exposure controls to adjust overall brightness after figuring out your sunlight etc.

Also couple this with step 2 to enhance dark areas that just aren't covered in sunlight or exposure.

2. Make sure you utilize emissive lighting for interior lights ie transparent light bulb , as well the usual point box or spotlight. You can also use a rectangular plane wifh emmisive properties to light a scene like a soft box. It will shown up in reflections however, so I usually only use it with little to no glass around. You can also control emissive brightness by alt+left clicking the material with the paint bucket tool, and adjusting the luminance slider in the material editor.

3. Try to break up then light entering the scene. Put a couple trees or plants outside an exterior window, add some shadow to the interior scene. Really helps improve the overall ambience and can really add more depth to complex textures. See my post in "material realism test" under the showcase topic and scroll down until you reach the concrete and wood corridor. I varied tree height and rotation outside all exterior windows to give me some soft shadows and it made the scene.

Let me know if that helps - I was planning on starting a tutorial / walkthrough series on YouTube if I have the time. There's a bunch of other things, but see how that works out for you.

Best,

Hans

I'm running a Predator Z35 GSYNC ultra wide at 200 fps without any problems as a single monitor setup.

I initially was using two of them but had some issues with slow performing instances of Revit 2018 and Sketchup. Which resulted in lots of crashing and bugsplats, and many phone calls with nvidia, auto desk and trimble. A system engineer with nvidia finally suggested single monitor.

It actually enhances my workflow, and is really immersive. The only thing would be resolution, and gpu power. Currently running an i7700k at 5 ghz (OC), 64 gb ram and a gtx 1080 ti with 12gb onboard ram and an 960 Pro SSD (which i find is crucial for smooth performance).

Overloaded build but I work with multiple programs open including substance designer and chrome - just nice to have that 64 gb overhead to handle open apps. Hope that helps you. You can check out my renders in the showcase topic - all taken on the z34. Excuse any errors in grammar, on my mobile.

Best, Hans