Skip to main content
Sep 26, 2025 7:31 PM UTC
Acknowledged

Creo View Navigation

Please include detailed documentation such as screenshots, images or video.

1. What product and version are you running?
Creo View 10.1


2. What is the problem?
Navigating through the model means moving the model itself

3. Are you using a workaround? If yes, please describe it.
I'm using a spacemouse with all the controls inverted to simulate flying around the model, however, its still wonky due to center of rotation being around an object instead of center of the camera.

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
Unified navigational controls between BCA and BDS. BCA uses IVT which works in this fashion where the model is stationary and what moves is the camera. This can be set up with/without a spacemouse.

 

Without the spacemouse, the controls would look like this, and most importantly, they would be movements to the camera, not the model:
W - forward

A - left

S - backward

D - right

X - down

Space - up

Q - rotate anti-clockwise about y axis (z axis is up, x is left/right, y axis is forward/backward)

E - rotate clockwise

Z - rotate anti-clockwise about z axis

C - rotate clockwise about z axis

F - gyroscope toggle (z axis remains up)

Right mouse-button click - single click toggle to enable/disable looking around (camera angle changes based on where mouse is pointing, but camera position does not change)

Mouse scroll-wheel - change flying speed

 

With a spacemouse, all the keyboard controls and mouse look-around would be replaced with the spacemouse movements, with the shared controls being flying sensitivity via scrollwheel, and a toggle for gyroscope (z axis will remain up).

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Anyone transferring from BCA to BDS or working a BDS SOW where they'd be using Creo View would have to go through a navigational learning curve. This translates to several users spending several hours due to several moments of trying to navigate in one way, and receiving a different response from the program.

1 reply

Community Manager
Oct 21, 2025 12:23 PM UTC
Status changed to: Acknowledged

Thank you @ZzCAD for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.