You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Debug" button only works once (or while "Perf" is also enabled). Otherwise you get "WebGL Context Lost" in the devconsole (not shown in video) and it doesn't work anymore / flickers the wireframe briefly.
Many bodies spawn in wrong position.
Spawn positions differ between body creation and after unpausing.
Despite all of this, physics mostly seem to work (there is no rendering issue here - the bodies are actually in the wrong position, but otherwise behave correctly).
I've also checked out the code I've tried checking out the code locally (@react-three/[email protected] and the latest main) and did npm install / npm run demo and also tried the online demo: all broken.
I've tried this in Chrome and Firefox - both of them are broken.
Probably not relevant, but this machine is ARM (Apple MacBook Pro M1 Max) running macOS.
(Not shown here, but the cradle demo appears to use a restitution > 1, so the balls actually accelerate if I tweak the demo so the rods "hang" initially - although I'm not sure why I have to apply odd rotation values to even get them pointing straight, so there might be more serious issues)
The text was updated successfully, but these errors were encountered:
This appears to be related to the order of rotations / position transformations. Especially with how / when collider transforms affect the rigid body.
I'm able to get Plinko working like this:
(The position on the group is used so the dropped bodies don't hit the front edge; I assume the entire model was originally turned 180 degree, so the 1.06+0.44=1.5 offset was incorrect)
I have issues with https://react-three-rapier.pmnd.rs/
Here's a video and some observations (Recorded on https://react-three-rapier.pmnd.rs/ just now):
rapier-error.mp4
I've also checked out the code I've tried checking out the code locally (
@react-three/[email protected]
and the latestmain
) and didnpm install
/npm run demo
and also tried the online demo: all broken.I've tried this in Chrome and Firefox - both of them are broken.
Probably not relevant, but this machine is ARM (Apple MacBook Pro M1 Max) running macOS.
(Not shown here, but the cradle demo appears to use a restitution > 1, so the balls actually accelerate if I tweak the demo so the rods "hang" initially - although I'm not sure why I have to apply odd rotation values to even get them pointing straight, so there might be more serious issues)
The text was updated successfully, but these errors were encountered: