In core example 24, we're using gen-mesh-cube because gen-mesh-cylinder gave me floating point errors. This also occurred with some of the other functions, like gen-mesh-cone, gen-mesh-sphere, and gen-mesh-torus, run directly via claylib/ll.
At one point I thought maybe Autowrap was using a double float for pi while Raylib was expecting a single float. After spending more time than I care to admit figuring out how to redefine pi, I was unable to prove this -- most likely a red herring but I couldn't completely rule it out either.
Curious whether it works for you, @mjkalyan. To test, all you have to do is replace the gen-mesh-cube call in core example 24 with a gen-mesh-cylinder call.
In core example 24, we're using
gen-mesh-cube
becausegen-mesh-cylinder
gave me floating point errors. This also occurred with some of the other functions, likegen-mesh-cone
,gen-mesh-sphere
, andgen-mesh-torus
, run directly viaclaylib/ll
.At one point I thought maybe Autowrap was using a double float for pi while Raylib was expecting a single float. After spending more time than I care to admit figuring out how to redefine pi, I was unable to prove this -- most likely a red herring but I couldn't completely rule it out either.
Curious whether it works for you, @mjkalyan. To test, all you have to do is replace the
gen-mesh-cube
call in core example 24 with agen-mesh-cylinder
call.