Showing posts with label Issues. Show all posts
Showing posts with label Issues. Show all posts

Wednesday, July 24, 2013

It is a Training Problem

I frequently get involved in conversations that start with someone wishing Revit would help resolve "x" problem. The essence of "x" is that somebody on the team keeps doing something that the team wishes they wouldn't. So we want Revit to fix a user, or make it impossible for a certain user to do something.

Usually it is just growing pains and those WILL subside after enough time is invested and experience is gained. That's the purpose of training, we can shorten the time required with training. Yes, I do work as a trainer but I'm not just saying that because I'm a trainer (the carpenter thinking every problem needs a hammer). The whole point of hiring a training consultant or going to classes (for anything) is to reduce the time it takes to become productive or knowledge.

    We SPEND money to SAVE time and invest in our skills.

Too many firms don't invest in their staff (or if they do, they don't do it effectively). They expect or assume that their staff will just manage to get by on their own. Give them a book, they're smart, they'll figure it out. They probably are smart and they will figure it out...eventually. How long can you wait for that to happen? They might pay for training but then after three days in a class they've been trained and therefore are experts! At least that's the perceived expectation or assumption. After all, that's why architecture is such a easy degree to get and getting licensed is a snap, right?

Getting training is a piece of the puzzle. Putting that training to work is how experience is gained. The training makes it possible to shorten the learning curve toward experience. No matter which way you approach the learning don't underestimate the importance of the experience of doing the job, the project. You'll just enjoy the job or project more if you get some good training and spend less time getting frustrated.

If a firm really keeps track of how much time is lost to inefficient task completion and inexperience leading to rework. They'd find out eventually that hiring that consultant or training facility would have been a bargain. If we don't treat "time lost" as "money spent" we don't realize how much it really cost. So many firms behave this way, they don't pay attention to the money going out the door the slow and "invisible" way. It goes out so slowly they convince themselves it isn't happening. If you are serious about seeing a return on investment (ROI) you need to know what it costs to do everything now (the established or "old way") and then later after becoming proficient with Revit. As they say, you can't manage what you don't measure. Keep in mind that lots of data doesn't necessarily mean it is useful.

A senior architect mentoring an intern architect is the same thing, your experience helps the future senior architect become one. You can be a mentor in your office for Revit and bring people up to speed sooner too! So it's not just about hiring a great trainer, it's also about striving for better continuously.

    We sprung for training and people are still making mistakes and they've been warned repeatedly!

Mistakes are one thing, we all make them. If people know better but keep doing the same thing over and over again you now know what they really think of you and the firm. They don't care! They don't care enough to "play along", be a "team player" (OMG, holy catch phrase Batman). Sorry but AEC is a team sport.

    Messing up other people's work IS a training issue, until it ISN'T anymore.

If people are trained and continue to be RUDE and refuse to work well with others it is no longer a training issue. It's a HR (Human Resources) problem, yeah I mean "possibly cost them their job". A firm (and it's staff) shouldn't have to tolerate people refusing to work together well. That's easy to write, not as easy to work through, I know that. Someone once said to me, "Yeah we have a few people who should work for our competition". So I say, "why aren't they?" (big grin)

Ignoring the problem, yeah how's that working?

Plaaaaay BALL!

Wednesday, June 5, 2013

Thin Lines and Printing Sheets

Reading reports (at RevitForum.org) of the Thin Lines feature affecting the output when printing from sheet views. In my own quick test I'm seeing the lines of the titleblock being printed respecting Thin Lines being on which isn't good.



The model views appear to be printing correctly, just the title block's own lines seem to be affected. When I printed a model view using Thin Lines the result was the same as with Thin Lines off. In other words, working as we've come to expect, the Thin Lines feature had no impact on printing. Or, we've not noticed it before.

When we use Temporary Hide Isolate we get this dialog to ask how we want the feature to be regarded. If Thin Lines is meant to be able to get printed then perhaps the same sort of warning/option ought to be offered?



Any readers that can confirm this too? Seems like an undesireable "feature".

Wednesday, May 29, 2013

Tag Slope of a Ramp

We can apply the Spot Slope annotation to a ramp but it isn't very useful because, while Revit does acknowledge the ramp element, when you attempt to tag it you see [no slope] (image using 2014).



Alfredo replied to my previous post with a tip in his comment:
    If you first place the spot slope tool on a floor and then move the slope annotation to a ramp, it works!

In this image I've dragged a slope annotation from a floor element over to a ramp element and it recognizes the ramp's slope!



