Friction Bug, workaround?

[Hans]

Hi @all,

I think I found a bug again. In this PG: http://playground.babylonjs.com/#249T6Y

Edit: New URL:http://playground.babylonjs.com/#249T6Y

I change friction for a to zero but friction b becomes zero too (See console too)

If it is no bug, please tell me how can I change the friction for just a.

 

[Dad72]

There is a forum for bugs. Here, are the questions and answers.

But of memory, I believe that Canon does not like 0. put rather 0.000001

[Hans]

@Dad72 I know. Thought the question is implicitly clear. Question: How can I workaround this bug?

If I change the friction of cube A to 0.0001 then friction of cube B is also 0.0001.

 

[Dad72]

When I look in the playgroud, I see no error.

a = 0.3 and b = 0

[Hans]

   console.log(b.physicsImpostor.physicsBody.material.friction)
   a.physicsImpostor.physicsBody.material.friction = 0;

I change just friction of a (ceteris paribus). I write friction of b in console. Friction of b is also = 0. It shouldn't be 0 too. You can see it also on mesh behavior.

[Dad72]

So this is a bug that should go in the bug section.

But your code difficult to watch the bug. when I look for me everything is Ok.

You need to add the change in value of A to see the bug of B also 0

[Hans]

The bug is even the strange behavior. How can I show my problem else?

BTW: Not only B changes his friction. If I add more meshs they change thiers friction too. I mean all change the friction by changing just one.

If I bug post this, I can not get a workaround. And maybe there is a special reason for this behavior and it is not a bug. I still looking for help/workaround this behavior.

[fenomas]

a.physicsImpostor.physicsBody.material == b.physicsImpostor.physicsBody.material
// true

For some reason both physics bodies have the same material object. Not sure if that's a bug on BJS's side or not.