Hello, fellow Clickers,
I have searched through this forum far and wide, didn't find a solution for this.
My game is a pixelated agility game that requires the use of both arrows and WASD for controls at the same time. Includes fast button pressing (possibly many buttons at once) for shooting insane numbers of generated enemies. It has so far about 160 events in total, still a prototype. Normal gameplay includes 60 objects on screen tops so far.
I work on a CTF2.5, Windows 8.1 ( ), laptop. Except for Ultimate Fullscreen, I use no other extensions here for now.
At some point I started encountering random sound system crashes, while the application continues as usual, no lags or stutters. In other words - on some random moment of the game all the sounds are cut, turn completely quiet, no new sound is played anymore. Sometimes this block happens after a few seconds, sometimes after a few minutes, it just stops and in 95% of cases never to come back (if it does, it usually comes back only for a very short while only to get crashed again). "Restart level" action does not help, I need to close and restart the runtime completely for the sound to "be there" again.
I used .ogg , also did a try with .wav files, without success. At first I thought it's a "regular" issue of too many sounds at the same time, some unfortunate sound events looping hundreds of sounds. I went a very long way to eliminate all possible occurences that could have done that. Then I started eliminating sounds in general to narrow down the problem. Finally, only one sound was left (the background music), which kept crashing randomily, too! I came to a realisation that maybe the sound bug is a consequence of something not neccesarily sound-based.
So far, all sounds except for the background music looped on the start of the level eliminated, I noticed that while I play with one hand only (arrows), against the general idea of the game, the crashes (according to my tests) do not happen, which might suggest the number of buttons smashed (events launched) may be part of the problem. Every button press starts a fast loop, there are 4 fast loops in total for recognising shot collisions, nothing too complicated. It's difficult to test it, as the crashes come up pretty randomly, but usually in a few minutes of gameplay.
Could you, please, help me out? Any technical perspectives on the matter?
Thank you for your time!