After 5 hours of fixing a none existant bug I have finally found the bug that bugged up my movement code. I search my code countless times and revised and cleaned it entirly. No reason for the bug inside. After using the console for debugging I found that pygames collision detection only worked every third frame. \u00a0Some other image related modules messed up as well. I could not find a solution to this, so after all those hours I finally decided to move on and be able to release at least something, be it buggy or not. I finally added the time related events and as soon as I wrote the last character of Clock() it stuck me like a lightning. NO WAY o_o ! Could it Be O_O?! \u00a0I set the framerate to 60 and started the programm. EVERYTHING WORKED FINE! I just wasted 5 hours on a non existing bug, revising and rewriting all of the 400 lines I already had. Added 20 lines here, 20 lines there and removed them again because they fixed nothing.<\/p>\n
But at the \u00a0same time I was really happy to have found the bug. It all had its upsides as well. My codebase is now perfectly tidy, dense and clean.<\/p>\n
I will post some pics as soon as the first part of the gameplay is finished.<\/p>\n
Good luck to all of you, especially to all the others struggeling with bugs \ud83d\ude09<\/p>","time":"August 26th, 2012 7:24 am","title":"Trial and Error or: The story of how I hunted a fatal bug that wasn\u2019t one"}