Matter-js: Weird chain behavior on external monitors.
Has anyone experienced the following behavior of chains acting weird when viewed on external monitors? Below is a video showing the behavior.
https://www.dropbox.com/s/bvsovw6w19o2zmy/IMG_3613.mp4?dl=0
About to pull my remaining hair out, fingers crossed!
cgknutt
All 5 comments
Has anyone experienced the following behavior of chains acting weird when viewed on external monitors? Below is a video showing the behavior.
https://www.dropbox.com/s/bvsovw6w19o2zmy/IMG_3613.mp4?dl=0
About to pull my remaining hair out, fingers crossed!
"link not found" when using the link you've provided.
I have the same issue but with collisions.
I drop a ball through a series of objects and on one monitor the route it takes is constant through an infinite replay of releasing the ball. as soon as I drag the chrome tab to a another monitor without changing the browser size, the ball starts to change it route.
also pulling my hair out
udisun
on 14 Nov 2019
Has anyone experienced the following behavior of chains acting weird when viewed on external monitors? Below is a video showing the behavior.
https://www.dropbox.com/s/bvsovw6w19o2zmy/IMG_3613.mp4?dl=0
About to pull my remaining hair out, fingers crossed!
Found the reason, hope this helps you too
https://stackoverflow.com/questions/58856537/matter-js-monitor-affects-the-engine-physics/58858869#58858869
udisun
on 14 Nov 2019
Thanks man, that’s perfect!
Sent from my iPhone
On Nov 14, 2019, at 8:17 AM, Ehud Shahak notifications@github.com wrote:

Has anyone experienced the following behavior of chains acting weird when viewed on external monitors? Below is a video showing the behavior.https://www.dropbox.com/s/bvsovw6w19o2zmy/IMG_3613.mp4?dl=0
About to pull my remaining hair out, fingers crossed!
Found the reason, hope this helps you too
https://stackoverflow.com/questions/58856537/matter-js-monitor-affects-the-engine-physics/58858869#58858869—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
cgknutt
on 14 Nov 2019
The issue is that the built in runner is pretty simplistic and assumes a 60hz monitor, but now that monitors are coming with higher refresh rates this is becoming a problem.
I've actually already been working on some improvements to the runner which will solve this, but for now go with a fixed timestep or a custom runner. Thanks for reporting but closing this one as it's a known issue.
liabru
on 6 Mar 2020
Thanks for replying man, that was it! Have a good one!
Sent from my iPhone
On Mar 6, 2020, at 6:37 AM, liabru notifications@github.com wrote:

The issue is that the built in runner is pretty simplistic and assumes a 60hz monitor, but now that monitors are coming with higher refresh rates this is becoming a problem.I've actually already been working on some improvements to the runner which will solve this. Thanks for reporting but closing this one as it's a known issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
cgknutt
on 6 Mar 2020
Related issues
Titozzz
·
4Comments
253153
·
3Comments
djipco
·
4Comments
christianmalek
·
4Comments
kunchenguid
·
3Comments