Autoeroticasphyxiationdesk

So I'm sitting there (again) trying to figure out why the fuck a goddamned panel won't let me re-host it onto another wall when I run across this from roughly one year ago:

http://www.linkedin.com/groups/ReHosting-face-based-Electrical-families-1550697.S.202799172


Apparently it's a known problem (would've been nice to know about) that Revit won't allow you to move a panelboard when it reaches a certain amount of circuits attached to it.

What the entire fuck?

My favorite post in the whole thing was this one:

"When we contacted Revit (I assume they mean Autodesk) about this problem we were asked the question: "Why would you want to move a panel after circuits have been connected?"

Now that is one motherfucking half-ass response right there - the kind of clueless bullshit that I've come to expect from AutoDicks:  'Why would you want to do this thing that you need to do so that you can get your project done and make money, instead of fucking off for half a day just trying to get ONE SIMPLE FUCKING PANEL TO MOVE?!?!?'

One guy claims to have 'made a macro' to migrate circuits to another panel - but when asked about it, does not reply - so he is either:

a) playing it close to the chest

or

b) full of shit

I'm leaning towards the latter since RevitBots, RevitTrainers and AutoDick Personnel (a disturbing number of whom are woefully unaware that this is not a fucking game) tend to be brimming with it.

Then - one of the posters mentions that 'instructors don't know everything' and that they should just admit they don't know (in reference to blaming something the architect did on why the panel won't re-host).

This is a good point - however it fails to take into account that (especially considering the cost, and at this point in the game) SIMPLE FUCKING SHIT LIKE THIS NEEDS TO WORK - EVERY FUCKING TIME, WITHOUT FAIL, NO FUCKING EXCUSES GODDAMMIT.

It also overlooks the fact that nearly 100% of the time when I have to move a panel, it IS because of something the architect did - if nothing else, failing to give a shit until it became a major issue).

An update on the post claims that '2014 fixes this problem' (which isn't true as far as I can tell), and someone else 'clarifies that panels put into the project in 2013 will still not work', meaning that you would have to un-circuit, insert a new panel, then re-circuit (if that even works).

In ACAD I can move a panel anywhere in the project in less than a second.

Fuck Revit.

Fuck the Dumb Shit.

And if you don't like the way ACAD rolls then eat up on a DICK!!!