mark.p.maldonado744484
2012-12-26, 03:56 PM
Hi everybody!
(hi Dr. Nick)
I just wanted to post about a possible glitch in Revit Structures that I've noticed from version 2011-2013 (at least), and it has to do with the Beam System. I started to notice that when I had the Beam System on a slope, my beams would start to move and not line up with the systems adjacent to it. Since then I've done some tests and isolated the problem to the pink boundary box in edit mode along the Beam Direction dimension specifically; it seems that every time I open the edit function and close it (without editing anything) this dimension will shrink by fractions of an inch causing the beams to shift. As stated in the title this only happens when the system is sloped and not horizontal, I've tried both taking a horizontal system and rotating it and also modeling the system sloped and that doesn't seem to make a difference.
I've searched the internet about this and haven't found anyone else having this problem, so I might be missing something, but if anyone else can duplicate this, then we might have a glitch on our hands.
Best,
Mark
(hi Dr. Nick)
I just wanted to post about a possible glitch in Revit Structures that I've noticed from version 2011-2013 (at least), and it has to do with the Beam System. I started to notice that when I had the Beam System on a slope, my beams would start to move and not line up with the systems adjacent to it. Since then I've done some tests and isolated the problem to the pink boundary box in edit mode along the Beam Direction dimension specifically; it seems that every time I open the edit function and close it (without editing anything) this dimension will shrink by fractions of an inch causing the beams to shift. As stated in the title this only happens when the system is sloped and not horizontal, I've tried both taking a horizontal system and rotating it and also modeling the system sloped and that doesn't seem to make a difference.
I've searched the internet about this and haven't found anyone else having this problem, so I might be missing something, but if anyone else can duplicate this, then we might have a glitch on our hands.
Best,
Mark