Whenever I try importing a .p8 file into an object, Voxatron just instantly crashes with no error. I saw someone else post about this on the BBS to no helpful response :(

Hoping this gets fixed or hoping there's a known workaround

@evman2k I tried this and it just imports the actual png (image of the cart) and not the cart itself.

@evman2k The last update for voxatron says you can import .p8 files as objects, so I feel it most certainly is a bug. https://www.lexaloffle.com/bbs/?tid=32743

I've also seen a video showing how to do it and they just opened a .p8 file when creating an object from a file.

The opening pico-8 files on Voxatron feature only works Voxatron 0.4.0 closed beta.
Version 0.3.5 and lower can't handle pico-8 files.

The video with the title screen was done on Voxatron 0.4.0 closed beta.

The post (https://www.lexaloffle.com/bbs/?tid=32743) doesn't completely state that you can open files on version 0.3.5. Instead, it says this, "Even though Voxatron and PICO-8 now share a lot more in common, I don't expect them to compete with each other. Voxatron is much more complex and better suited to different kinds of projects. But it is still fun to fool around with PICO-8 adaptations and view old code in a new light."

This proves this isn't a bug. The feature hasn't been implemented in Voxatron yet.

voxatron segfaults on pico8 import (P8 or PNG):

openat(AT_FDCWD, "/path/to/natural-landings.p8/", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOTDIR
openat(AT_FDCWD, "/path/to/natural-landings.p8", O_RDONLY) = 23
brk(0x55993a1f8000)                     = 0x55993a1f8000
fstat(23, {st_mode=S_IFREG|0644, st_size=41234, ...}) = 0
read(23, "pico-8 cartridge // http://www.p"..., 4096) = 4096
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV +++

Caught zep on discord!

> I'm going to get to that soon! It's just totally lagging behind PICO-8 -- you can hack around it by back-dating the version number in the .p8 file
> I was never expecting PICO-8 to keep getting updates after that last Voxatron update (api-breaking updates, that is)
> 0.3.6 is out next month and mostly just about catching up with PICO-8

This is great to hear! Thanks for keeping me updated :)

@merwok Let's hope 0.3.6 is on it's way

zep said «wait couple of weeks» two days ago!

it’s voxappening

Vox going on? :)

0.3.6 is out now, has someone tested this?
(Can’t know but could try later)