|
4151
|
Larper's Player Supreme by @dbkickva | Stardan Larper's Player Supreme by @dbkickva | Stardance...
|
dbkickva
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Larper's Player Supreme by @dbkickva | Title: Larper's Player Supreme by @dbkickva | Stardance...
|
1792716913.1485014
|
1793321713.1485014
|
|
4152
|
My awesome macropad! by @alejandro86 | Stardance
|
alejandro86
|
0
|
0.49
|
0
|
[]
|
[{"post_id": 5411, "ts": "2026 [{"post_id": 5411, "ts": "2026-06-09T05:08:50Z", "hours": 0.4911, "text": "I just finished the schematic. It took me a little while to begin working on it, I was following the given guide as practice to get familiar with KICAD before I began working on my official design. I’ve also been using AI to help guide me with resolving any errors I might have made."}]...
|
Title: My awesome macropad! by @alejandro86 | Star Title: My awesome macropad! by @alejandro86 | Stardance
Devlogs:
I just finished the schematic. It took me a little while to begin working on it, I was following the given guide as practice to get familiar with KICAD before I began working on my official design. I’ve also been using AI to help guide me with resolving any errors I might have made....
|
1792745364.322187
|
1793350164.322187
|
|
4154
|
My first slack bot! by @bartoszszafir1 | Stardance
|
bartoszszafir1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @bartoszszafir1 | St Title: My first slack bot! by @bartoszszafir1 | Stardance...
|
1793166759.1536922
|
1793771559.1536922
|
|
4155
|
My awesome macropad! by @Odilbek | Stardance
|
Odilbek
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Odilbek | Stardanc Title: My awesome macropad! by @Odilbek | Stardance...
|
1792662823.6481204
|
1793267623.6481204
|
|
4156
|
My awesome macropad! by @bartoszszafir1 | Stardanc My awesome macropad! by @bartoszszafir1 | Stardance...
|
bartoszszafir1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @bartoszszafir1 | S Title: My awesome macropad! by @bartoszszafir1 | Stardance...
|
1792770771.6804023
|
1793375571.6804023
|
|
4158
|
macropad! by @sh8nn0n_ | Stardance
|
sh8nn0n_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: macropad! by @sh8nn0n_ | Stardance
|
1793145046.1435757
|
1793749846.1435757
|
|
4159
|
Alala Data Analyzer by @Jaxon_Mazu | Stardance
|
Jaxon_Mazu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Alala Data Analyzer by @Jaxon_Mazu | Starda Title: Alala Data Analyzer by @Jaxon_Mazu | Stardance...
|
1792677223.3354704
|
1793282023.3354704
|
|
4160
|
TTB by @RyanB | Stardance
|
RyanB
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: TTB by @RyanB | Stardance
|
1793159414.0568807
|
1793764214.0568807
|
|
4161
|
vexID by @eli_ozcan | Stardance
|
eli_ozcan
|
0
|
11.77
|
0
|
[]
|
[{"post_id": 60448, "ts": "202 [{"post_id": 60448, "ts": "2026-09-02T19:40:56Z", "hours": 8.1142, "text": "Lots of engineering went into this build, but I finally got a few new things working. 3D scanning: LiDAR depth is now filtered and fused with the AR mesh for cleaner, more accurate surfaces. Meshes now weld seams, remove bad geometry, preserve corners, and repair small holes. Blurry or fast-moving frames are rejected for sharper textures. AprilTags are “lock”able now and after a few positions viewed + ray casts on the mesh they cannot move. UI changes: The scanner now shows mapped surfaces, live depth points, coverage, range, tracking quality, and tag-lock progress. Photos and 3D scans are now both “Areas”. The 3D viewer looks nicer and has highlighting + better camera controls now. Photo areas can rerun AprilTag detection without being deleted and recreated. AprilTag Metal backend: I looked at some NVIDIA shaders and the C++ code and built a Metal backend for AprilTag detection. This runs on the GPU and gets a way higher fps for me. This reduces lag when scanning around as well as 3D scanning (makes the position more accurate to the mesh). Concurrency is also possible. Fallback to CPU."}, {"post_id": 33439, "ts": "2026-07-23T11:59:50Z", "hours": 1.3664, "text": "improved UI. app performance, added accurate privacy policy, 3d scanning fixed and it actually works now except it’s rly laggy but the meshes don’t look ahh anymore."}, {"post_id": 12747, "ts": "2026-06-20T20:52:28Z", "hours": 1.3389, "text": "Tracking works better now, I also added support for tag groups. Example: high strength gears are their own tag now instead of needing to place EVERY HS gear tag on a box"}, {"post_id": 11804, "ts": "2026-06-19T06:44:46Z", "hours": 0.9525, "text": "improving model performance by adding new items to the dataset and recording new real data. I also worked on the 3D scanning feature on iOS and Ifixed the missing triangles error as well as got the raycast to work on the mesh instead of an AR plane which makes the positions of AprilTags 10000x better."}]...
|
Title: vexID by @eli_ozcan | Stardance
Devlogs:
i Title: vexID by @eli_ozcan | Stardance
Devlogs:
improving model performance by adding new items to the dataset and recording new real data. I also worked on the 3D scanning feature on iOS and Ifixed the missing triangles error as well as got the raycast to work on the mesh instead of an AR plane which makes the positions of AprilTags 10000x better.
Tracking works better now, I also added support for tag groups. Example: high strength gears are their own tag now instead of needing to place EVERY HS gear tag on a box
improved UI. app performance, added accurate privacy policy, 3d scanning fixed and it actually works now except it’s rly laggy but the meshes don’t look ahh anymore.
Lots of engineering went into this build, but I finally got a few new things working. 3D scanning: LiDAR depth is now filtered and fused with the AR mesh for cleaner, more accurate surfaces. Meshes now weld seams, remove bad geometry, preserve corners, and repair small holes. Blurry or fast-moving frames are rejected for sharper textures. AprilTags are “lock”able now and after a few positions viewed + ray casts on the mesh they cannot move. UI changes: The scanner now shows mapped surfaces, live depth points, coverage, range, tracking quality, and tag-lock progress. Photos and 3D scans are now both “Areas”. The 3D viewer looks nicer and has highlighting + better camera controls now. Photo areas can rerun AprilTag detection without being deleted and recreated. AprilTag Metal backend: I looked at some NVIDIA shaders and the C++ code and built a Metal backend for AprilTag detection. This runs on the GPU and gets a way higher fps for me. This reduces lag when scanning around as well as 3D scanning (makes the position more accurate to the mesh). Concurrency is also possible. Fallback to CPU....
|
1792587240.4579005
|
1793192040.4579005
|
|
4162
|
zkFog: Referee-Less Fog of War Chess by @kev | Sta zkFog: Referee-Less Fog of War Chess by @kev | Stardance...
|
kev
|
0
|
1.77
|
0
|
[]
|
[{"post_id": 44259, "ts": "202 [{"post_id": 44259, "ts": "2026-08-09T21:49:26Z", "hours": 1.7703, "text": "Hey Hack Clubbers! I’m building zkFog , a website that lets you play fog-of-war chess without a trusted server. In fog chess you only see the squares your pieces can move to, and normally a server hides the rest of the board and everyone trusts it. I’m replacing that server with zero-knowledge proofs so that each player’s view is secret to only them, not even the server, and cryptography proves that the moves are legal. ~2 hours in: built a 6x6 Los Alamos chess UI to keep implementation simple for now. Using Bun + Vite + Biome , and chessgroundx for the UI. I also added a bit of CSS to emulate the snappiness of chess.com’s UI. I’ve also coded from scratch the engine that determines move legality (the dots that show up when you drag a piece)."}]...
|
Title: zkFog: Referee-Less Fog of War Chess by @ke Title: zkFog: Referee-Less Fog of War Chess by @kev | Stardance
Devlogs:
Hey Hack Clubbers! I’m building zkFog , a website that lets you play fog-of-war chess without a trusted server. In fog chess you only see the squares your pieces can move to, and normally a server hides the rest of the board and everyone trusts it. I’m replacing that server with zero-knowledge proofs so that each player’s view is secret to only them, not even the server, and cryptography proves that the moves are legal. ~2 hours in: built a 6x6 Los Alamos chess UI to keep implementation simple for now. Using Bun + Vite + Biome , and chessgroundx for the UI. I also added a bit of CSS to emulate the snappiness of chess.com’s UI. I’ve also coded from scratch the engine that determines move legality (the dots that show up when you drag a piece)....
|
1792806461.5754397
|
1793411261.5754397
|
|
4163
|
My awesome macropad! by @crepperibrahim2 | Stardan My awesome macropad! by @crepperibrahim2 | Stardance...
|
crepperibrahim2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @crepperibrahim2 | Title: My awesome macropad! by @crepperibrahim2 | Stardance...
|
1792579829.1887467
|
1793184629.1887467
|
|
4164
|
Untitled project by @Astrino | Stardance
|
Astrino
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Astrino | Stardance
|
1792799553.2927914
|
1793404353.2927914
|
|
4165
|
DevKeep by @madankhatri | Stardance
|
madankhatri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DevKeep by @madankhatri | Stardance
|
1792702246.624912
|
1793307046.624912
|
|
4166
|
Project New Heavens by @AmanAV | Stardance
|
AmanAV
|
0
|
14.68
|
0
|
[]
|
[{"post_id": 17645, "ts": "202 [{"post_id": 17645, "ts": "2026-06-28T15:09:23Z", "hours": 10.0122, "text": "Hey everyone, My CAD model of Project New Heavens (It’s Supposed to be another version of the name Project Hail Mary), is almost complete. As this will be more than 20 metres in length and about a metre in height, I will not be able to make it in real life, but big Space companies with humungous 3D printers will be able to make this. ––––––––––––––––––––––––––Anyway, about the design updates. I have made the wings into a better shape so that it stays steady in high vibration. I have tried making a new kind of engine that uses only the gases that enter the ducts to the exhaust, on the way getting pressurised by a turbocharger and also being turned to plasma by passing high voltage electricity through a porous metal piece. So, I be soon making a video and shipping it with the model."}, {"post_id": 1322, "ts": "2026-06-03T08:03:57Z", "hours": 4.6647, "text": "Hey everyone, I’m working on a 3d model of a space ship that could possibly go interstellar if made in real life. As I’m new to 3d modelling and simulations, things might look sketchy at first, but I’ll try my best to make it look cool and practical…[below is just the outer body, the rest is coming up(even some more parts for the outer body), and I’ll update soon…"}]...
|
Title: Project New Heavens by @AmanAV | Stardance
Title: Project New Heavens by @AmanAV | Stardance
Devlogs:
Hey everyone, I’m working on a 3d model of a space ship that could possibly go interstellar if made in real life. As I’m new to 3d modelling and simulations, things might look sketchy at first, but I’ll try my best to make it look cool and practical…[below is just the outer body, the rest is coming up(even some more parts for the outer body), and I’ll update soon…
Hey everyone, My CAD model of Project New Heavens (It’s Supposed to be another version of the name Project Hail Mary), is almost complete. As this will be more than 20 metres in length and about a metre in height, I will not be able to make it in real life, but big Space companies with humungous 3D printers will be able to make this. ––––––––––––––––––––––––––Anyway, about the design updates. I have made the wings into a better shape so that it stays steady in high vibration. I have tried making a new kind of engine that uses only the gases that enter the ducts to the exhaust, on the way getting pressurised by a turbocharger and also being turned to plasma by passing high voltage electricity through a porous metal piece. So, I be soon making a video and shipping it with the model....
|
1792529604.0671952
|
1793134404.0671952
|
|
4167
|
My awesome macropad! by @pushkar_jadhav2419 | Star My awesome macropad! by @pushkar_jadhav2419 | Stardance...
|
pushkar_jadhav2419
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @pushkar_jadhav2419 Title: My awesome macropad! by @pushkar_jadhav2419 | Stardance...
|
1792619448.5687125
|
1793224248.5687125
|
|
4168
|
My first slack bot! by @psyduck | Stardance
|
psyduck
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @psyduck | Stardance
|
1792579939.1722047
|
1793184739.1722047
|
|
4169
|
Breakerz by @Nasir | Stardance
|
Nasir
|
0
|
1.18
|
0
|
[]
|
[{"post_id": 1300, "ts": "2026 [{"post_id": 1300, "ts": "2026-06-03T06:21:30Z", "hours": 1.1783, "text": "Making Basic models for my starting weapons :)"}]...
|
Title: Breakerz by @Nasir | Stardance
Devlogs:
Ma Title: Breakerz by @Nasir | Stardance
Devlogs:
Making Basic models for my starting weapons :)...
|
1792918147.6483126
|
1793782147.6483126
|
|
4170
|
The Chair by @eli_ozcan | Stardance
|
eli_ozcan
|
0
|
37.21
|
0
|
[]
|
[{"post_id": 70558, "ts": "202 [{"post_id": 70558, "ts": "2026-09-19T11:23:04Z", "hours": 3.655, "text": "CAD and Cleaning. Cleaned the chair with some rags and also lubricated gears with WD-40 to prepare for submission to my local fair. I also CADded a significant portion of the wheelbase in OnShape."}, {"post_id": 62832, "ts": "2026-09-06T11:17:28Z", "hours": 3.0989, "text": "Software Completion The chair finally drives reliably, and I can actually sit in it and move around now.The biggest challenge throughout the software was communication between the three Brains. I built a serial protocol that handles the startup handshake, LEFT/RIGHT assignment, health packets, retries, sequence/session validation, malformed frames, and local command timeouts. Early versions would still lose the link even when bytes were clearly being transmitted. This came from a combination of partial frames, serial self-echo, startup timing, and motor queries taking long enough to delay communication. I fixed these issues by improving the framing and recovery system, adding direction tags, limiting how much serial data can be processed in one loop, safely retrying packets, and prioritizing communication before slower motor checks.Motor initialization also caused problems because all of the V5 motors do not necessarily become available at exactly the same time after startup. Earlier versions would sometimes report motor disconnects or H-Bridge faults during startup. The drivetrain Brains now wait for every motor to begin returning valid health information before considering initialization complete. I also flipped the motor directions for the top and bottom of the drivetrain where needed.The controls were completed during this process. The broken throttle potentiometer was replaced with the Rotation Sensor on port 17. It now supports CENTER calibration and provides signed forward/reverse input. I corrected the steering direction and tuned the steering feedback. Controller mode now supports forward, reverse, normal turning, and turning in place.The safety system was also simplified into clear startup, parked, armed, and fault states. E-STOP is always available and is intentionally not recoverable without restarting the system. The drivetrain brakes use COAST.I moved the displays out of the main control path so rendering cannot interfere with serial communication. The master and drivetrain displays now provide live motor temperatures, faults, battery status, link state, steering/throttle positions, and communication diagnostics.I also updated VEXide and Rust during development. Current Issue I encountered one intermittent power issue during testing. The master Brain does not have its own battery and is powered through the Smart Cable connections from the two drivetrain Brains. During several tests, the master entered a white-screen state while one drivetrain Brain went completely black. The drivetrain side that shut off was not always the same.At the time, both drivetrain batteries were fairly low and were also at different charge levels, roughly 30–50%. I completely shut down the system, replaced both batteries, and restarted all three Brains. The issue stopped occurring after that, and the chair completed additional driving tests normally.My current theory is that the two independently powered drivetrain Brains may be interacting electrically through the master because the Smart Cable connections also carry power. Different battery voltages, or voltage sag while the motors were under load, may have caused a brief power transient. I have not confirmed this yet, so I am leaving the wiring unchanged while I collect more evidence.If the issue happens again, I may restructure the system so one drivetrain Brain also acts as the master, which would remove one Brain from the power-sharing arrangement. Another option would be changing how power is carried between the Brains while still keeping wired communication."}, {"post_id": 62524, "ts": "2026-09-05T22:56:47Z", "hours": 4.5833, "text": "Hardware Completion I finished the hardware on the chair. I added the bottom 2 drivetrain cortexes and connected everything to the master with smart cables. I added the batteries for them too. I figured out that the master cortex doesn’t need it’s own battery as it can be powered through the smart cables on p19-20 which connect to the drivetrain nodes. The batteries are shared across the whole system (3 cortex -> 2 lower bats powering wheels and controls + health checks). I added a small potentiometer and a gear to act as a speed controller but I have not determined exactly how I want to do that yet. I zip-tied all cables and such and tested that each one works and powers the device it connects to. All systems seem to be good in that regard. Added some bad off-center racing stripes lol and also fixed the sag on the steering wheel by adding an additional support screw. I also dusted and cleaned it because it was SO DIRTY from literally nothing. I temporarily moved it to my house so I can debug and program it at home. Bringing it back Sunday. TODO: Software & QA + Validation Master node will turn on first and wait for a connection from the two DT nodes. Then the DT nodes will recieve commands for voltages and will send back temperature and health records to ensure nothing breaks. If it gets too hot or too much tourque, it will initiate an emergency stop to ensure the saftey of the driver. Controls are TBD but it will also support a vex controller to drive it remotely. If a motor disconnects it will also shut down. I’m so excited this project is becoming real!!"}, {"post_id": 60426, "ts": "2026-09-02T18:48:45Z", "hours": 3.2472, "text": "Improve construction of chair and make it support ~160lbs of load(tested with the largest kid in my class). I am going to continue work on this. TODO: add more bar supports until I eventually reach the top. The wheels of the actual chair now float in the air which means it is fully supported by the base. I also switched the side the bars are on with the front half of the chair, they are held from the rear facing end now. This leaves plenty of room in the front for an eventual foot support, it also increases stability. Armrests were reinstalled again onto the new bar which goes across the front AND BACK. I ditched the middle-connectors and moved it to the back. This shifted where the center of mass could be which gives more opportunities for a rider stick their legs out. I personally rode around in it (not powered) by pushing the floor with my feet. This caused only the motors to spin. At this stage, enough rider weight will cause the chair to sag. To resolve this I am going to simply make the 4 pillars stronger on the cross-section by adding more horizontal bars. Overall difficulties when building this: the fact that the chair itself has weight and i couldn’t screw in or change stuff without having something holding it up… I chose to support it by 4 vex motors at a point. Screwing in at weird angles through multiple bars was pretty hard but I managed it (slowly). Overall TODO: MORE METAL everywhere. After this, I will add the cortexes and the steering wheel. This version is due for me by september 8th by lunch, we are going to use the chair to promote our robotics club at my high school at our club day fair (best decorated club table wins money for us) I plan on working more after school today. This log incorporates ~2 days of solid working hours."}, {"post_id": 21199, "ts": "2026-07-03T00:30:42Z", "hours": 2.7692, "text": "It works. I attached the drivetrain fully and then (not tracked oops) programmed a very simple mock control program and put it all on one brain (not final design). I no longer have access to my school as my job ended, I’ll finish this project when I come back to school in early August. I plan on (1) fixing the height of the drivetrain so it actually presses into the floor enough to drive smoothly, (2) reinstalling wheel and programming it for self driving, (3) final tweaks for stability"}, {"post_id": 16359, "ts": "2026-06-26T16:46:38Z", "hours": 2.2614, "text": "I got the drivetrain basically done"}, {"post_id": 14616, "ts": "2026-06-23T19:57:29Z", "hours": 1.1542, "text": "kinda dumb but I built the drivetrain and now I realize the gear is bigger than the wheel so it won’t move oops"}, {"post_id": 14565, "ts": "2026-06-23T18:48:45Z", "hours": 5.3917, "text": "Working on drivetrain now I also programmed the rest of the chair with a few safety settings so nobody gets hurt!"}, {"post_id": 12180, "ts": "2026-06-19T21:56:43Z", "hours": 2.2119, "text": "Re-added steering wheel with much stronger support bars and a shallower angle with a lower placement that makes it easier to see over and more comfortable to grip. I added the battery and a license plate to a new crossbar in the back."}, {"post_id": 12027, "ts": "2026-06-19T16:50:22Z", "hours": 0.7644, "text": "I took off the steering wheel so I can fix the wobble later, I am keeping that module though but extending the bar on the seatbelt thing"}, {"post_id": 11696, "ts": "2026-06-19T01:48:49Z", "hours": 0.5522, "text": "I switched this to a hardware project so I don’t have to use lapse anymore. I lost 4 hours today !! :| Anyways, I added the steering wheel today. It holds (kinda) well and it will (should) not fall off. Uses a Yoke design with a screen for HUD statistics like km/h and each node’s battery life, will program this later today. HUD will also be used for “ignition” and the unlock procedure. Considering using an SD card as a “key” for the “car”. The buttons on the wheel represent forward/reverse although I may want to make that it’s own gear shifter on the side and use both buttons as a forward (you have to click both, for saftey) I will also need to add the E-Stop somewhere. Excited how real this project is becoming!! Up next: 3D Printing a support bracket for the wheel bracket so that it doesn’t fall tf off anymore. (ribbed setup on the angled piece)"}, {"post_id": 11111, "ts": "2026-06-18T05:33:47Z", "hours": 6.0411, "text": "oh lord i forgot to make a devlog again… anyways throughout this time and many timelapses I have fully programmed the steering wheel code, it has a full resistance turning wheel that is based on a motor + its encoder. it uses the angle to determine what direction to steer and the wheel speed to determine how much force it adjusts back to the center with like a real automobile also I added a new bracket that mounts to the bottom of the chair with some drilled holes, this removes all wobble moreover, I added the steering wheel / front brace / steatbelt bar that falls down over you so you can grab the wheel and not go flying out (see fig. 1) room empty as week 1-2 kids no longer stay until 3rd and 4th period, however I now have much more time as my 4th period doesn’t exist anymore and I can grind for 2 hours minus my lunch time. That’s all folks, more updates coming soon. Hopefully, I’ll try to remember to post them this time."}, {"post_id": 3325, "ts": "2026-06-06T06:02:34Z", "hours": 1.4778, "text": "Started working on this old hunk of junk again. Me and my very technically literate friends got this idea at the start of the year. When we first entered the PLTW lab for the first time, we saw the chairs had wheels. Like a lightbulb, it clicked in all of our minds that we wanted to make a go kart… We didn’t work on it much, we snuck in during lunch freshman year but eventually the teacher in that room made us take it apart because we “were destroying school property” or whatever. To me, you just don’t like to have fun :( However, I’ve recently restarted. My friend group has recently been employed at our school to teach robotics to smelly middle schoolers over the summer (dude I thought me saying 67 was bad, GET A LOAD OF THESE GUYS). Together, our schedule has 2 free periods (as well as lunch) out of our 4 period day to do whatever in the PLTW room. Since we self-moderate ourselves and have our own keycards, we truly have free will to mess around with anything and everything. Currently, there is at least one Xbox from home and 3 computers loaded with Roblox on the DAILY. Overall, it’s just really nice being with your friends at school without going to school… Some of the middle schoolers like to stay in there during break/lunch to mess around with the parts, so I can’t lapse it during then. However, during my extra time, I am working on the chair or homework for my 4th period (pfft, I’d rather do the chair, its cool asf) To begin with the actual devlog, the chair part of the chair is a Rio 2 4-Leg Armless chair from SitOnIt Seating. It has an angled bottom with 4 screw holes – perfect for mounting something. Firstly, I dug up the old CAD files and trashed all of them starting from scratch. I took some measurements and 3D printed a new bracket for the bottom of the chair. Before, I just bent a piece of metal; but this time, i’d like to actually have something perfectly angled so it’s flat with the floor. I used Fusion 360 for all of my CAD work. In CAD, I designed a left and right armrest as well as a bar + some ziptie locations to keep everything stable (note, none of this was tracked. Moreover, I did some quick planning with ChatGPT to find an optimal drivetrain configuration. We settled on 200RPM with a 72:48T gear ratio (72T on motor, 48T on wheel) with 4 motors per side of a differential drivetrain for a total of 8. Some quick numbers: 24.8 lbf push forse and 3.57 mph, reasonable for a small vehicle but not a death kart. .. and then stardance started.. YUP! None of that work was tracked!! YIPEEE. Now, this is what I did in the 1h 28m: Afterwards, I began work on the actual construction. First I bolted on the bracket to the 3x C-Channel main bar. I then screwed it onto the chair and OOPS we need to drill some holes because my measurements were way off (screw you, old dial caliper.. or maybe I can’t read it idk). I built the left and right armrest models in real life in the PLTW room at my school. (lapsed) I then put them onto the bracket (lapsed) .. and finally, I built the motor frame for the left half of the drivetrain. That’s all folks, I hope (and am on track) to finish this in under a month, which is good because my summer school ends in 3 weeks.."}]...
|
Title: The Chair by @eli_ozcan | Stardance
Devlog Title: The Chair by @eli_ozcan | Stardance
Devlogs:
Started working on this old hunk of junk again. Me and my very technically literate friends got this idea at the start of the year. When we first entered the PLTW lab for the first time, we saw the chairs had wheels. Like a lightbulb, it clicked in all of our minds that we wanted to make a go kart… We didn’t work on it much, we snuck in during lunch freshman year but eventually the teacher in that room made us take it apart because we “were destroying school property” or whatever. To me, you just don’t like to have fun :( However, I’ve recently restarted. My friend group has recently been employed at our school to teach robotics to smelly middle schoolers over the summer (dude I thought me saying 67 was bad, GET A LOAD OF THESE GUYS). Together, our schedule has 2 free periods (as well as lunch) out of our 4 period day to do whatever in the PLTW room. Since we self-moderate ourselves and have our own keycards, we truly have free will to mess around with anything and everything. Currently, there is at least one Xbox from home and 3 computers loaded with Roblox on the DAILY. Overall, it’s just really nice being with your friends at school without going to school… Some of the middle schoolers like to stay in there during break/lunch to mess around with the parts, so I can’t lapse it during then. However, during my extra time, I am working on the chair or homework for my 4th period (pfft, I’d rather do the chair, its cool asf) To begin with the actual devlog, the chair part of the chair is a Rio 2 4-Leg Armless chair from SitOnIt Seating. It has an angled bottom with 4 screw holes – perfect for mounting something. Firstly, I dug up the old CAD files and trashed all of them starting from scratch. I took some measurements and 3D printed a new bracket for the bottom of the chair. Before, I just bent a piece of metal; but this time, i’d like to actually have something perfectly angled so it’s flat with the floor. I used Fusion 360 for all of my CAD work. In CAD, I designed a left and right armrest as well as a bar + some ziptie locations to keep everything stable (note, none of this was tracked. Moreover, I did some quick planning with ChatGPT to find an optimal drivetrain configuration. We settled on 200RPM with a 72:48T gear ratio (72T on motor, 48T on wheel) with 4 motors per side of a differential drivetrain for a total of 8. Some quick numbers: 24.8 lbf push forse and 3.57 mph, reasonable for a small vehicle but not a death kart. .. and then stardance started.. YUP! None of that work was tracked!! YIPEEE. Now, this is what I did in the 1h 28m: Afterwards, I began work on the actual construction. First I bolted on the bracket to the 3x C-Channel main bar. I then screwed it onto the chair and OOPS we need to drill some holes because my measurements were way off (screw you, old dial caliper.. or maybe I can’t read it idk). I built the left and right armrest models in real life in the PLTW room at my school. (lapsed) I then put them onto the bracket (lapsed) .. and finally, I built the motor frame for the left half of the drivetrain. That’s all folks, I hope (and am on track) to finish this in under a month, which is good because my summer school ends in 3 weeks..
oh lord i forgot to make a devlog again… anyways throughout this time and many timelapses I have fully programmed the steering wheel code, it has a full resistance turning wheel that is based on a motor + its encoder. it uses the angle to determine what direction to steer and the wheel speed to determine how much force it adjusts back to the center with like a real automobile also I added a new bracket that mounts to the bottom of the chair with some drilled holes, this removes all wobble moreover, I added the steering wheel / front brace / steatbelt bar that falls down over you so you can grab the wheel and not go flying out (see fig. 1) room empty as week 1-2 kids no longer stay until 3rd and 4th period, however I now have much more time as my 4th period doesn’t exist anymore and I can grind for 2 hours minus my lunch time. That’s all folks, more updates coming soon. Hopefully, I’ll try to remember to post them this time.
I switched this to a hardware project so I don’t have to use lapse anymore. I lost 4 hours today !! :| Anyways, I added the steering wheel today. It holds (kinda) well and it will (should) not fall off. Uses a Yoke design with a screen for HUD statistics like km/h and each node’s battery life, will program this later today. HUD will also be used for “ignition” and the unlock procedure. Considering using an SD card as a “key” for the “car”. The buttons on the wheel represent forward/reverse although I may want to make that it’s own gear shifter on the side and use both buttons as a forward (you have to click both, for saftey) I will also need to add the E-Stop somewhere. Excited how real this project is becoming!! Up next: 3D Printing a support bracket for the wheel bracket so that it doesn’t fall tf off anymore. (ribbed setup on the angled piece)
I took off the steering wheel so I can fix the wobble later, I am keeping that module though but extending the bar on the seatbelt thing
Re-added steering wheel with much stronger support bars and a shallower angle with a lower placement that makes it easier to see over and more comfortable to grip. I added the battery and a license plate to a new crossbar in the back.
Working on drivetrain now I also programmed the rest of the chair with a few safety settings so nobody gets hurt!
kinda dumb but I built the drivetrain and now I realize the gear is bigger than the wheel so it won’t move oops
I got the drivetrain basically done
It works. I attached the drivetrain fully and then (not tracked oops) programmed a very simple mock control program and put it all on one brain (not final design). I no longer have access to my school as my job ended, I’ll finish this project when I come back to school in early August. I plan on (1) fixing the height of the drivetrain so it actually presses into the floor enough to drive smoothly, (2) reinstalling wheel and programming it for self driving, (3) final tweaks for stability
Improve construction of chair and make it support ~160lbs of load(tested with the largest kid in my class). I am going to continue work on this. TODO: add more bar supports until I eventually reach the top. The wheels of the actual chair now float in the air which means it is fully supported by the base. I also switched the side the bars are on with the front half of the chair, they are held from the rear facing end now. This leaves plenty of room in the front for an eventual foot support, it also increases stability. Armrests were reinstalled again onto the new bar which goes across the front AND BACK. I ditched the middle-connectors and moved it to the back. This shifted where the center of mass could be which gives more opportunities for a rider stick their legs out. I personally rode around in it (not powered) by pushing the floor with my feet. This caused only the motors to spin. At this stage, enough rider weight will cause the chair to sag. To resolve this I am going to simply make the 4 pillars stronger on the cross-section by adding more horizontal bars. Overall difficulties when building this: the fact that the chair itself has weight and i couldn’t screw in or change stuff without having something holding it up… I chose to support it by 4 vex motors at a point. Screwing in at weird angles through multiple bars was pretty hard but I managed it (slowly). Overall TODO: MORE METAL everywhere. After this, I will add the cortexes and the steering wheel. This version is due for me by september 8th by lunch, we are going to use the chair to promote our robotics club at my high school at our club day fair (best decorated club table wins money for us) I plan on working more after school today. This log incorporates ~2 days of solid working hours.
Hardware Completion I finished the hardware on the chair. I added the bottom 2 drivetrain cortexes and connected everything to the master with smart cables. I added the batteries for them too. I figured out that the master cortex doesn’t need it’s own battery as it can be powered through the smart cables on p19-20 which connect to the drivetrain nodes. The batteries are shared across the whole system (3 cortex -> 2 lower bats powering wheels and controls + health checks). I added a small potentiometer and a gear to act as a speed controller but I have not determined exactly how I want to do that yet. I zip-tied all cables and such and tested that each one works and powers the device it connects to. All systems seem to be good in that regard. Added some bad off-center racing stripes lol and also fixed the sag on the steering wheel by adding an additional support screw. I also dusted and cleaned it because it was SO DIRTY from literally nothing. I temporarily moved it to my house so I can debug and program it at home. Bringing it back Sunday. TODO: Software & QA + Validation Master node will turn on first and wait for a connection from the two DT nodes. Then the DT nodes will recieve commands for voltages and will send back temperature and health records to ensure nothing breaks. If it gets too hot or too much tourque, it will initiate an emergency stop to ensure the saftey of the driver. Controls are TBD but it will also support a vex controller to drive it remotely. If a motor disconnects it will also shut down. I’m so excited this project is becoming real!!
Software Completion The chair finally drives reliably, and I can actually sit in it and move around now.The biggest challenge throughout the software was communication between the three Brains. I built a serial protocol that handles the startup handshake, LEFT/RIGHT assignment, health packets, retries, sequence/session validation, malformed frames, and local command timeouts. Early versions would still lose the link even when bytes were clearly being transmitted. This came from a combination of partial frames, serial self-echo, startup timing, and motor queries taking long enough to delay communication. I fixed these issues by improving the framing and recovery system, adding direction tags, limiting how much serial data can be processed in one loop, safely retrying packets, and prioritizing communication before slower motor checks.Motor initialization also caused problems because all of the V5 motors do not necessarily become available at exactly the same time after startup. Earlier versions would sometimes report motor disconnects or H-Bridge faults during startup. The drivetrain Brains now wait for every motor to begin returning valid health information before considering initialization complete. I also flipped the motor directions for the top and bottom of the drivetrain where needed.The controls were completed during this process. The broken throttle potentiometer was replaced with the Rotation Sensor on port 17. It now supports CENTER calibration and provides signed forward/reverse input. I corrected the steering direction and tuned the steering feedback. Controller mode now supports forward, reverse, normal turning, and turning in place.The safety system was also simplified into clear startup, parked, armed, and fault states. E-STOP is always available and is intentionally not recoverable without restarting the system. The drivetrain brakes use COAST.I moved the displays out of the main control path so rendering cannot interfere with serial communication. The master and drivetrain displays now provide live motor temperatures, faults, battery status, link state, steering/throttle positions, and communication diagnostics.I also updated VEXide and Rust during development. Current Issue I encountered one intermittent power issue during testing. The master Brain does not have its own battery and is powered through the Smart Cable connections from the two drivetrain Brains. During several tests, the master entered a white-screen state while one drivetrain Brain went completely black. The drivetrain side that shut off was not always the same.At the time, both drivetrain batteries were fairly low and were also at different charge levels, roughly 30–50%. I completely shut down the system, replaced both batteries, and restarted all three Brains. The issue stopped occurring after that, and the chair completed additional driving tests normally.My current theory is that the two independently powered drivetrain Brains may be interacting electrically through the master because the Smart Cable connections also carry power. Different battery voltages, or voltage sag while the motors were under load, may have caused a brief power transient. I have not confirmed this yet, so I am leaving the wiring unchanged while I collect more evidence.If the issue happens again, I may restructure the system so one drivetrain Brain also acts as the master, which would remove one Brain from the power-sharing arrangement. Another option would be changing how power is carried between the Brains while still keeping wired communication.
CAD and Cleaning. Cleaned the chair with some rags and also lubricated gears with WD-40 to prepare for submission to my local fair. I also CADded a significant portion of the wheelbase in OnShape....
|
1792730942.941369
|
1793335742.941369
|
|
4171
|
dialbreak by @stellenium | Stardance
|
stellenium
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: dialbreak by @stellenium | Stardance
|
1792925464.8783562
|
1793789464.8783562
|
|
4172
|
eear by @rizvifalak216 | Stardance
|
rizvifalak216
|
0
|
0.5
|
0
|
[]
|
[{"post_id": 693, "ts": "2026- [{"post_id": 693, "ts": "2026-06-02T08:03:48Z", "hours": 0.5031, "text": "so this project is divided into many stages STAGE-1 STRUCTURAL ARCHITECTURE sound concentration a pinna figure funnel structured, to the eardrums a thin rubber layer which vibrates when sound waves strikes. STAGE-2 RESONANCE STAGE-3 ACCUMULATION accumulation of vibration through piezoelectric disk + rectification of pulsed ac + storage of this tiny amount of dc produce through capacitors. right now my main task is to find the piezoelectric disk of right diameter and place it at the right position to get the best results"}]...
|
Title: eear by @rizvifalak216 | Stardance
Devlogs Title: eear by @rizvifalak216 | Stardance
Devlogs:
so this project is divided into many stages STAGE-1 STRUCTURAL ARCHITECTURE sound concentration a pinna figure funnel structured, to the eardrums a thin rubber layer which vibrates when sound waves strikes. STAGE-2 RESONANCE STAGE-3 ACCUMULATION accumulation of vibration through piezoelectric disk + rectification of pulsed ac + storage of this tiny amount of dc produce through capacitors. right now my main task is to find the piezoelectric disk of right diameter and place it at the right position to get the best results...
|
1792630344.594576
|
1793235144.594576
|
|
4173
|
Cosmic STIMULATOR by @manya | Stardance
|
manya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cosmic STIMULATOR by @manya | Stardance
|
1792666247.5107384
|
1793271047.5107384
|
|
4174
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792892921.3016458
|
1793756921.3016458
|
|
4176
|
spotify car thing :3 by @neset | Stardance
|
neset
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: spotify car thing :3 by @neset | Stardance
|
1793029725.9008267
|
1793634525.9008267
|
|
4178
|
My awesome macropad! by @TylerTeGoober | Stardance
|
TylerTeGoober
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @TylerTeGoober | St Title: My awesome macropad! by @TylerTeGoober | Stardance...
|
1793159452.4283164
|
1793764252.4283164
|
|
4179
|
Untitled project by @khantminnyi | Stardance
|
khantminnyi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @khantminnyi | Stardanc Title: Untitled project by @khantminnyi | Stardance...
|
1792558199.3129625
|
1793162999.3129625
|
|
4180
|
My awesome macropad! by @Amy | Stardance
|
Amy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Amy | Stardance
|
1792550883.6322696
|
1793155683.6322696
|
|
4182
|
learning JS by @dimple | Stardance
|
dimple
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: learning JS by @dimple | Stardance
|
1792749069.7574403
|
1793353869.7574403
|
|
4183
|
My first slack bot! by @azka_ziaa | Stardance
|
azka_ziaa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @azka_ziaa | Stardan Title: My first slack bot! by @azka_ziaa | Stardance...
|
1792666098.556565
|
1793270898.556565
|
|
4184
|
My awesome macropad! by @yatanveer | Stardance
|
yatanveer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @yatanveer | Starda Title: My awesome macropad! by @yatanveer | Stardance...
|
1792558490.868615
|
1793163290.868615
|
|
4185
|
Self Driving Car by @Devansh | Stardance
|
Devansh
|
0
|
6.0
|
0
|
[]
|
[{"post_id": 20839, "ts": "202 [{"post_id": 20839, "ts": "2026-07-02T15:29:13Z", "hours": 4.0, "text": "I finished the pcb design and sent it for printing to pcb power. like the dumb idiot i am i forgot adding mounting holes, so i had to reorder. I had some issues with lookout so i lost like 5 hours of work on the pcb and it took me over a WEEK to get the time added. Then i printed robot top plate, and due to my bad design it blocked the sensor so i got out the best tool in the world, pliers and cut the blocking part out. after sensor started working i then started coding, which is what i am doing now, im trying to tune it with the new camera angle and stuff"}, {"post_id": 12596, "ts": "2026-06-20T15:57:08Z", "hours": 2.0, "text": "Made a schematic for my robot I started by importing the library of symbols and footprints i used last year. Then i got a HAT+ template, so i know all dimenions correct. after that i placed all the symbols, wired sda and scl to all 4 tof sensors and bno086. oh and i made the bno086 symbol as i used bno055 last year. then i wired in the motor driver, this year i connected both channels together as the faster motor eats more current(yummy). then i got claude and its kicad mcp to review the erc. the hat+ templete used heirhcal sheet lables or something which kicad dint like as i removed the nested sheet so that solved many erros. also it had a genric 40 pin header for the pi which was pin type passive, for 3v3 too which gave erros so i fixed it by adding PWR_FLAG."}, {"post_id": 11938, "ts": "2026-06-19T14:01:09Z", "hours": 0.0, "text": "Today i ported the parking function from the old robot over to the new one. the new robot is alot faster so before anything i had to write a function to drive at a specific rpm instead of just slamming a fixed pwm duty like before. first try was a plain P controller off the encoder feedback but that failed, at low rpm the motor just sits there and stalls because it needs a bigger push to break free. so i added an I term, basically if the encoder says the wheel isnt moving the integral keeps winding up the duty till it hits the cap and that shoves the robot forward, then once its actually rolling the controller eases the power back down to hold the target rpm. after i got it moving (slowly at first) i swapped all the old set_speed() calls in parking for start_rpm_control() and stop_rpm_control() so the rpm loop runs in the background while the main code does the steering.then because the camera sits at a diffrent angle on this robot i had to retune the wall following distances too. last year doing wall follow off the distance sensor dint work well so this time im doing it from the camera, which means the numbers from before were all off.debugging wise there was a couple of annoying ones. one time i forgot to start the motor in reverse and it drove forward instead of back, took me ages to find because the encoder was reading distance as a absolute value so going the wrong way still looked like “progress” to the controller. there was also a issue when i hit ctrl c, the thread that runs the rpm loop wasnt closing cleanly so it kept re commanding the motor and the robot would keep going for like 2-3 sec after i killed it, fixed that by stopping the thread first before the gpio gets torn down.lastly once the whole thing actually worked end to end i went back and tuned the stop distances so it parks cleanly and doesnt clip the walls. robot finally parked."}]...
|
Title: Self Driving Car by @Devansh | Stardance
D Title: Self Driving Car by @Devansh | Stardance
Devlogs:
Today i ported the parking function from the old robot over to the new one. the new robot is alot faster so before anything i had to write a function to drive at a specific rpm instead of just slamming a fixed pwm duty like before. first try was a plain P controller off the encoder feedback but that failed, at low rpm the motor just sits there and stalls because it needs a bigger push to break free. so i added an I term, basically if the encoder says the wheel isnt moving the integral keeps winding up the duty till it hits the cap and that shoves the robot forward, then once its actually rolling the controller eases the power back down to hold the target rpm. after i got it moving (slowly at first) i swapped all the old set_speed() calls in parking for start_rpm_control() and stop_rpm_control() so the rpm loop runs in the background while the main code does the steering.then because the camera sits at a diffrent angle on this robot i had to retune the wall following distances too. last year doing wall follow off the distance sensor dint work well so this time im doing it from the camera, which means the numbers from before were all off.debugging wise there was a couple of annoying ones. one time i forgot to start the motor in reverse and it drove forward instead of back, took me ages to find because the encoder was reading distance as a absolute value so going the wrong way still looked like “progress” to the controller. there was also a issue when i hit ctrl c, the thread that runs the rpm loop wasnt closing cleanly so it kept re commanding the motor and the robot would keep going for like 2-3 sec after i killed it, fixed that by stopping the thread first before the gpio gets torn down.lastly once the whole thing actually worked end to end i went back and tuned the stop distances so it parks cleanly and doesnt clip the walls. robot finally parked.
Made a schematic for my robot I started by importing the library of symbols and footprints i used last year. Then i got a HAT+ template, so i know all dimenions correct. after that i placed all the symbols, wired sda and scl to all 4 tof sensors and bno086. oh and i made the bno086 symbol as i used bno055 last year. then i wired in the motor driver, this year i connected both channels together as the faster motor eats more current(yummy). then i got claude and its kicad mcp to review the erc. the hat+ templete used heirhcal sheet lables or something which kicad dint like as i removed the nested sheet so that solved many erros. also it had a genric 40 pin header for the pi which was pin type passive, for 3v3 too which gave erros so i fixed it by adding PWR_FLAG.
I finished the pcb design and sent it for printing to pcb power. like the dumb idiot i am i forgot adding mounting holes, so i had to reorder. I had some issues with lookout so i lost like 5 hours of work on the pcb and it took me over a WEEK to get the time added. Then i printed robot top plate, and due to my bad design it blocked the sensor so i got out the best tool in the world, pliers and cut the blocking part out. after sensor started working i then started coding, which is what i am doing now, im trying to tune it with the new camera angle and stuff...
|
1792918094.798037
|
1793782094.798037
|
|
4186
|
My awesome macropad! by @Harry525 | Stardance
|
Harry525
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Harry525 | Stardan Title: My awesome macropad! by @Harry525 | Stardance...
|
1792756526.6823761
|
1793361326.6823761
|
|
4187
|
My awesome macropad! by @Annie | Stardance
|
Annie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Annie | Stardance
|
1792587158.3287897
|
1793191958.3287897
|
|
4188
|
My first slack bot! by @Apricitylxy | Stardance
|
Apricitylxy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Apricitylxy | Stard Title: My first slack bot! by @Apricitylxy | Stardance...
|
1792619409.4996207
|
1793224209.4996207
|
|
4189
|
Faceless channel ai tool by @aadrsh1001012 | Stard Faceless channel ai tool by @aadrsh1001012 | Stardance...
|
aadrsh1001012
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Faceless channel ai tool by @aadrsh1001012 Title: Faceless channel ai tool by @aadrsh1001012 | Stardance...
|
1792792361.7498314
|
1793397161.7498314
|
|
4191
|
My first slack bot! by @Shem | Stardance
|
Shem
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Shem | Stardance
|
1792568860.5846984
|
1793173660.5846984
|
|
4193
|
I am Iron Man by @Coffe404 | Stardance
|
Coffe404
|
0
|
1.06
|
0
|
[]
|
[{"post_id": 30959, "ts": "202 [{"post_id": 30959, "ts": "2026-07-18T23:37:26Z", "hours": 1.06, "text": "Devlog #1 - Hiii over there! This is my first devlog for this hahaha, so I don’t know where to start. I’ve already finished the web app for the “JARVIS” system, so its more comfortable for using it from your phone. I’m looking for an option to make an entire app with all of my requirements included for making it easier to install and use. That’s all for my first devlog hahaha :) Stay tuned!"}]...
|
Title: I am Iron Man by @Coffe404 | Stardance
Dev Title: I am Iron Man by @Coffe404 | Stardance
Devlogs:
Devlog #1 - Hiii over there! This is my first devlog for this hahaha, so I don’t know where to start. I’ve already finished the web app for the “JARVIS” system, so its more comfortable for using it from your phone. I’m looking for an option to make an entire app with all of my requirements included for making it easier to install and use. That’s all for my first devlog hahaha :) Stay tuned!...
|
1793159493.0369544
|
1793764293.0369544
|
|
4194
|
My awesome macropad! by @sagarchhatkuli953 | Stard My awesome macropad! by @sagarchhatkuli953 | Stardance...
|
sagarchhatkuli953
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sagarchhatkuli953 Title: My awesome macropad! by @sagarchhatkuli953 | Stardance...
|
1792651969.6223776
|
1793256769.6223776
|
|
4195
|
My awesome macropad! by @mus | Stardance
|
mus
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @mus | Stardance
|
1792630051.7376015
|
1793234851.7376015
|
|
4197
|
My awesome macropad! by @Oshin-Jovian | Stardance
|
Oshin-Jovian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Oshin-Jovian | Sta Title: My awesome macropad! by @Oshin-Jovian | Stardance...
|
1792666366.5355842
|
1793271166.5355842
|
|
4198
|
My first slack bot! by @TheWired | Stardance
|
TheWired
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @TheWired | Stardanc Title: My first slack bot! by @TheWired | Stardance...
|
1792695278.6228454
|
1793300078.6228454
|
|
4199
|
Squall by @polarizedGale1 | Stardance
|
polarizedGale1
|
0
|
8.05
|
0
|
[]
|
[{"post_id": 18308, "ts": "202 [{"post_id": 18308, "ts": "2026-06-29T12:42:14Z", "hours": 3.85, "text": "I added a draw image to render to which should making screenshots in the future possible. I also managed to get rid of all the validation warnings when resizing."}, {"post_id": 17879, "ts": "2026-06-28T20:18:41Z", "hours": 4.2008, "text": "I created the project boilerplate and setup the swapchain properly for a browser. I managed to fix all the vulkan validation warnings and added utility functions to make further development easier."}]...
|
Title: Squall by @polarizedGale1 | Stardance
Devl Title: Squall by @polarizedGale1 | Stardance
Devlogs:
I created the project boilerplate and setup the swapchain properly for a browser. I managed to fix all the vulkan validation warnings and added utility functions to make further development easier.
I added a draw image to render to which should making screenshots in the future possible. I also managed to get rid of all the validation warnings when resizing....
|
1792540109.2887335
|
1793144909.2887335
|
|
4201
|
My first slack bot! by @priyavishnuch | Stardance
|
priyavishnuch
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @priyavishnuch | Sta Title: My first slack bot! by @priyavishnuch | Stardance...
|
1792770627.048289
|
1793375427.048289
|
|
4202
|
Screen Time Tracker Widget by @Mathman14159 | Star Screen Time Tracker Widget by @Mathman14159 | Stardance...
|
Mathman14159
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Screen Time Tracker Widget by @Mathman14159 Title: Screen Time Tracker Widget by @Mathman14159 | Stardance...
|
1792662720.093664
|
1793267520.093664
|
|
4203
|
Flapy bird AI model by @CY3er | Stardance
|
CY3er
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Flapy bird AI model by @CY3er | Stardance
|
1792727488.291065
|
1793332288.291065
|
|
4204
|
A galaxy website by @Trixie | Stardance
|
Trixie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A galaxy website by @Trixie | Stardance
|
1792551222.420632
|
1793156022.420632
|
|
4205
|
Untitled by @starlitfire | Stardance
|
starlitfire
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @starlitfire | Stardance
|
1792795826.3219178
|
1793400626.3219178
|
|
4206
|
Lyrically Inclined by @RishabhGarg | Stardance
|
RishabhGarg
|
0
|
1.6
|
0
|
[]
|
[{"post_id": 997, "ts": "2026- [{"post_id": 997, "ts": "2026-06-02T19:36:01Z", "hours": 0.9886, "text": "Installing postgres and setting up the vector + regular database of lyrics"}, {"post_id": 657, "ts": "2026-06-02T05:57:00Z", "hours": 0.6136, "text": "Set up the initial app structure and webpage with Flask and Bulma"}]...
|
Title: Lyrically Inclined by @RishabhGarg | Starda Title: Lyrically Inclined by @RishabhGarg | Stardance
Devlogs:
Set up the initial app structure and webpage with Flask and Bulma
Installing postgres and setting up the vector + regular database of lyrics...
|
1792554763.511527
|
1793159563.511527
|
|
4207
|
Froststrap by @SysError06 | Stardance
|
SysError06
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Froststrap by @SysError06 | Stardance
|
1792630256.5313296
|
1793235056.5313296
|
|
4208
|
Slice of a pie - goal tracker by @adwitha | Starda Slice of a pie - goal tracker by @adwitha | Stardance...
|
adwitha
|
0
|
13.14
|
0
|
[]
|
[{"post_id": 47769, "ts": "202 [{"post_id": 47769, "ts": "2026-08-15T22:41:18Z", "hours": 1.0153, "text": "I worked on adding two new functionalities for this devlog, which were the new sidebar and making the check-in frequency value chosen be used for its intended purpose Goal The main goal of this devlog was just setting up the necessary features for the big upcoming addition which is the daily check-in feature where the app keeps track of what progress has been made on goals that have check-ins due on that day. This information will also be used for the journal feature that will be added later on. The Sidebar For the sidebar, I realized that I wouldn’t need a dedicated sidebar to store all the buttons for navigation, as there aren’t many buttons necessary, so I decided to create a sort of hybrid sidebar that just lived on the side of the main page. I also think this is much more visually pleasin design as the floating logos glide behind it and it feels very integrated. This was a simple addition where I just made a sidebar outside of the main homepage content div and styled it to look the way it is. It also has a hover effect, which simply makes the background’s opacity increase. Currently, I have not built either of these menus yet so the buttons do not do anything. I will be adding functionality to the Daily Check-in button in the next devlog. Check-in frequency This is what I originally started working on for this devlog, but I realized that I don’t even have a way to get to the check-in page besides when it automatically pops up once daily. Therefore, I added the sidebar. As for progress on this, I have made the goal object take in the chosen option and store it in a variable. I have added a function which uses this info and the last done check-in to find out whether there is a check-in due on that particular day for the passed in goal. This will be called in the daily check-in menu function that I will be making next. If this gives true, then that goal will have a check-in in today’s check-in"}, {"post_id": 44793, "ts": "2026-08-10T20:06:52Z", "hours": 0.8836, "text": "I worked on two new features for this devlog. One was kind of an impulse decision to add floating logos that bounce off the edges of the main page, like the DVD logo, and the other was making the time remaining section work on the goal cards instead of being a placeholder. Floating logos I felt like the background was super plain here and it felt kind of soulless, so I decided to give it that little nostalgic touch and have logos bounce around the user’s screen without making them too distracting. I made this by adding 7 floating logos outside of the main HTML, and then I Used the Math.random function to randomize the object’s size, speed, and starting point Adjusted the opacity of them so they won’t be too annoying Bounded the speed so they all are roughly moving at the same type of speed with slight variation Made them bounce off the edges of the screen using the window width and height and negating their speed value when they come in contact with the boundary With that done, I was testing the app’s functionality and discovered that the days remaining was still using a placeholder of “5 days,” which I had put there earlier. Days Remaining I made this work by writing a function that calculated how many days remained between the current day and the chosen completion date. I did this by using the new date() function to get dates in the format where I could directly subtract them to get the remaining days. This made it very convenient to work with."}, {"post_id": 44411, "ts": "2026-08-10T04:17:17Z", "hours": 3.1861, "text": "I have been working on adding functionality to the app as I was getting pretty satisfied with how the UI looked. I started by adding the functionality for the goals to be saved as one object so they can be stored and retrieved easily Setting up goals I did this by creating a goals array that holds each goal, and I added a function that is triggered when the “add goal” button is pressed in the add goal menu. Within this function, I added a goal object which held the following: A randomly generated ID to easily access a goal The title The description The completion date The category of the goal The chosen check-in frequency The milestones With this, the goal could be easily stored, accessed, and edited by simply changing the information within the goal object in the goals array. With this made, I needed a way to display the information entered on the screen, so I created what I call goal cards. Goal Cards Making the goal cards was a very cool learning experience as I got to deal more with dynamic HTML creation. Once the Add Goal button was clicked, it would call the displayGoal function. This function would: Get all the information from the particular goal object we are displaying Create the goal card using dynamic object creation and add CSS classes that have been made for it Update the goal card every time it is edited, like when milestones are checked off; it will update the progress bar. Speaking of the progress bar, clicking on the goal card brings up the menu shown in the image below, which allows the user to see a bigger view of the goal and allows them to check off milestones. I plan on expanding this to add editability to goals and other functionality. Goal menu This was created using the same technique as the add goal menu from a previous devlog, but instead of showing the same information for everything, it changes based on the goal object being targeted. The styling is not perfect yet, as I was focusing on the functionality more, but as more is changed, it will look closer to the true final product. Conclusion Overall, this was a very productive devlog, and I think I learned a lot of new valuable skills in JavaScript. I think the next thing I will work on is adding the check-ins and setting up the data to be stored locally so it doesn’t go away after a page refresh."}, {"post_id": 32686, "ts": "2026-07-22T00:16:02Z", "hours": 6.3917, "text": "I have been working on the frontend of the app updating it to look more like how I want it to when the app is published. The first image showcases the main page of the app where the goals that are added will show up seperated by short term, medium term, and long term. New goals can be added by pressing the add goal button under each subdivision. Pressing that button brings up the menu from the second image, which is the menu to add a new goal. This menu sets up not only a goal to achieve, but a plan to stick to it. This includes setting up a check-in frequency that tells the app how often in the daily check-ins there should be a progress update for this particular goal. This also includes setting up milestones/steps to achieving a certain goal. This allows for progress tracking of a goal that was set up, and even a feature where the app tells you if you are behind, on track, or ahead on your goal. The biggest challenge I faced while creating this was the feature for adding your own custom milestones, as it was designed to give a lot of freedom to the user. You can move the milestones that were added, give them specific completion dates, or choose to let the app space them evenly. You can add as many milestones as you want, and you can even choose not to add specific milestones and let the app deduce how many and how to split up the milestones. The reason this was difficult was that I have very minimal experience with JavaScript, so this took a lot of time to design, troubleshoot, and iron out. My next steps are to start working on the backend so that the stuff that is entered in the goal setup menu is actually reflected in the main page, and the daily check-in system is setup"}, {"post_id": 7627, "ts": "2026-06-12T19:05:30Z", "hours": 1.6583, "text": "Hi, I am currently learning HTML, CSS, and JavaScript, and along the way, I wanted to make a project to solidify my learning: A goal tracking app! I am very excited to share my current progress, as I was able to make an overlay menu that displays over the app without going to a different page. This was a difficult task as I had not worked with JavaScript before, but with the help of resources like Stack Overflow, I was able to figure out how to implement it! I used an on() and an off() function that displayed a full-screen overlay, which had a child overlay containing the pop-up menu. This can be seen in the second picture below. The overlay is display= “none” by default and then gets set to display= “flex” when the on() function is called. Off() sets it back to none. I haven’t added the exact content that I want or styled anything yet, but I just wanted to share this milestone! The app that I am making is a goal-tracking app that allows the user to add different types of goals (short, medium, long term) to keep track of their goals. The app will also keep the user accountable as it will require the user to set steps/mini goals that need to be achieved, and will have the user complete a daily check-in to track their progress. Different types of goals can have different time frames, and the app will account for that. The user can input a time frame, or the app will use pre-determined values."}]...
|
Title: Slice of a pie - goal tracker by @adwitha | Title: Slice of a pie - goal tracker by @adwitha | Stardance
Devlogs:
Hi, I am currently learning HTML, CSS, and JavaScript, and along the way, I wanted to make a project to solidify my learning: A goal tracking app! I am very excited to share my current progress, as I was able to make an overlay menu that displays over the app without going to a different page. This was a difficult task as I had not worked with JavaScript before, but with the help of resources like Stack Overflow, I was able to figure out how to implement it! I used an on() and an off() function that displayed a full-screen overlay, which had a child overlay containing the pop-up menu. This can be seen in the second picture below. The overlay is display= “none” by default and then gets set to display= “flex” when the on() function is called. Off() sets it back to none. I haven’t added the exact content that I want or styled anything yet, but I just wanted to share this milestone! The app that I am making is a goal-tracking app that allows the user to add different types of goals (short, medium, long term) to keep track of their goals. The app will also keep the user accountable as it will require the user to set steps/mini goals that need to be achieved, and will have the user complete a daily check-in to track their progress. Different types of goals can have different time frames, and the app will account for that. The user can input a time frame, or the app will use pre-determined values.
I have been working on the frontend of the app updating it to look more like how I want it to when the app is published. The first image showcases the main page of the app where the goals that are added will show up seperated by short term, medium term, and long term. New goals can be added by pressing the add goal button under each subdivision. Pressing that button brings up the menu from the second image, which is the menu to add a new goal. This menu sets up not only a goal to achieve, but a plan to stick to it. This includes setting up a check-in frequency that tells the app how often in the daily check-ins there should be a progress update for this particular goal. This also includes setting up milestones/steps to achieving a certain goal. This allows for progress tracking of a goal that was set up, and even a feature where the app tells you if you are behind, on track, or ahead on your goal. The biggest challenge I faced while creating this was the feature for adding your own custom milestones, as it was designed to give a lot of freedom to the user. You can move the milestones that were added, give them specific completion dates, or choose to let the app space them evenly. You can add as many milestones as you want, and you can even choose not to add specific milestones and let the app deduce how many and how to split up the milestones. The reason this was difficult was that I have very minimal experience with JavaScript, so this took a lot of time to design, troubleshoot, and iron out. My next steps are to start working on the backend so that the stuff that is entered in the goal setup menu is actually reflected in the main page, and the daily check-in system is setup
I have been working on adding functionality to the app as I was getting pretty satisfied with how the UI looked. I started by adding the functionality for the goals to be saved as one object so they can be stored and retrieved easily Setting up goals I did this by creating a goals array that holds each goal, and I added a function that is triggered when the “add goal” button is pressed in the add goal menu. Within this function, I added a goal object which held the following: A randomly generated ID to easily access a goal The title The description The completion date The category of the goal The chosen check-in frequency The milestones With this, the goal could be easily stored, accessed, and edited by simply changing the information within the goal object in the goals array. With this made, I needed a way to display the information entered on the screen, so I created what I call goal cards. Goal Cards Making the goal cards was a very cool learning experience as I got to deal more with dynamic HTML creation. Once the Add Goal button was clicked, it would call the displayGoal function. This function would: Get all the information from the particular goal object we are displaying Create the goal card using dynamic object creation and add CSS classes that have been made for it Update the goal card every time it is edited, like when milestones are checked off; it will update the progress bar. Speaking of the progress bar, clicking on the goal card brings up the menu shown in the image below, which allows the user to see a bigger view of the goal and allows them to check off milestones. I plan on expanding this to add editability to goals and other functionality. Goal menu This was created using the same technique as the add goal menu from a previous devlog, but instead of showing the same information for everything, it changes based on the goal object being targeted. The styling is not perfect yet, as I was focusing on the functionality more, but as more is changed, it will look closer to the true final product. Conclusion Overall, this was a very productive devlog, and I think I learned a lot of new valuable skills in JavaScript. I think the next thing I will work on is adding the check-ins and setting up the data to be stored locally so it doesn’t go away after a page refresh.
I worked on two new features for this devlog. One was kind of an impulse decision to add floating logos that bounce off the edges of the main page, like the DVD logo, and the other was making the time remaining section work on the goal cards instead of being a placeholder. Floating logos I felt like the background was super plain here and it felt kind of soulless, so I decided to give it that little nostalgic touch and have logos bounce around the user’s screen without making them too distracting. I made this by adding 7 floating logos outside of the main HTML, and then I Used the Math.random function to randomize the object’s size, speed, and starting point Adjusted the opacity of them so they won’t be too annoying Bounded the speed so they all are roughly moving at the same type of speed with slight variation Made them bounce off the edges of the screen using the window width and height and negating their speed value when they come in contact with the boundary With that done, I was testing the app’s functionality and discovered that the days remaining was still using a placeholder of “5 days,” which I had put there earlier. Days Remaining I made this work by writing a function that calculated how many days remained between the current day and the chosen completion date. I did this by using the new date() function to get dates in the format where I could directly subtract them to get the remaining days. This made it very convenient to work with.
I worked on adding two new functionalities for this devlog, which were the new sidebar and making the check-in frequency value chosen be used for its intended purpose Goal The main goal of this devlog was just setting up the necessary features for the big upcoming addition which is the daily check-in feature where the app keeps track of what progress has been made on goals that have check-ins due on that day. This information will also be used for the journal feature that will be added later on. The Sidebar For the sidebar, I realized that I wouldn’t need a dedicated sidebar to store all the buttons for navigation, as there aren’t many buttons necessary, so I decided to create a sort of hybrid sidebar that just lived on the side of the main page. I also think this is much more visually pleasin design as the floating logos glide behind it and it feels very integrated. This was a simple addition where I just made a sidebar outside of the main homepage content div and styled it to look the way it is. It also has a hover effect, which simply makes the background’s opacity increase. Currently, I have not built either of these menus yet so the buttons do not do anything. I will be adding functionality to the Daily Check-in button in the next devlog. Check-in frequency This is what I originally started working on for this devlog, but I realized that I don’t even have a way to get to the check-in page besides when it automatically pops up once daily. Therefore, I added the sidebar. As for progress on this, I have made the goal object take in the chosen option and store it in a variable. I have added a function which uses this info and the last done check-in to find out whether there is a check-in due on that particular day for the passed in goal. This will be called in the daily check-in menu function that I will be making next. If this gives true, then that goal will have a check-in in today’s check-in...
|
1792731051.952001
|
1793335851.952001
|
|
4209
|
My awesome macropad! by @baluwaladaniyal | Stardan My awesome macropad! by @baluwaladaniyal | Stardance...
|
baluwaladaniyal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @baluwaladaniyal | Title: My awesome macropad! by @baluwaladaniyal | Stardance...
|
1792738164.965687
|
1793342964.965687
|