Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(+1)

Nice story and great sound effects!

It seems that there is a bug somewhere in linux version - sometimes it freezes with the following message:

debugger invoked on a SDL2-MIXER:SDL-MIXER-ERROR in thread
#<THREAD tid=10152 "SDL2 Main Thread" RUNNING {1005D10003}>:
  SDL Error (-1): No free channels available
The current thread is not at the foreground,
SB-THREAD:RELEASE-FOREGROUND has to be called in #<SB-THREAD:THREAD tid=10150 "main thread" RUNNING {1005D100E3}>
for this thread to enter the debugger.

Ah ha! I had exactly the same error on my Linux box, whenever I pressed my arrow keys quickly.

Actually we don’t need to press the arrow keys so frequently, since the player in this game has a auto-moving feature, it will move forward automatically and stop at the first intersection.

It is due to my clumsy code that every time the player presses the arrow key, a new SDL2_Mixer channel will be needed, so if one presses quickly enough, it will run out of channels, but if one presses slowly or not so frequently, the SDL2_Mixer channel will be automatically released in time.

Thank you for pasting the error, good catch!

I was thinking that I could get away with this without being caught, shame to me.

;-P

So it seems to be a bug in CALM itself, right? Seems like a great tool by the way!

Have you thought about using harmony instead of sdl2-mixer? It seems to be more flexible.

So it seems to be a bug in CALM itself, right?

It could be defined as that, and it could also be defined as the problem of the game developer, like Steve Jobs blamed the iPhone 4 users “doing it wrong” for the iPhone 4 antenna issue.

Who should we blame? Anyway, they are all me. T_T

Harmony seems great, I’m gonna check it later. The current version of CALM is in its very early stage, the reason of using SDL2_Mixer is that it just worked and could be compiled to the WebAssembly.

(+1)

I see :) Have fun developing CALM further!

Actually, this bug exists in all the desktop version.