I seem to have found a weird bug. Normally sfx(-1, -2) will stop sfx on all channels, but if it is triggered by a menuitem callback, it doesn't work; in that case only explicitly stopping sfx on each channel works

to reproduce, enter some notes on sfx 8 (so you can hear when playback stops), then use this code and compare the behavior of the two menu items:

function stop_all_sfx_short()
  sfx(-1, -2)
end

function stop_all_sfx_long()
  for i = 0, 3 do
    sfx(-1, i)
  end
end

function _init()
  menuitem(1, 'stop sfx (-2)', stop_all_sfx_short)
  menuitem(2, 'stop sfx (long)', stop_all_sfx_long)

  sfx(8)
end

function _update()
end

function _draw()
end

In the web player here on the BBS which currently says it's version 0.2.1, it appears print() now displays numbers as hex:

EDIT: oh wow I didn't realize v0.2.1 was out for real and not just in the BBS web version; I downloaded it and tried running the same cart (#xmasfish) and figured out how to reproduce it so I have corrected the title and description since my first report wrongly said the issue was with tostr()

as you can see here, it only displays as hex when x,y arguments are given to print():

btnp seems to completely stop working iff _update60 is used instead of the normal _update

to reproduce:

1. run the program below
2. press Esc
3. type some sort of statement (for some reason the bug only occurs if you type something before typing resume) e.g. ?"hello"
4. type resume
5. push or hold down the button (O)

expected: "pushed" will appear onscreen
actual: "pushed" no longer appears onscreen

function _update60()
  pushed = btnp(4)
end

function _draw()
  cls()
  if pushed then
    print("pushed", 52, 60, 8)
  end
end

shift + q/w can be used to move up/down in the spritesheet, but when zoomed, the number of sprites it moves by seems to be greater than it should be, i.e. different from how normal q/w (left/right) works when zoomed.

(version 0.2.0i)

@zep seems like something in 0.2.0d (I don't know if it's present in earlier bugfixes of 0.2.0) is wonky with coroutines not updating sometimes or something?? different unpredictable problems are actually happening almost every time I run it; check this out (the dialogue is updated in a coroutine):

so far it seems like most of the time it seems to lead to crashing because variables that are declared inside coroutines are attempted to be referenced by code in the main thread but the variable hasn't been defined yet, which seems to also point to the culprit being coroutines mysteriously not updating every frame like they should (the _update60 method in this cart calls coresume on both of the coroutines every frame; there is one for the dialogue and one for controlling the presentation of the "pins" in each level--both of those are the things that seem to be breaking)

EDIT: okay I've done a bit more testing and there is definitely an issue where a coroutine just starts updating suuuper slowly (seems likely the same issue as is visible in the GIF above) and basically yields in the middle of itself where I don't have any yield statement. For reference, here is some code inside a coroutine where I added debug printh statements:

    repeat
        printh('offset.y:' .. offset.y)
        printh('vy:' .. vy)
        if offset.y >= maxtargetoffset then
            vy = -abs(vy)
        end

        printh('one')
        if targetzipy then
            if vy < 0 and offset.y < targetzipy then
                vy -= .1
            end
        elseif offset.y <= 0 then
            vy = abs(vy)
        end

        printh('two')
        offset.y += vy

        printh('three')
        for _, t in pairs(targets) do
            if not t.isknocked then
                t.y += vy
            end
        end

        printh('four')
        while playercount == 0 do yield() end
        yield()
    until state ~= state_play or all_offscreen(targets)

and here is the console output:

vy:0.09
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
one
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
two
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines
resuming coroutine 1
resuming coroutine 2
done updating coroutines

you can see it's yielding all by itself in the middle of those lines for some reason?? (i.e. the "offset.y:whatever", "vy:0.09", "one", "two", "three", "four" should all be next to each other in the console but they are interrupted by several frames)

