Scene.Ray_Cast misses/fails against CURVE Objects in multiple cases. #79194

New Issue

Matt · 2020-07-23T16:57:08+02:00

Matt commented

2020-07-23 16:57:08 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67

Blender Version
Broken: version: 2.90.0 Beta, branch: master, commit date: 2020-07-22 14:02, hash: 0e280b96ca
Worked: None that I know of.

Short description of error
In testing an Addon I'm developing, I came across an issue when Raycasting to CURVE Objects via Scene.Ray_Cast. It appears it will NOT hit the Curve, even if it's displayed as 3D Mesh. Unless I Apply a subSurf Modifier or other modifiers (Bevel/Solidify), then it will detect it. It appears that until it's actually had some sorta of Mesh Modifier applied, it's not considered a Mesh, even though it's displayed as one....

I also hit another issue in 2.9 (build above), where if the CURVE Object is Active, but De-selected, it cannot be raycast against it, until another object has been set active. Then I can RayCast to the Curve once again. In 2.83 (a8441fc90086-windows64) this bug doesn't exist. I can RayCast to the Curve over and over, without issue, if its set active, but de-selected.

Exact steps for others to reproduce the error

Install / Use the attached RayCast Modal Addon, or Raycast yourself with Scene.Ray_Cast against a Curve Object Displayed as 3D.
Observe Raycast missing.
Apply SubSurf Modifier or Solidify / etc
Raycast again and notice Raycast now works.
RayCast to empty area in the Scene, and Try to RayCast/Select Curve Object again.
Notice that it doesn't become selected again, unless you Raycast to another object/Curve doesn't stay Active between Raycast.

Blender_2.9_Scene.Ray_Cast_Bug.blend

TT_Object_Select_Raycast.py

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67 **Blender Version** Broken: version: 2.90.0 Beta, branch: master, commit date: 2020-07-22 14:02, hash: `0e280b96ca` Worked: None that I know of. **Short description of error** In testing an Addon I'm developing, I came across an issue when Raycasting to CURVE Objects via Scene.Ray_Cast. It appears it will NOT hit the Curve, even if it's displayed as 3D Mesh. Unless I Apply a subSurf Modifier or other modifiers (Bevel/Solidify), then it will detect it. It appears that until it's actually had some sorta of Mesh Modifier applied, it's not considered a Mesh, even though it's displayed as one.... I also hit another issue in 2.9 (build above), where if the CURVE Object is Active, but De-selected, it cannot be raycast against it, until another object has been set active. Then I can RayCast to the Curve once again. In 2.83 (a8441fc90086-windows64) this bug doesn't exist. I can RayCast to the Curve over and over, without issue, if its set active, but de-selected. **Exact steps for others to reproduce the error** 1. Install / Use the attached RayCast Modal Addon, or Raycast yourself with Scene.Ray_Cast against a Curve Object Displayed as 3D. 2. Observe Raycast missing. 3. Apply SubSurf Modifier or Solidify / etc 4. Raycast again and notice Raycast now works. 5. RayCast to empty area in the Scene, and Try to RayCast/Select Curve Object again. 6. Notice that it doesn't become selected again, unless you Raycast to another object/Curve doesn't stay Active between Raycast. [Blender_2.9_Scene.Ray_Cast_Bug.blend](https://archive.blender.org/developer/F8716266/Blender_2.9_Scene.Ray_Cast_Bug.blend) [TT_Object_Select_Raycast.py](https://archive.blender.org/developer/F8716264/TT_Object_Select_Raycast.py) ![Unvown1QWd.gif](https://archive.blender.org/developer/F8716261/Unvown1QWd.gif)

Matt commented

2020-07-23 16:57:08 +02:00

Added subscriber: @mattli911

Matt commented

2020-07-23 17:19:25 +02:00

Here's a GIF showing the same thing in 2.83, except that it doesn't have the 2nd issue with active object, as noted above.

2.83 has no problem selecting back and forth on the Curve if it's active but de-selected. But as I mentioned, raycast fails to hit the Curve still, unless it has a modifier applied.

Here's a GIF showing the same thing in 2.83, except that it doesn't have the 2nd issue with active object, as noted above. 2.83 has no problem selecting back and forth on the Curve if it's active but de-selected. But as I mentioned, raycast fails to hit the Curve still, unless it has a modifier applied. ![Hv3agB4XaT.gif](https://archive.blender.org/developer/F8716311/Hv3agB4XaT.gif)

Germano Cavalcante commented

2020-07-23 20:55:18 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-07-23 20:55:18 +02:00

This is a known issue that has already been addressed in #78434 (Support snapping to faces for objects with DispList (Curve, Surface, Metaballs and Text)).
Basically, this was never implemented.

This is a known issue that has already been addressed in #78434 (Support snapping to faces for objects with DispList (Curve, Surface, Metaballs and Text)). Basically, this was never implemented.

Germano Cavalcante commented

2020-07-23 20:55:42 +02:00

Closed as duplicate of #78434

Germano Cavalcante closed this issue

2020-07-23 20:55:42 +02:00

Matt commented

2020-07-23 21:47:47 +02:00

In #79194#984146, @mano-wii wrote:
This is a known issue that has already been addressed in #78434 (Support snapping to faces for objects with DispList (Curve, Surface, Metaballs and Text)).
Basically, this was never implemented.

Ah, ok, great! That would be fixed in 2.91 then i would guess...?

> In #79194#984146, @mano-wii wrote: > This is a known issue that has already been addressed in #78434 (Support snapping to faces for objects with DispList (Curve, Surface, Metaballs and Text)). > Basically, this was never implemented. Ah, ok, great! That would be fixed in 2.91 then i would guess...?

Germano Cavalcante commented

2020-07-23 22:49:29 +02:00

Anyone can propose a patch and proceed with implementation.
In my case there are other items that have priority (#73993)

Anyone can propose a patch and proceed with implementation. In my case there are other items that have priority (#73993)

Matt commented

2020-07-24 01:19:31 +02:00

Yeah that makes sense. Ok. I will just have to wait and see! I don't think there is a good way for me to get around the issue otherwise, in a performant way... using Python.
Unless I can temp. add some modifier/cheapest modifier possible to CURVE objects to get around it, during my Modal operator.
Is not a HUGE issue though, but more of an annoyance/thing I will have to note for now.

Thank you!

Yeah that makes sense. Ok. I will just have to wait and see! I don't think there is a good way for me to get around the issue otherwise, in a performant way... using Python. Unless I can temp. add some modifier/cheapest modifier possible to CURVE objects to get around it, during my Modal operator. Is not a HUGE issue though, but more of an annoyance/thing I will have to note for now. Thank you!

Matt commented

2020-07-27 21:33:36 +02:00

For now i am using another workaround, where i just apply a modifier, like Decimate to a CURVE object, which causes Raycast to work, and the modifier does't impact the Object visually in any way, by default.
Definitely not ideal, but "works" in the meantime.

For now i am using another workaround, where i just apply a modifier, like Decimate to a CURVE object, which causes Raycast to work, and the modifier does't impact the Object visually in any way, by default. Definitely not ideal, but "works" in the meantime.

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

Scene.Ray_Cast misses/fails against CURVE Objects in multiple cases. #79194