Log In  

Cart #p8x8-4 | 2024-04-03 | Embed ▽ | No License
46

p8x8: convert PICO-8 carts into Picotron carts (some assembly required)

I'm declaring p8x8 good enough for public release! It's a tool to convert pico8 carts to picotron -- it's not perfect and it requires some manual intervention in most cases, but it's magical being able to play a bunch of games on the new system without much effort.

Lots more info (instructions, compatibility notes, license, etc) here: https://github.com/pancelor/p8x8/

Teaser video here: https://mastodon.social/@pancelor/112162470395945383

changelog

v1.4 (#p8x8-4)

  • bugfixes for add(), rnd()
  • organize github docs
  • fix sfx()/music() (used to be noop; now passthrough to p64)

v1.3 (#p8x8-3)

  • better default fullscreen border
  • better warnings

v1.2 (#p8x8-2)

  • support fullscreen border images
  • easier main.lua tweaking (fullscreen, pause_when_unfocused)
  • more docs / warnings / ux

v1.1 (#p8x8-1)

  • nicer error/warning handling (e.g. when there's no code section)
  • handle windows CRLF carts properly
  • generate warnings much faster (smarter sorting algorithm)

v1.0 (#p8x8-0)

  • public release
P#144532 2024-03-26 14:35 ( Edited 2024-04-03 06:09)

2

Absolute magic

P#144535 2024-03-26 14:40

Wow! It's not even been two weeks and we already have full backwards compatibility with PICO-8?! Incredible stuff!

P#144547 2024-03-26 16:09

looks great! though trying to use it on poom (the pico-8 doom port) it seems to crash

P#144597 2024-03-26 23:04

thanks for the report! I've fixed the bug in the exporter

(but note: POOM itself will not run using this tool -- it uses too many advanced/intricate features of PICO-8 which are out of scope for this tool. sorry! that would definitely be cool to see, but it would require a dedicated port)

P#144627 2024-03-27 03:55
1

Great work!! I've used it on several Pico carts and it works very well! Mostly just editing out special characters is enough to get things going.

Do you know how to run the carts (or any cart for that matter) in fullscreen mode? I see the vid() command in the Picotron readme on the desktop, but inserting it into LUA code just gives me an error ... although I can run it in the terminal and it changes the screen rez as it should.

Again, well done! P8x8 (great name too) is also very useful as a first step for porting things over, even on carts that don't run as-is ... takes care of getting maps and sprites and all the source code over to Picotron in one shot.

Thanks for sharing your work!

P#144633 2024-03-27 05:48 ( Edited 2024-03-27 05:53)

thank you @cystedtwister! It's a nice feeling to see someone else using it, and it's great to hear that the warnings and manual editing wasn't too much hassle!

fullscreen is already supported! but it is a bit hidden:

  • load my-exported-cart.p64
  • scroll halfway down main.lua
  • change one variable from false to true
  • now it runs in fullscreen!
  • if you want a cool border image, that's supported in the version on github (I haven't uploaded it here yet, but that'll happen in the next day or two)

I need to organize the docs better, but FYI the reason vid wasn't working for you was probably because you put the vid() call inside your pico8 code. The pico8 code is run in a sandbox that sees different global variables from normal code, so it doesn't know what vid is. You can escape the sandbox by calling p64env.vid() from inside pico8 code, but in this case it's best to use the builtin fullscreen support in main.lua

P#144684 2024-03-27 13:23 ( Edited 2024-03-27 13:27)
1

Ah, right! I forgot about the sandbox. Nice! Well that worked and it looks beautiful! Super cool. The only issue I'm getting is the keys don't work in fullscreen mode. Could this be an issue with the screen not getting focus? I haven't had a chance to look it over this morning, but will do this afternoon.

Super groovy. Thanks for your reply!

P#144725 2024-03-27 17:47
1

This is so cool!! Maybe this will motivate me to finish my pico8 game now that I can import it into picotron :>

P#144732 2024-03-27 18:51

So this can't handle Pico-8's extended character set? That's kind of a big roadblock for me then, as my projects have generally either used lots of shorthand symbols, or 8-bit strings for storing data.

P#144765 2024-03-28 00:08

I'm so stoked to get started with picotron now that this exists!!!

...one thing though, I can't find any info in main.lua on your git about borders or fullscreen.

P#144800 2024-03-28 07:37 ( Edited 2024-03-28 07:55)

@arrowonionbelly (hm, you might have been looking in the wrong main.lua -- the fullscreen toggle is in baked/main.lua. Also, I just pushed it much higher in that file, to a more noticeable location)

@cystedtwister yep exactly -- has_focus=true needed to move out of the windowed section (it's updated now, both here and on github)

P#144822 2024-03-28 11:55
1

@JadeLombax -- correct, unfortunately. some assembly required! Pico8's extended characters get all unicode-y (they become 3-6 characters each) and break the parser in picotron; you could write a tool to replace them but the tool would need to guess what context/purpose the symbols have. If you write a down-arrow character in your code, is that meant to be the number 3 (if btnp(⬇️) then), the image of an arrow (print("use ⬇️/⬆️ to move!")), or the binary encoding of 131? It seems possible to make heuristics to decide which one to choose, but that sounds like a huge rabbit-hole and a lot of work for me to solve something that would be more easily solved by my users, who have the specific context to know what their code is supposed to mean.

I've decided that this sort of automatic conversion is out-of-scope for this tool, but maybe there are more things I could do to make it easier -- suggestions welcome. Currently, p8x8 generates warnings every time it notices pico8 extended characters, and the warnings suggest an easy upgrade path for the btn/fillp use case: WARN(minor): 1.lua#102 (p8:234) special chars (shift-X / chr(151)) are not supported. use this, for example: fillp(p8x8_symbol"❎") instead of fillp(❎) (p8x8_symbol is a simple function I added to the sandbox environment that makes this work as expected)

For 8-bit strings in particular, the easiest thing to do is probably to regenerate those strings -- something like mydat=userdata("u8",length_here,"1234deadbeef") or mydat={[0]=0x12,0x34,0xde,...}. Maybe I should make a function like p8x8_symbol for this use case too? But I suspect you might run into other major issues with p8x8 (like the difference between number types in pico8 and picotron, and the way this affects bitwise operations. or the fact that p8x8 doesn't attempt to emulate the pico8 memory layout)

P#144823 2024-03-28 12:10 ( Edited 2024-03-29 02:45)

ok. I'll try it from the cart on here because I have no idea how to use the loose files on the git yet 😅

P#144864 2024-03-28 16:29

"@cystedtwister yep exactly -- has_focus=true needed to move out of the windowed section (it's updated now, both here and on github)"

Works like a charm!

P#144869 2024-03-28 17:25
3

ok I got it working! kinda... seems like my particle physics are boned, something to do with x and y values, not sure how that's gonna pan out, and NONE of the sounds carried over, but it's a start!

P#144871 2024-03-28 17:39
1

I just tried it with my new game and it worked straight away. This is brilliant. Thank you so much!

P#144963 2024-03-29 09:54 ( Edited 2024-03-29 09:59)
1

I made a rad border for my game in fullscreen mode and it prints my opening screen on top of the border, plus when I get game over and it restarts to the start screen, it blanks out the border.

Is it because I'm in vid3 mode? I tried it and rather liked the pixel resolution and didn't experience any blinking so I kept it, but if that's what's interfering with it that... would kinda suck lol.

My particle physics for starfield and rage are all starting way off-screen at the top. Other particles, like the explosions of enemies, are all localized where they need to be. Not sure what the issue there is but if anyone knows why picotron did that, please let me know.

Anyway, in case it's a ME-issue that nobody else is having, here's my pod

load #pony9k_2_0-0
// to load from inside Picotron

EDIT:

oh wait you updated it today. crap. How do I... use your updated code on my game, when I've already imported it and started editing my code in picotron?

EDIT EDIT:

Copied main.lua from baked over and ran it again but that doesn't seem to be the issue. Also switched from vid(3) to vid(0) and same issue of drawing the initial sprite on the left side of the screen. Strange. Anyone else experiencing this?

P#145012 2024-03-29 18:14 ( Edited 2024-03-29 18:31)

@arrowonionbelly - vid(3) versus vid(0) shouldn't make a difference -- I bet the problem is that you're calling drawing functions outside of _draw(). (confirmed by commenting out line 88 (spr(spr_border[0].bmp)) and line 102 (if p8env._draw then p8env._draw() end) of main.lua). If you're on github, lets talk here: https://github.com/pancelor/p8x8/issues/9 (but if not, here is fine)

> How do I... use your updated code on my game, when I've already imported it and started editing my code in picotron?

Oh, good question -- I'll add docs for that soon. Replacing main.lua is a good idea, since I've made some changes there to fullscreen mode. (note that you'll need to move your fullscreen border image to sprite slot 1) My other updates have generally been better compatibility warnings -- the code conversion hasn't changed, so you aren't missing much. But yes I'll add some docs.

thanks for the bug reports!

P#145100 2024-03-30 09:32
1

I tried making something similar to this a while back (even trying to emulate the 16.16 fixed point) but gave up when things became too convoluted. Insane stuff @pancelor!

P#145377 2024-04-01 17:09
1

THANKS SO MUCH FOR THE TOOL!! CONVERSION IS UNDERWAY!!!
if anyone makes a sound importer that would be rad, please let me know. Took me hours to manually make all my base instruments and then transcode just one sound effect (even the octaves and volume are different...ish)

P#145543 2024-04-03 04:29

super noob question, maybe someone can help me?

when I import the cart, I get an error message at the bottom that reads, "want a '.p8' file and not a '.p8.png' file."

am I saving Pico 8 carts incorrectly? thanks!

P#145730 2024-04-04 22:40

I appreciate you!

P#145922 2024-04-06 19:56

[Please log in to post a comment]

Follow Lexaloffle:          
Generated 2024-04-15 12:16:09 | 0.091s | Q:52