More styles of 3d grass other than the default now (like Lumion offers) would be awesome.
Posts by TowerPower
-
-
Image 14/15 are definitely unfortunate, I'm guessing that's a result of multiple reflections, which is an issue wherever two mirrors meet at a right angle. Not sure there's an easy solution though, it may just be a fundamental limitation of realtime raytracing right now.
-
The asset library is cached locally. The first time you open it and something changed it needs to be downloaded. After that initial wait it should open rather quickly. Are you experiencing the slow load on consecutive uses?
I see what you mean now, but would still say it could be a lot better. The simple fact that it takes so long to load the first time is a deterent to users, as it was for me. It makes people think it's going to take that long every time, and maybe not worth using at all. As John Carmack would say, it's too much friction. With the power of today's machines, I see no reason why it shouldn't load instantly.
-
I agree, the new assets are great, though I'm still hoping for more hi-quailty vegetation (the ones from Evermotion are really nice, there just aren't enough).
My main complaint though is with how long it takes the asset library to load. Is there a good reason for this? Perhaps it's because they're all being stored online and need to be downloaded each time, in which case I think the hold up is on the Enscape server end, since our internet connection is quite fast. Maybe you could store the image previews on our local machines at the very least, that way they load right away? As it stands currently, it takes several seconds for them all to appear. It's quite frustrating.
-
It would still be useful to have the correct controller models show up in VR though. I found some here: https://3docean.net/item/oculu…with-controllers/23765771 (though it seems like the sort of thing that should be provided with Oculus's SDK as a developer tool).
-
I get the same result with the Rift S, and am thinking it may have to do with the controller model still being from the old Rift, with the band on the bottom rather than the top.
-
More realistic realtime clouds are definitely doable, it's likely just a question of resources. https://kotaku.com/the-clouds-…truly-next-gen-1726461687
Right now I'd say the lighting is quite realistic, it's the repetitive shapes that are unconvincing. Are there procedural cloud packages you can license or purchse for use in Enscape? No idea how that works...
-
Sorry to disappoint, but RTX based ray traced shadows are currently not in development. That's a feature that might come some time in the future, but RTX integration right now is basically a replacement for our existing path tracing implementation that does reflections and indirect lighting, but with better quality.
Here's hoping shadows make there way into the list of RTX features next, especially since it sounds like that's one of the areas where ray tracing can actually outperform rasterization (ie. not only more accurate, but faster as well).
-
It's also worth noting that at GDC a few weeks ago, Nvidia announced that it would be turning on RTX support for a select number of 10 series cards, meaning Enscape could support them too. The major caveat of course is that since the Pascal series lacks the dedicated raytracing cores of Turing, they're orders of magnitude slower, so performance will likely be too low to be acceptable for usage in real time, but perhaps they can enable it for still renders only.
-
Guys, I understand that you might not have the material editor ready for ArchiCAD just yet but why are we paying the same price for a product that clearly doesn't function equally with other versions?
As Damian Gutberlet said "but since ArchiCAD is our newest integration, it is currently not as "complete" when it comes to some functionalities"
To be fair, the same has held true for all the software implementations since Revit. Sketchup didn't have a material editor for the first several months when it was released, yet we paid the same then. Rhino didn't have a material editor for the first several months when it was released - yet we paid the same then. If fairness is what you're looking for, we've all gone through the same thing (or looking at it another way, we've all been treated equally unfairly
). I understand it's frustrating, but they can only move so fast. And the truth is we're all paying for the same thing. This isn't V-ray with dedicated plugins for every piece of software. We all get access to Revit, we all get access to Sketchup - the fact that we choose to use one software over another is our choice, but Enscape is still a holistic package offered to everyone the same. -
TowerPower
I just want the functionally that has been promised and paid for, bring all of the plugins up to the same standard BEFORE releasing new features is my main gripe. I understand that the developers cannot satisfy all user requests and i am not asking for that, but selling me an incomplete versions for the same price is just wrong
JUST UPDATE IT SO WE HAVE PARITY nothing more nothing less
I feel your pain - I'd be frustrated if that were the case too. There was a time not so long ago when Sketchup didn't have a material editor either yet Revit did. Sketchup folks were clamoring for Enscape to release one, and while it took awhile, it was worth the wait when it finally came out. We were paying the same price then as we are now for less features than Revit, just as you'll still be paying the same price when they release a material editor for ArchiCAD. I suppose the alternative is they could simply have not released an ArchiCAD version at all, and waited until they had time to develop the material editor, but would you want that either? Last I heard Enscape had over 30+ employees, so chances are there's someone working on the material editor currently. And while it's nice to think that if everyone at Enscape dropped what they were working on currently and just focused on that it would be done in no time, I'm not sure that's how things actually work. Too many cooks in the kitchen, as they say. Things take time, and you can only accelerate them so much.
Full disclosure - I haven't been following the developments with ArchiCAD closely, so it's possible I'm way off base here, but I suspect it isn't going any slower than it did for any of the other software.
-
I've noticed this is a common theme with pretty much all pieces of software today. The die-hard users (ie. those speaking out on the forums) are never satisfied, no matter how much is being done to develop the software, and there's always something that doesn't work or needs to be implemented. It never ends. Humans are great at taking things for granted. In my opinion, Enscape is near the top in terms of quick development cycles and responsiveness to user requests, much better than most companies. This doesn't mean we shouldn't keep requesting things and advocating for improvements, since we all want to see Enscape get better, but I get the impression you all don't appreciate it as much as you should. I think the new asset content is great and worthwhile, and while they haven 't released it yet, they've also been working on RTX implementation, which in my own biased opinion eclipses all of the requests above
I'd love to see displacement and rounded edges too, but understand that not everything can be done at once. -
so u will bound your software with specific hardware ?
It already is bound by specific hardware; older/weaker graphics cards won't run Enscape at all, and for VR they recommend a 1070ti or higher.
Granted, I understand your concern. There are a relatively small number of RTX cards out there at the moment, and they're expensive. To make Enscape dependent on them to do certain features seems unfair to all those who don't have access to the cards. Unfortunately, with a disruptive new technology like RTX, sometimes that's the price of progress. I applaud Enscape and others for taking advantage of the new features now, which in turn should lead to greater adoption of dedicated raytracing hardware in the future (hopefully offered by AMD as well).
That said, from the sounds of it, you may still be able to do most of the same things on older cards like the 1080ti, just at lower speeds and/or lower fidelity. As Thomas explained, Enscape already uses raytracing for a number of features, and is one of the only real time engines that supports path traced global illumination. They've been able to accomplish many of the lauded features of RTX even without dedicated hardware for a couple years now. This will just make it that much better!
-
Micha RTX will bring little performance improvement to VR as the pure ray traversal in VR is not the bottleneck.
TowerPower Internally, we also use a super high quality reference path tracer. But these reference path tracers lack any tricks and hacks (hence reference) and therefore they are a few hundred times (at least) slower than Enscape. Does not make sense to release it. But we intend to move at least the Ultra configuration very close to the visual quality that the reference provides.
Thanks for the explanation Thomas, that sounds great. Regarding VR then, it sounds like there will be no improvements to framerate as a result of the RTX cores, but since ray traversal isn't the bottleneck in VR, are you then saying you'll be able to turn on RTX features in VR with no performance hit? If so, that's incredible.
One other benefit I'm curious about is light leaking. Given that raytracing is very good at calculating occlusion (for shadows, ambient occlusion etc.), is light leaking no longer going to be a problem?
-
Looks like Unreal just officially released 4.22 with RTX support: https://www.unrealengine.com/e…real-engine-4-22-released
It includes a number of raytracing features such as soft shadows, reflections, ambient occlusion, refraction, and global illumination. There's also an interesting inclusion of a full path tracer, that they say can be used to test ones lighting against ground truth images. Makes me wonder whether Enscape might be able to have a similar option to be able to crank up the number of indirect bounces when rendering out still images and videos, for a little added realism (though only if it was going to take a few more seconds, not minutes, since that would be antithetical to the whole real time render thing).
Either way, I'm really looking forward to trying out the new experimental RTX features now that 2.5 is out! I'm also curious whether any of the performance enhancements will carry over into VR.
-
Looking forward to trying it
-
Lumion has this feature already, so it's definitely doable for real-time applications. Unlike in Corona however, Lumion doesn't actually modify the geometry at all, it just fakes it via normal maps (I think). It's quite effective still though, and really adds a ton of realism.
-
It started working again, yes. It's been so long now though, I don't remember how. I think they (Oculus) fixed the issue, since it was something a lot of people were having difficulty with at the time.
-
You should already have my upvotes from an earlier thread than this one, but just in case, here's me voting again
Hopefully this topic can find it's way to the top of your priority list in the near future... it's been languishing for awhile and really is important.
-
That's exactly it.
