It's the Ambient Brightness Slider, right? The default is 50%, but turning it all the way up to 100% will eliminate ambient occlusion (or turn it down significantly). Personally, I usually go the other way, turning Ambient Brightness down to like 10% or less because it makes the shadows and contrast feel more realistic on interior scenes. The default is washed out and lacks definition. It will make the scene much darker overall, but you can turn up the exposure or artificial light brightness slider to bring it back within an acceptable range.
Posts by TowerPower
-
-
Although I personally don't mind how the current release works, I do have sympathy for Herbo's (and others) concerns.
Perhaps part of their frustration is that what they are proposing (keep the settings in the render window but don't start the renderer automatically) seems like a good solution, without compromising on the advantages of the current design of having the settings integrated in the frame buffer. It also (perhaps wrongly) sounds like relatively simple to implement. But maybe it's waaay harder than it sounds, and is that also part of what's holding you back?
It's been awhile since I've used it, but I believe this is the way Thea Render worked. The full render dialog box would comes up every time, but it would only begin rendering if you wanted it to. This made sense and was necessary for a non realtime renderer, but I think the same principle could apply with Enscape. If I had to guess, the vast majority of Enscape users won't have a problem with the way 3.0 is setup currently, but a loud and frustrated minority will. Most of my models aren't large enough to present an issue, but I've had some in the past that are, for which I've had to turn the render settings down and switch to White mode in order to get the model to load succesfully. It's a real issue and deserves attention. It seems to me it would be easy enough to add a check box, similar to the RTX dialog now, which you turn off if you don't want Enscape to automatically begin rendering on startup. Most users will never mess with it and it will continue to work just as you've designed it. For the small minority that do need it however, it will ensure Enscape continues to be functional. Win win.
-
-
Not really, Placemaker doesn't use Google Earth's data. They use 2D and 3D data from Nearmap.
You have to pay because Nearmap provides a paid service, accessing their data is not free. And I guess Mind.Sight.Studio probably takes a small margin on top of it to cover their own costs as well.
Interesting, I guess I didn't realize the degree to which the two services are distinct from one another. This quote from their CEO seems to explain it well.
-
Very cool, nice work Herbo! Extracting photogrammetry data from Google Earth has long been a wish of mine, and I'm glad to see there's finally a practical way to do it.
Has anyone else seen the new 3d Textured Mesh Cities option from Placemaker though? I believe they must be using a similar process to yours to get the GE data into Sketchup. The catch is you have to pay for it and it only appears to be available for North America and Australia at the moment. Given how involved the import process is though, I could see it being worth it for a lot of folks. They have a price estimator if you scroll to the bottom of their page, around $200/ sq. kilometer, which isn't bad unless you're trying to download a whole city...
https://www.suplacemaker.com/3d-mesh-cities/
-
Add my upvote for high quality vegetation assets. You've made some great additions to the library over the past year including the many potted plants that were included, but the number of exterior trees and plants remains rather limited. The Evermotion ones are in general pretty high quality, we just need more of them. And ditto for the advanced grass system others have mentioned. Skatter is nice, but it's not very practical for larger site models, so the more things can be automated, the better.
-
I'm sure it's possible - other companies such as the Wild already support the Quest, but with very basic graphics (think Draft mode in Enscape) and a fairly limited model (polygon) size. The Quest 2 is much more powerful than the first, so I'm sure the supported size of models will go up significantly now.
-
Great suggestion, I run into the same thing as well.
-
-
Hi Gwengosch, it sounds like even using the Oculus debug tool to manually increase the resolution, the experience still isn't the greatest.
You can see the comments from people in the thread here:
-
I agree Thanh Chuong , in my opinion enscape glass and mirror materials are far from perfect.
Sounds like a good use case for RTX! Clemens Musterle, there are some great ideas in this video. The caustics performance enabled by RTX (as well as DLSS 2.0) is seemingly very impressive. The visuals speak for themselves. With the 3000 cards out now I'm guessing it won't be long before more than half of Enscape customers own RTX cards. I know you don't want to make hardware specific rendering features that folks on older cards can't use, but HW accelerated RT is the future so I wouldn't hold back just because a few folks won't have all the bells and whistles in the meantime (AMD have their own hardware accelerated ray tracing cards coming out soon as well, although with less than 10% of market share, they're not really a big factor either way).
-
Pretty darn close I'd say, you'd be splitting hairs to choose a favorite. Shows the huge progress realtime rendering has made thanks to Enscape.
-
@Gwengosch Apparently the cable solution hasn't been updated by Oculus yet so it's still using the old, lower resolution of the Quest 1. If you search around on reddit r/oculus you'll see there's an option to manually set the resolution at 3600 px (can't remember the exact number so you should check) which should hopefully fix the problem.
From the sounds of it though, people have been getting better quality just by using Virtual Desktop and their home wifi network assuming you have a really fast router hooked up directly to your computer. Both of these solutions should be further optimized in the coming weeks. The much more powerful hardware on the Quest 2 promises better compression quality.
I'm still on the fence about getting a Quest 2, but with basically doubled resolution over the Rift S (3.5 mp vs. 1.8 mp) coupled with the ability to go fully wireless, it's extrememly tempting. If only I hadn't just watched The Social Dilemma (Netflix documentary) and wasn't freaked out about how we're all being brainwashed by Facebook and others (and the entire fabric of society imploding) I'd be much quicker to jump on the bandwagon. Demian Gutberlet, is it true the new Quest isn't available in Germany due to the requirement to log into a Facebook account? I've heard people have been getting them from France instead.
-
-
Interesting, I hadn't noticed that yet either. I agree it was a great feature and wish it hadn't been abandonded, but perhaps it's hiding somewhere like you say.
Was there a reason for eliminating this?
-
Thanks!
Appreciate it Demian, it's really a joy creating videos with Enscape, especially when using a space mouse for navigation, which gives you much more fine grained camera control. My one complaint (and this isn't necessarily specific to videos) is that preserving settings is still a bit of a mystery to me. The video editor allows you to store field of view, depth of field, and time of day, which is great, but when it comes to a host of other visual settings such as clouds, wind, bloom, etc, those presumably are stored elsewhere. I guess I just need to look into the newly revamped settings management in Enscape (perhaps creating scenes in Sketchup will do the trick).
But regardless, it's still frustrating to me (and seems counterinuitive) that when you open a Sketchup model you last worked on a couple months prior, Enscape doesn't automatically remember the visual settings you used then. Instead, it inherits them from whatever the latest copy of Enscape you had open was, even if it was with Revit or another piece of software. I'm sure there's still a way to save them, but it seems like the most obvious and user friendly way to do so would be for Enscape to automatically remember them anytime you save your model, rather than forcing you to do so manually. The manual save option is important too if you want to have multiple different scene setups for a single file, but it should be in addition to the automatic save option. It's common for me to have multiple copies of Enscape open simultaneously, and it's frustrating that settings don't get remembered automatically within each project.
Demian Gutberlet I think I've located the new settings functionality (link below). In general it makes a lot of sense, but I still feel like you shouldn't have to do anything other than save your model file for Enscape to rememember visual settings. Forcing people to go into the presets tab risks they'll forget to do so after making changes, or not even be aware of the presets tab in the first place, as I was. The general principle of software should be to do as much for the user as possible automatically, and then only require manual action when necessary. Unless there's a compelling reason not to save visual settings automatically for you, I don't see why this wouldn't be a default.
It's akin to if Sketchup were to revert to the basic visual style every time you reopened a model (or actually, in this case, whatever visual style you happened to have in the last Sketchup model opened). Is it possible to manually save scenes in Sketchup and remember style settings? Yes. But should that be necessary to prevent them from reverting to the look of some other random model you had open previously that bears no relationship at all to the one you're working on currently? Obviously not. In my mind, this is where Enscape still falls short.
https://enscape3d.com/communit…tings%20icon%20has,the%20
Edit: feel free to move these comments to the 'Enscape Settings' thread under Ideas and Requests - it's obviously a bit off topic here.
-
Did you altered the grass with the Herbo trick?
Nope, just standard Enscape grass, though I did use a larger aerial image for the texture to give more natural color variation.
-
That closing shot... Great work.
Thanks!
TowerPower , great work indeed! The video turned out fantastic too.
Appreciate it Demian, it's really a joy creating videos with Enscape, especially when using a space mouse for navigation, which gives you much more fine grained camera control. My one complaint (and this isn't necessarily specific to videos) is that preserving settings is still a bit of a mystery to me. The video editor allows you to store field of view, depth of field, and time of day, which is great, but when it comes to a host of other visual settings such as clouds, wind, bloom, etc, those presumably are stored elsewhere. I guess I just need to look into the newly revamped settings management in Enscape (perhaps creating scenes in Sketchup will do the trick).
But regardless, it's still frustrating to me (and seems counterinuitive) that when you open a Sketchup model you last worked on a couple months prior, Enscape doesn't automatically remember the visual settings you used then. Instead, it inherits them from whatever the latest copy of Enscape you had open was, even if it was with Revit or another piece of software. I'm sure there's still a way to save them, but it seems like the most obvious and user friendly way to do so would be for Enscape to automatically remember them anytime you save your model, rather than forcing you to do so manually. The manual save option is important too if you want to have multiple different scene setups for a single file, but it should be in addition to the automatic save option. It's common for me to have multiple copies of Enscape open simultaneously, and it's frustrating that settings don't get remembered automatically within each project.
-
Thanks for the feedback. I attempted to load it up gradually and believe the culprit to be a ceiling panel file (the ceilings across 6 storeys are broken up into several thousand small panels! 😬). I managed to get everything loaded and saw it briefly in the Enscape window before it crashed again.
I’ve requested the standalone from the Architect so I can circumnavigate the problem. Wasting too much time on loading and continuing my hate for all things Revit! 😂As for that Titan...🤔
Glad to hear it's working finally (hopefully). As for the 'Titan', I wouldn't bother with anything less than the newly released 3080 or 3090 cards (the latter being the 2080ti or Titan equivalent this generation, though it's possible they could release an even faster variant in another year or so and call it 'Titan'). As of now though, the 3090 will knock the socks off of any Titans, and comes with 24 GB of VRAM to boot ( the cards appear to be around 50% faster than their previous generation predecessors, even more so when you start factoring in RTX performance).
-
This is a chapel concept we did a few months back that I just recently made some improvements to (such as wind in the trees now). I've included still images below, but the video gives the best overview.
PS - There's a bonus clip if you watch till the end
