Revit 2016 - Hyperblast Issue (Possible Fix)

[guitarchitect]

So I just got a SpaceNavigator over the weekend, and I'm really enjoying it so far! Still getting used to it, but it's great... If 3Dconnexion could maybe work with Autodesk to push for better Revit support, I'd upgrade to the Spacemouse Enterprise in no time at all. But I digress...

After two days in a file, I still had yet to experience the "hyperblast" issue that users were reporting... I was zooming in and out just fine. Then... it happened. I'd try to zoom in, and everything would vanish. I'd zoom to fit, rotate the model, and the instant I'd nudge in a zoom direction, bam - gone.

I have always found Revit's 3D Views a bit buggy, so I took a look at the culprit of the occasional 3D View issue - Eye Elevation and Target Elevation. If you have a "working" view and you do a lot of camera movements, these numbers get completely messed up in Axo Views... they can get huge. Sometimes they get into 7+ digit territory. The culprit, I think, is zooming. If you zoom way out, the numbers change accordingly... sometimes. Hit Zoom to Fit, and they... don't. Zoom out again and you get further away. Hit Zoom to Fit and... you're still further away.

So the fix is simple... reset these values. Set the target to zero, and the eye elevation to something that makes sense for your project. Or click one of the box corners for a default view, which physically moves the camera. Just like that, you should have your full 3D Mouse zoom and orbit functionality back.

Here's the thing that I've realized that is important to remember with this device: you're always moving the camera. Even though the default setup is to make you feel like you're "moving an object in space", you're always moving the camera. So when things go sideways, have a look at your Target and Eye elevation.

All of that being said, it's still a bit messed up. I can't figure out how on earth the camera itself decides to move in an Axo view - sometimes zooming in and out doesn't move the camera at all... sometimes zooming out moves it but if you hit "zoom to fit" then it doesn't, which is how those numbers seem to get so huge. Picking an object to orbit around seems to help keep the numbers under control, and perspective views seem far, far more reliable (but still gets some wacky target elevation numbers, even with object selected to orbit around).

Hope that helps somebody that's having this issue!

[UtaSH]

Hello guitarchitect,

thanks for your feedback. We are in contact with Autodesk concerning some issues. But we need the help of our customers to make clear that this needs improvement. The navigation with the 3D mouse in Revit has been implemented by Autodesk. Only their developers can make that implementation better. Please address the issues with the Support team of Autodesk.

Thanks for your help.

[JeremyL]

Hi -
I'm having the same Space Navigator problems. Can everyone - including 3D Connexion - pester Autodesk for a fix.
3D Connexion people - it's in your interest to work on this; it's putting a lot of people off your products!