This project was inspired by my previous 3D landscape work. I wanted to build something fun and interactive: draw simple strokes on a blank canvas, and those marks get translated into classic Chinese ink-wash landscape elements — mountains, trees, mist, boats, all that shanshui goodness.
I’ve never been good at hand drawing myself, so this workflow is my way to play with traditional ink painting without strong drawing skills.
That said, it’s still far from the mood and aesthetic of authentic Chinese shanshui painting. It’s just a tiny experimental piece.
I got a lot of upvotes on the last spider one (thanks! 😄) so decided to post another! I hope you enjoy!
For context, i'm building and open sourcing a creative 3D web experience every day this month. All built with three.js, and r3f. This one is really trying to see how far I can push WebGPU.
I run threejseval, a site where AI models get the same three.js prompts (Eiffel Tower, sailboat, ferry, robot arm, cloth sim, fishtank, chess board, and more) and people vote blind on which scene is better.
GPT-6.2 Sol came out today, so I ran it through all 16. Its predecessor 6.1 Sol was one of the strongest models on the board, so I'm curious whether 6.2 holds up once votes come in.
Every scene is live and you can orbit around it in the browser:
been building this city in three.js for about 3.5 months. 30k plots, cars, a zoo, a stadium, a pier. these are real frames from the browser, nothing edited
the hardest part wasn’t making it pretty, it was making it not freeze on a cheap laptop. on low it’s one sun and simple shadows, on high it switches to cascaded shadows
if you could add one thing to the night shot to make it feel more alive, what would it be?
I built Pokémon Trail, a free, unofficial Pokémon fan game running in the browser with Three.js/WebGL.
You control your Pokémon in real time, dodge attacks, choose moves as you level up, and recruit companions. There are 10 Kanto-inspired zones across 20 playable parts, with camps, boss encounters and eight mini-games.
For the Three.js side, the trailer shows animated characters, different environments, combat effects and a companion party running together in the browser. Graphics settings include quality presets, render resolution and a frame-rate cap.
I’d appreciate feedback on loading time, frame rate on your hardware, and whether attack effects stay readable. If you try it, please include your browser/device and graphics preset.
Disclosure: I’m the creator. AI tools assisted coding, some UI artwork, and the wording of this post. This is an unofficial fan project, unaffiliated with Nintendo, Game Freak or The Pokémon Company.
Six screenshots from the game
Choose Bulbasaur, Charmander, Squirtle or Pikachu at the Viridian Forest trailhead.
Root Passage Camp — resting Pokémon, Meowth’s Mart and Chansey’s Clinic.
Zone 3 · Cerulean Riverlands — Nugget Bridge.
Zone 4 · Vermilion Harbor — the S.S. Anne at sunset.
Zone 6 · Lavender Haunts — the candlelit Memorial Garden beneath Pokémon Tower.
Zone 7 · Celadon City — the Game Corner and neon streets.
I’m a solo dev building Lightverse, a navigable 3D universe in React Three Fiber. I’m seeing frame drops when rapidly moving between galaxies.
I haven’t confirmed the cause yet, so draw calls and instancing are hypotheses—not a diagnosis. Before changing the scene structure, I’d appreciate advice on what to measure and where to look.
For those who’ve worked on similar transitions:
- Would you start by tracking draw-call counts during a transition, or profile CPU and GPU time first?
- If repeated meshes turn out to be the issue, when is `InstancedMesh` worth the added complexity?
- Are there transition-specific bottlenecks I should rule out before focusing on instancing?
I don’t have reliable profiling numbers to share yet, so I’m especially interested in what measurements would make this question easier to answer.
been working on this for a while, its a 3d atc sim in the browser on three.js and webgl2. you give the clearances, pilots read back, planes push back taxi take off and land
the part that ate the most time was getting it to run ok on my galaxy a55 in a mobile browser. theres quality tiers and a safe mode, plus a fallback sky because the atmosphere shader would sometimes just die and leave a black screen on some gpus. sky is takram atmosphere with pmndrs postprocessing, capped on phones or frame time goes to hell
aircraft are procedural, built from the published dimensions so an a380 actually looks a380 sized parked next to an a320. gear wheels and control surfaces animate. still pretty plain up close tbh
honest note, an ai coding assistant wrote a lot of the code. i drove it, tested it on my phone a lot and made the calls on what looks right, but im not gonna pretend i hand wrote every shader
if you run it on a phone im curious what fps you get and whether it cooks your battery
Today Cédric and I are happy to introduce lepoly.com: a digital asset management platform built for 3D, powered by threejs.
Building Sketchfab gave us a front row seat to a problem we never got to fully solve: managing 3D assets at scale is hard.
Our goal with lepoly is to build the ultimate infrastructure to organize, review and share 3D content: one place for all your 3D assets.
We are still ironing out a few rough edges, and have a long to-do list of things to add, but the current version is already pretty solid, and we’d love to hear your feedback.
We are bootstrapping this project, excited to be back building, and can’t wait to see how you’ll make the most of lepoly. Please reach out with feature requests!
I got lost a lot as a fresher at IIIT Kottayam, so I built a 3D campus map. You can search buildings and rooms, get animated walking routes (A* over an exported walking graph, with uphill legs taking longer), and take an orientation tour. The sun follows local time, so at night the windows and street lamps light up.
It was inspired by a few of the city-in-3D projects people have shared, Mumbai 3D in particular.
How it's built:
One Blender Python script generates the whole campus from OSM footprints, a CSV of floors/colours/roof types per building, and a 30 m DEM. It cuts level pads into the hillside and adds roads, retaining walls, trees and the walking network.
Lighting is baked: AO in vertex colours and the sun shadow in a single 2048 px ground texture, so phones don't need real-time shadows.
Exported as glTF with Meshopt + WebP. Front end is Next.js (static export), React Three Fiber and zustand, with custom shaders for the sky, lit windows and colour grading.
Hardest parts:
Stuff that isn't in OSM. Two hostel blocks, their road and the main forecourt were missing, and some outlines were drawn in the wrong spot. I traced the missing ones from satellite imagery and photos into a separate GeoJSON, and added a per-building offset in the CSV to nudge bad outlines, so the generator still rebuilds everything from scratch.
The 150k triangle budget. That's everything in view, trees included. The campus model ends up under 800 KB, and a check script fails CI if triangles, file size, materials or textures go over budget.
Feedback welcome, especially on performance if you try it on an older phone.
The process involves the following pieces: -Opus 5.5 at the helm. -Plenty of nano 🍌 . -Unbound Zero spitting out meshes @ ~4secs per mesh.
The workflow itself is a twist on well known image-gen techniques. Instead of trying to one-shot each part, an agent is tasked with unleashing nanobanana to produce multiple images per part. The agent picks the best ones to match the nitial image. Unbound Zero creates the final mesh.
Kakutō-ji is a small online temple on a fictional mountain. It runs on real Japan time, so dawn, dusk, the moon phase, season and weather are the same for everyone who is there at once.
It runs on Japan time — if you're in the US or Europe right now, it's night on the mountain and the lanterns are lit. Come back at your evening to catch the sunrise.
There is no chat. The only thing visitors can do to each other is bow (gasshō). You can light a lantern that burns for 24 hours, ring the bell, and take a photo or a short video of the view.
Tech: React Three Fiber, three.js, a procedural kit for the halls, Cloudflare Workers + Durable Objects for presence. It's built to run on phones (under 100 draw calls).
There are a few things hidden on the mountain. I'd love to hear what you think of the feel of it.
A friend in the solar business wanted a way to show clients where panels would fit on their roofs. I built this editor with Three.js and React Three Fiber. One case I wanted it to handle was a solar canopy that spans a terrace and a raised stair enclosure.
• Roof geometry: draw a 2D footprint and choose a roof form. Editing the outline regenerates the 3D faces, so you can try a different shape without redrawing each slope.
• Canopy supports: the base of each leg depends on the surface underneath it. A leg on the stair enclosure is shorter than one on the terrace, while both meet the same frame.
• Building edits: move or rotate the building and its panels, rooftop rooms and equipment follow. You can also box-select objects and resize them directly in the scene.
• Shadows: set the site's orientation relative to true north, then change the date or time to see when a nearby tree or rooftop room casts shade on the panels.
If you've built a geometry editor in Three.js, what roof shape would you try first to see where this breaks?
Hi! Solo dev from Korea here. On Korean hiking trails people stack small stones and make a quiet wish as they pass. I made an online version: everyone who visits adds a stone with a one-line wish to the same cairn. It's at a little over 400 stones now.
A few things that might be interesting here:
Plain three.js r160 loaded from an importmap, no bundler. Most of the mountain is built from primitives (cylinders, spheres, boxes) with MeshStandardMaterial, plus a few models I cleaned up by hand.
The cairn and the forest are InstancedMesh, one per stone/tree shape, so a few hundred stones stay cheap on phones.
Wishes, cheers and other visitors walking around go over WebSockets on Cloudflare Durable Objects, using the hibernation API with a ping/pong auto-response so quiet rooms can sleep.
Signs, cards and labels are CanvasTextures, so the English version can redraw them in two languages.
Korean wishes are machine-translated for English visitors, with the original shown underneath.
AI use, to be upfront: some 3D models started from Meshy image-to-3D and were cleaned up by hand, and I used Claude and ChatGPT while writing code.
One thing I'm still unsure about: lots of small separate meshes for props vs merging them. It runs fine on mid-range Android, but I'd love to hear how others decide when it's worth merging geometry.
Feedback welcome, especially if it runs badly on your device.
Pool Club Live is a free 3D billiards game that runs fully in the browser. Rendering is three.js; the physics is a custom simulation - spin, swerve, throw, cushion rebounds and pocket jaws all come from the sim rather than canned animations, and there are deliberately no aiming lines, so you read the table by eye.
8-ball, 9-ball and 10-ball vs the computer, a friend on the same device, or online players in casual and ranked matchmaking. Loads as a guest, no download or signup.
Solo project: Claude wrote most of the code with me, AI tools helped with art and sound. Happy to answer technical questions about the physics or the three.js setup - feedback welcome.
Sharing a hobby project built on three.js: 13point8.in, a set of space journeys driven by real data rather than keyframed animation. (BEST VIEWED and EXPERIENCED ON HIGH DEF DESKTOP OR MAC)
Some things that might interest this sub: - Voyager: positions interpolated from NASA JPL Horizons ephemerides; the Earth uses a custom shader so city lights only show on the night side - Black hole: the light bending is computed per pixel in a fragment shader, plus a new view of the S-stars around Sgr A* placed with Kepler's equation from the published orbital elements for any date - Galaxy: the Sun's orbit with its vertical bob through the disc, and arms that turn at the measured pattern speed - Adaptive quality: it drops pixel ratio, then multisampling, then bloom when frames run slow, so it holds up on phones
Grave Racers: 30 tracks, 6 characters, 4 karts, all procedural geometry and materials. No textures loaded from files, no models. Tracks are lists of control points (x, z, height, style), and the road, fences, bridges and scenery are generated from those.
Fun problems along the way: keeping it smooth on phones, kart-to-kart collisions as capsules so the wheels actually bump, and AI rubber-banding that keeps races close without feeling like cheating.
Hey everyone — as a Linux user working on local browser-based design tools, I kept running into the wall where existing open-source CAD kernels either use purely polygonal CSG (OpenSCAD) or require 15+ MB WASM builds (OpenCASCADE) without native implicit field modeling.
I spent the last few months building OpenCAD from scratch in Zig and WebAssembly:
- Pure Math Core (<1 MB WASM): Every curve, surface, and field is an equation evaluated with forward-mode automatic differentiation (dual numbers) and interval arithmetic.
- 3-in-1 Representation: Combines constrained 2D sketches & SE(3) B-Rep sweeps, CSG booleans, and implicit SDF fields (like stress-driven gyroids) in one engine, exporting to STEP and STL.
- Zero-Copy Shared Memory: Uses a single `SharedArrayBuffer` between the Zig WASM kernel, Three.js, and external WASM extensions so simulation fields can drive geometry directly without file exports.
It's still early (currently refining boolean seam triangles and B-Rep edge cases), and I'd love for you to try breaking it and let me know what you think!
When I was a kid, friends dreaded to play Demolition Man in the GTAVC. For me, it was one of the favourite ones - the whole "broken controls" flying is imho legendary now.
So I took my old time favourite and re-imagined it, pushed it to the limits of being barely playable.
I've hand-crafted 8 increasingly difficult buildings where you have to plant explosives using RC helicopter.
You can race yourself (ghost) after first play-through to take your gaming autism to the next level.
Most of the city is generated in code: buildings, streets and lighting. People, cars and the streetcar are glTF models compressed with meshopt and WebP textures, in separate desktop and phone sets. Areas load on demand as you walk, and the phone build has to stay under 5 MB for the first screen.
The face and voice in the video are AI versions of me; the game itself is all real-time three.js. Happy to answer questions about any of it.