go3d alternatives and similar packages
Based on the "Game Development" category.
Alternatively, view go3d alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
-
Pitaya
Scalable game server framework with clustering support and client libraries for iOS, Android, Unity and others through the C SDK. -
-
-
-
-
-
-
-
Azul3D
DISCONTINUED. Azul3D - A 3D game engine written in Go! [GET https://api.github.com/repos/azul3d/engine: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository] -
-
-
-
-
tile
Tile is a 2D grid engine, built with data and cache friendly ways, includes pathfinding and observers. -
-
-
-
-
-
-
InfluxDB – Built for High-Performance Time Series Workloads
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of go3d or a related project?
README
Package go3d is a performance oriented vector and matrix math package for 2D and 3D graphics.
Every type has its own sub-package and is named T. So vec3.T is the 3D vector type. For every vector and matrix type there is a String() method and a Parse() function. Besides methods of T there are also functions in the packages, like vec3.Dot(a, b).
Packages under the float64 directory are using float64 values instead of float32.
Matrices are organized as arrays of columns which is also the way OpenGL expects matrices. DirectX expects "arrays of rows" matrices, use the Transpose() to convert.
Methods that don't return a specific value, return a pointer to the struct to allow method call chaining.
Example:
a := vec3.Zero
b := vec3.UnitX
a.Add(&b).Scale(5)
Method names in the past tense return a copy of the struct instead of a pointer to it.
Example:
a := vec3.UnitX
b := a.Scaled(5) // a still equals vec3.UnitX
Note that the package is designed for performance over usability where necessary. This is the reason why many arguments are passed by pointer reference instead of by value. Sticking either to passing and returning everything by value or by pointer would lead to a nicer API, but it would be slower as demonstrated in mat4/mat4_test.go
cd mat4
go test -bench=BenchmarkMulAddVec4_PassBy*
Documentation: https://pkg.go.dev/github.com/ungerik/go3d