![]() This sucks for both terminology and coding. It's already somewhat used in upstream and fully cleaned in ()Ĭode behind actors: The softbody actors (I'll call them such from now on) comprise of 2 structs: `class Beam` and ancestor `struct rig_t`. Let's refer to simulated softbody objects as 'Actors' instead. We employ a threadpool but make limited use of it. But for historical reasons, some physics calculations run on variable timestep (time since last frame). ![]() We accumulate time spent rendering and then advance physics. Our physics use Euler integration and run on 2khz frequency. But for historical reasons, the parsed object is not reused. When loading an actor ( Truck file format ()) we load+parse the file first into `RigDef::File` object, then spawn from it. Our main simulation loop lives in `RoRFrameListener::EnterSimulationLoop()` and calls OGRE's 'renderOneFrame()' which invokes `frameStarted()` callback (same thread). We use OGRE 3D () for rendering - we init engine at startup and shut down on exit. Our entry point is straightforward 'main()' function - it performs inits and then enters game state loop governed by GVar 'app_state' We embrace global variables via 'GVar' mechanism inspired by Quake's cvars - see file 'Application.h' and older 'GlobalEnvironment.h' However, some previous authors seem to have loved OOP while disregarding common sense. RoR isn't OOP, it's structured and just makes use of objects. Hopefully I'll compose something meaningful to put to our Doxygen docs. ![]() ** split to multiple posts because of character limit **Įarly draft, just notes from the top of my head. The reason to write it down right here right now is this excellent contribution from a new developer This is an entry point for new RoR developers - it describes how RoR currently works, why it sucks and what I'd like to do about it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |