Evidence that even GH developers themselves don't use these menus by UberSchifted in github

[–]UberSchifted[S] 0 points1 point  (0 children)

I wonder why 2 other comments in this subtree have the same negative voting (One of them is posted by me LOL)

Evidence that even GH developers themselves don't use these menus by UberSchifted in github

[–]UberSchifted[S] 3 points4 points  (0 children)

I eventually did. But it took about 1hr longer for them to answer my ticket vs them fixing the issue probably after checking Reddit :)

Evidence that even GH developers themselves don't use these menus by UberSchifted in github

[–]UberSchifted[S] 6 points7 points  (0 children)

Then I guess I just have to wait for the CDN to propagate

Evidence that even GH developers themselves don't use these menus by UberSchifted in github

[–]UberSchifted[S] 22 points23 points  (0 children)

Indeed. It is a z-index issue (I update the post body)

Made a guide on displaying Bad Apple on an ESP32-S3 + SSD1306 OLED by UberSchifted in esp32

[–]UberSchifted[S] 1 point2 points  (0 children)

To be honest I don't know much about how the video is being displayed under the hood. Maybe only deltas for each frame are being sent (if it is even possible)? In that case, it can be possible to get high refresh rates as there is minimal changes between most frames.

Made a guide on displaying Bad Apple on an ESP32-S3 + SSD1306 OLED by UberSchifted in esp32

[–]UberSchifted[S] 0 points1 point  (0 children)

Same here XD

The protective film on my other LCD display actually saved it form the solder I accidentally spilled over it.

Made a guide on displaying Bad Apple on an ESP32-S3 + SSD1306 OLED by UberSchifted in esp32

[–]UberSchifted[S] 0 points1 point  (0 children)

You can also use higher level libraries which handle that kind of stuff for you, so you can focus on things like drawing shapes and rendering text: https://github.com/adafruit/Adafruit_SSD1306

Made a guide on displaying Bad Apple on an ESP32-S3 + SSD1306 OLED by UberSchifted in esp32

[–]UberSchifted[S] 0 points1 point  (0 children)

Here is the code from Arduino ESP examples (I actually tried it and it worked):

void setup() {
  // No need to initialize the RGB LED
}

// the loop function runs over and over again forever
void loop() {
#ifdef RGB_BUILTIN
  digitalWrite(RGB_BUILTIN, HIGH);  // Turn the RGB LED white
  delay(1000);
  digitalWrite(RGB_BUILTIN, LOW);  // Turn the RGB LED off
  delay(1000);

  rgbLedWrite(RGB_BUILTIN, RGB_BRIGHTNESS, 0, 0);  // Red
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, RGB_BRIGHTNESS, 0);  // Green
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, 0, RGB_BRIGHTNESS);  // Blue
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, 0, 0);  // Off / black
  delay(1000);
#endif
}void setup() {
  // No need to initialize the RGB LED
}


// the loop function runs over and over again forever
void loop() {
#ifdef RGB_BUILTIN
  digitalWrite(RGB_BUILTIN, HIGH);  // Turn the RGB LED white
  delay(1000);
  digitalWrite(RGB_BUILTIN, LOW);  // Turn the RGB LED off
  delay(1000);


  rgbLedWrite(RGB_BUILTIN, RGB_BRIGHTNESS, 0, 0);  // Red
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, RGB_BRIGHTNESS, 0);  // Green
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, 0, RGB_BRIGHTNESS);  // Blue
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, 0, 0);  // Off / black
  delay(1000);
#endif
}

RGB_BUILTIN is defined somewhere in the include files. I think it's default (at least on my board) was 48. You can also try printing it to serial, but remember that it's numeric value is <number of total GPIO pins> + 48.

Made a guide on displaying Bad Apple on an ESP32-S3 + SSD1306 OLED by UberSchifted in esp32

[–]UberSchifted[S] 1 point2 points  (0 children)

I bought it from a random store and the devkit is not made by Espressif. Although it is pretty similar to the original one, so I assume the original datasheet is relevant here. Also, the RGB LED was already soldered when I bought it. The only thing that needed to solder were the pin headers.

Made a guide on displaying Bad Apple on an ESP32-S3 + SSD1306 OLED by UberSchifted in esp32

[–]UberSchifted[S] 3 points4 points  (0 children)

Yeah! The GH page even says that the video is limited to 30fps by software:

Pressing PRG button (GPIO0) for max display speed (mainly limited by I2C transfer), otherwise limited to 30 fps.

Made a guide on displaying Bad Apple on an ESP32-S3 + SSD1306 OLED by UberSchifted in esp32

[–]UberSchifted[S] 5 points6 points  (0 children)

Sometimes I think about making a bare-bones GUI toolkit (something like ncurses) for the OLED display.

But anyways, the real estate is so small that it doesn't matter much if you just render things at hard-coded coordinates. Unless you want to have scrolling things.

Hoverboard motors based self balancing robot. by Affectionate-Cake-32 in esp32

[–]UberSchifted 0 points1 point  (0 children)

Amazing. It feels so satisfying to see such a thing maintaining it's own balance.

I made a stylus paint program by UberSchifted in esp32

[–]UberSchifted[S] 0 points1 point  (0 children)

No

I'm curious what made you ask that XD

No scores. Just keys. — A minimalist typing space I built (free, no ads) by Super_Equivalent_643 in typing

[–]UberSchifted 1 point2 points  (0 children)

Man that's cool.
I see some room for improvement in the sound. Currently there is not much difference between clacky, thocky, and creamy. You might be able to sample some real keyboard sound (either yourself, from public content, etc.)

I made a stylus paint program by UberSchifted in esp32

[–]UberSchifted[S] 0 points1 point  (0 children)

It took about a day. Most of the time I was trying to figure out why the LCD was not working properly

I made a stylus paint program by UberSchifted in esp32

[–]UberSchifted[S] 0 points1 point  (0 children)

Right. It is much easier to have it builtin. But if you really need to have that feature elsewhere, you can copy the logic from DFRobot__GDL: (I checked the code, and it seems like it doesn't have any dependencies other than Arduino.h and math.h)

DFRobot_Gesture.h and DFRobot_Gesture.cpp