3D cursor sets to "-nan(ind)m" or "nanm" on click #68344

New Issue

Patrick · 2019-08-07T01:20:55+02:00

Patrick commented

2019-08-07 01:20:55 +02:00

System Information
Operating system: Windows 10 Home 64-bit
Graphics card: 2048MB ATI AMD Radeon HD 7800 Series (ATI AIB)

Blender Version
Broken: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449

Short description of error
Clicking to move the 3D cursor returns "-nan(ind)m" in the the XYZ fields. Then clicking back on an empty space returns "nanm".

Exact steps for others to reproduce the error
I can't reproduce the bug from a new file but this is how it goes in the attached .blend:

cursor starts out at (0,0,0)
clicking an empty space at this point works as expected (I have moving the 3D cursor set to LMB)
clicking any object will set it to (-nan(ind)m, -nan(ind)m, -nan(ind)m)
clicking an empty space after this point returns (nanm, nanm, nanm)
can only be set to a working value manually or with shif+s or shift+c

system info system-info.txt

blender file bugTest.blend

**System Information** Operating system: Windows 10 Home 64-bit Graphics card: 2048MB ATI AMD Radeon HD 7800 Series (ATI AIB) **Blender Version** Broken: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e **Short description of error** Clicking to move the 3D cursor returns "-nan(ind)m" in the the XYZ fields. Then clicking back on an empty space returns "nanm". **Exact steps for others to reproduce the error** I can't reproduce the bug from a new file but this is how it goes in the attached .blend: - cursor starts out at (0,0,0) - clicking an empty space at this point works as expected (I have moving the 3D cursor set to LMB) - clicking any object will set it to (-nan(ind)m, -nan(ind)m, -nan(ind)m) - clicking an empty space after this point returns (nanm, nanm, nanm) - can only be set to a working value manually or with shif+s or shift+c system info [system-info.txt](https://archive.blender.org/developer/F7652312/system-info.txt) blender file [bugTest.blend](https://archive.blender.org/developer/F7652313/bugTest.blend)

Patrick commented

2019-08-07 01:20:55 +02:00

Added subscriber: @pwcb

Jesse Yurkovich commented

2019-08-07 02:07:37 +02:00

Added subscriber: @deadpin

Jesse Yurkovich commented

2019-08-07 02:07:37 +02:00

This is a result of the Clip End value being set very high. Setting to a lower, more reasonable, value returns behavior back to normal.

A dev will have to comment further on if this can be improved. In the meantime, keep the Clip start/end values to something appropriate for the scene being modeled.

This is a result of the Clip End value being set very high. Setting to a lower, more reasonable, value returns behavior back to normal. A dev will have to comment further on if this can be improved. In the meantime, keep the Clip start/end values to something appropriate for the scene being modeled.

Patrick commented

2019-08-07 02:11:34 +02:00

I just realized this looking through all the setting I'd changed. Maybe an easy solution would be putting a cap on clip end, I don't know if this is even a bug considering how extreme 9999999m is

Philipp Oeser commented

2019-08-07 11:27:05 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-08-07 11:27:05 +02:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2019-08-07 11:27:05 +02:00

Philipp Oeser self-assigned this 2019-08-07 11:27:05 +02:00

Philipp Oeser commented

2019-08-07 11:27:05 +02:00

I would not consider this a bug atm.
Setting clip start/end is still a manual thing [there might be ways to improve this e.g. taking scene bounds into account] and setting this up is expected to be done by the user atm.
(There are also some tools depending on this, so it is really recommended not just throwing some extreme values at it...)

That being said, will close this now (feel free to comment again if issues persist...)

I would not consider this a bug atm. Setting clip start/end is still a manual thing [there might be ways to improve this e.g. taking scene bounds into account] and setting this up is expected to be done by the user atm. (There are also some tools depending on this, so it is really recommended not just throwing some extreme values at it...) That being said, will close this now (feel free to comment again if issues persist...)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

3D cursor sets to "-nan(ind)m" or "nanm" on click #68344