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

Console output may show incorrect variable values on a real device #1251

kevinjwalters opened this issue Aug 27, 2019 · 1 comment


Copy link

commented Aug 27, 2019

Describe the bug
This is a strange bug and can take a while to reproduce. It's challenging to describe the exact sequence of events to trigger it. I made a video so the timing can be analysed. This is not necessarily a console bug, this is equally likely to be something where the game look breaks.

This may have something to do with when or how long the user spends in the menu to turn on the console? Or perhaps some scoping or optimisation issue? Or something else!

This is for beta beta currently 0.14.4 5.21.6.

I've not seen this in the simulator.

To Reproduce
Steps to reproduce the behavior:

  1. Do a lot of different combinations of pressing A and B and turning console on with different timings around the application's first 5 and second 5 second pause.
  2. Be lucky.
  3. Video what you do to then work out the exact sequence of inputs.

Expected behavior
Most of the time the logged values are counters and these increment as one would expect and can be inspected by tapping the B button.

Obscure MakeCode Arcade bug only on devices (YouTube).

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Chrome
  • Version: n/a

Smartphone (please complete the following information):

  • Device: Adafruit PyGamer
  • OS: bootloader v3.7.0

Additional context
This is mentioned on MakeCode Forum: Sequence of execution between outer blocks in Arcade.

Here's the code (embedded png):



This comment has been minimized.

Copy link

commented Sep 4, 2019

I don't think it's directly related but it's interesting to see from #1272 that there are some fringe cases where the game loop/event are buggy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.