after moving (via cut/paste) some SFX in the new super-cool pattern editor view, it seems sometimes it breaks the SFX editor's copy/paste in that when I highlight a few notes, copy them, and try to paste them, it keeps saying a message like "pasted 2 sfx" (instead of "notes") and has no apparent effect (at least not that I can see from within the SFX editor). I haven't found any way to fix it besides reloading the cart.

EDIT: actually I just saw it happen even without using the pattern editor...copy/paste just mysteriously stops working sometimes. it looks like entering some notes makes it start working again though?

The new options menu with controls documentation is so great to have in the binary exports! :)

There just seems to be a small problem where it says there are "0 joysticks" even though I have one plugged in and it is working fine:

(this is in a exported binary player on Linux)

Skills of Detection

Cart File | Forum Post |

	More cartridges by kittenm4ster

More Cartridges [View All]

 

Skills of Detection

by kittenm4ster

Cart #skills_of_detection-1 | 2020-01-02 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

9

i barely finished this in time for the jam, but here it is in its raw form for your enjoyment :)

this was made for Toy Box Jam!

Christmas In The Coral Caves

by kittenm4ster

Cart #xmasfish-1 | 2019-11-27 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

44

This is my entry for the 2019 Advent Calendar =^w^=

Controls

• Up/Down/Left/Right: move
• O: do actions
• X: show/hide inventory

Backstory

My wife Aubrianne wrote a 100% completely original poem which provides the deep lore behind this game:

Credits/Special Thanks

• the amazing cover/intro art was drawn by Aubrianne
• gfx were compressed by zep's PX9​
• fade routine colors were based on this tool by kometbomb

The new (just noticed it changed today) HTML player here on the BBS doesn't seem to be able to keep a steady 60 FPS

I can really feel a bunch of frame jitter when playing Alfonzo's Bowling Challenge and it makes the physics feel very noticeably off

(testing on a MacBook Pro in both Chrome and Firefox. The old exported HTML version (0.1.12c) on itch still runs smoothly on this same computer)

The layout of the clickable buttons (fullscreen, control help, mute, etc.) on the side in the 0.1.12c version of HTML exports appears to have broken in Google Chrome all of the sudden. All of the buttons now appear stacked on top of each other :\

screenshot:

The layout still works in Firefox. I guess Chrome recently changed their interpretation of CSS rules in a way that broke this?

ghosthouse

by kittenm4ster

Cart #ghosthouse-0 | 2019-10-01 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

68

here is my submission for Spooky September 4-Color Jam!

it was a collaboration between me and my wife; she drew all the amazing background art! (using a vector drawing tool I made)

enjoy, and happy september/october/autumntimes! :>

The BBS PICO-8 player is showing up blurry in Chrome on macOS.

(version 76.0.3809.100)

This seems like it might be a bug with Chrome, not this site, but I'm posting it here just in case...

The other puzzling factor is that this started happening all of the sudden, without updating Chrome or anything, e.g. I had the same Chrome session running and at some point this started happening. I then tried restarting my computer and it's still happening.

Screenshot

A Workaround (as a user)

1. Use "inspect element" on the canvas (e.g. push Option + Cmd + I, click the hover tool thing, and then click on the canvas)
2. uncheck image-rendering: pixelated
3. check it again

That fixes it for some reason :| It makes no sense, which makes me think it's Chrome's fault.

(EDIT: actually sometimes unchecking/checking that CSS rule makes the canvas start flickering like crazy...uggh)

More Info

• It works fine on the big TV player on the front page (in macOS Chrome)
• It works fine in HTML exports of carts (in macOS Chrome)
• It works fine in Firefox on macOS
• It works fine in Chrome on Linux
• It works fine in Chrome on Android

anyway this is lame and I hope it magically starts working again soon :p

feature request: a keyboard shortcut to switch tabs/pages of the sprite editor. Something like a Page Up/Down.

(if this already exists, someone please let me know!)

holding W technically works but it takes foreverrrr :)

edit: WHOAA I just discovered you can hold Shift + Q/W to go up/down which is a much better workaround! Still I think if there are tabs which are selectable via mouse, they should also be selectable via keyboard somehow.

