Revit cable tray not converting to Speckle MEP about speckle-sharp HOT 6 CLOSED

Thanks for the report, @timglewis !
Do you know if this type of family used to work before?

Possibly related to #2337 #1436 #1915

from speckle-sharp.

We haven't tried previous versions for this element so I can't confirm if it's a regression.

It does appear to be similar to #2337

from speckle-sharp.

Hi @timglewis,

Sometimes Revit has multiple display meshes for an object. One (or more) default and then one (or more) view specific. I wonder if the image of the cable tray in the Revit modeling space is a view-specific mesh, and the one in the Speckle viewer is the default mesh.

Try sending to Speckle using the view filter

this will send the cable tray's mesh as the view specific mesh. I'm not completely sure this is the issue, but give it a shot and let me know if that shows up correctly.

Also make sure you are on the connector version 2.15 (or newer)

from speckle-sharp.

Hi @connorivy,

I work with @timglewis and have just tested out your suggestion. It looks like upgrading the speckle connector to the latest and specifying the view to select has resolved the issue.

Looking into this a bit further it seems that when you change the 'Detail Level' in Revit from fine to medium, the simplified mesh is shown, so based on what you're saying it appears speckle exports the Medium detail level by default. Is there a way to specify the level of detail to export in the speckle connector settings, or is exporting a specific view the only solution at this stage?

from speckle-sharp.

Hi @katelewis13

That is good insight. I looked into this and what I found appears to be a bug (or maybe a quirk) with the Revit api. If you look at our CableTrayToSpeckle method you'll see the line where we assign the display value

displayValue = GetElementDisplayValue(revitCableTray, SolidDisplayValueOptions)

And the SolidDisplayValueOptions is defined as

public Options SolidDisplayValueOptions = new Options()
    {
      DetailLevel = ViewDetailLevel.Fine,
      ComputeReferences = true
    };

As you can see, the Revit api allows you to retrieve meshes with a given detail level, but our detail level is already set to ViewDetailLevel.Fine. I double checked this with the very helpful RevitLookup tool and I saw the same thing. I guess revit considers this geometry to be view specific and therefore will not give the correct view unless you use view-specific geometry retrieval.

from speckle-sharp.

Closing as a revit limitation

from speckle-sharp.