The Forge sounds pretty great but there does not seem to be much in the way of documentation.
I don't even see simple "How to compile" or build instructions. Which seems like a good place to start.
The description talks about it being like "Legos" where you can use the different parts of the system as needed. So does that mean it can be built in sections and integrated into other projects pi
I wish doxygen documents is hosted online somewhere, it's kinda annoying just to clone and make my own copy to read documentations.
Anyway, this framework really helps me to make my own game engine.
I would like a function that verifies that all naively using the document (only checking indices against -1) will not cause a buffer overrun; i tried writing this but i just started learning the gltf format this week and got confused.
I'm also pretty sure that Animation::Channel::Target::Path has only 4 valid values in the spec, and should be an enum, not a string, but maybe you know somethin
The current demo project shows off the features of the project well, but it's probably better to have some kind of written guide to get developers up to speed.
Using ISPC, Microsofts nBodyGravity DX12 sample has been modified to provide a fully vectorized and fully threaded CPU based backend for the compute part of the workload.
The Forge sounds pretty great but there does not seem to be much in the way of documentation.
I don't even see simple "How to compile" or build instructions. Which seems like a good place to start.
The description talks about it being like "Legos" where you can use the different parts of the system as needed. So does that mean it can be built in sections and integrated into other projects pi