Definitely quirky and subtle but at least it is possible after all. A word of caution, it will probably be necessary to check the slope value before printing, for example if Revit regenerates information because the ramp is altered. The tag could could start to report [no slope] again. Fwiw, in my casual testing so far it hasn't broken the slope value even after altering a ramp's parameters. Your mileage may vary...

Monday, May 13, 2013

Options Bar and the Mouse Wheel Zooming

In past releases we needed to be careful about using the mouse wheel button to zoom in and out after entering a value on the options bar, in particular with Revit MEP users. When we selected a duct or pipe and set the dimensions on the Options Bar and then rolled the wheel on the mouse the dimension values changed instead of zooming in or out in the view.

I am happy to report that I’ve observed this is fixed in 2014. When entering an offset value for walls though the Options Bar still keeps the focus so it is necessary to use the "pan with the mouse in the view" trick to return the focus to the drawing window.

Tuesday, May 7, 2013

Autodesk 360 Kills my Internet Connection

Each time I let Autodesk 360 sync it seems to block all my other internet activity and my PC goes back and forth repeatedly between reporting access and no access to the internet. Very annoying. For this reason, I tend to log out and exit the application, not very 360ish, sad to say.

Monday, March 18, 2013

Revit HotFix for 2012

Recently people reported a Windows update causing the blue annotation symbols and temporary dimensions to change their color in Revit 2012 versions. I saw it too. Autodesk has release a hotfix to resolve the .net version issue that created the situation in the first place. The Revit Clinic wrote about the hotfix earlier today. You can go to the site to check out the ReadME file and download the HOT FIX HERE.

Saturday, February 2, 2013

Move with Disjoin

Using the Move tool and checking Disjoin is equivalent to "cut to clipboard" (in effect delete) and then "paste from clipboard". This is necessary to break a wall or line away from other walls or lines that may be connected. Without Disjoin the other walls or lines will attempt to stretch to stay connected.


It is not really just moving the existing elements but recreating them in a new location. This means the elements will get new Mark parameters, assuming Revit numbers them automatically, like doors for example.

If you really need to separate walls or lines (ducts or pipes too) you can move without using the Disjoin option and then manually pull the other elements away from the wall using their own grips instead. A bit more work but maybe less than renumbering elements?

Something to keep in mind.

Monday, January 28, 2013

Tag on Placement Quirk

My friend Tom wrote to me the other day asking if he was crazy or if I could confirm that Revit 2013 has a quirk when placing a light fixture in a ceiling plan. Well he isn't crazy, at least not about that. It isn't just for light fixtures either, seems to be for any component. When placing a component in a floor plan view you get this ribbon configuration, or close to it.


When in a ceiling plan you get this version...sans "Tag on Placement".


Seems unfair to me. There was a recent Hotfix posted for Revit 2013 but it does not appear to address this issue. I demand equal opportunity for Tag on Placement!

Tuesday, January 10, 2012

All Capital Letters

Saw a request recently to change the "Grand Total" (title as Revit calls it) that appears at the bottom of Revit schedules from Sentence Case to Upper Case.


My first reaction was to wander down the path of reminiscing why we use upper case in documentation at all. Going back to hand drafting and reducing the number of characters to master for simplicity and consistency sake. Whenever something like this comes up you can go the route of justification/explanation, "Well, here's why Revit does it that way. I know you don't feel better, but at least you know why though?" Alternatively you can just go the route of apologizing, "Nope it doesn't do that, sorry!"

    Something like this request both seems like such a tiny thing to fuss over and still such a tiny thing for the developers to overlook. Why can't we change the "case" of such automagic labeling?? Surely it can't be hard? If we add in localization, making Revit use a different language, there are some examples of where users are stuck with the English text even though the rest of the words on the documentation aren't. I seem to recall the word Scale for the view scale is/was one of those.

If you really want to get your way, you can, not hard...just isn't automatic, you'll have to keep after it. Alter the schedule so it uses the Totals Only option. Then at the bottom of the schedule add a text element that says "GRAND TOTAL". You've got to move this as the schedule expands/contracts. Remember to check it before printing.


Maybe someday they'll make it possible to change these "little things"? Definitely a Dept. of Reviteristic or perhaps Dept. of Quirky or Dept. of Subtle. Heck all three work for me!

[Added: 1/10/2012] Paul Aubin mentions in a follow up POST that we can use a font that only has upper case characters. That's a trick that a few people I'm met or know from the user forums on the "internets" have used. Assuming you can find such a font that is acceptable it might just work. Remember you've got to make any downstream users also have the font.

