After a bit of head scratching, I realised it was simply because Revit wasn't detecting a work plane to drop the line onto once converted.
In writing this blog, I thought I would try and replicate the issue in a new family...except, I couldn't.
I tried removing reference plane names, deleting previous work planes and I even successfully got the Revit workplane to report <not associated>, yet I couldn't get the 'Convert Lines' button to grey out again. Weird.
I tried removing reference plane names, deleting previous work planes and I even successfully got the Revit workplane to report <not associated>, yet I couldn't get the 'Convert Lines' button to grey out again. Weird.
If I work out a way, or find something on the forums I will update the post, but for now it seems like one of those rare events. At least now I know what the fix is.
I have had something similar happen before. It happened to me when working in plan and then switching to elevation but not switching workplanes - or as shown above when the workplane disassociates. I had to manually set workplane first and it will always convert it after that. I've had it happen in project as well as in family editing.
ReplyDelete