4 ms·
Yes, best practises were more what I was looking for especially since I'm a noob at gamedev. Having lots of code samples does help to address that however. One
by jiggy2011 14y ago
Yes, best practises were more what I was looking for especially since I'm a noob at gamedev. Having lots of code samples does help to address that however.
One thing I noticed when comparing libGDX to XNA was that the basic game framework that you can extend from in XNA has 2 "tick" methods in it's main class, update() and render() (or something to that effect). Also the Java library "slick2D" follows this convention. This makes it simple to seperate out rendering code from logic updating code.
LibGDX on the other hand only provides a render() method which confused me a little. Should my render() method be handling logic updates? Should it call another method that does, but check time deltas on each loop to decide whether it should run, or should game logic happen in it's own thread?
- badlogic 14y agomoat people put their logic updates in render, others have a separate thread. we don't want to force any architecure on anyone as libgdx is a framework, not an engine. this is getting way to off-topic. i suggest you register at our forums where you can get input from lots of knowledgeable people on such matters :)