FreeGameDev

Hello, everyone!

As I was working on my game development framework, I decided to decouple my math sources into a library itself.

It's an alternative to GLM (C++ library) and more complete than linmath.h (another C library).

It's licensed under ZLIB

Github: https://github.com/ferreiradaselva/mathc

Deleted.

> It's strange that you use vec for both 2d and 3d, seems wasteful.

It's actually very common to use a single structure to represent all the type of vectors. Using the same structures for all kind of vectors allow more flexibility with OpenGL operations. For example, if you are making a 2D game, you will often use the functions vector2_*(), but you still have the Z component to use to specify depth.

> It would also be great if you rewrote it in C++ and templates

I don't have intentions to support C++. There's already a complete math library for C++ (https://github.com/g-truc/glm). Afik, this library I made is the most complete there is for C.

> so people could use double instead of float.

Is there any specific reason for the need of doubles? Physics can run nicely with float (e.g. Chipmunk2D) and everything sent to the rendering pipeline will be converted to float, anyway.

This is remarkable, If it was in c++ I wouldn't use it btw, this library gave me a lot of help, thanks mate!

Deleted.

By the way, most of the game engines uses floating point arithmetic, mainly increasing performances, including my own physics engine, Chipmunk and many other alternatives, and they do work very fine and reliable, as for doubles, it could cause issues in performances is many hardware, and mostly used for real life simulations, which isn't the case in games for that precision to be needed.

imaZighen {l Wrote}:This is remarkable, If it was in c++ I wouldn't use it btw, this library gave me a lot of help, thanks mate!

Lyberta {l Wrote}:Float tends to have a very small precision when you start working with larger numbers.

For the reason @imaZighen mentioned, double isn't that suitable for games (the only thing I can think where it's really useful is for time precision). As for the imprecision of large numbers, it's actually a good practice to divide the world in chunks and translate the objects back to the chunk [0.0f, 0.0f, 0.0f]. For example, if the nearest object to the origin is [600.0f, 500.0f, 300.0f], translate everything with [-600.0f, -500.0f, -300.0f]. And use scale whenever you can, instead of large numbers.

If you were using double, your physics would work correctly with lager numbers, but the rendering still would shake, as the double values would be converted to float.

Deleted.

We are not saying it's impossible, it's just bloody awful for games. And thought you can have a define for the floats to be changed to doubles, not that hard. Just like Chipmunk 2D and ODE and many others, but whose going to use it, thanks, peace.

@ferriera btw check your mail please, thanks.