2D Physics Engine Help
#5
(06-12-2023, 04:11 PM)madscijr Wrote:
(06-12-2023, 03:16 PM)TerryRitchie Wrote: I figured the process of converting the Java OOP code to functions and procedures would be fairly straight forward ... not so much.
Yikes! I would recommend sticking with procedural code, if you can find it. Regular C is procedural, and would surely be easier to translate to procedural QB64PE.
Yeah. Box2D is C++. So, it might be problematic to make a binding for QB64-PE.

There is Chipmunk2D that is a plain ANSI C 2D physics library.
Then there is also the tiny single header Physac that I am planning to write a QB64-PE binding for as part of my larger raylib binding library.
Reply


Messages In This Thread
2D Physics Engine Help - by TerryRitchie - 06-12-2023, 03:16 PM
RE: 2D Physics Engine Help - by a740g - 06-12-2023, 03:35 PM
RE: 2D Physics Engine Help - by madscijr - 06-12-2023, 04:11 PM
RE: 2D Physics Engine Help - by Ultraman - 06-12-2023, 04:30 PM
RE: 2D Physics Engine Help - by a740g - 06-12-2023, 05:22 PM
RE: 2D Physics Engine Help - by justsomeguy - 06-12-2023, 09:34 PM
RE: 2D Physics Engine Help - by justsomeguy - 06-12-2023, 09:36 PM
RE: 2D Physics Engine Help - by TerryRitchie - 06-16-2023, 02:25 PM
RE: 2D Physics Engine Help - by Kernelpanic - 06-12-2023, 11:11 PM
RE: 2D Physics Engine Help - by Sprezzo - 06-13-2023, 02:13 AM
RE: 2D Physics Engine Help - by justsomeguy - 06-15-2023, 03:43 AM
RE: 2D Physics Engine Help - by TerryRitchie - 06-15-2023, 05:08 AM



Users browsing this thread: 6 Guest(s)