Timeline for How can I improve the performance of this rendering code?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2013 at 0:45 | comment | added | BotskoNet | This answer was essentially correct, in the sense that the code was creating the VBO and loading the data each time. By exploding the idea of the buffer IDs more, I realized they work like the display lists in that I don't need to re-build the VBO every render call. By building the VBO data when it changes, and just binding that ID each render call, performance is pretty much back to 60fps. It drops a little now and then for an unknown reason, but using the buffer ID properly worked wonders. | |
| Dec 8, 2013 at 0:43 | vote | accept | BotskoNet | ||
| Dec 7, 2013 at 22:44 | comment | added | BotskoNet | Currently, each chunk is just rendered once, and if a player makes a block change in that chunk, we clear the cache and re-render the chunk. We only then just transform what the player is looking at as they walk around. | |
| Dec 7, 2013 at 21:46 | history | answered | Lucas | CC BY-SA 3.0 |