Live data from Hacker News

Show HN: Consol3 – A 3D engine for the terminal that executes on the CPU

github.com

1–10 of 38 posts

Show HN: Consol3 – A 3D engine for the terminal that executes on the CPU

#1
Hi all

This has been my hobby project for quite a few years now

It started as a small engine to serve as a sandbox to try out new 3d graphics ideas

After adding many features through out the years and re-writing the entire engine a few times, this is the latest state

It currently supports loading models with animations, textures, lights, shadow maps, normal maps, and some other goodies

I've also recently added voxel raymarching as an alternative renderer, along with a fun physics simulation :)

Show HN: Consol3 – A 3D engine for the terminal that executes on the CPU
github.com

Re: Show HN: Consol3 – A 3D engine for the terminal that executes on the CPU

#8
post #7
post #6

This is so unbelievably awesome! Projects like these are why I browse HN

And it has shaders. Can't get any cooler

What am I missing here? Why is it cool to not use the fast GPU and instead do everything slow in a software renderer on the CPU? It surely is interesting to do it for the sake of it, but are there any practical use cases?

Re: Show HN: Consol3 – A 3D engine for the terminal that executes on the CPU

#9
post #8
post #7

Earlier quoted context omitted.

And it has shaders. Can't get any cooler

What am I missing here? Why is it cool to not use the fast GPU and instead do everything slow in a software renderer on the CPU? It surely is interesting to do it for the sake of it, but are there any practical use cases?

Running it remotely on a cloud instance? Or on any machine without a GPU.

Re: Show HN: Consol3 – A 3D engine for the terminal that executes on the CPU

#10
post #8
post #7

Earlier quoted context omitted.

And it has shaders. Can't get any cooler

What am I missing here? Why is it cool to not use the fast GPU and instead do everything slow in a software renderer on the CPU? It surely is interesting to do it for the sake of it, but are there any practical use cases?

It's much easier to debug. And CPUs are actually fast enough to do real-time rendering of simple scenes. Because writing for the CPU is so different, and so much easier than writing for the GPU, a pure software stack allows you to explore new ideas.
Post reply on HN