The wait is over and Warchart is available for download from Autodesk App Store – go right ahead and get your fresh copy of our new product and start cleaning those pesky Warnings, enjoying yourself every step of the way!

Ok, you might be thinking – wait, whatchart? Warwho? Alright, let’s take it one step at a time.

History of Revit Warnings

Warnings have always been a part of Revit’s grunt. Their existence is important in two ways.

First and probably most important, Revit is doing you a great service in telling you that something is wrong with your model. Understanding Revit Warnings, in Autodesk’s own words, is important and you would want to prioritize those areas in your project where you might be punished later down the road – for example, having “Duplicate Instances in the Same Place” might result in a misleading schedule – not ideal.

Hint: clear Warnings which lead to program implications first.

The second way in which accumulating Revit Warnings should be of interest to you is because it directly affects Model Performance. Yup, every character is a byte of information and it just adds up, slowing your model in the process. There is no hard limit as to how many Warnings is a definite no-no – I bet my BIM hat that everyone has their own opinion, my

Hint: let’s say Warning Number = N and File Size in MB = S. Then:

  • Wow: N = 0
  • Good: N < S
  • Alright: N < 2 x S
  • Poor: N < 4 x S

For example, if you have a model of 350mb, you can tap yourself on the shoulder at 350 Warnings, go ‘meh’ at 700 and feel bad about yourself at 1400. Each project is different and those values will vary.

Let’s see what Autodesk has to say:

“Ideally, all warnings should be addressed and the total number of unresolved warnings should be zero. But in reality, this is a tall order in most projects. So the pragmatic approach is to resolve as many of the warnings that you reasonably can.”

User Interface (UI)

Revit provides you with a simple but thorough UI to let you go through the different Warnings in your Model. While it has everything that’s needed to get the job done, I feel that the main problem the community has had with the default Warning Dialogue was the difficulty with which you navigate and isolate the affected elements.


After Autodesk Development Team released the Document.GetWarnings() method a number of community created alternatives came to live each attempting to give a better way of dealing with Warnings. In all fairness, the process started even before Revit 2018, but the extra step of having to export and parse an .html file made those solutions a bit .. uglier I guess is the word. GetWarnings() created a really elegant way of interacting with what was already inside Revit.

Enter Warchart

Warchart stands for Warning (Pie) Chart. The great thing about Warchart is that it builds on the fluidity of this new feature. It’s absolutely adorably interactive. It gives you an immediate feedback. That’s a really powerful feature and we can talk about gamification, dopamine release all we want but the fact of the matter is that it’s just super cool watching you eating through those Warnings like the proverbial Pacman (see what I did there?). A part of this, of course, is the Modeless WPF which allows you to keep Warchart open while you go about your business.

The other really potent feature is the ability to zero on those warnings which matter the most – because the interface is actually one big colorful pie-chart, you know the distribution of Warnings in your project immediately.

To give you a taste of what Warchart looks and feels like, here are a couple of screenshots from it.




Download Now!

With Warchart you can have your Pie and eat it too! Actually, I’m not entirely sure how applicable to Warchart this saying is, but we do have a tasty-looking image of a Pie so I couldn’t resist.

If you are burning with excitement like we do, head to the App Store and download Warchart! You’ll see how much more enjoyable your model management becomes with this intuitive and easy to use gem of a Plugin.

I hope you like our new release. If you have any questions about it or ideas on how to improve it, drop us a line – we’d love your feedback and we’d appreciate your time!


The room was packed – with people as well as with ideas, knowledge and information. In short – it was a blast and I can’t wait to see the next one!

If you want to stay for the long version of my improvised review of the event that took place at the office of AKT on the night of 4-Feb 2016, let me first explain what DCC is and why it is so important for humanity.

DCC stands for “Design Computing Community” and that’s pretty much what it is – a hub where the geeky part of the AEC industry meets. A social place, a forum for computationally imbued ideas. The initiative is based in London and this was their third event  (at least as far as I know).

The talks are usually hosted in the office space of a friendly architectural or engineering practice and give the lucky attendee the chance to hear between four and five highly-entertaining, high-quality computational talks with presenters coming from every niche of our industry – Gregory Epps and Robots? – good!  Atelier One and hanging giant human figures? – good!

Last night was no different – there were four talks split among six speakers and in less than three hours we were introduced to a good mix of design, research, fabrication, architecture, application, mathematics, processes, custom tools and much, much more. It is difficult to describe every single discourse in detail as they all packed quite a substantial mental punch – I can say that I found interest in all of them and they kept me highly engaged during the whole affair. And although I hold the talk which Michael Hudson gave on the first Summer Event as a personal favorite, I must admit that an interesting trend is starting to emerge – I find myself drawn to the more technical talks of those specialists who work in the later stages of the design process. Both AKT’s Uli Horner from the second edition and Newtecnic’s Howard Tee yesterday gave incredibly in-depth, sophisticated, no-bs, mesmerizing lectures in fabrication, manufacturing, and all the post-project disciplines which we, as architects, tend to sometimes neglect.

The talks are getting the right amount of love from the community and last night was a good showcase in that regard – the big conference room packed with people was full of vibrant, healthy chatter during the breaks; this trend shows that the community is recognizing the forum as a much-needed place, turning DCC into a source of specialized knowledge that is sometimes hard to come by.

My personal opinion – I love this event! It infuses me with that tribal feeling of belonging, of being part of something meaningful and greater than myself. And, to be honest, after the informational outpour from last night, it might have increased my brain size a little.

Keep up the great work guys! See you in three months.


P.S You can find more information about the Design Computing Community on their web page or follow them on Twitter @dcctalks.