Showing posts with label Testing. Show all posts
Showing posts with label Testing. Show all posts

Wednesday, March 17, 2021

Topography Links and Using Tag by Category Makes Revit Angry

This one is subtle, like so many Reviteristics.

A team is testing the Revit to Civil 3D relationship via BIM 360 and Autodesk Desktop Connector. I don't think there are enough moving parts for this equation but I digress. A user reported that Tag by Category (TbC) causes Revit to crash.

We narrowed it down to linked Topography. If any exists then TbC gets dicey. Here's what we know so far:

  • Topography link Not Loaded status > Topography category visible in active view > TbC crash
  • Topography link Loaded status > Topography category NOT visible in active view > TbC NO crash
  • Topography link Loaded status > Topography category visible in active view > TbC NO crash

The team's project has two different linked topography sources so there are two of them in the Manage Links dialog. I haven't tried with just one present yet.

I'd be curious to see if anyone else can corroborate our situation. I've submitted crash reports (several/many) as I worked on this so perhaps Autodesk will find some lurking evil to contend with in the meantime.

Happy troubleshooting...


Friday, June 10, 2016

Revit Safe Mode - Wish Fulfilled

The other day I wrote about David's idea for a Revit Safe mode and Robert Manna responded in a serious way. He and the gang at Stantec created and have just shared an application to do just what we were suggesting. This is a screen shot of it running (from Robert's post).


It runs outside of Revit, prepares for opening Revit without the add-ins you choose to disable. It allows us to be fairly surgical in our troubleshooting even if it's akin to exploratory surgery ... "Hmmm, maybe we need to remove the appendix? No, that wasn't it...maybe the spleen?"

If you're curious head over to Robert's post on their blog for more information and to download the application.

Saturday, April 09, 2016

Warning Messages and Profile Families

Profile families are loadable (component) families but they don't exist on their own in projects. They are either used to create solid and void forms in the family editor, in-place families in projects or applied to System Families in projects. For example, a Railing, Sweep, Reveal and Floor Slab Edge can all use a Profile family.
Occasionally I'll get a generic sort of warning regarding the system family I'm trying to make, telling me "Sorry Steve, I can't make this thing for you".

Quite often the reason Revit is complaining is because I was sloppy making the Profile family. You may recall I've written about good sketches and bad sketches in the past.
Regardless the error message could certainly be written better; to mention that such an error may be related to a profile that isn't created properly. At this time, the error trapping process may not be able to reach deeply enough into the sketch mode process, for example like we use to create a Floor Slab Edge. Regardless, there is no reason the error message couldn't mention a common culprit, something to prod us to look more deeply for.

Technically the error is in a component family and then evaluated as part of a system family that references it. In a sense it is too far removed from the active operation for Revit to properly recognize what's wrong precisely. Therefore I think it would help if, while saving a profile family type, Revit tested it for proper closed boundaries to help us catch errors while editing the family. Revit does this when we attempt to finish a sketch for a solid or void form. Perhaps it could be a button on the ribbon? Something like Test Profile.

Help us help you Revit!

Friday, August 09, 2013

Naming a Reference Plane

I read recently that just adding a name to a reference plane would cause it to be "strong". The notion of Strong, Weak and Not a Reference are related to the IsReference parameter, which I've written about before. It's my observation that adding a name to a reference plane has no impact on it's behavior in a project. To test my belief I created a small family with a collection of reference planes with various combinations of Name and IsReference parameter values.


The reference plane on the far right is set to Not a Reference and has the Name No 3. Its the only one that is invisible in the project environment. The two on the far left have IsReference values (Weak and Strong) but have no Name either, they still are detectable in the project. I sketched dashed lines from the detectable ends of the reference planes. The dashed line on the far right is sketched where the reference plane should be but I couldn't snap to the end because it isn't detectable there. I also added a dimension string across each detectable reference plane.


I think my beliefs are intact, just adding a name to a reference plane does not alter its IsReference conduct in a project. When we create a new reference plane Revit assigns Weak Reference to its IsReference parameter. If we copy a reference plane, those that Revit lets us copy, it also assign Weak Reference to the copy.

Sunday, November 04, 2012

System Inspector Inspect

Using Revit MeP, this feature makes me think of Monty Python's Dept. of Redundancy Department every time I use it. When you have elements connected together well Revit's System Inspector icon will be available.


Reading between the lines, that means if you don't see it when you think you should, something is wrong. The part that gets me is as soon as you activate it you get a little ribbon panel like the one we get for Groups. To inspect a system what's the next thing we have to do?


Yeah, tell Revit we want to Inspect. Department of Inspection Inspector?

