+1! Very important and logical improvement.
I also think the projection mode (perspective/orthographic/two point) should be part of the view, not the preset.
+1! Very important and logical improvement.
I also think the projection mode (perspective/orthographic/two point) should be part of the view, not the preset.
am I the only one who finds it incredibly impractical? same with the "perspective/orthogonal and 2pt perspective" switch
Nope everyone I've worked with had the same feeling to be honest. It's been remarked and proposed many times on this forum but unfortunately it's still not on the (public) roadmap to change this.
I'm familiar with Revit phasing and partly familiar with Design options - switching between various 3D views with different phased elements visible updates correctly in the Revit view, but Enscape does not change, it displays only the view that was active when Enscape was started.
Hopefully I'm missing something simple
Once enscape is launched, you can open the view list in the Enscape render window (hotkey: F) and select another view that you want Enscape to load the geometry from. Just make sure the 'geometry update' slider at the bottom of the view list is on. If it's off, Enscape will only move the camera and sun to match the newly selected view, but the geometry will still be tied to your launch view (it was added to make fast camera switching possible without the need to reload geometry when switching views).
You need to make a shared (public) link to the panorama on the enscape web portal.
I wonder which Nvidia drivers work the best with Enscape: the 'game ready' drivers or the 'studio' drivers?
I checked the knowledge article on the Enscape website, and it doesn't mention about that: https://learn.enscape3d.com/bl…ommended-graphic-drivers/
Which drivers do the Enscape developers use? Because I want to use whatever you guys are testing with
but frequent amount of crashes are not normal
Fwiw: we've experienced more crashes with every release since 2.9, with 3.4 being the least stable to date. We're trying to report issues as much as we can, but we rarely get any further then 'upgrade your driver and reinstall enscape'. It's very time consuming for us to play that game every time, so we often just give up trying to get to the real root of the problem.
I have to admit I often have a feeling that new releases aren't fully QA/QC'd on large (Revit) models. The sample models you made are great for promotional purposes, but real world projects are often an order of magnitude larger/more complex.
I just submitted my logs. I can reproduce this is a file with only a single wall so I don't think it's tied to a heavy scene.
I can reliably reproduce it in both Revit 2022, 2023 and Sketchup 2022.
When I launch enscape, and change the time of day (shift+rightmousebutton drag), Enscape freezes for +20 seconds (sometimes a full minute). After that Enscape wakes up and I can start changing the time of day. Subsequent time of day changes are faster.
Tested in Revit 2023 and all Enscape 3.5 preview versions.
I cannot give a specific release date yet, but you can expect our full release of Enscape 3.5 in about 2-3 months. Beforehand we'll release further previews as well of course.
I hope that we will have enough opportunity to test the new 'asset override' feature before the new version is released. In the past it happened that a major feature showed up in the last preview release, only to be released a few days after.
If you have the asset projects (.assetpkg files) you could combine the libraries by
1) making sure your export path is set to the new library (in the enscape asset editor, click "configure" and set both paths to the respective folders for your 'merged' library
2) now click the button "import project", select the .assetpkg file of one of the asset you want to add
3) now you can make edits to the asset and/or categorize it. The changes will be saved in your new 'merged' library only
Right click on the appearance tab and click "duplicate as generic". That will convert any non-generic appearance tab to a generic one. Then they will appear in the Enscape material editor.
Revit – Improve Revit Worksharing Integration
Previously, when using Revit Worksharing, you would have to synchronize with central when changing the currently active preset. Now, syncing to central will only be necessary when you have made changes to the views or the visual presets. This improvement only works when using Enscape accounts.
Why does this only work with Enscape accounts? That adds a huge overhead on our side to set everyone up with an account and make sure everyone is properly signed in.
Edit; I see this is already released as an official pack. Although I appreciate the urgency but what's the point in releasing a preview release and than releasing it officially before anyone has had the opportunity to provide feedback?
The tutorial you linked to is really outdated. The most up to date version you can find here: https://blog.enscape3d.com/con…08ee989607ec0d67392abacbe
In it, I cover the process of preparing an asset in Blender to be imported in Enscape.
how to bring the textures, hair/fur, tutorials, etc.
In the video I touch on the material system. Enscape does not support fur (nor do the formats that you can import in the enscape asset editor really). You would need to create the illusion of hay bails through textures, which is probably fairly doable as long as you don't get too close.
Is the only way to bring/assign textures for custom assets on Enscape is using the custom asset editor (or would be possible to import the final model without any extra changes)
You will always need to go through the Enscape asset editor, but in theory you could set up your model perfectly in blender (including materials) so that you don't need to do any work in the asset editor other then filling in the name, clicking render (to create the thumbnail) and hitting save. Do keep in mind that not every type of material that you can create in Blender will be supported in Enscape.
It would be really helpful to get a saturation slider for textures. Also, it would be helpful if the brightness slider would work in both directions (so we can also brighten textures, not just darken them).
Pieter, based on your experience, if you were on our shoes, would you upgrade?
It's a tough decision. You'll need to take a look at the release logs of 3.0 through 3.4 and decide whether the new features are worth the (very serious) issues with worksharing. Perhaps also worth noting: the latest releases seem to be less stable for us than the older 2.x series. We are definitely experiencing more crashes.
We are using the latest version because the combination of these new features makes it worth for us:
- the "safeframe" toggle
- the ability to edit camera and sun position of existing views
- the enscape material editor for Revit
- custom asset categories
- better reflections
But this list is personal and it will depend on how you guys use Enscape. It also depends on how many people you typically have working in a project. If you only have one user working in Enscape concurrently, the worksharing issues aren't going to be a big deal. But if you have multiple users simultaneously trying to work in Enscape, it's...real bad.
I agree. Luckily they are working on it! See https://portal.productboard.co…g1/tabs/18-in-development
I have only seen this a couple of times. I have no clue what the cause is though, but would love to known. Demian Gutberlet do you have any idea what might be causing Phil's saving error?
How did that do the trick, exactly?
Could anyone give a step by step tutorial on updating existing views in Enscape and save them in Revit?
thank you
Editing views was edited in Enscape 3.4 so make sure you have that version (or newer).
From the 3.4 release notes: "Go to View Management, select the edit icon next to the view you wish to amend, and easily change the name, visual preset, camera position using the mouse, and the sun position in one place."
The "view management" is the binoculars icon in the top menu bar when you are inside the Enscape render window.
I've seen this issue a couple of times. It required restarting Revit & Enscape and then things showed up again.