It can also show you more advanced information, such as the state of your textures and surfaces, current graphics options, values of buffers, etc. GameMaker's debugger allows you to run your code line by line, checking the values of every variable and their changes along the way. This is fine for quickly debugging a small feature, but when you have many moving parts working together, generating these messages can quickly get out of hand. The first solution that comes to mind is to check the values of variables, or the results of conditional statements, by using debug messages or drawing text to the screen. Then we go back to the code and look at it for 20 minutes thinking it should work. We've all been in that situation where we write code, run the game, and nothing works like expected. The Game Is Paused in the Section I Want.Reading the official documentation is also a great way to learn more about it after you've read this article. It's a good idea for you to experiment with all these tools yourself and figure out ways to make your debugging experience easier and better. I will try to cover as much as possible on these tools, but I will most likely miss a few points, given it is such an extensive topic. In this post, I will explain my process when debugging my games, and some tips to find bugs quickly and identify bottlenecks in your game. Written in January 2018 by Alejandro Hitti, a video game programmer and designer from Venezuela.
0 Comments
Leave a Reply. |