I was under the impression that the “Display Revit Objects, Filters and Elements” setting also applied to linked models, is that not the case? Tried a quick search to see if it’s a known issue but similar results were years old or unrelated.
See attached (crude) screenshot; in Revit the linked building model is overridden to be green, and so is a loose furniture item in the model natively. When shown in Enscape though the override doesn’t display for the linked model. It correctly shows the furniture item in green though, so the setting is clearly working, just not for the linked model. We’re using Enscape 4.18.2 LTS.
Thanks for reporting this. The “Display Revit Objects, Filters and Elements” setting should also apply to linked models. However, there are some limitations around how Revit display overrides are handled.
Currently, overrides from linked models are supported when using the standard Revit display settings, but they are not supported when using the Custom Display Settings option. Additionally, accurate display of overrides for nested links is not supported at this time.
Could you share a bit more about how you are building the filtering setup?
This will help us confirm whether the behavior you are seeing matches the current limitations.
In the original scenario the linked model did indeed have Display Settings set to ‘Custom’, however, this was purely to switch off visibility of specific model categories. Within the ‘Custom’ settings window the option for ‘View Filters’ was set to , so the actual overriding of surface colours wasn’t being handled by the Custom Display Settings.
The 3D view in Revit has a filter that is targeting all elements not on our Workset (i.e. everything in the linked model). Surface patterns are overridden to be solid green as shown.
I’ve opened the file again to test and have removed the custom Display Settings for the link. It’s now set to By Host View as normal, the Revit 3D view continues to show everything in green as directed by the filter. Relaunching Enscape though and there is still no effect in the Enscape rendered view.
Thank you for the detailed explanation - that helps clarify the setup.
Would you be willing to share the project file with us so we can take a closer look? Our internal tests haven’t revealed any issues with this behaviour, so reviewing your specific case would be very helpful in verifying what’s happening.
I’ve recreated the issue in a very simple project and attached, let me know if there’s a better way to get the files to you though. The .zip contains:
LinkedModel.rvt - a workshared file with a wall and floor on the default Workset1
MainModel.rvt - a workshared file with some furniture on a custom named workset “MainModel_Workset1”. The LinkedModel is linked in.
There is a filter that looks for elements not on “MainModel_Workset1” (i.e. everything in the LinkedModel file) and overrides them to be green. There is also a filter for the Piano family, also overriding it to be green, purely to confirm that Enscape is attempting to display the Revit view filters.
When viewed in Enscape the piano is green, the linked file is not.
It appears to be something specifically related to when the filter is using Workset Does Not Equal “X”.
If I use WorksetDoes Not Contain “MainModel_Workset1” then Enscape correctly displays the override. If I use WorksetDoes Not Equal “MainModel_Workset1” then Enscape doesn’t display the override. (Despite the filter technically doing the exact same thing in both cases, and Revit 3D view correctly showing the override.)
I’m not sure if long term this limitation will still cause us/others issues, but in the interim the workaround of using Does Not Contain rather than Does Not Equal seems like it will suffice.
The team checked the example and unfortunately turns out that this is a hard limitation on the Revit side. While Revit displays these filter overrides correctly in its UI, their API does not reliably return the same results for certain filter rules. Enscape depends entirely on that API, and in cases like this (including your linked model rule), the data we receive is incomplete or incorrect.
At this point, there isn’t a workaround we can implement on the Enscape side to fix this behavior. Any improvement would require changes in how Revit exposes this data through their SDK.
No problems, good to know (and perhaps not all that surprising given how inconsistent/limiting Revit seems to be in terms of allowing user access to info even within the project environment). Thanks for the quick confirmation.
