Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible to get breaking speeds by manipulating momentum of balls. #220

Open
KatieWoe opened this issue Sep 30, 2024 · 1 comment
Open
Labels
type:wontfix This will not be worked on

Comments

@KatieWoe
Copy link
Contributor

KatieWoe commented Sep 30, 2024

Device
Any
OS
Any
Browser
Any
Problem Description
Found by a user and reported to @amanda-phet:

Someone told me about a Collision Lab bug! They broke the sim with some extreme things. I didn't quite follow but took a video of him explaining it. He said the students got it going 145k the speed of light and the sim broke.

I was able to reproduce this using a simpler method.

  1. Go to the second screen
  2. You only need two balls. Set one at max mass and one at min mass
  3. Set both at top speed.
  4. Pause the sim
  5. Step forward until collision makes small ball faster
  6. Make small ball big and big ball small
  7. Repeat 5 and 6 until you get ridiculous speeds

Note that the sim breaks well before a crash happens. The balls will step forward once and then stop moving, whether you press step forward or press play. They will un stop for another step forward when you change the masses. This still requires rather absurd speeds, though I didn't notice exactly when it happened.

Discussion from Slack:

I think this is using knowledge of momentum, and is just fun "let's try to break this" behavior. So I don't think we should spend time on any "fix" for this.

Marking as won't fix, but leaving open since there is the extra element.

Visuals:
easyreplicate

PXL_20240926_215419502.TS.mp4
@KatieWoe KatieWoe added the type:wontfix This will not be worked on label Sep 30, 2024
@kathy-phet
Copy link

@arouinfar - I think even with this additional info Katie shared, we should still not fix. It feels pretty odd to pause and change things in this very manipulated way. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants