cursor surface project innacuracy #59890

Closed
opened 2018-12-27 10:36:33 +01:00 by Marcin Twarowski · 12 comments

Win10, GTX1080
Broken: 2.80, 2018-12-26 22:09, e4dbfe0a98
Worked: 2.79

Cursor surface project is not as accurate as in 2.79, especially when projection is at a steep angle:

cursor_surface_project_innacuracy.PNG

It's better when projected at a shallow angle, although still not perfect:

cursor_surface_project_innacuracy_b.PNG

Win10, GTX1080 Broken: 2.80, 2018-12-26 22:09, e4dbfe0a98c1 Worked: 2.79 Cursor surface project is not as accurate as in 2.79, especially when projection is at a steep angle: ![cursor_surface_project_innacuracy.PNG](https://archive.blender.org/developer/F6084158/cursor_surface_project_innacuracy.PNG) It's better when projected at a shallow angle, although still not perfect: ![cursor_surface_project_innacuracy_b.PNG](https://archive.blender.org/developer/F6084171/cursor_surface_project_innacuracy_b.PNG)

Added subscriber: @MarcinTwarowski

Added subscriber: @MarcinTwarowski

Added subscriber: @ZedDB

Added subscriber: @ZedDB

I can not reproduce this with the default cube. The cursor seems to snap to the cube sides.

On my end the error seem to be minimal. Cube sides are located at 1.0, the cursor snaps to ~1.0005.

What error range do you observe?

I can not reproduce this with the default cube. The cursor seems to snap to the cube sides. On my end the error seem to be minimal. Cube sides are located at 1.0, the cursor snaps to ~1.0005. What error range do you observe?

It depends on zoom level. From around 1.001 / 1.002

cursor_surface_project_innacuracy_c.PNG

up to 1.01 when I zoom out.

cursor_surface_project_innacuracy_d.PNG

For comparison, in 2.79:

cursor_surface_project_innacuracy_e.PNG

It depends on zoom level. From around 1.001 / 1.002 ![cursor_surface_project_innacuracy_c.PNG](https://archive.blender.org/developer/F6085430/cursor_surface_project_innacuracy_c.PNG) up to 1.01 when I zoom out. ![cursor_surface_project_innacuracy_d.PNG](https://archive.blender.org/developer/F6085451/cursor_surface_project_innacuracy_d.PNG) For comparison, in 2.79: ![cursor_surface_project_innacuracy_e.PNG](https://archive.blender.org/developer/F6085481/cursor_surface_project_innacuracy_e.PNG)
Clément Foucault was assigned by Sebastian Parborg 2018-12-27 15:56:11 +01:00

Added subscriber: @fclem

Added subscriber: @fclem

I'm guessing that the snapping is using the depth buffer to do this. So inaccuracies will happen. @fclem known limitation or not?

I'm guessing that the snapping is using the depth buffer to do this. So inaccuracies will happen. @fclem known limitation or not?

Added subscriber: @mano-wii

Added subscriber: @mano-wii

We could use raycast.
But currently the raycast only works for the Mesh type objects.
And also depending on the Mesh, it can take up a lot of memory space.

However, when you enable the Cursor tool, you can change the orientation from View to Geometry.
That way it will use raycast. But it will not work well for example with MetaBall objects.

A general solution is complicated. I think it best to let the user work around the problem by using the snap or by choosing the Cursor tool plus Geometry orientation.

We could use raycast. But currently the raycast only works for the Mesh type objects. And also depending on the Mesh, it can take up a lot of memory space. However, when you enable the `Cursor` tool, you can change the orientation from `View` to `Geometry`. That way it will use raycast. But it will not work well for example with `MetaBall` objects. A general solution is complicated. I think it best to let the user work around the problem by using the snap or by choosing the `Cursor` tool plus `Geometry` orientation.

@mano-wii So this is more of a limitation than a bug? What is strange is that it was also working with metaballs in blender 2.79 without the precision loss.

@mano-wii So this is more of a limitation than a bug? What is strange is that it was also working with metaballs in blender 2.79 without the precision loss.

In #59890#644733, @fclem wrote:
@mano-wii So this is more of a limitation than a bug? What is strange is that it was also working with metaballs in blender 2.79 without the precision loss.

The depth accuracy at 2.79 was greater but the technique used for projection in both Metaball and Meshes was glUnProject and not raycast.
However, I did a test again and realized that in Blender 2.8 objects such as Camera, GreasePencil, Empty and Bones are being ignored in the Cursor projection.
If this is not considered a regression, then we can use raycast, since only Meshes are affected.

Perhaps by increasing the resolution of the texture used for depth drawing, the projection will match that of blender 2.79 (but not as good as raycast).

> In #59890#644733, @fclem wrote: > @mano-wii So this is more of a limitation than a bug? What is strange is that it was also working with metaballs in blender 2.79 without the precision loss. The depth accuracy at 2.79 was greater but the technique used for projection in both `Metaball` and `Meshes` was `glUnProject` and not raycast. However, I did a test again and realized that in Blender 2.8 objects such as `Camera, GreasePencil, Empty and Bones` are being ignored in the Cursor projection. If this is not considered a regression, then we can use raycast, since only `Meshes` are affected. Perhaps by increasing the resolution of the texture used for depth drawing, the projection will match that of blender 2.79 (but not as good as raycast).

This issue was referenced by 1f1e90a013

This issue was referenced by 1f1e90a013301b4283fdf9300e7e68b7fc55d894

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#59890
No description provided.