Thursday, April 14, 2011

Taking Tests

I wrote this after reading a thread at RevitForum called Autodesk Certification.

In the thread there, a quick mock-up "test" that one member submitted is a good example (I think) of why it's hard to make a test. When we write a question for a test, it and the answers we offer have a bias. If five people submitted their own 15 question tests, I'm confident that anyone who takes it would be able to take exception with at least a couple questions in each. That's why test instructions say "pick the BEST answer", which usually translates into, the one that the test's writer wants selected.


Oddly enough, I often think that people with a lot of experience can have a rougher time with a test because they are aware of exceptions to the rule, all the ways that something can be twisted into being. That and these tests are written by people that are presumed to have significant experience, but what kind of experience? Projects...sales...development...support... training?

How about this question and set of answers? (which btw I've actually seen, not word for word but the essence of that test's question)

In-Place Families...
  • a) should never be used.
  • b) should only be used sparingly.
  • c) can only used for custom casework.
  • d) are best used for sloped walls.
  • e) are used for massing.

  • Answer A is an opinion
  • Answer B is a recommendation
  • Answer C suggests an office preference or standard
  • Answer D is too specific/limiting and suggest a preference
  • Answer E is true, people often forget that massing is in-place families.

They are all "true" depending on your point of view. Which one did I intend to be the "best" answer? Perhaps "E"? It depends on what I wanted to test "for". Revit knowledge or appreciation of subtleties? Applying Revit to our office standards?

    A test's wrong answers can be as interesting as the correct ones. Failing the "right" kind of test might actually demonstrate deeper knowledge of the subject.

Something Aaron Maller once wrote somewhere (AUGI/RevitForum/Blog) that his employer (Beck Group) strives to hire the best architect/engineer they can. They'll teach them the software if necessary. It's a good strategy assuming "you" aren't hunting for an office guru. If nobody in your office has guru status it will be a bit harder to select one (evaluate one), he/she only has to know more than your smartest user to "impress".

There is a lot more a potential candidate can do to prove their value besides showing they passed a test. Remember getting a license to practice architecture (no small feat) means that person passed the minimum qualifications to be able to do so. These other things could be their past work history, references, teaching experience, problem solving examples, writing, and speaking. Oh and the interview shouldn't just be with the HR folks, how will they know they've got the right person? With something like this?

HR Check List:
  • Nice suit/outfit - check
  • Grooming Excellent - check
  • Revit tattoo on forehead - check
  • Degree at BIM Tech - check
  • Autodesk Certification - check
  • Can spell Rivit - check
Recommendation: Hire at 3x the salary

Imagine being eliminated from consideration only because you didn't take the Autodesk test? At best a test is just one of many possible ways to evaluate someone's fitness for a job.

As for testing and an unsolicited plug, you could check out Knowledge Smart.


I got a chance to take one of their beta tests last year or so, been awhile. Their process involves using Revit and provides a nice summary of results afterward. It isn't inexpensive, but they'd like to remind us that the cost of hiring the "wrong" person can be pretty costly. So their testing methodology isn't pennywise/pound foolish. Fellow blogger David Light recently posted a recommendation after talking about them with Robert Manna (another blogger). I vaguely recall hearing the conversation while we were at Autodesk last week.

As for the original question at RevitForum, does anyone recommend taking the Autodesk certification exam? The answer remains elusive and personal. Why do you need it? Is it a requirement? Do you like taking tests and having certificates? Will it help differentiate you from other people at your company, your region, your realm of influence? If many people take it will it no longer be special or rare? In the job hunt, are you competing for a position with just a few others or hundreds? These days with so many out of work it might well be the latter. A candidate will have to have a resume that has some pretty special stuff in it...regardless of Revit certification.

Is there an answer in there somewhere? Only you can know for sure...good luck!

[edit: Seth Godin posted something this morning that I thought was slightly related.]

Tuesday, March 15, 2011

ModelMedic from D|C|CADD

Just read about this new application this morning as well.


ModelMedic is…

Model analysis software: Quickly and easily find all loaded elements – even hidden elements – within a Revit project.
A diagnostic tool: Locate elements which may be impairing Revit’s performance and stability. Find and fix problems faster and easier. You don’t have to be a Revit Guru to spot the potential problems in your model.
A reporting program: Detailed model reports can be saved to PDF, Microsoft Excel or Word for archiving and sharing with all project participants.
Inexpensive: Pay for the tool in just one use by finding problems that could keep you from meeting a critical deadline. 5-pack Licenses and Site Licenses are available, making it
affordable to deploy ModelMedic to all Revit users in your firm.

You can download this video from their site: (or listen here)


Check it out!