Timeline for Checking game objective status in efficient way on each update call
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2013 at 1:21 | comment | added | Malakai | You should not assume that the person who asks a question is less intelligent/knowledgeable than you are. This thing only happens to average programmers who think they are "good". Look at the answer of Vaughan Hilts. This is how you help. | |
| Mar 26, 2013 at 22:12 | comment | added | AB. | How about you profile your code first instead of preaching the nonsence of exorbitant cost of 20 ifs (branch misses of course) ? | |
| Mar 26, 2013 at 15:44 | comment | added | Malakai | It DOES matter. I have been testing my game on LG Optimus GT540. It runs on Android 1.6. One more calculation matters. You can run a nice particle effect on it. You can rotate a 3d model on it. But a game is not made just to display a cool particle effect, or cool animated hud layer, or a cool flying hero with a gun. A game is composed of all these and many more. So, yes it matters. | |
| Mar 26, 2013 at 15:17 | comment | added | AB. | It doesn't matter. 1.5 devices are more than enough. You need to iterate. The cost is low. | |
| Mar 26, 2013 at 13:35 | comment | added | Malakai | I know it's 2013 and I know there are still 1.5 Android devices that people use. | |
| Mar 26, 2013 at 13:28 | history | answered | AB. | CC BY-SA 3.0 |