You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supporting Fixed32 is an interesting idea and could be beneficial in scenarios where memory efficiency is crucial, such as mobile applications or games. Currently, FixedMathSharp leverages Fixed64 (the underlying value is a long, which is a 64-bit value, hence the name) to ensure high precision and a larger range for computations. I built this specifically for a deterministic physics engine.
Adding Fixed32 would require careful consideration of range and precision trade-offs, as a Fixed32 would inherently have a smaller range and lower precision than Fixed64. I’d need to rework some of the logic and rounding methods to suit the 32-bit format while maintaining accuracy.
I'm open to exploring Fixed32 support if there’s enough interest. If you or the community would benefit from this, please feel free to reach out or contribute ideas. I’d love to hear more about specific use cases where Fixed32 would be a valuable addition!
Is there a plan to support fixed32?
The text was updated successfully, but these errors were encountered: