Thursday, November 15, 2018

All In Together Now!

Achtung!

So I randomly typed in 'Revit Licks Balls' into Google - and ran across the personal blog of someone who had posted here a few times:

https://revitsucksballs.blogspot.com

He hasn't updated it in a while so my hope is that he managed to find gainful employment outside of the Revitsphere and just left the whole goddamned thing behind him.  Its got some great insight into how fucking retarded Revit, Autodesk, and pretty much everyone involved are a bunch of inbred dipshits that don't understand the industry that they ostensibly 'serve'.

Then I ran across this little gem:

http://revit-sucks.blogspot.com

It's only a short couple of quick posts done by someone back in 2011 that pretty much encapsulates the entire Revit experience - slower than fuck, frustrating as hell, and assumes that you already know what the final building is going to look like before you start modeling it (because god only knows what will happen when you start moving stuff around).

They had this cute little cartoon that sums it all up (and has the distinct advantage that the 'Revitworld' frathouse looks almost exactly like my old firm):







Finally I came across this article from 2014 from a guy who managed to complete rid himself of all Autodesk products, and does a fantastic job of explaining exactly what the fuck happened in his industry.  It's more focused on 'Softimage' (which Autodesk acquired), 3DS Max/ Maya/etc. but almost every single thing he says about it could probably be applied to Revit:


http://www.stefandidak.com/2014/03/autodesk-the-metastasizing-cancer-of-the-3d-world/

But enough of that, now it's time to make fun of the idiots who just sent me a small hotel - including this fucking showerhead:



That's FOUR THOUSAND THREE HUNDRED AND TWENTY FUCKING LINES just to show a GODDAMNED SHOWER HEAD.  And it LOOKS LIKE ASS!!!

Oh - and when you put 48 of them into my drawing - that's 207,360 lines (except that many locations inexplicably had two of them - one over the other), so it probably ended up being in excess of 300K lines.

I deleted every single goddamned one, then went about my normal process of cleaning up the garbage infested bullshit that they seemed to think would pass for 'floor plans'.  Tubs that extended into walls, missing countertops, notes/detailing that wipe out parts of walls/fixtures - pretty much the standard nonsense.

Once I get that squared away, I get to figure out what in the fuck the incompetents that laid it out intended (as opposed to what they showed), and it will surprise the fuck out of me if we issue it and they don't come back later having completely changed their design intent (after someone who knew what the fuck they were doing actually looked at it).

Huzzah!!!

Now it's time to say 'Fuck Autodesk' and especially 'Fuck Revit'.

Fuck 'em all.

-uckSkullf

Next Time: ?!?!?!!?

2 comments:

  1. It's been a while since I've commented on your blog. I recently made the transition from a mid-size MEP consulting engineering firm to a much smaller firm. It's been a really positive change, but there is still no escaping from Revit Hell.

    Shortly after I started my new job, I was assigned to a project that was already under design: a high school campus consisting of several buildings. The architect decided to use one architectural model for the entirety of the project. On our end, we had one MEP model. As soon as I realized this, my heart sank. I had been down this road before, and I knew what was ultimately going to happen.

    Weeks went by and we made significant progress on the project. The deadline for 100% Construction Documents was about 4 to 6 weeks away. And then our BIM Manager broke the news: the architect had decided to split up the architectural model, and we were to split up our MEP models in a similar fashion. I will never know the official reason for the decision, but I am assuming that it has something to do with the fact that one, giant model containing multiple buildings made Revit run even worse than it usually does.

    After the breakup, all of the emergency panels that I had circuited to the generator located at one of the buildings (Now in its own, separate MEP model) were no longer circuited, forcing us to resort to makeshift methods of accounting for the emergency panels and their associated loads. Instead of managing lighting fixtures, which were nowhere close to being fully specified, within one MEP model, I now had to manage them across several models. Generating one Lighting Fixture Schedule from several linked models is harder than it sounds. Every single parameter must match up across the board - otherwise the fixture either won't be scheduled, or it will be scheduled without any information. I think our mechanical engineers still use Excel for scheduling their equipment, and now I understand why.

    Here was the real kicker, though. One of the buildings moved several hundred feet away from its original location. And it was mirrored, rotated, or some combination of the two. All of our work was lost. Lighting fixtures, switches, wires, receptacles, panels, you name it. Fucking gone. In the architect's defense (A phrase I never thought I would use), the decision to relocate and modify the building came from the owner. Still, in the days of AutoCAD, it would have been possible to preserve some of our work in such a scenario. And before you even ask - no, we did not receive an additional service fee for these changes. It seems that architects and engineers are no longer professionals, but that's a rant for another day.

    ReplyDelete
  2. If you had one grain of rice for every minute that Revit has wasted - the pile would cause gravity to collapse in on itself and form a black hole (which some dumb fuck would want to try to model in Revit).

    When a client or another firm tells you that they need you to do something in Revit, what they really mean is 'We would like you to bend the fuck over and take it up the ass (without lube) so hard that your great-grand children will feel it.

    And smile at us while we do it.

    ReplyDelete