Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Modular Play

A modular synth playground for Playdate · By Orllewin

Bug reports Sticky

A topic by Orllewin created Oct 29, 2023 Views: 2,057 Replies: 68
Viewing posts 21 to 27 of 27 · Previous page · First page

My app (version 0.0.17 Alpha) more often than not ends up crashing and causing the playdate to automatically shut down and restart. Seems to happen most often when I'm using (connecting to or manipulating pots) on the 4-channel output modules, but I've had it happen otherwise. I've tried deleting the app and doing a fresh download after the update to 2.2, hoping it was related to that issue mentioned in your recent post when 2.2. came out. The problem persists, unfortunately. Here are the latest few entries on my device's error log, in case this helps in diagnosing the problem(s): 

2024/02/05 18:31:12

/Games/User/user.100948.orllewin.playdate.modularplayer.pdx

CoracleViews/rotary_encoder.lua:96: bad argument #1 to 'setImage' (playdate.graphics.image expected, got no value)

stack traceback:

[C]: in method 'setImage'

CoracleViews/rotary_encoder.lua:96: in method 'setValue'

Modules/Synths/OrlSynth/synth_mod.lua:336: in method 'turn'

Modules/module_manager.lua:233: in method 'handleCrankTurn'

Interface/modular_screen.lua:320: in function <Interface/modular_screen.lua:301>

2024/02/05 18:32:06

/Games/User/user.100948.orllewin.playdate.modularplayer.pdx

CoracleViews/rotary_encoder.lua:96: bad argument #1 to 'setImage' (playdate.graphics.image expected, got no value)

stack traceback:

[C]: in method 'setImage'

CoracleViews/rotary_encoder.lua:96: in method 'setValue'

Modules/Synths/WavetableSynth2D/wavetable_synth2d_mod.lua:208: in method 'turn'

Modules/module_manager.lua:233: in method 'handleCrankTurn'

Interface/modular_screen.lua:320: in function <Interface/modular_screen.lua:301>

2024/02/05 18:35:07

/Games/User/user.100948.orllewin.playdate.modularplay.pdx

CoracleViews/rotary_encoder.lua:96: bad argument #1 to 'setImage' (playdate.graphics.image expected, got no value)

stack traceback:

[C]: in method 'setImage'

CoracleViews/rotary_encoder.lua:96: in method 'setValue'

Modules/Synths/WavetableSynth/wavetable_synth_mod.lua:149: in method 'redrawBackground'

Modules/Synths/WavetableSynth/wavetable_synth_mod.lua:260: in method 'invalidate'

Modules/module_manager.lua:215: in method 'invalidate'

Modules/module_manager.lua:178: in method 'move'

Interface/modular_screen.lua:557: in method 'move'

Interface/modular_screen.lua:616: in method 'draw'

main.lua:227: in function <main.lua:220>


2024/02/08 11:10:13

/Games/User/user.100948.orllewin.playdate.modularplayer.pdx

Modules/Mixers/Mixer4Sliders/mix4sliders_component.lua:35: attempt to index a nil value
stack traceback:
Modules/Mixers/Mixer4Sliders/mix4sliders_component.lua:35: in method 'setPan'

Modules/Mixers/Mixer4Sliders/mix4sliders_mod.lua:268: in method 'turn'

Modules/module_manager.lua:233: in method 'handleCrankTurn'

Interface/modular_screen.lua:320: in function <Interface/modular_screen.lua:301>

Developer

Thanks for the detailed report, that makes fixing bugs so much easier. I don’t get the constant crashes you report though, the buggiest area of the code is removing modules. That can create a bad state that makes everything subsequently misbehave. I fix the issues when I find them so it should get more and more stable. I’ll look through the crash reports you’ve posted and see what I can do.

(1 edit)

Hey, I get prettyconsistent crashes on the new firmware. It's to the point that I can't really sink in and create anything at all. Would really love a fix, was looking forward to getting into this. After seeing the above post isn't really answered I'm a bit worried-- do you plan to address this?

Developer

of course I’ll address it. Give me time, I’m a sole developer and this is a MASSIVE project compared to most Playdate software. I’ve just got the latest OS update will see how it performs over the next few days,

Of course, I really appreciate the work you're doing, and look forward to sinking in when it doesn't crash on me. I don't know how to access the crash report the other user posted, but can send them if it's simple enough to tell me how.

Didn't mean to sound rushy, just saw the last post wasn't replied to. Gld to hear you're workign on the project still, I think it's amazing

Another bug to report, causing a crash. Repeatable by following these steps: 

Add then connect these modules: Clock, generative std sequencer, orl synth, 4-channel basic output. Then I connect another clock output to the top right input of the synth, and while turning the crank on top of the (hidden until turned) pot on the top right of the synth (just to the left of the input I just connected), it crashes. I’ll upload the detailed bug report and keep posting additional glitches. Because literally every time I try to use this app, I get a crash. And I’m not removing modules ever. 

Developer

Fixed in 0.1.0 - these are all the same bug, that input requires a value input 0.0 to 1.0, so the bug was clock sources shouldn’t have been able to connect to that socket

next one: follow these steps to get crash and play date restart:

Add clock, generative rnd., wavetable synth, 4-channel output. Connect generative rnd out to wave table in, synth out to mixer in; then clock out to the top right input of the synth, then try to turn one of the pots w the crank on the wave table synth, and it crashes. 

Developer

Fixed in 0.1.0 (coming soon)

next one: follow these steps for crash: 

Add bubble chamber, add wavetable. Connect bubble chamber to the top right input of wave table, then turn the crank and it crashes. 

Developer

Fixed in next release 0.1.0

Anyone else able to replicate these crashes? @Orllewin, have you been able to review the crash report I sent a couple months ago?

Developer

I don’t get the constant crashes you reported - is that still happening?

Developer

ps. working through the above now.

Developer

Hey all, new release coming in the next week or so with lots of fixes, but if you have a recurring problem please join the new Discord Server and I’ll try and fix them 1:1 instead of going back and forth here or on email: https://discord.gg/7yVR2cWV

The Discord link is invalid. I'm curious about the new release -- I've been waiting to jump in and learn this once the update is pushed, though I may just give it a go this weekend regardless!

Viewing posts 21 to 27 of 27 · Previous page · First page