Thanks Danny, I can repeat that over here.

It appears to be creating a line that is shooting immensly far off in z, one endpoint appears to be at z =
215339230865702500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

which as you can see is a pretty big number. :)

Then a bounding box that size basically ruins the 3D view projection with an overflow.

I guess the right solution is to actually not generate a result when you move the mouse into the Top view, (same as V1), is that right?

I'll take a look tomorrow at fixing this up, should not be too difficult. Thanks for reporting it and taking the screencap!

- Michael

Hi Michael,

> I guess the right solution is to actually not generate a result when you move the mouse into the Top view, (same as V1), is that right?

Yeah, sounds right. This wasn't the actual model I was working on, I just modelled some primitives to see if the actual model I was working on wasn't causing the problem.

How would you pronounce that number in words, that's crazy :o

Cheers

< How would you pronounce that number in words, that's crazy :o
A googleplex! http://en.wikipedia.org/wiki/Googolplex :)

Hi Danny, this offset-makes-view-disappear problem is fixed up now for the next v2 beta, thanks for reporting it!

- Michael