Revit Can I add skipped elements to my previous Send?

Help
1

What is the protocol when I send my model from Revit and it either skips elements or fails to send them?

I’m in Revit and I select my whole model to send it as my initial Send. It goes well and the only Failed elements are some openings that I am not concerned about.

I do notice that the concrete stairs are missing from my Send though. I check the Skipped list and I find these:

Architecture.StairsRun 150mm Structural Depth 64ebe359-cf84-4f26-8476-137a33eff8a4-0016eec3 Skipped
StairsRun are handled by the Stairs conversion
Architecture.StairsRun 150mm Structural Depth fcef2ab3-b835-4cdc-a003-227b2b0c7c6d-00b350df Skipped
StairsRun are handled by the Stairs conversion

Is there a way that I can amend my last send? With Git I can do another commit and then tick a box that will amend my last commit with the stuff I am now sending?
If I sent a bunch of stuff with the wrong selections and I notice that then Send was not what I expected, can I then Remove that Send and replace it with a better one?

If I cannot amend a Send, then what can I do to my selection process to get it to include my stair?

I had read that the system was designed to make it really difficult to delete a Sent commit. As the author of the content I feel like I should have complete control over the sent information.

Super keen to implement Speckle into our workflow once I have a solid handle on the Sending of the models.

1 Like
2

Is this something that is being resolved in the V3 that just got announced?

3

Thanks for this @Dombowsky I think there are three valuable points we can make, while not quite resolving your root issue :smiling_with_tear_spockle:

  1. Skipped elements should never be arbitrary, it is usually caused by a not yet implemented conversion, a bug or a legitimate skip where hosting conditions mean that an object has already been converted as a child element to another. In case of those first two conditions only an update to the connector is likely to resolve things, so this breaks the expectation of “amend last commit”

  2. However, a request for “ Amend last commit” like behaviour is legitimate in the case of sending a model version based on a selection. Where the new NextGen connectors help here is that adding those few forgotten elements and pressing send again will be Uber fast relative to the current v2 experience where the full selection would be converted again, consequently it is “cheap” to just send the full selection again.

    This leaves the possible feature request of incrementally publishing a model version over many separate selections, we could add this for consideration.

  3. The nub of your post we can potentially address. The skipped elements you report, are they present in the model but not in the record in Speckle server? In which case we should address this as either bug or missing conversion.

So again, thanks for this contribution and let us know if we can act on point 3.

4

Hi @jonathon, thanks for the response! The Skipped Stairs are present in my Revit model but do not show up in the app.speckle.systems viewer.

Is there a different way to check what is on the server? The stairs also didn’t show up when I received the models in my Unity project.

I’m excited to hear that this functionality should likely be resolved in this latest update.

Regarding point 2. do I still have to select everything with the NextGen connector and send again, hoping that the stairs don’t get skipped again? (I could be wrong but) The value of the Amend function in Git is selecting new objects that are then added to the last commit. This would be super useful if I wanted to do my Send in sections, or add specific things that were missed.

Thanks, I am all in on Speckle and am super keen to help it progress.

5

Thanks for prompt follow up.

  • If you could share a minimal reproducible of the stairs model that doesnt convert and publish to Speckle we can use to debug and hopefully fix.

  • This is probably the most straightforward way to check.

  • Adding to a previous version would be considered a feature request, I’ll log that. No confirmation we will do it, or estimates of timeline

  • the next gen connectors experience, given your confirmation of the missing objects, will only fix things if the conversion happens. I know there is a much better fallback to failed conversions happening now, but I havent myself tested how universal that is.

Thank you for your commitment and contribution

6

Thanks for the info, I can strip this part out and send it when I’m back in the office on Monday. I can tell you that I likely used the function that added runs above the modelled stair by adding “Connected Levels”.

I’ve got more examples of pieces being missed (also at the office). The most consistently missed things are Fascia and gutters. If I just send the view, these always get missed. If I send by selection, then I can get them sent, but only if I am in the file and am not trying to send a Link.

Links have a host of issues, but I’ll need my notes from the office to better explain that.

Thanks @jonathon!

7

All the details of your modelling technique is very welcome, Revit sees people become very inventive with bending it to their will, and sometimes this produces unexpected edgecases so thanks.

I think I will gather several of the Linked model issues no floating for the team to triage together.

There are many ways to contribute to open source, not just code. We can only get better with better inputs from you all in the community. :spockle_joy: