DEV Community

Cover image for 3Draft: Vibe first, explain later!
Peter Vivo
Peter Vivo Subscriber

Posted on

3Draft: Vibe first, explain later!

This is Part I of the explanation, simply because there is so much to talk about.

So, 11 days of madness, but my competition entry, 5%, is finally complete. It is just a small — although particularly important — piece of a much bigger story.

The development was an indescribable rush, yet I was in a state of flow almost the entire time.

Luckily, I already had Spider Paint. Knowing what I had at my disposal, I thought I could actually build a VR application with just 11 days left before the submission deadline.

At the time, I naively thought that implementing stereoscopic rendering would be enough to satisfy most of the requirements.

The sad truth, however, is that VR is an entirely different reality.

But let's not get too far ahead of ourselves.

The Globe try load the globe!

I wanted to speed up development, and since AI was already capable of 3D modeling through MCP, I asked it to create a globe.

My first step was to implement transparent and soft materials. Now a sphere actually looked like a sphere, and with transparent oceans, I could immediately see what was on the other side of the planet.

My partner and I often joke about digging all the way to China. Well, it quickly became clear that we would actually end up somewhere in the ocean.

As always, I continued developing Spider Paint following the KISS principle. I adopted Blender's keyboard shortcut philosophy, but unlike Blender, I was thinking in terms of first-person modeling, an approach I described in my article Eye of the Beholder.

So I actually developed the early versions on my phone.

The most important feature was the M key, which allows me to shoot cuboids into the air or onto existing surfaces.

And before long, I ended up with the following sight.

... and that's when it hit me: I could create an application about space travel.

Conceptually, my 3D editor isn't built around having an object in the center of the scene and editing it. Instead, any object can become a target, and once selected, it becomes the center of attention.

Since I already had MCP capabilities, and despite being a huge Star Wars fan, I started wondering: what if I could actually travel between real, known stars?

I MCP-ed the 500 nearest stars into the scene, and that's how my journey through space began ... on my phone.

From there, things escalated quickly.

I realized how cool it would be to have a 3D editor that allowed you to travel from the edge of your desk to the most distant galaxies — all within a single scene.

The next challenge was rendering galaxies. It quickly became obvious that I couldn't add enough individual stars to represent entire galaxies, so I turned to shaders. The downside, of course, is that you can't visit individual stars within these shader-generated galaxies.

Then there was no stopping me. I added some well-known black holes and exoplanets, and, of course, an Enter-activated search feature so you might even find your favorite celestial object.

I deliberately wanted to avoid hyperspace jumps because, in my opinion, they take away the experience of actually traveling through the universe.

So there was only one option left:

SNP Drive — SPEED NO PROBLEM.

I made the speed levels increase exponentially, allowing you to travel across the entire universe.

You can explore the universe yourself by loading the Deep Sky scene.

Controls

(When orbit mode locks onto a target, your movement becomes orbital.)

 W - speed forward   R - up          tab - next target
 S - speed backward  F - down          T - target ( cursor )
 A - left            [ - left roll   esc - cancel target/orbit
 D - right           ] - right roll.   0 - orbit
                 space - stop      enter - search target
Enter fullscreen mode Exit fullscreen mode

Maximum speed: there is no limit, but there's not much point in traveling faster than a few million light-years per second.

If you get hopelessly lost, search for the Sun and keep accelerating until you're halfway there.

Agent Q

Pressing the Q key takes you into model editor mode. If your cursor is hovering over an object, it will select that object. If you're pointing at empty space, you'll get a cube with the material currently selected in the P palette.

You can then edit it using the familiar Blender keyboard shortcuts. Hopefully, I've included them all in the Help section.

I'll write about this in more detail later.

You can try the evolving development environment online at https://spider-paint.vercel.app/.

Five Percent, my competition entry, is essentially a snapshot of this development environment.

I'd really appreciate it if you gave my competition entry a like on Devpost — and even more so if you left a comment there!

Top comments (5)

Collapse
 
alexcodebytes profile image
Oleksandr •

What I find particularly interesting here is how the original purpose of the project evolved during development. You started with a relatively straightforward idea of getting VR rendering to work, but ended up building something much more ambitious.

The concept of treating any object as the center of attention rather than keeping the scene organized around a fixed central object is especially intriguing. Combined with the ability to move seamlessly from a desk-scale environment to interstellar distances, it opens up some really interesting possibilities.

I also like the decision to avoid traditional hyperspace jumps. Actually experiencing the scale of the universe, rather than simply skipping across it, makes the whole concept much more compelling.

Eleven days is an impressive timeframe for something of this scope. I'd be particularly interested in seeing how you approach the transition from desktop controls to an actual VR interaction model.

Collapse
 
pengeszikra profile image
Peter Vivo • • Edited

This transition Is a painful process. Of course, I didn't have a proper VR device. Well, not a usable one. Just a mobile phone VR headset, but I couldn't cross my eyes enough to make the stereo images merge into a proper 3D view. So, three days before the deadline, I rented a Meta Quest headset. That's when the real trouble started. The moment I switched my application into VR mode, absolutely nothing was visible. What followed was seven hours of impossible vibe debugging, with two AIs working on the problem in parallel: GPT-6 and Claude Opus 5.5.
At first, they suggested that I should just give up on my own 3D engine and switch to Three.js.
Instead, I spent those seven hours vibe coding a debugging system with Claude, giving it direct access to real-time data and screenshots from my device. I also had two applications running side by side: my own engine and a simple Three.js example containing just a cube and a sphere. The Three.js example worked. Mine didn't. I was sweating like crazy and swearing heavily, which is something I rarely do. One of the problems turned out to be the controllers. At that point, I was still using VR controllers, and one of their components kept returning a null value. My engine treated this as an error and shut down the entire scene.

What happened next? I'll tell that story in the next article. ...

Game of Code 2017 24hour hackhaton, Luxemburg - VR challenge, at the end my actual HP laptop GPU is burned down

Collapse
 
alexcodebytes profile image
Oleksandr •

The part about spending seven hours building a debugging system instead of abandoning your engine is particularly interesting. The null controller value causing the entire scene to shut down is exactly the kind of failure that makes VR debugging so frustrating—everything can appear broken when the actual problem is one unexpected input.

I also like that you kept your own engine and Three.js running side by side. Having a known-working reference probably saved you from chasing rendering issues that weren't actually rendering issues. Now I'm curious how much of that debugging infrastructure you ended up keeping after the hackathon, because real-time screenshots and device data sound like tools that could be useful long after that particular bug was fixed.

Thread Thread
 
pengeszikra profile image
Peter Vivo •

The debugg function is still in the code, and the UI also. On the right hand you have a bug icon.

Thread Thread
 
alexcodebytes profile image
Oleksandr •

That's actually great! Keeping the debugging system accessible in the final application is even better than I expected. A dedicated bug icon in the UI makes it sound like the whole seven-hour debugging detour turned into a permanent developer tool. 😄

I'd love to know whether you still use it for regular development or whether it remains primarily a VR-specific troubleshooting feature. Either way, that's a pretty useful outcome from a very stressful deadline!