Raycast and replaceMesh #38335

New Issue

Fred-Eric Kirsi · 2014-01-23T15:25:50+01:00

Fred-Eric Kirsi commented

2014-01-23 15:25:50 +01:00

Win 7, Geforce 730m

Broken: 2.67.0

Raycasting on a mesh which has two materials gives wrong materials on wrong faces, when replace mesh is used even once.
It seems to affect only one triangle on a square mesh in the physics view ( triangle mesh?) only.
The same setup i am using works by only removing the connection to the replace mesh actuator.

I use replace mesh to update the phys mesh.
I detect the material on the mesh with python:
rayCast(to, from, distance, property, face, xray, poly)
mat_name = ray[-1].getMaterialName()
The face it hits gives wrong material.

I suggest looking at my post on BA forum:
http://blenderartists.org/forum/showthread.php?322524-Impaling-projectile-and-equipment-parenting&p=2562865&viewfull=1#post2562865

Pictures:
The cones should impale the wood (brown) and ignore the steel(grey).

The last one in particular:
"Splitting the mesh into two planes (top plane wood, bottom plane metal) the script works.
So from this I then joined the split planes using CTRL + J"
And the problematic face changed into the upper one.

Blend:
raycast_replaceMesh_2_(1)_(1).blend
Press space to execute script.
Manually re/dis-connect replace mesh.

In the console i print The material recieved and the objects name.
None of the Cone_Lower duplicates should recieve the Material Wood, but they do....

Hopefully this is the right place, as i got no answer in my thread where to report bugs.

Win 7, Geforce 730m Broken: 2.67.0 Raycasting on a mesh which has two materials gives wrong materials on wrong faces, when replace mesh is used even once. It seems to affect only one triangle on a square mesh in the physics view ( triangle mesh?) only. The same setup i am using works by only removing the connection to the replace mesh actuator. I use replace mesh to update the phys mesh. I detect the material on the mesh with python: rayCast(to, from, distance, property, face, xray, poly) mat_name = ray[-1].getMaterialName() The face it hits gives wrong material. I suggest looking at my post on BA forum: http://blenderartists.org/forum/showthread.php?322524-Impaling-projectile-and-equipment-parenting&p=2562865&viewfull=1#post2562865 Pictures: The cones should impale the wood (brown) and ignore the steel(grey). ![First_2.png](https://archive.blender.org/developer/F73987/First_2.png) ![First_3.png](https://archive.blender.org/developer/F73990/First_3.png) ![Oh_jolly.PNG](https://archive.blender.org/developer/F73992/Oh_jolly.PNG) The last one in particular: "Splitting the mesh into two planes (top plane wood, bottom plane metal) the script works. So from this I then joined the split planes using CTRL + J" And the problematic face changed into the upper one. Blend: [raycast_replaceMesh_2_(1)_(1).blend](https://archive.blender.org/developer/F73978/raycast_replaceMesh_2__1___1_.blend) Press space to execute script. Manually re/dis-connect replace mesh. In the console i print The material recieved and the objects name. None of the Cone_Lower duplicates should recieve the Material Wood, but they do.... Hopefully this is the right place, as i got no answer in my thread where to report bugs.

Fred-Eric Kirsi commented

2014-01-23 15:25:50 +01:00

Changed status to: 'Open'

Fred-Eric Kirsi commented

2014-01-23 15:25:50 +01:00

Added subscriber: @vegetablejuicef

Fred-Eric Kirsi commented

2014-01-23 19:05:47 +01:00

I was pointed to a workaround:
triangulating the mesh before manually seems to solve the problem!

Still, i would expect this to work also with square mesh.

I was pointed to a workaround: triangulating the mesh before manually seems to solve the problem! Still, i would expect this to work also with square mesh.

Adam Friesen commented

2014-01-23 21:23:15 +01:00

Added subscriber: @Ace_Dragon

Adam Friesen commented

2014-01-23 21:23:15 +01:00

Some advice, I think it would help if you retested for the issue in one of the latest buildbot builds, there's been so many changes since 2.67 that one wouldn't know for sure if it since has been fixed, taken a different form, or is still there as is.

That's what a lot of other people do and it often leads to their reported issues fixed.

Some advice, I think it would help if you retested for the issue in one of the latest buildbot builds, there's been so many changes since 2.67 that one wouldn't know for sure if it since has been fixed, taken a different form, or is still there as is. That's what a lot of other people do and it often leads to their reported issues fixed.

Fred-Eric Kirsi commented

2014-01-24 08:11:06 +01:00

Tested it with: blender-2.69-fd0b104-win64
from : http://builder.blender.org/download/

The problem persists.
No change.

Hopefully this was meant by " latest buildbot builds ", as i have no idea what you suggested for me to do otherwise.

Tested it with: blender-2.69-fd0b104-win64 from : http://builder.blender.org/download/ The problem persists. No change. Hopefully this was meant by " latest buildbot builds ", as i have no idea what you suggested for me to do otherwise.

Adam Friesen commented

2014-01-24 21:08:40 +01:00

By buildbot, I was meaning this.
http://builder.blender.org/download/

But since I cannot recall changes to the rayCast() function from the release logs, I would have reason to believe the bug will still be there.

By buildbot, I was meaning this. http://builder.blender.org/download/ But since I cannot recall changes to the rayCast() function from the release logs, I would have reason to believe the bug will still be there.

Fred-Eric Kirsi commented

2014-01-27 11:40:46 +01:00

Well, what now?
Is it a bug?
Is it being worked on?

I have been messing around with this since first of January.
Kinda wish to get some confirmation whether i am mad or this IS a thing.

Well, what now? Is it a bug? Is it being worked on? I have been messing around with this since first of January. Kinda wish to get some confirmation whether i am mad or this IS a thing.

Raf Colson commented

2014-07-20 02:22:36 +02:00

Added subscriber: @raco