@Kirill

Seeing if I can recreate this with a PICO, and hopefully increasing my size of the screen later on..

Devlog #2

After several hours of experimenting, I finally got an interactive mesh working properly.
This started as a “quick test” and slowly turned into one of those situations where every fix created a new problem… (guys this devlog was supposed to be done by YESTERDAY….)
The mesh was originally glitching, rotating incorrectly, and behaving in ways I did not expect or design for.
After a lot of iteration, restarting, and adjusting parameters, it is now stable and behaves as intended. It responds correctly to interaction instead of producing inconsistent movement or visual artifacts.
Alongside that, I also implemented a proper screenshot button. It captures the current state of the application cleanly without relying on external tools or manual screen capture. It is a small feature, but it makes testing and documentation significantly easier.
There is a 10 second delay to allow you to set where you want the structure to freeze at.
Current state of the project is more stable than before, but still fragile in the way most early builds tend to be.
My next steps would be to add a draw and color organizer feature if possible..

Devlog #1 (~5-6 hrs)AFTER grueling hours of fighting with my laptop, I FINALLY got WakaTime and Hackatime working in VS Code. 🎉It actually logs my coding time now… a whole 30 minutes of productivity has officially been recorded….except for whatever reason it refuses to upload my VS Code stats.So that’s nice. 👍I also finished a little test.py after realizing my laptop was missing some drivers needed to run the project. Not exactly the groundbreaking progress I imagined, but progress is progress.Then I discovered the next boss fight…Some of the libraries this project depends on are basically fossils.They only work with older Python versions and older package versions, so every single time I want to run the project I have to spin up a fresh virtual environment just to stop everything from exploding.It’s one of those projects where the setup takes longer than writing the code.Part of me wants to just vibecode my way through this……but my previous “I’ll just wing it” projects usually ended with broken code, questionable decisions, and me somehow making the project worse than when I started.So maybe we’ll take the slow route this time.

🚧 What’s Next?

Devlog #2 ~5-6 hrs

Devlog #3 ~24 hrs

Devlog #4 ~tomorrow

Prototype v0.5 ~48 hrs

Devlog #5 ~53 hrs

Touches v0.9 ~60 hrs

Release v1.0 ~67 hrs

Hotfixes v1.1 ~72 hrs

👌 Hopefully I don’t completely slack off before then.Once v1.0 is out, I’m probably just going to ship it immediately because patience is overrated.If something catches on fire, I’ll pretend it was intentional and upload the fixes to GitHub afterward 😭.

made the wires look cleaner..

Making an ESP32 mini monitor. Check it out. Right now I made the base model which is ran on a 128/64 OLED screen and converts an mp4 file on your desktop into a specialized file that is uploaded directly into the esp. This allows for short clips to be played on the ESP32s screen.

Making an ESP32 mini monitor. Check it out. Right now I made the base model which is ran on a 128/64 OLED screen and converts an mp4 file on your desktop into a specialized file that is uploaded directly into the esp. This allows for short clips to be played on the ESP32s screen.