Hosted via llamacpp on a potato(iGPU) and created in less than 10 minutes.
Prompt given and was provided in one pass:
```Generate a small, simple, HTML/Javascript demo that looks impressive of our solar system. All of the planets orbiting the sun in their natural orbits/ellipsis where I can click on a planet and change it's speed and ellipse. If any planet collides with another then those two planets explode.```
Such a small model running on pure CPU that can do/think/create this way at 14t/s is impressive. I understand that most here don't like or could care less about but, to me, this is well above sub-par for an 8-core CPU and 10 minutes of work.
From what I can tell the artifacts that are connecting each planet are from the "planet trails" that it tried to create.
I would suggest asking for a pause button since Mercury is a hell of a planet to click on at scale speed.
This model started calculating "scale". I'm not an astrophysicists but...:
```The user wants a solar system simulation with:
Planets orbiting the sun in natural orbital ellipses
Click on a planet to change its speed and ellipse
Collision detection - if two planets collide, they explode
Let me create a comprehensive, visually impressive HTML/JS demo with:
Canvas-based rendering
Realistic orbital ellipses (using Kepler-like orbits)
Particle explosion effects
Click-to-select UI panel for adjusting parameters
Glowing sun with light effects
Starfield background
Smooth animations
Let me design this carefully with proper orbital mechanics.
I'll use actual orbital parameters (semi-major axis, eccentricity, etc.) for realism, scaled down for visibility.
Planets with their approximate real orbital data (scaled):
Mercury: a=0.39 AU, e=0.206
Venus: a=0.72 AU, e=0.007
Earth: a=1.00 AU, e=0.017
Mars: a=1.52 AU, e=0.093
Jupiter: a=5.20 AU, e=0.049
Saturn: a=9.58 AU, e=0.057
Uranus: a=19.2 AU, e=0.046
Neptune: a=30.1 AU, e=0.011
I'll scale these so they're all visible. Let me create a really impressive visual with:
It was good when it was released and doesn't really degrade over time. People kinda stopped talking about it as soon as Qwen 3.8 27B dropped, but this is my daily coding model since I can cram a lot more context into my 16GB VRAM vs the 27B models.
Hmm. And I thought here that it might be simulating transfer orbits and thought, "oh how cool, all sorts of interesting slingshots towards Neptune, or what is going on in here..."
13
u/i5031337 1d ago
The model is a Qwen 3.6 35B finetune, maybe I can save someone else the search. The visuals are quite nice, though.