Hi all; since installing Revit 2021 I have been encountering an intermittent issue with inputting alternate units that do not match the project units. For example my default project units are Feet and Fractional inches, but I often need to input metric lengths/heights for working with zoning setbacks, survey data etc. One of the best things about Revit is that I shouldn't have to pre-calculate this data in the project units.
i.e. I need to put in 1.2m so I enter that in the offset/dimension/ etc. Sometimes it will scale this properly into the default project units, but then at random it will start scaling it incorrectly.
Screenshot of my input length
Screenshot of the scaled result:
Obviously 1.2m should not = 7291' 4 1/16".
Closing and reopening Revit seems to correct this for a while, but it will randomly start the same behaviour again, and doesn't stop until I've restarted. Has anyone else seen this? Any suggestions for some setting I'm not considering? Or is this just an install glitch and a fresh install would take care of it?
Thanks!
Gelöst! Gehe zur Lösung
Gelöst von Lance.Coffey. Gehe zur Lösung
Hmm Interesting. It does seem to be case sensitive. I get the correct result when entering it in as 1.2m instead of 1.2M.
I always work with caps-lock on and have never had this issue before (working in Revit since 2006); does the upper case M now refer to some other unit? I was thinking Miles but the scaling doesn't work out, 1.2 miles = 6336'
Anyways thanks for the insight, I hadn't thought to check the case of the letter, that's an easy fix for now!
This is new in the 2021 version (I tested 2020, and it does not do this).
It looks like the M abbreviation is used for Nautical Miles, so when you type 1.2M, its converting that from Nautical Miles to your project units (feet).

Ya I had just gone back to 2020 to make sure I wasn't remembering incorrectly.
It's not noted in the release notes, but is this to do with the fix noted in the "Issues Resolved"
"Fixed an issue while trying to scale an imported object so that it would be greater than 20 miles (32 km) in size"
Anyway thanks for clarifying Lance! That had us puzzled here; will have to just get used to holding a shift key a bit more often. ![]()
I checked in with our developers on this, and it doesn’t look like this was an intended change.
I’ve setup the following article to track the status of this issue: Unit conversion from Revit input field scales incorrectly
Thank you for letting us know about this!

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.