We know OSM is not good
What enscape should do is connect to Cesium and use nearmap or areometrix metromap
or have an import for services such as Context Map
happy to pay for it
and give us at least an option to edit the whole thing
Cesium: The Platform for 3D Geospatial
Guess it would be better to connect to something like Nearmap or MetroMap - MetroMap even if you must pay
it will not make the Open-Source fans happy: try OSM in Australia it is completely useless.
The fact is good 3D information costs Money to create but the more use it the cheaper it gets
so the ability to connect to a different data source would be useful.
same here
Installed Version 8
Placed Assets multiple from the Enscape Window committed crashed Revit and Enscape without a chance to send a report
Tried again just opening the Enscape Window zoomed into view crashed both again
Completely untestable
crashes Revit 2022.1 the moment I place an asset from the Enscape Window
I would not mind it: if this tool would have an option to stop updates in Revit when placing content via the Enscape window
For placing books and other small items I don't want to see in Revit. If there would be a way to add them without syncing to Revit
To me, that would be great
It's possible now to scale by instance from Revit have a look at this link I uploaded a family as well towards the end of the post
I do this for years
Scaling / Nesting / 'Shared' - Revit - Enscape Community Forum (enscape3d.com)
Display MoreBut most experiments lead to nothing, so in your example, more often than not, I will have messed up my preset with no way to undo
I know you can "right click>duplicate a setting and use that for testing, than when you are satisfied relink the setting and delete the old one" but that's very unintuitive and cumbersome.
I was hoping that changing the default behavior of the "new preset" button would take away at least some of the pain of the workflow above.
But since you brought it up: I also struggle a LOT with the auto-save
. The 2.9 version had a superior workflow in that regard (and 3.0 a better UI). It discourages experimentation. It also increases the chances of someone on the team (we share a model with many designers) will accidentally mess up someone's settings.
Rather than auto-save, why not have a save button, and perhaps a warning when you are about to switch to another preset (or close the settings panel) whether you want to save/discard any unsaved settings. You would achieve the same thing as auto-save (not accidentally losing any settings) while giving users an options to experiment/make mistakes without irreversible damage.
I did a small training yesterday on the Enscape settings and polled people on whether they preferred the 3.0 or 2.9 handling of presets. Although the UI of 3.0 was preferred, all 5 people preferred the explicit save of 2.9.
It's also important to note that Enscape doesn't exist in a vacuum. People have gotten used to certain software paradigms because they exist in so many other programs. Many programs that we use has the concept of 'presets', but almost all of them have the option to save/cancel changes to them.
I fully agree with Pieter; my Users are endlessly confused about how the new presets work
Auto-magic is not always the better solution. Give us a sense of control
If we can't work it out easily and it's not apparent what is happening it is not a good UI
looks like you're Enscape Library is not connected or right path or you're offline Library is not fully downloaded
Happened to me as it takes a long time
I'm wondering whether Enscape Materials for Revit is going to support only Legacy Generic type materials? Or is it planned to support the new PBR shaders?
I ask this because we want to migrate to Enscape Material Editor and all of our materials were created with Revit PBR Shaders (not the legacy ones) and for now Enscape seems to support only generic legacy materials.
Same for us we moved with Revit 2019 to PBR shaders
hope this will be next as far as I know Enscape does support also glTF supports now more advanced shader features
New glTF Extensions Raise the Bar on 3D Asset Visual Realism - The Khronos Group Inc
:thumbsup: :thumbsup: :thumbsup:
saved my issues with crashing the Lot when running over GPU RAM Limit
Great Job
Hi oolaef
I do the same type of instance conversion as you described
I think you may be trying too many tricks at the same time
If you want the tree to be Type and the Grate Type as well but independent
Simply nest the shared Grate family but don't link those parameters at all
you can change the type size by tap selection the Grate and then change the type or change the type in the Project browser.
This is normal shared family behaviour
We need our trees to be Instance for Width and Height and a few more parameters and then it gets far more complex
I attached a tree and grate just taken from the Escape Library and this should just give you what you want
Hi oolaef
I had to rip your tree a little apart as it was overconstrained when changing to Instance
Also, the nested family had an issue
But this works now on my comp
Hi oolaef
I cant share our tree regarding IP as it virtually can make a cup of coffee
But happy to have a look at you're family if you share it here
Hi oolaef
It works also as a linked Instance parameter
But you must trick the nested shared Family with an extra parameter.
Shared families' parameters turn into type parameters by default like in groups
If you link them directly nothing will happen
But linking them by an intermedia parameter does the Magic
see the below screenshots you can control them completely independent or link them via a formula
Make the Lantern shared add an instance parameter "EnscapeHeight" add EnscapeHeight as Formula
to Height then nest into Tree Family and create New LinkedAssetHeight Parameter and link the Nested EnscapeHeigth Parameter to it.
Now you can control both scaling independently
and you don't need even a nested Planting Family in this case I changed it to a Lighting Family, and I can still control the height of both independently.
Having said this working with shared families can be very confusing for new Revit users.
Therefore, I do try to avoid using them when I have other options. For instance, if you must deal with Phases then this quickly becomes a liability.
As said, we use 2 Dynamo Scripts one to Place a Family at the same place as the tree and another one that will move a family based on the tree location
Hi oolaef
It is possible to have nested elements in Revit Families and control the Height/Scaling independent in Enscape
The way you gone about it will not work as you nested two Meshes and Revit will see them as One and not scale the Mesh separate
But you can add a simple Revit Family with Revit Geometry controlled by the Height Parameter and link whatever Enscape Asset you want to It
then select the shared nested Family and adjust the Height and the Enscape Asset will scale separate from the Tree
I just attached a quick mockup nesting a Person into my Tree Family
the Person does not scale in Revit because its a mesh and not nested
That's why for something like a Tree Grate, make a quick parametric Revit family and add the Enscape Parameters.
But on a different note, we had the same discussion hers but decided to place the Grates separate with a quick and simple Dynamo Script
that gives us more flexibility.
My experience was similar to Herbo's with running at the memory limit.
I did not have time to test it again but avoiding Out of Memory issues or even crashes as in my case is really important when sharing with clients where you don't know on what kind of comp it is played back.
Great additions very much appreciated
But I had some horrible crashes with scenes close to my 6 gig limit of my RTX2060 it crashed Revit as well wit5h no chance to sent a report.
With smaller scenes, I had no issues.
One thing I missed was a way to selecting elements that tell me what material is used like the BIM feature just for Materials only
the new view switching is far too slow
agree with others
+1 I get many requests
