Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit) (+1)

Hi,
Thanks a lot for letting me know !
I've just uploaded a new version with the missing information.
Can you please try if it works ?

Had the same problem as them but it now works properly on an actual playdate! Thank you, cranking in rhythm to the song is very satisfying lol. If I had any suggestion it would be to make it louder if possible, the song is kind of quiet compared to other things at the same volume on the playdate. Thanks again!

(+2)

Thank you !
You are right, there was a sound problem with the left channel being too low. The problem is fixed now in the latest (1.01) uploaded version.

Thanks for updating it so quickly! I can also confirm that it's now fixed, and it's great! :) Thanks for making such a fun little thing to mess around with.

(1 edit)

Thank you :)

(1 edit)

I just downloaded it today and I’m getting this issue.

EDIT: I fixed it by manually editing the pdxinfo to have the “buildNumber” value.

(1 edit) (+1)

Thank you for reporting the problem and sorry for that!

(i made a fix in  1.02 version if needed)

This field did not seem mandatory, but apparently it was :)

Fyi, the system seems to lock /freeze the whole device (requiring holding down the power button to crash reboot) if the game is launched with the crank holstered (I assume you’re trying to read a value and get null or something).

(2 edits) (+1)

Thank you.

Here are the limits of not having the real device yet :)

I've just added in version 1.03 a check preventing to read the crank values if the crank is docked. 

Hopefully this will fix the issue !

Firstly, love the new home screen animation.

Secondly, no - still broken - It runs (can push the button for instructions, but then crashes when you take the crank out. I’m seeing a “run loop stalled for more than 10 seconds” on screen.

(1 edit) (+1)

Thank you.

I'm clueless on what is happening. I suspect a bug in the SDK, but without a device it is hard to investigate.

I've asked for some help in the dev forum. I'll let you know if I make any progress !

(+1)

Hi, latest 1.05 version should fix the issue ! 🙂