Thursday, December 15, 2011

Show Title Option

Revit viewports have a parameter called "Show Extension Line". The Type Properties dialog offers us "Yes", "No" and "When multiple viewports". This post deals with the wordy one.


The "When multiple viewports" option is meant to make it easier to leave off a view title when you are only putting one view on the sheet. Most of the time the sheet title is the same as the viewport title, like for overall plans. Seems a bit redundant to put a view title on too?

Unfortunately using it means we have to give up the option of having the viewport title extension line snapping into alignment with other viewport extension lines. I'm referring to the line that shows up when you check the box for "Show Extension Line".


If you are used to these lines snapping into alignment with one another, they won't when you use the "When multiple viewports" option. I captured a short video to help see it in action.



Thursday, November 17, 2011

Stairs by Sketch and Worksets

I've written about this a couple times in the past. Hanging around with a serious Revit guru tonight I was surprised that he wasn't aware of the issue. He'd encountered it but had not sorted out the cause. The previous posts are THIS ONE and THIS OTHER ONE.

The essence of the problem is how the sketch is created in a workset enabled project. If you create individual segments so the stringers are formed properly Revit complains about having "two boundaries".


If you sketch segments that will not generate stringers correctly the stair will finish but generate another error. If you immediately edit the sketch and use the Split tool to break up the segment it then works properly.


Do the same thing in a stand alone project file and no problem. This is ages old but for some reason it only showed up on the radar when I submitted the issue back in 2007. Still with us today, go figure! Hey for those of you out there that I tried to blame it as "user error", sorry bout that! :) An apology is better late than never...

Thursday, November 10, 2011

File Saving Issues

There have been a few threads at AUGI and Revitforum.org alike that discuss an error like this one.


The folks at Autodesk support have apparently pinned the cause down and are now offering a solution via a post at The Revit Clinic yesterday morning. Here's the text of their post.
____ ____ ____ ____ ____ ____ ____

This post is contributed by Niranjan Kamath who supports Revit on our team in India.

While working with a workshared file, Revit will report an error whereby the central file is not accessible.This issue occurs only when the clients had a different OS version. We could not recreate the file access issue if the clients were both W7, or both XP for example.

The reason this happens: Windows 7 client communicates with the server using SMB2, while the Windows XP client uses SMB. This difference in version may cause some file handling issues.

To resolve this issue disable SMB2 from Server and Win 7 users.

To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems, run the following commands:

  • sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
  • sc config mrxsmb20 start= disabled
  • Note there's an extra " " (space) after the "=" sign.

To restore SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems, run the following commands:

  • sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
  • sc config mrxsmb20 start= auto
  • Again, there's an extra " " (space) after the "=" sign.

In order to disable SMB 2.0 on the server-side computer, follow these steps:

Warning!
This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.

  • Run "regedit" on Windows Server 2008 based computer.
  • Expand and locate the sub tree as follows.
  • HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters
  • Add a new REG_DWORD key with the name of "Smb2" (without quotation mark)
    • Value name: Smb2
    • Value type: REG_DWORD
    • 0 = disabled
    • 1 = enabled
  • Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0.
  • Reboot the server.

Thursday, October 27, 2011

Show When Multiple Viewports

When you put a view on a sheet, its viewport has a parameter (Show Title) that determines when we see a view title. There are three choices; Yes, No and When Multiple Viewports. The third option (When multiple viewports) will cause Revit to only show the view title when there is more than one viewport on a sheet.


An interesting thing happens when you actually use the When Multiple Viewports option, we lose the snapping sensitivity that the view title line has when adjusting the length/position of the line. I've created a short video that shows it in action since it's easier to see that way.



Monday, October 17, 2011

Elevation Update Update Updated

Part three of the trilogy... (following up these other posts)

Steve Faust and Nick Kovach of Revolution Design are sharing a free fix for the elevation update issue.


This only affects projects that don't use Worksharing. If that's you then check out their solution until Autodesk delivers a patch or update to resolve it. While you are there you might as well check out their Keynote Manager and Selection Master apps, might find them useful!?

Tuesday, October 11, 2011

Elevation Tag Update Not Happening

Uh oh Spagetti O's... with the recent update I've noticed that the elevation annotation tags do not update when the their detail number values are changed. I don't recall this happening before the update but it's definitely going wrong now.


I find it necessary to change the annotation type to another or alter a setting in the family before Revit will "wake up" and change the tag to the new value. Boohoo...

Here's a quick VIDEO to demo the issue.