Closed jordanbleu closed 1 year ago
Thanks for reporting this! I'm not sure what's happening based on your description, and unfortunately I have not been able to reproduce this (VSCode 1.75.1, macOS Ventura 13.2.1, Playdate SDK 1.13.1).
I have a few more questions:
You could trying using the tasks.json
and launch.json
from the basic configuration example instead of using the "Debug file in Playdate Simulator" button. That button is intended to help you get up and running quickly, but I would expect the dedicated task/launch configuration to be a bit more stable.
Also, is there any logging information in the VSCode task console? You should see something like this:
* Executing task: Playdate: Build
Compiling...
> "/Users/me/Developer/PlaydateSDK/bin/pdc" --main -sdkpath "/Users/me/Developer/PlaydateSDK" "/Users/me/Developer/MyGame/source/main.lua" "/Users/me/Developer/MyGame/main.pdx"
* Terminal will be reused by tasks, press any key to close it.
* Executing task: Playdate: Run
Starting Playdate Simulator...
> /usr/bin/open -a "/Users/me/Developer/PlaydateSDK/bin/Playdate Simulator.app"
* Terminal will be reused by tasks, press any key to close it.
I think i may have found a reliable fix though, it seems that if I attach my debugger to some other process it fixes the issue for some reason.
Closing because I cannot reproduce this issue.
It works perfectly fine, but once in a while I'll go click the 'debug file in playdate simulator" and nothing happens at all. Any tips on fixing that? Re-installing doesn't seem to fix the issue, nor does restarting. I'm on MacOS, VSCode v1.69.0. I can build and run the file just fine in the PlayDate SDK CLI.