ctrl+wheel not Walking forward/backward in connect

Hello Dan, 

  Can you please provide a few more details. I am able to walk with the CTR + Wheel action.

can you try after resetting the Preference by using the 'Defaults'

Regards,

Nilesh

Found the issue you need camera turned on in view attributes. But it changes the view to perspective.. Didn't have this problem in V8i 

Walk requires a perspective view, the best you can do in an orthographic view is zoom in/out, which is what happens in MicroStation Connect.

In V8i ctrl+wheel didn't seem to do anything useful in an orthographic view when I just tried it, it sort of slowly panned up/down in an iso view, in a top/front view it appeared to do nothing...

Brien Bastings said:

ctrl+wheel didn't seem to do anything useful in an orthographic view when I just tried it, it sort of slowly panned up/down in an iso view, in a top/front view it appeared to do nothing...

Brien,

To actually understand what is happening to the camera when you manipulate the view controls try the following:

1. In addition to your active view window, open view windows for Top, Front, and Right orthographic views.
2. Start the Define Camera command,
   1. Set the Active View to your current view, 
   2.  Display View Cone.
3. Fit View in each orthographic view if necessary to see the entire view cone.

Now when you make changes to your active view you will be able to see the behavior of the view cone in the other views.

Regards,
Ron

Its for use in a clipped view (set display depth). Its extremely handy for clash detection especially when viewing point clouds with a model. but you need to be able to orthographic.

Its for use in a clipped view (set display depth). Its extremely handy for clash detection especially when viewing point clouds with a model. but you need to be able to orthographic.

I see, with front/back clipping enabled the "navigate walk forward" and "navigate walk backward" commands mapped to ctrl+wheel forward/backward in V8i would adjust the front/back clipping planes.

It's not walking as there is no camera position to move in a parallel projection, so with front/back clipping off it appears to do nothing. It's for this reason that we check for a perspective view in Connect and default to zoom instead of walk if the view is orthographic. 

I would suggest seeing if clip volumes in Connect could be used instead of setting display depth...select the clip volume (probably in a 2nd view) and use the modify handles to preview "depth" changes.

You could also assign "navigate walk forward" and "navigate walk backward" to a couple function keys or keyboard shortcuts...

-B

Ron Jones said:

To actually understand what is happening to the camera when you manipulate the view controls try the following:

Yes, using the Define Camera tool with 2 views can be quite helpful, I remember adding this tool for MS/J I think. :) In this case it wouldn't have helped without the missing information about front/back clip planes as there weren't any changes to see.

Anyone know how to map commands (in connect) to ctrl+wheel forward/backward to adjust the front/back clipping planes. As per V8i???

Unlike button events, we never made wheel events customizable...probably would make a nice enhancement.