The other day I listened to @Gruber's nice transcription of Giant Steps and I felt inspired, so here's another late-1950s jazz standard, this time from the great Dizzy Gillespie: "Con Alma".

My transcription is based on the version from the album Duets (1958) with Dizzy (trumpet) and Sonny Stitt (tenor sax).

I of course didn't have room for all the solos (the recording is over 9 minutes long), so I picked my favorite sections, but otherwise tried to stay faithful to their improvisations. I also made a loop out of the whole thing, so I didn't have to try to make room for the ending :)

It can be quite challenging and awkward trying to mimic the expressive, organic sound (and swung rhythm) of wind instruments with PICO-8's limited beeps and boops, but I'm pretty happy with the result, considering the medium :D

[sfx]

Scenario 1 (correct, IMHO)

1. In the music editor, use the keyboard to select a note in a channel
2. Switch to the SFX editor using the keyboard (Alt + left)

Result: The SFX which the cursor was in (in step 1) is selected in the SFX editor.

Scenario 2 (correct, IMHO)

1. In the music editor, use the keyboard to select a note in a channel
2. Switch to the SFX editor using the mouse (click on the SFX tab)

Result: The SFX which the cursor was in (in step 1) is selected in the SFX editor.

Scenario 3 (correct, IMHO)

1. In the music editor, use the mouse to select a note in a channel
2. Switch to the SFX editor using the keyboard

Result: The SFX which the cursor was in (in step 1) is selected in the SFX editor.

Scenario 4 (bug, IMHO)

1. In the music editor, use the mouse to select a note in a channel
2. Switch to the SFX editor using the mouse (click on the SFX tab)

Result: The SFX which the cursor was in (in step 1) is NOT selected in the SFX editor. It looks like whichever SFX was previously selected in the SFX editor is there...or something. It's not what I expect.

Summary

• If the keyboard is used to select the note in the music editor, that SFX will be selected when switching to the SFX editor regardless of whether keyboard or mouse was used to switch to the editor
• If the mouse is used to select the note in the music editor, that SFX is only selected if switching to the editor with the keyboard, which feels unintuitive/buggy.
• this is in version 0.1.12c

Whereas in PICO-8 v0.1.11 it was possible to run a cart at 60 FPS and get a higher sampling frequency (than at 30 FPS) when querying the value of stat(26) (i.e. number of ticks played on current pattern), it seems that in v0.1.12 this behavior has been changed so that in 60 FPS the stat(26) value still only updates 30 times per second.

What led to my discovering this was that I thought I perceived a visual difference when using v0.1.12 to run part of my "Not A Creature Was Stirring" cart that uses stat(26) ticks as the input for some easing functions, so I created a standalone test cart and ran it in both v0.1.11 and v0.1.12 and it looks like the behavior has indeed changed.

Here's a test cart. Try changing the "_update60" function to "_update" and see that in v0.1.12 the average diff between sampled ticks (only counting when there is an actual change) is the same (roughly 5.59) either way. But if you run the same cart (I had to change the cart version to 16 to do this) in v0.1.11 you can see that in 60 FPS mode, the average diff between sampled ticks is roughly half (about 2.8), which is better for syncing things to music.

demonstration of stat 26 bug

by kittenm4ster

Cart #jigudetipo-0 | 2019-04-20 | Code ▽ | Embed ▽ | No License

EDIT: oh well now that I see it on the web, it seems the 0.1.12c web player does not have this bug :D (it says about 2.8 for me) so apparently the problem is only with the native (I'm using Linux btw) version?

The changelog for v0.1.11c (from a year or so ago) says:

> Added: F11 to toggle fullscreen

...but F11 has never actually worked in any version of PICO-8 so far, to my knowledge. Alt + Enter is still the only way to do fullscreen.

So I'm just making a bug report to track this, and as a reminder in case a fix might make it into 0.1.12b or something ;)

found a bug in the config for the new v0.1.12: "gui_theme 2" is actually black but it looks like anything higher than 2 is grey now, as if the grey and black swapped :)

the dark blue is pretty nice as the new default btw!