microsoft / microsoft/pxt-microbit

Beta: Neopixels in simulator show wrong colours when not GRB

Open
#5,152 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

extension help wanted neopixel P2
Dominant language
TypeScript
Stars
804
Forks
721
Avg merge
2d 9h
Merged PRs (30d)
2

Description

Describe the bug
Neopixels in the simulator show wrong colours, unless the strip is specified to be GRB. It's the same in live and beta.

Related: https://github.com/microsoft/pxt-microbit/issues/3134 https://github.com/microsoft/pxt-microbit/issues/2940

Arising from https://support.microbit.org/helpdesk/tickets/63295 (private)

To Reproduce
Steps to reproduce the behavior:

  1. Load https://makecode.microbit.org/_D7bVAgdLYdEr
  2. See red in simulator

Expected behavior
The neopixels in the simulator show the correct colours

Screenshots
image

micro:bit version (please complete the following information):
not hardware related

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows
  • Browser [e.g. chrome, safari] Chrome
  • Version [e.g. 22] 113

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the linked MakeCode reproduction and compare simulator output when the Neopixel strip is configured with non-GRB colour ordering. Read the related issues #3134 and #2940 for context, then verify that simulator colours match the configured ordering in both live and beta versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.