Fun stuff with unigi and haloo3d
Go to file
2024-09-07 00:38:59 -04:00
haloo3d@317393d033 Brought in changes needed for ps2 2024-09-07 00:38:59 -04:00
old Small cleanup + fixes 2024-08-26 01:28:02 -04:00
resources No external files needed for maze 2024-09-06 21:18:31 -04:00
unigi New library stuff 2024-09-06 20:01:11 -04:00
.gitignore Paintings ALMOST worked 2024-08-21 23:52:01 -04:00
.gitmodules Added submodules 2024-08-12 20:34:22 -04:00
camera.h Nearly working freecam 2024-08-13 02:08:21 -04:00
ecs2.h Maze complete v1 2024-08-23 23:33:15 -04:00
keys.h Nearly working freecam 2024-08-13 02:08:21 -04:00
LICENSE License 2024-08-12 21:54:25 -04:00
Makefile Somewhat working maze thing 2024-08-18 04:33:01 -04:00
maze_ecstypes.h Maze complete v1 2024-08-23 23:33:15 -04:00
maze_todo.txt Very fast fb fill 2024-08-17 18:11:00 -04:00
maze.c Brought in changes needed for ps2 2024-09-07 00:38:59 -04:00
README.md Update README.md 2024-08-24 05:09:14 +00:00
scene_freecam.c Small cleanup + fixes 2024-08-26 01:28:02 -04:00
scene.c Small cleanup + fixes 2024-08-26 01:28:02 -04:00

3D Toys

Everything in here is a little sample program or otherwise which uses haloo3d and unigi. It's all software rendered, but you'll need to get sdl1 so it can render to screen.

The libraries required are set as submodules, so you can pull them when cloning with:

git clone --recurse-submodules https://git.lumen.sh/haloopdy/3dtoys.git

Or if you already cloned, you can do this after the fact:

git submodule update --init

Then, to build any example, just do make name.exe. For example, to build maze.c, you would do

make maze.exe
./maze.exe

If you're having trouble building, you can try to force past the warnings (they're usually nothing):

make FORCE=1 maze.exe

Unigi

For the time being, unigi is designed such that it expects you to compile your entire program as a single unit. This means you must include all your .c files into the main file, in the right order.

This may change in the future.

Unigi expects some kind of graphics backend to run. In this case, our samples use SDL1, so you'll need to get that.

Haloo3d

You can compile haloo3d using the makefile provided in the library repo, or include the .h and .c files directly into the main translation unit like unigi currently expects.

For these samples, they expect you to build the haloo3d_full.a library using make full in the haloo3d submodule. For convenience, the makefile for the samples assumes you are using the submodule and runs make in there for you.