|
8501
|
My awesome macropad! by @link-timo | Stardance
|
link-timo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @link-timo | Starda Title: My awesome macropad! by @link-timo | Stardance...
|
1793202736.287764
|
1793807536.287764
|
|
8502
|
Rjmacx by @officialsachinrajbhar | Stardance
|
officialsachinrajbhar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Rjmacx by @officialsachinrajbhar | Stardanc Title: Rjmacx by @officialsachinrajbhar | Stardance...
|
1793184926.644968
|
1793789726.644968
|
|
8503
|
My first slack bot! by @zombieking1555 | Stardance
|
zombieking1555
|
1
|
1.0
|
1
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-07T22:22:33Z", "hours": 1.0, "multiplier": 2.15, "payout": 1, "blessing": "neutral", "text": "I made my own Slack bot following the Stardance mission tutorial. This project, although beginner-level, was a challenge to me. It was my first time working with APIs, Hosting, and generally programming with JavaScript. I am proud of my custom Calendar command; it taught me a lot about working with APIs and allowed me to dip my toes past what was provided for me in the tutorial. My bot should be live using Nest and testable by anyone on Slack!", "repo": "https://github.com/zombieking1555/slack-zombot", "demo": "https://hackclub.enterprise.slack.com/archives/C0APH2MMHH7"}]...
|
[{"post_id": 4562, "ts": "2026 [{"post_id": 4562, "ts": "2026-06-07T22:07:19Z", "hours": 0.6578, "text": "First devlog for a project I’m working on - likely last for this project. I wanted to create this project to learn the flow of creating and shipping for the Stardance challenge. Almost everything I did here was entirely new to me: coding in JS, using API keys and tokens, and SSHing to host my bot on Nest. Luckily, I was able to figure out how to have my coding time properly logged to have enough to devlog. My 37 minutes reflect the time I spent tidying the project for shipment, not the 2 and a half hours spent figuring out how to parse a command into API parameters. This Slack bot was a lot of fun, looking forward to devlogging again on my next project."}]...
|
Title: My first slack bot! by @zombieking1555 | St Title: My first slack bot! by @zombieking1555 | Stardance
Devlogs:
First devlog for a project I’m working on - likely last for this project. I wanted to create this project to learn the flow of creating and shipping for the Stardance challenge. Almost everything I did here was entirely new to me: coding in JS, using API keys and tokens, and SSHing to host my bot on Nest. Luckily, I was able to figure out how to have my coding time properly logged to have enough to devlog. My 37 minutes reflect the time I spent tidying the project for shipment, not the 2 and a half hours spent figuring out how to parse a command into API parameters. This Slack bot was a lot of fun, looking forward to devlogging again on my next project.
Ships:
I made my own Slack bot following the Stardance mission tutorial. This project, although beginner-level, was a challenge to me. It was my first time working with APIs, Hosting, and generally programming with JavaScript. I am proud of my custom Calendar command; it taught me a lot about working with APIs and allowed me to dip my toes past what was provided for me in the tutorial. My bot should be live using Nest and testable by anyone on Slack!...
|
1793292991.690258
|
1793379391.690258
|
|
8504
|
The Saxprinter™ by @_tenorangesax_ | Stardance
|
_tenorangesax_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The Saxprinter™ by @_tenorangesax_ | Starda Title: The Saxprinter™ by @_tenorangesax_ | Stardance...
|
1793375381.2400386
|
1794239381.2400386
|
|
8505
|
Arduino Distance-Sensor by @experi_mentalkid | Sta Arduino Distance-Sensor by @experi_mentalkid | Stardance...
|
experi_mentalkid
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Arduino Distance-Sensor by @experi_mentalki Title: Arduino Distance-Sensor by @experi_mentalkid | Stardance...
|
1793371748.9427958
|
1793976548.9427958
|
|
8506
|
My awesome macropad! by @rkiss369 | Stardance
|
rkiss369
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @rkiss369 | Stardan Title: My awesome macropad! by @rkiss369 | Stardance...
|
1792799664.5540137
|
1793404464.5540137
|
|
8507
|
Untitled by @gameminder | Stardance
|
gameminder
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @gameminder | Stardance
|
1793271185.4721055
|
1793875985.4721055
|
|
8508
|
Macro Tracker by @sankalpyeleti | Stardance
|
sankalpyeleti
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Macro Tracker by @sankalpyeleti | Stardance
|
1793429281.1334128
|
1794034081.1334128
|
|
8509
|
My awesome macropad! by @Brayan | Stardance
|
Brayan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Brayan | Stardance
|
1792716628.7905247
|
1793321428.7905247
|
|
8510
|
My awesome macropad! by @REN | Stardance
|
REN
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @REN | Stardance
|
1793180869.1449287
|
1793785669.1449287
|
|
8511
|
My awesome macropad! by @code5010 | Stardance
|
code5010
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @code5010 | Stardan Title: My awesome macropad! by @code5010 | Stardance...
|
1793191891.4120414
|
1793796691.4120414
|
|
8512
|
My awesome macropad! by @Paetynclaire | Stardance
|
Paetynclaire
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Paetynclaire | Sta Title: My awesome macropad! by @Paetynclaire | Stardance...
|
1793199320.9115598
|
1793804120.9115598
|
|
8513
|
Untitled project by @joaolucascarreiraa | Stardanc Untitled project by @joaolucascarreiraa | Stardance...
|
joaolucascarreiraa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @joaolucascarreiraa | S Title: Untitled project by @joaolucascarreiraa | Stardance...
|
1793325075.4433305
|
1793929875.4433305
|
|
8514
|
My first slack bot! by @harshalpatil6188 | Stardan My first slack bot! by @harshalpatil6188 | Stardance...
|
harshalpatil6188
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @harshalpatil6188 | Title: My first slack bot! by @harshalpatil6188 | Stardance...
|
1793414890.9365938
|
1794019690.9365938
|
|
8515
|
Ubiverse by @Akhzar | Stardance
|
Akhzar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ubiverse by @Akhzar | Stardance
|
1793181279.354719
|
1793786079.354719
|
|
8516
|
Decentralised Git by @hidryde | Stardance
|
hidryde
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Decentralised Git by @hidryde | Stardance
|
1793307236.81525
|
1793912036.81525
|
|
8517
|
Untitled project by @tigerjdeng_stardance | Starda Untitled project by @tigerjdeng_stardance | Stardance...
|
tigerjdeng_stardance
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @tigerjdeng_stardance | Title: Untitled project by @tigerjdeng_stardance | Stardance...
|
1793314301.579914
|
1793919101.579914
|
|
8518
|
My awesome macropad! by @darkeyexcode | Stardance
|
darkeyexcode
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @darkeyexcode | Sta Title: My awesome macropad! by @darkeyexcode | Stardance...
|
1793227742.6224875
|
1793832542.6224875
|
|
8519
|
My awesome macropad! by @oguh_sevla | Stardance
|
oguh_sevla
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @oguh_sevla | Stard Title: My awesome macropad! by @oguh_sevla | Stardance...
|
1793256576.8185573
|
1793861376.8185573
|
|
8520
|
My first slack bot! by @chitrakshgupta | Stardance
|
chitrakshgupta
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @chitrakshgupta | St Title: My first slack bot! by @chitrakshgupta | Stardance...
|
1792731095.2074518
|
1793335895.2074518
|
|
8521
|
ToDo app by @Tigerente10 | Stardance
|
Tigerente10
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ToDo app by @Tigerente10 | Stardance
|
1792767203.4336467
|
1793372003.4336467
|
|
8522
|
SideLine - Match Recorder by @Osmosis | Stardance
|
Osmosis
|
0
|
9.6
|
0
|
[]
|
[{"post_id": 9675, "ts": "2026 [{"post_id": 9675, "ts": "2026-06-16T02:42:47Z", "hours": 0.4956, "text": "The pivot — drone → courtside gimbal (and a lesson) Here’s where the project hit its biggest wall, and I want to log it honestly because the recovery taught me more than any milestone. I was about to spec a drone. Then I actually researched drone law in Qatar and found out it’s one of the strictest regimes in the world: every single flight needs a QCAA permit (owning a drone gives you no right to fly it), and there’s a privacy law (Penal Code Art. 333) against filming people without consent, penalties up to two years. For a system whose whole job is filming school matches full of players and spectators, that’s not a paperwork hurdle, it’s a wall. My original picture a drone autonomously filming matches was effectively dead. The lesson, written down so I don’t forget it: research the constraints of the real world before you fall in love with a plan. I’d validated the software to machine precision, but I almost skipped checking whether the deployment was even legal. Check the boring stuff first. So I swapped the drone for a 3-DOF gimbal on a rail: a motorised camera mount (pan / tilt / roll) that slides along a track, parked courtside. No permit. Same filming-consent terms my existing fixed cameras already navigate. And it runs every match, not the one-off a permitted drone flight would’ve been. It’s more deployable than the drone ever was. A gimbal is also a categorically real difference from just pointing a camera, for one optical reason that isn’t arguable: a fixed camera can only ever crop the pixels it already has, but a gimbal physically moves the lens real parallax, a real push-in that changes perspective, footage that simply doesn’t exist in a static feed. The human directs the intent (“orbit that player,” “push in”) and the system, which understands the scene, executes the move. That’s the thing a fixed camera can’t do, and it survived the pivot completely intact. M9 — the gimbal’s brain (software) Stardance just opened a hardware track, but this milestone was deliberately software: adapt the system to the gimbal before the parts arrive, so the maths is proven when the hardware lands. The beautiful part: because I’d kept the architecture cleanly separated for nine milestones, the drone→gimbal pivot touched exactly one layer. The gesture engine, the scene tracking, the intent commands, the flight-path engine, the live bridge all unchanged. The only new code is a converter that takes an ideal 3D camera pose and works out what the gimbal can physically do with it: pan/tilt/roll angles to aim, plus a position along the rail. And it stays honest, which is the whole point. A gimbal at a fixed pivot can rotate perfectly but can’t translate so a true orbit (circling a subject) is impossible without the camera leaving its rail. The converter proves this with numbers instead of faking it: a follow shot aims with 0.00° error and zero positional gap (the rig does it cleanly), while an attempted orbit still aims perfectly but reports a 9.05-unit gap, flagged out-of-reach on every frame the system refuses to pretend it can do something the hardware can’t. Honest problems that will probably come up: this is geometry on a perfect simulator. The real gimbal will have motor speed limits, inertia, and backlash, it won’t snap to an angle instantly. That’s the hardware phase’s problem, and I’m not pretending the clean sim is the real rig. Up next: the glove parts are shipping. When they land, the build goes physical. breadboard, sensors, solder. Then the gimbal it is"}, {"post_id": 4838, "ts": "2026-06-08T11:14:50Z", "hours": 1.9914, "text": "Hi I’m Aarav Sharma and I want to direct a drone with my hands, not just piloting but actual direction. Introducing AirLine: direct a drone with your hands, don’t pilot it. Most gesture drones map your hand to a flight stick (tilt to bank, raise to climb) — you become the joystick. AirLine instead reads cinematic intent (“follow that player,” “orbit the subject”) and figures out the flight itself, because it understands the scene. It’s a branch off my capstone SideLine (an AI sports-analytics system that already tracks “the player with the ball”), reusing its vision core untouched. Software first, glove I build myself next, drone last. Devlog: M1: AirLine runs SideLine’s tracker through a clean seam, vision core untouched. ~19 FPS. M2: Lock onto one subject. Found track IDs fragment — 293/540 frames “lost.” Quantified the re-ID problem on footage, not a $400 drone. M3: Virtual camera follows like an operated shot, drifts to wide when the target’s lost. First time it looked real. M4: Webcam gestures (MediaPipe) — but it conflicts with my vision stack. Setup stopped instead of breaking it. Best decision of the day. M5: Quarantined gestures in their own environment. First real-hand numbers: mostly 10/10 after fixing bugs unit tests missed. M6: Two-process live system — my hand directs the shot in real time. ~297ms latency, only 35ms of it transport. M7: First 3D camera move: orbit on a tiltable plane, proven by geometric invariants to machine precision (~4e-16). M8: Added push-in, pull-out, dolly. Full shot vocabulary done. 146 tests, vision core never touched. Next: hardware actually building the gesture glove by hand and integrating a drone"}, {"post_id": 4178, "ts": "2026-06-07T12:19:57Z", "hours": 7.1161, "text": "Hi I’m Aarav Sharma, I started this before Stardance, so this first devlog covers everything built so far (about 6 hours of work) in one go. Sideline is an AI system that films a school football or basketball match from a single fixed camera and turns that one recording into three different things: tactical analytics for coaches, event highlight reels for the school socials, and a personal highlight clip for every player, not just the goal-scorers. It runs entirely on a local laptop with no subscriptions, which matters because the commercial equivalents (Veo, Pixellot) cost hundreds up front plus monthly fees, putting them out of reach for a normal school. The computer vision (both football and basketball). The core is one shared pipeline that detects players and the ball, tracks them across the match, works out which team each player is on, and maps the camera view onto real court coordinates so distances and positions actually mean something in metres. Getting each piece trustworthy was the bulk of the time, and a lot of it was fighting genuinely hard problems. The basketball ball tracker kept locking onto players’ heads (round, ball-sized, and constantly held right next to the ball during a shot), and I had to prove that no shape or size rule could ever separate them before fixing it with a small appearance classifier I trained on a few thousand hand-sorted image crops (head rejection went from hopeless to 98.5%). Team detection on similar kits kept collapsing into one cluster until I switched to appearance embeddings, which also caught a possession stat that was confidently pointing at the wrong team entirely. The three deliverables. Coach analytics come out as a one-page report plus an annotated tactical video (heatmaps, distance covered, possession, formation, territory), with every number honestly labelled as either validated or derived. Event highlights are auto-detected and ranked so the best moments float to the top instead of flooding whoever is editing. Player highlights are built to be inclusive by construction: every player who steps on the court gets footage, using their on-ball moments where they have them, which is the part no commercial product bothers with and the part a school actually cares about. The app. All of that is wrapped in a working local web app, “Sideline, Match Studio”, with a dark cinematic interface a non-technical teacher can run start to finish: upload a match, click the four court corners on a freeze-frame, pick which deliverables they want, and download the results. The backend is a FastAPI server that runs the heavy AI as background jobs (a full match takes around 3 hours, so it processes while you walk away and can survive a restart), and it wraps my existing pipeline scripts rather than rewriting them. The whole thing is tested end to end with 62 passing checks, and I have already stress-tested it on a full 47-minute match to see what breaks at real scale. Next stop is real deployment at my school, which is the one thing I cannot fully validate until I have footage from our own courts and teams."}]...
|
Title: SideLine - Match Recorder by @Osmosis | Sta Title: SideLine - Match Recorder by @Osmosis | Stardance
Devlogs:
Hi I’m Aarav Sharma, I started this before Stardance, so this first devlog covers everything built so far (about 6 hours of work) in one go. Sideline is an AI system that films a school football or basketball match from a single fixed camera and turns that one recording into three different things: tactical analytics for coaches, event highlight reels for the school socials, and a personal highlight clip for every player, not just the goal-scorers. It runs entirely on a local laptop with no subscriptions, which matters because the commercial equivalents (Veo, Pixellot) cost hundreds up front plus monthly fees, putting them out of reach for a normal school. The computer vision (both football and basketball). The core is one shared pipeline that detects players and the ball, tracks them across the match, works out which team each player is on, and maps the camera view onto real court coordinates so distances and positions actually mean something in metres. Getting each piece trustworthy was the bulk of the time, and a lot of it was fighting genuinely hard problems. The basketball ball tracker kept locking onto players’ heads (round, ball-sized, and constantly held right next to the ball during a shot), and I had to prove that no shape or size rule could ever separate them before fixing it with a small appearance classifier I trained on a few thousand hand-sorted image crops (head rejection went from hopeless to 98.5%). Team detection on similar kits kept collapsing into one cluster until I switched to appearance embeddings, which also caught a possession stat that was confidently pointing at the wrong team entirely. The three deliverables. Coach analytics come out as a one-page report plus an annotated tactical video (heatmaps, distance covered, possession, formation, territory), with every number honestly labelled as either validated or derived. Event highlights are auto-detected and ranked so the best moments float to the top instead of flooding whoever is editing. Player highlights are built to be inclusive by construction: every player who steps on the court gets footage, using their on-ball moments where they have them, which is the part no commercial product bothers with and the part a school actually cares about. The app. All of that is wrapped in a working local web app, “Sideline, Match Studio”, with a dark cinematic interface a non-technical teacher can run start to finish: upload a match, click the four court corners on a freeze-frame, pick which deliverables they want, and download the results. The backend is a FastAPI server that runs the heavy AI as background jobs (a full match takes around 3 hours, so it processes while you walk away and can survive a restart), and it wraps my existing pipeline scripts rather than rewriting them. The whole thing is tested end to end with 62 passing checks, and I have already stress-tested it on a full 47-minute match to see what breaks at real scale. Next stop is real deployment at my school, which is the one thing I cannot fully validate until I have footage from our own courts and teams.
Hi I’m Aarav Sharma and I want to direct a drone with my hands, not just piloting but actual direction. Introducing AirLine: direct a drone with your hands, don’t pilot it. Most gesture drones map your hand to a flight stick (tilt to bank, raise to climb) — you become the joystick. AirLine instead reads cinematic intent (“follow that player,” “orbit the subject”) and figures out the flight itself, because it understands the scene. It’s a branch off my capstone SideLine (an AI sports-analytics system that already tracks “the player with the ball”), reusing its vision core untouched. Software first, glove I build myself next, drone last. Devlog: M1: AirLine runs SideLine’s tracker through a clean seam, vision core untouched. ~19 FPS. M2: Lock onto one subject. Found track IDs fragment — 293/540 frames “lost.” Quantified the re-ID problem on footage, not a $400 drone. M3: Virtual camera follows like an operated shot, drifts to wide when the target’s lost. First time it looked real. M4: Webcam gestures (MediaPipe) — but it conflicts with my vision stack. Setup stopped instead of breaking it. Best decision of the day. M5: Quarantined gestures in their own environment. First real-hand numbers: mostly 10/10 after fixing bugs unit tests missed. M6: Two-process live system — my hand directs the shot in real time. ~297ms latency, only 35ms of it transport. M7: First 3D camera move: orbit on a tiltable plane, proven by geometric invariants to machine precision (~4e-16). M8: Added push-in, pull-out, dolly. Full shot vocabulary done. 146 tests, vision core never touched. Next: hardware actually building the gesture glove by hand and integrating a drone
The pivot — drone → courtside gimbal (and a lesson) Here’s where the project hit its biggest wall, and I want to log it honestly because the recovery taught me more than any milestone. I was about to spec a drone. Then I actually researched drone law in Qatar and found out it’s one of the strictest regimes in the world: every single flight needs a QCAA permit (owning a drone gives you no right to fly it), and there’s a privacy law (Penal Code Art. 333) against filming people without consent, penalties up to two years. For a system whose whole job is filming school matches full of players and spectators, that’s not a paperwork hurdle, it’s a wall. My original picture a drone autonomously filming matches was effectively dead. The lesson, written down so I don’t forget it: research the constraints of the real world before you fall in love with a plan. I’d validated the software to machine precision, but I almost skipped checking whether the deployment was even legal. Check the boring stuff first. So I swapped the drone for a 3-DOF gimbal on a rail: a motorised camera mount (pan / tilt / roll) that slides along a track, parked courtside. No permit. Same filming-consent terms my existing fixed cameras already navigate. And it runs every match, not the one-off a permitted drone flight would’ve been. It’s more deployable than the drone ever was. A gimbal is also a categorically real difference from just pointing a camera, for one optical reason that isn’t arguable: a fixed camera can only ever crop the pixels it already has, but a gimbal physically moves the lens real parallax, a real push-in that changes perspective, footage that simply doesn’t exist in a static feed. The human directs the intent (“orbit that player,” “push in”) and the system, which understands the scene, executes the move. That’s the thing a fixed camera can’t do, and it survived the pivot completely intact. M9 — the gimbal’s brain (software) Stardance just opened a hardware track, but this milestone was deliberately software: adapt the system to the gimbal before the parts arrive, so the maths is proven when the hardware lands. The beautiful part: because I’d kept the architecture cleanly separated for nine milestones, the drone→gimbal pivot touched exactly one layer. The gesture engine, the scene tracking, the intent commands, the flight-path engine, the live bridge all unchanged. The only new code is a converter that takes an ideal 3D camera pose and works out what the gimbal can physically do with it: pan/tilt/roll angles to aim, plus a position along the rail. And it stays honest, which is the whole point. A gimbal at a fixed pivot can rotate perfectly but can’t translate so a true orbit (circling a subject) is impossible without the camera leaving its rail. The converter proves this with numbers instead of faking it: a follow shot aims with 0.00° error and zero positional gap (the rig does it cleanly), while an attempted orbit still aims perfectly but reports a 9.05-unit gap, flagged out-of-reach on every frame the system refuses to pretend it can do something the hardware can’t. Honest problems that will probably come up: this is geometry on a perfect simulator. The real gimbal will have motor speed limits, inertia, and backlash, it won’t snap to an angle instantly. That’s the hardware phase’s problem, and I’m not pretending the clean sim is the real rig. Up next: the glove parts are shipping. When they land, the build goes physical. breadboard, sensors, solder. Then the gimbal it is...
|
1793289281.7954512
|
1793894081.7954512
|
|
8523
|
Untitled project by @RyanM | Stardance
|
RyanM
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @RyanM | Stardance
|
1793242122.9653492
|
1793846922.9653492
|
|
8524
|
very kewl website by @axie | Stardance
|
axie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: very kewl website by @axie | Stardance
|
1793238923.6149578
|
1793843723.6149578
|
|
8525
|
My awesome macropad! by @tillus | Stardance
|
tillus
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tillus | Stardance
|
1793411508.2376857
|
1794016308.2376857
|
|
8526
|
Untitled project by @baruchgeuze | Stardance
|
baruchgeuze
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @baruchgeuze | Stardanc Title: Untitled project by @baruchgeuze | Stardance...
|
1793195406.8698118
|
1793800206.8698118
|
|
8527
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792889484.6566658
|
1793753484.6566658
|
|
8528
|
My first slack bot! by @billy | Stardance
|
billy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @billy | Stardance
|
1793260057.92829
|
1793864857.92829
|
|
8529
|
fishin by @tillus | Stardance
|
tillus
|
0
|
0.52
|
0
|
[]
|
[{"post_id": 4255, "ts": "2026 [{"post_id": 4255, "ts": "2026-06-07T14:38:27Z", "hours": 0.5228, "text": "I was re-exploring an iOS Metal project I worked on a few weeks ago. I want to use it as a starting point to create a game based on procedural animations like in this YouTube video: https://www.youtube.com/watch?v=qlfh_rv6khY"}]...
|
Title: fishin by @tillus | Stardance
Devlogs:
I w Title: fishin by @tillus | Stardance
Devlogs:
I was re-exploring an iOS Metal project I worked on a few weeks ago. I want to use it as a starting point to create a game based on procedural animations like in this YouTube video: https://www.youtube.com/watch?v=qlfh_rv6khY...
|
1793386151.4776037
|
1793990951.4776037
|
|
8530
|
3D models by @anay_ | Stardance
|
anay_
|
1
|
32.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-15T20:27:30Z", "hours": 8.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "So i have been learning autodesk fusion for the past weeks now and I decided to design models and then put them on github for everyone to see. I have attached a printables link which includes all the files I have. I am trying to get better by the day trying my best lol. All my models i have done so far which are ALL done in fusion 360: 2x4 Toy Block.stl Complex Glass Bottle.stl Day 3 PaperClip.stl DogBowl.stl DogBowlMetalPart.stl DogBowlRubberPart.stl DoorStop.stl Drawer.stl Glass Soda Bottle.stl HandleBar.stl Hex Nut.stl IceCubeTray.stl LightBulb.stl Saturn V Rocket.stl ScrewDriver.stl SnowFlake.stl Star.stl Starship.stl vase.stl", "repo": "https://github.com/anaygoyal09/3D-Fusion-Models", "demo": ""}]...
|
[{"post_id": 29246, "ts": "202 [{"post_id": 29246, "ts": "2026-07-16T01:08:42Z", "hours": 4.0, "text": "During this time, I made many changes. Fixed accuracy of the 747-400 (not really visible, but I can see them). These changes were mostly in the body and the wing accuracy. I also added the windows for the doors to make it more accurate. Underwing pylons: Not that hard, but I wanted to make them look good, so it took a bit of time. I made the outline of the pylon, extruded it, and then cut it so it comes to a point. Then I finished off with the fillets. The hardest part was the Engines. I had to create a cross-section sketch of the engine and then revolve it. After that i created tiny sketches of the back part of the engine and then created a shell to open up the engine opening. Adjusting the engine took a lot of time (cuz my blueprints are not the best) and then I had to create the connector. I did that by creating an airfoil and then creating the vertical sketch. Finished off by sweeping it. Then I created a new component, moved the engine to the right place and then created a new connected in the same way. It was always not turning out the best so i spent a lot of time fixing all of it to make it look better. It will take me almost 2-4 hrs to finish this airplane, I will fix the shape more, add the underbody and then the livery. I put an image of how the engine was not looking that good and a video on how i made it."}, {"post_id": 26989, "ts": "2026-07-12T03:42:30Z", "hours": 2.0, "text": "FINALLY FINISHED THE DETAILS!!! I added windows , the passenger windows, wing details, fuselage details, and appearances. I created sketches an then split the body, added the appearances. Seems simple but it can take quite a bit of time and making it look good is quite hard."}, {"post_id": 25733, "ts": "2026-07-10T05:24:51Z", "hours": 2.0, "text": "DONE I FINSHED THE WINGS IN THE 747!!! I created the airfoil and then created a plane at an angle and sweeped it. Seems easy enough but fusion kept throwing errors for some reason so it took much longer than i wanted. Also when i was trying loft to round the edges it wasnt working for some reason and kept saying it cant solve. Well im happy its working now so here it is!"}, {"post_id": 24159, "ts": "2026-07-07T15:24:25Z", "hours": 2.0, "text": "completed the 747 body! I first made a t-splines (Form) and made the base of the body and then I patched the edges (2nd Image). Then after that I made a sketch outlining the front and back of the fuselage. Then, I lofted the edges. I took most time on perfecting the edges of the form so its as realistic as possible."}, {"post_id": 23223, "ts": "2026-07-06T01:33:50Z", "hours": 0.0, "text": "made a boomerang just used a reference image and traced it not too big im going to start the 747 now"}, {"post_id": 22986, "ts": "2026-07-05T17:54:08Z", "hours": 4.0, "text": "Printed the A330-300! Took me way too long because I was splitting the body and I’m still new, so it wasn’t coming out exactly how I wanted at first. Also the print kept on failing and that took me quite a lot of time to fix. There are going to be 4 folders affiliated with my project: Colored, No Splitting the Body No Color, Without Split No Color, With Split While it was printing, I went about making a ninja star (image attached). Next, I’m probably either going to make a 747 model or a better version of the Saturn V rocket. If I do the 747, it will include significant design improvements, such as easier 3D print assembly and a custom display stand :)"}, {"post_id": 19703, "ts": "2026-07-01T03:04:37Z", "hours": 1.0, "text": "Modifications for printability, using split tool in slicers and then printing, Probably Im going to print one colored and one with indentation in the windows with no color. Model is fine in terms of the printability just need to split now."}, {"post_id": 18157, "ts": "2026-06-29T05:28:38Z", "hours": 4.0, "text": "IM DONE, finished the livery, engines, rounded edges made finishing edits. I will continue to make edits by splitting the object up so its printable!"}, {"post_id": 16513, "ts": "2026-06-26T21:22:31Z", "hours": 1.0, "text": "Finishing up the details added rudder details and tried rendering. I also added flap track beams into the model! Will add engines next I will see if i want to add wheels or not"}, {"post_id": 14895, "ts": "2026-06-24T05:53:50Z", "hours": 1.0, "text": "working more on the finer parts of the airplane"}, {"post_id": 14125, "ts": "2026-06-23T03:13:28Z", "hours": 1.0, "text": "working on fine details"}, {"post_id": 13551, "ts": "2026-06-22T05:41:41Z", "hours": 1.0, "text": "I am bit of a perfectionist so im taking a little more time than I should + I am new so yea worked on adding the wings of the a330!"}, {"post_id": 13411, "ts": "2026-06-21T23:20:30Z", "hours": 0.0, "text": "Started wings. Used an airfoil template to trace out the wing shape"}, {"post_id": 12358, "ts": "2026-06-20T05:07:20Z", "hours": 1.0, "text": "went about making the airplane body for an A330-300"}, {"post_id": 11539, "ts": "2026-06-18T20:45:44Z", "hours": 0.0, "text": "Completed outlet cover I didn’t know it would be that complicated lol. Was experimenting with constraints in fusion 360 so took a bit of time"}, {"post_id": 11097, "ts": "2026-06-18T04:32:06Z", "hours": 0.0, "text": "I 3d modeled a vase that involved revolving around pipes to create a cool design and then designed a fuesalage of an airplane."}, {"post_id": 10937, "ts": "2026-06-17T22:32:24Z", "hours": 0.0, "text": "Working on making a 3d model for an airplane so far I have completed the fuselage wings and other minor details will come after"}, {"post_id": 7777, "ts": "2026-06-13T00:05:06Z", "hours": 0.0, "text": "screwdriver and a drawer in fusion"}, {"post_id": 6964, "ts": "2026-06-11T17:56:09Z", "hours": 0.0, "text": "Dog Bowl"}, {"post_id": 6638, "ts": "2026-06-11T03:56:10Z", "hours": 0.0, "text": "Snowflake!"}, {"post_id": 6368, "ts": "2026-06-10T18:40:26Z", "hours": 0.0, "text": "Tried to model a phone case using a step file as a reference or a blueprint to create it"}, {"post_id": 5967, "ts": "2026-06-10T00:03:19Z", "hours": 0.0, "text": "vase in blender"}, {"post_id": 5829, "ts": "2026-06-09T19:27:06Z", "hours": 0.0, "text": "Light Bulb"}, {"post_id": 5763, "ts": "2026-06-09T17:43:28Z", "hours": 0.0, "text": "Made a doorstop and customizable handle bar in fusion"}, {"post_id": 5245, "ts": "2026-06-08T23:08:39Z", "hours": 0.0, "text": "Hex Nut in fusion"}, {"post_id": 5122, "ts": "2026-06-08T20:12:53Z", "hours": 0.0, "text": "Finished starship model"}, {"post_id": 4661, "ts": "2026-06-08T02:04:50Z", "hours": 1.0, "text": "Working on new starship model in fusion!"}, {"post_id": 4398, "ts": "2026-06-07T18:32:31Z", "hours": 0.0, "text": "Completed 3d model For Saturn V rocket"}, {"post_id": 4315, "ts": "2026-06-07T15:58:52Z", "hours": 0.0, "text": "Working on making a rocket Model"}, {"post_id": 3800, "ts": "2026-06-06T21:03:38Z", "hours": 0.0, "text": "IceCube tray I made"}]...
|
Title: 3D models by @anay_ | Stardance
Devlogs:
I Title: 3D models by @anay_ | Stardance
Devlogs:
IceCube tray I made
Working on making a rocket Model
Completed 3d model For Saturn V rocket
Working on new starship model in fusion!
Finished starship model
Hex Nut in fusion
Made a doorstop and customizable handle bar in fusion
Light Bulb
vase in blender
Tried to model a phone case using a step file as a reference or a blueprint to create it
Snowflake!
Dog Bowl
screwdriver and a drawer in fusion
Working on making a 3d model for an airplane so far I have completed the fuselage wings and other minor details will come after
I 3d modeled a vase that involved revolving around pipes to create a cool design and then designed a fuesalage of an airplane.
Completed outlet cover I didn’t know it would be that complicated lol. Was experimenting with constraints in fusion 360 so took a bit of time
went about making the airplane body for an A330-300
Started wings. Used an airfoil template to trace out the wing shape
I am bit of a perfectionist so im taking a little more time than I should + I am new so yea worked on adding the wings of the a330!
working on fine details
working more on the finer parts of the airplane
Finishing up the details added rudder details and tried rendering. I also added flap track beams into the model! Will add engines next I will see if i want to add wheels or not
IM DONE, finished the livery, engines, rounded edges made finishing edits. I will continue to make edits by splitting the object up so its printable!
Modifications for printability, using split tool in slicers and then printing, Probably Im going to print one colored and one with indentation in the windows with no color. Model is fine in terms of the printability just need to split now.
Printed the A330-300! Took me way too long because I was splitting the body and I’m still new, so it wasn’t coming out exactly how I wanted at first. Also the print kept on failing and that took me quite a lot of time to fix. There are going to be 4 folders affiliated with my project: Colored, No Splitting the Body No Color, Without Split No Color, With Split While it was printing, I went about making a ninja star (image attached). Next, I’m probably either going to make a 747 model or a better version of the Saturn V rocket. If I do the 747, it will include significant design improvements, such as easier 3D print assembly and a custom display stand :)
made a boomerang just used a reference image and traced it not too big im going to start the 747 now
completed the 747 body! I first made a t-splines (Form) and made the base of the body and then I patched the edges (2nd Image). Then after that I made a sketch outlining the front and back of the fuselage. Then, I lofted the edges. I took most time on perfecting the edges of the form so its as realistic as possible.
DONE I FINSHED THE WINGS IN THE 747!!! I created the airfoil and then created a plane at an angle and sweeped it. Seems easy enough but fusion kept throwing errors for some reason so it took much longer than i wanted. Also when i was trying loft to round the edges it wasnt working for some reason and kept saying it cant solve. Well im happy its working now so here it is!
FINALLY FINISHED THE DETAILS!!! I added windows , the passenger windows, wing details, fuselage details, and appearances. I created sketches an then split the body, added the appearances. Seems simple but it can take quite a bit of time and making it look good is quite hard.
During this time, I made many changes. Fixed accuracy of the 747-400 (not really visible, but I can see them). These changes were mostly in the body and the wing accuracy. I also added the windows for the doors to make it more accurate. Underwing pylons: Not that hard, but I wanted to make them look good, so it took a bit of time. I made the outline of the pylon, extruded it, and then cut it so it comes to a point. Then I finished off with the fillets. The hardest part was the Engines. I had to create a cross-section sketch of the engine and then revolve it. After that i created tiny sketches of the back part of the engine and then created a shell to open up the engine opening. Adjusting the engine took a lot of time (cuz my blueprints are not the best) and then I had to create the connector. I did that by creating an airfoil and then creating the vertical sketch. Finished off by sweeping it. Then I created a new component, moved the engine to the right place and then created a new connected in the same way. It was always not turning out the best so i spent a lot of time fixing all of it to make it look better. It will take me almost 2-4 hrs to finish this airplane, I will fix the shape more, add the underbody and then the livery. I put an image of how the engine was not looking that good and a video on how i made it.
Ships:
So i have been learning autodesk fusion for the past weeks now and I decided to design models and then put them on github for everyone to see. I have attached a printables link which includes all the files I have. I am trying to get better by the day trying my best lol. All my models i have done so far which are ALL done in fusion 360: 2x4 Toy Block.stl Complex Glass Bottle.stl Day 3 PaperClip.stl DogBowl.stl DogBowlMetalPart.stl DogBowlRubberPart.stl DoorStop.stl Drawer.stl Glass Soda Bottle.stl HandleBar.stl Hex Nut.stl IceCubeTray.stl LightBulb.stl Saturn V Rocket.stl ScrewDriver.stl SnowFlake.stl Star.stl Starship.stl vase.stl...
|
1792882069.5571966
|
1793746069.5571966
|
|
8531
|
Guitar Learning Tool by @oguh_sevla | Stardance
|
oguh_sevla
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Guitar Learning Tool by @oguh_sevla | Stard Title: Guitar Learning Tool by @oguh_sevla | Stardance...
|
1793444142.3063335
|
1794048942.3063335
|
|
8532
|
Varanasi by @rishwith_24bes7048 | Stardance
|
rishwith_24bes7048
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Varanasi by @rishwith_24bes7048 | Stardance
|
1793188284.6790159
|
1793793084.6790159
|
|
8533
|
Robotic arm by @AC | Stardance
|
AC
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Robotic arm by @AC | Stardance
|
1793231516.9351013
|
1793836316.9351013
|
|
8534
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792950734.7823067
|
1793814734.7823067
|
|
8535
|
Student Mentoring by @Shourya_Patel | Stardance
|
Shourya_Patel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Student Mentoring by @Shourya_Patel | Stard Title: Student Mentoring by @Shourya_Patel | Stardance...
|
1793414996.3761375
|
1794019796.3761375
|
|
8536
|
Untitled project by @AxicFortis | Stardance
|
AxicFortis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @AxicFortis | Stardance
|
1792716556.3532252
|
1793321356.3532252
|
|
8537
|
Camera Control Extension by @purvika | Stardance
|
purvika
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Camera Control Extension by @purvika | Star Title: Camera Control Extension by @purvika | Stardance...
|
1793228036.9758759
|
1793832836.9758759
|
|
8538
|
My awesome macropad! by @pravinheisnam | Stardance
|
pravinheisnam
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @pravinheisnam | St Title: My awesome macropad! by @pravinheisnam | Stardance...
|
1792760113.48935
|
1793364913.48935
|
|
8539
|
FPS Shooter by @rudranshm007 | Stardance
|
rudranshm007
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FPS Shooter by @rudranshm007 | Stardance
|
1793324853.4731777
|
1793929653.4731777
|
|
8540
|
My first slack bot! by @Darch | Stardance
|
Darch
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Darch | Stardance
|
1792749268.90548
|
1793354068.90548
|
|
8541
|
EmPad by @Matej | Stardance
|
Matej
|
1
|
10.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-14T08:44:23Z", "hours": 10.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "My 4x3 numpad/keypad with a wheel for volume adjustment. Fully customizable controls after, with a temporary html configurator to paste in after for QMK key adjustment. Will hopefully polish up firmware when I obtain the actual keyboard and build it, but compiles and runes now.", "repo": "https://github.com/MatejPechoucek/hackpad", "demo": ""}]...
|
[{"post_id": 5798, "ts": "2026 [{"post_id": 5798, "ts": "2026-06-09T18:39:50Z", "hours": 10.1867, "text": "Hackpad Case + PCB and Firmware"}]...
|
Title: EmPad by @Matej | Stardance
Devlogs:
Hackp Title: EmPad by @Matej | Stardance
Devlogs:
Hackpad Case + PCB and Firmware
Ships:
My 4x3 numpad/keypad with a wheel for volume adjustment. Fully customizable controls after, with a temporary html configurator to paste in after for QMK key adjustment. Will hopefully polish up firmware when I obtain the actual keyboard and build it, but compiles and runes now....
|
1793317892.600565
|
1793404292.600565
|
|
8542
|
My awesome macropad! by @o_p_luque | Stardance
|
o_p_luque
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @o_p_luque | Starda Title: My awesome macropad! by @o_p_luque | Stardance...
|
1793285777.7705414
|
1793890577.7705414
|
|
8543
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792882146.97209
|
1793746146.97209
|
|
8544
|
Personal website portfolio by @aakash | Stardance
|
aakash
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Personal website portfolio by @aakash | Sta Title: Personal website portfolio by @aakash | Stardance...
|
1793328567.3079555
|
1793933367.3079555
|
|
8545
|
flock camera detector by @joey2 | Stardance
|
joey2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: flock camera detector by @joey2 | Stardance
|
1793306898.4161127
|
1793911698.4161127
|
|
8546
|
a godot game by @moayedjouini | Stardance
|
moayedjouini
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: a godot game by @moayedjouini | Stardance
|
1792738297.4692936
|
1793343097.4692936
|
|
8547
|
Building a Cyberdeck file viewer for photos/videos Building a Cyberdeck file viewer for photos/videos. Aswell as Cad on the cyberdeck. by @parks | Stardance...
|
parks
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Building a Cyberdeck file viewer for photos Title: Building a Cyberdeck file viewer for photos/videos. Aswell as Cad on the cyberdeck. by @parks | Stardance...
|
1793191739.1921017
|
1793796539.1921017
|
|
8548
|
Portfolio by @ashishsharma_mail10 | Stardance
|
ashishsharma_mail10
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Portfolio by @ashishsharma_mail10 | Stardan Title: Portfolio by @ashishsharma_mail10 | Stardance...
|
1793426125.9156075
|
1794030925.9156075
|
|
8549
|
Verizuke by @rishwithgharshakurthi | Stardance
|
rishwithgharshakurthi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Verizuke by @rishwithgharshakurthi | Starda Title: Verizuke by @rishwithgharshakurthi | Stardance...
|
1793339822.4335139
|
1793944622.4335139
|
|
8550
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792925640.1158197
|
1793789640.1158197
|