ecker
-
https://git.ecker.tech/ aims to provide a place to share my efforts while maintaining true ownership of my code, as I do not trust GitHub.
XMR: 4B9TQdkAkBFYrbj5ztvTx89e5LpucPeTSPzemCihdDi9EBnx7btn8RDNZTBz2zihWsjMnDkzn5As1LU6gLv3KQy8BLsZ8SG
- Joined on
2022-10-10
Block a user
fff258917e
fixed dynamic/static split BVHs because of some dumb assumptions, fixed contacts being order dependent from not flipping the normals for '*Mesh' contacts generated, some other things (scenes don't lag to high hell but my props and doors aren't collidable...)
00b61c1c22
fixed dynamic/static split BVHs because of some dumb assumptions, fixed contacts being order dependent from not flipping the normals for '*Mesh' contacts generated, some other things (scenes don't lag to high hell but my props and doors aren't collidable...)
e1d824a5ac
further ironing out the underlying math lib / SIMD intrinsics (theoretically now if -march=native binaries are shipped they shouldn't crash through multi-versioning)
c87eac5e05
bigly refractors vector/quaternion/matrix all around (and beginning to ensure SIMD optimizations for physics)
a66f56ad9f
refractor to try and minimize differences between reactphysics and internal physics engine (that i really need to optimize now), reverted some things with the graph system to get it to work again on scenes with more than one mesh (because for some reason instance IDs need to be global and i cant for the life of me figure out how to properly remap them)
0ce6b57867
fixes because i neglected to test the uf::graph changes on other scenes (just to realize i really need to optimize the internal physics system...)
3b5db2c32c
finally it works (to-do: support for reading from fp16/bf16/quantized vertex data, some method of emitting contact information to the colliding bodies, collision masking, per-body gravity, fix sinking occuring when using the collider offset, some other things)
461894741f
using a PSG solver is almost stable sans some weird oddities, would love to use a block solver but the current one is flawed
40da94c422
wasted a week on trying to roll out my own physics system just to be humbled when it almost works but doesn't work well enough (probably a bad solver, will probably revisit it at a later date)
02338bc841
wasted a week being humbled by wanting to cobble together my own physics system to avoid having to sync to/from a different physics system (it's mostly there but the solver is a pain to get right)
65cf3887b7
finally nailed a memory leak because past me made assumptions RP3D cleared the triangle parts on body destruction per the documentation (although I still crash after a while on the DC build from fragmentation at 9MiB consumed......), crammed filetype preference to resolveURI since everything should be using that anyways, some other cruft I forget trying to nail down this memory leak
532c4054b6
audio cleanup or something (because it's lagging the dreamcast build when emitting sounds)
c5f0ec69b2
crammed linux support and spent several hours trying to hunt down static initialization demons just for my .so lib to be made wrong
329dd5ef4d
crammed linux support and spent several hours trying to hunt down static initialization demons just for my .so lib to be made wrong
0fb2e3b750
removed storing model/prev-model matricies and color for every instance entry (by adding another indirection via objectID...), fixed rt pipeline because the BLAS's weren't being generated
a099c562a2
remove the weird redundancy of having drawcommands + instances + primitives (which store draw commands and instances) (although i should probably do the opposite to not tie instances to draw commands)