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

Should Scratch 3 collisions be deterministic? #2073

Open
griffpatch opened this issue Mar 27, 2019 · 1 comment
Open

Should Scratch 3 collisions be deterministic? #2073

griffpatch opened this issue Mar 27, 2019 · 1 comment

Comments

@griffpatch
Copy link
Contributor

Expected Behavior

Playback of gameplay movements recorded into a list should result in the same game play video each time independent of screen resolution.

Actual Behavior

At full screen / project view sizes the game play changes, I suspect due to differing collision regions / rasterized silhouettes? This may well be something that is the desired behavior based on Scratch 2 compatibility? But it would be nice for your project to run the same no matter fullscreen or windowed. Would be nice to know if this is expected :) thanks.

Steps to Reproduce

  1. Open this project but do not go fullscreen - https://scratch.mit.edu/projects/292297781
  2. Run project and 'watch' level 2 - Level will complete
  3. Now go fullscreen and do the same again - This time the player dies hitting one of the enemies.
  4. Go back to project player size and repeat - Player continues to die.
  5. Reload the project and now step 2 works once more...

The game was designed to be deterministic. I can't guarantee this is the case at present as I haven't done thorough tests of how the broadcasts might get out of sync under heavy load, but it does appear to play back consistently at a given resolution. This leads me to my conclusions in 'actual behavior'.

Operating System and Browser

Chrome on windows PC

@griffpatch griffpatch changed the title Should Scratch 3 be deterministic? Should Scratch 3 collisions be deterministic? Mar 27, 2019
@AmazingMech2418
Copy link
Contributor

This issue seems to be in scratch-renderer.

Seems like there is already an issue there too: scratchfoundation/scratch-render#656

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants