Hello everyone! Welcome to Debugging Diaries!
See the Live here:
3 Likes
Now after completing the Debugging Diaries Lesson I have learned to peek values so I can just see the numbers. This helps me work on a old Pinball project. Thanks for the great Lessons. Have a great Week everyone :o)
2 Likes
From today’s learning, I’ve learned a huge things such as:
Testing your visual script as you go is crucial to catch bugs early on and save time in the long run.
Breaking down your notes into small modules and testing each part individually can help locate the source of the bug more efficiently.
Understanding execution order is essential, and using subgraphs like “Wait for Seconds” can help control timing and sequencing in your effects.
Testing on different devices and optimizing UI is important to ensure your effect works well for all users.
Performance optimization is vital to avoid rejections, so be mindful of asset size, avoid excessive effects, and follow technical optimization guidelines.
Some of Qinyu’s approaches has already been implemented by me in some of my projects like using ‘do once’, ‘wait for seconds’, and ‘peek’ (this one is a life saver).
Here’s my implementation by using ‘do once’ when I start a game effect, so the user won’t tap screen continuously
btw check out my latest effect called Chimp vs You on TikTok
1 Like
I managed to finish my version by adding a timer and some startup and game over screens that I made myself supported with artificial intelligence. I also did a resizing of the icons.
This is the game:
Thought I would throw my super basic tip into debugging diaries in case someone down the road finds it useful.
This debugging tip is more of a handy trick I use to quickly test if a signal is being sent correctly. I often attach a blank image object at the end of my code and set its visibility to change if the logic executes correctly. It’s a simple visual way to ensure everything is running smoothly.
1 Like