erroneous error "Slab shape edit failed" (vertices distances are OK)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi!,
I get an error message in Revit 2016 that shouldn't be generated (and wasn't generated in Revit2014) and would like to correct or ignore it, but I cannot find a way to do it.
When transforming building models by moving walls (e.g. making the building smaller) using transactions, the slabs (floors and roofs) are being edited automatically and everything stays correctly joined and attached. However, sometimes in Revit 2016 it gives the error message "Slab Shape Edit failed. Some slab shape edit vertices were too close to each other or too close to an edge." This error occurs even though the distances between all vertices of all elements, including the slab that throws the error, remain large (at least >30cm), both before and after the transformation. The slab that throws the error is a truncated pitch roof (3 faces: two faces with an inclination between 30° and 50°, and one horizontal face joining both at the top) of 40cm thickness, which is not a very complex shape (very regular, with only 16 vertices).
I can reproduce the error when moving the wall manually in Revit (as a regular user, not using the API).
Strangely enough, the error only occurs when moving the wall over a large distance at once, making the building much smaller, but it does not occur when doing the same transformation in small steps (e.g. moving the wall 10 times 0.5m instead of 5m at once). Moreover, when the error is thrown (when doing the translation of the wall in 1 time), the building, including that roof slab, is already rendered correctly on the screen. Additionally, the exact same model and translations worked perfectly using Revit 2014, but fail now with Revit 2016 (and also in more recent versions).
All this confirms that the shape of the slab and the distance between the vertices are not a problem (nor before, nor after the total transformation). I assume that the errors results from substeps that Revit 2016 is doing in the background (e.g. moving one vertex before the other, in such way that they are temporarily too close), with intermediate checks, that are different from how it was done in Revit 2014.
Is there any way to solve this?
I cannot break the translations in smaller steps in my code, because this would require trial and error on all different models and it would drastically slow down the process.
I have tried using failure preprocessors, but they cannot seem to deal with this problem because it is not a warning, but an error that 'cannot be ignored'. I can roll everything back in the API, but cannot reach the wanted shape.
Any help is welcome!
Thank you!,
d