SOUND NOT WORKING YET
If anyone wants to tell my why my one sfx isn't getting called when the pony is hurt I'd love to know
CONTROLS
...are a bit sticky in the main menu, idk why, but anyway HAVE A BASTARD MODE!
WASD/arrow keys: Fly
G/O: Fire Prism Laser
V/X: Release Rage Attack
Changelog/to-do coming soon
2 comments
Here's a simple raytracer for my first picotron cart. Just playing around and runs at about 1fps.
To run locally: load #eigenbom_ray
6 comments
Some trouble understanding basic functionalities:
-Open Picotron and go to the editor. Type in some code into the blank tab called
main.lua. hit ctrl-s which saves as a cart: untitled.p64.
-Loads fine, runs great. Can change the name later.
-Now I want to create a new, different cart. Go to the desktop and open Files.
Click on the hamburger menu and select New File.
-I enter in myNewFile and it gives filetype not found.
-I enter in myNewFile.p64 and it gives filetype not found
-I enter in myNewFile.lua and it likes that. very good.
-It opens myNewFile.lua as a tab alongside main.lua in the editor.
But when saved, it doesn't save as a .p64 and it cant be loaded obviously.
I've taken to shutting down and restarting in order to start a new cart. What is the correct way to do it?? (v 0.1.0e)
A basic explanation of the mechanics of how this all functions would also be of great interest for anyone up to it. Like, are new files just tabs of whatever is loaded into ram/cart? Is there a way to 'unload' a cart to start fresh without a reboot?
3 comments
Hi all,
I decided very soon after getting started in Picotron that I was going to try and use it as the primary workstation for my projects (instead of working in external editors like I did for PICO-8). I created a /projects folder and realized very quickly that if I wanted to do this, I was going to need to write some utilities to quickly "build" my projects. So I started working on a build utility in /appdata/system/util that I could call from the terminal.
Pretty quickly, however, I ran into an issue of trying to get user input from this utility. The idea was simple: if the user tries to build into /ram/cart, get confirmation from them before potentially clobbering whatever cart was currently loaded. This is pretty trivial stuff in any "real world" scripting language but every approach I tried in Picotron seemed to not work.
Basically, the "program" completes instantly instead of hanging and waiting for user input. Here's the main way I tried getting user input:
1 comment
I'm new to Pico 8
I've been developing this simple game as a first project where you play as "GeK" a simple character that has animations when walking around, however i've found that when moving diagonally it makes the character faster than usual. This issue is very confusing to me and I know it has something to do with the Pythagorean theorem, and I need something called a "movement vector" My code is simple as it has a variable known as speed that is set to 1 and is used when pressing a direction to move by 1 pixel. The character also has a hat and tail that follows it and is supposed to be locked on at all times.
I'd really appreciate it if anyone knows the solution to my problem.
3 comments
This is my first cart to test out making games with picotron! It's a simple lights-out game.
In this version only the basic logic is there.
In the next release we should have a win screen after turning all of the lights out, some levels, and a score!
1 comment
Not sure if this is a bug or not but it is really hard for me to get left-clicks to register on my macbook pro. Whether I'm tapping to click or actually pushing the trackpad it generally takes 4 to 5 clicks to register 1. I don't have any issues in any other apps so it isn't my hardware.
Is anyone else having this issue? Are there any known workarounds? Thanks!
EDIT: I am having this problem on a 2015 macbook pro but I was able to test with a new m2 macbook pro and all the push left clicks registered correctly but the tap left clicks still took 5 or 6 solid taps to register.
5 comments
just noting that the following crashes picotron:
function _draw () print (tostring (1 * vec(1, 1, 1))) end |
0 comments
You won't need a widget to check the time in style while you work in Picotron.
Instructions:
-
run
load #pocket_watch_wallpaper-2 -
run
save /appdata/system/wallpapers/pocket_watch_wallpaper.p64.png(you might have to create the wallpaper folder, if you haven't done that yet) - open System Settings and select this wallpaper from the list.
Updated to show more realistic proportions
0 comments
Show how fancy you are by displaying your own Picotron pocket watch. Load it by typing load #pocket_watch-3 in the terminal. It actually tells the time (in GMT only at the moment).
Updated to show more realistic proportions
0 comments
So I just wanted to know if there is a way to export your music / sprites created in picotron to like png / wav format, or if it will ever be possible.
0 comments
First windowed demo for the Picotron, with some exploratory misuse of the window command and the audio system, and the usual pushing of bad lua code to its' extremes.
released at Revision 2024 Fantasy Computer compo.
code and music by visy
2 comments
So I know the documentation is a bit spotty at the moment but I was curious if the btn() function is the same as in P8?
I set up a simple sprite to move around and used the usual btn() setup for up down left and right but am getting weird behavior. Sometimes when I press left or right it will go up, or go diagonally randomly.
Sometimes it will work perfectly normal.
Anyone else experience this?
4 comments
I tried to adapt this classic tweetcart for picotron. when i couldn't make it work the way i wanted i decided to break it further :3
0 comments
Okpal is a tool to create and edit color palettes. You can easily use those palettes in your programs, and even directly in Picotron's sprite and map editors.
Features
- Any change to the palette is propagated to Picotron's sprite and map editors.
- Use a perceptually uniform color space (oklab).
- Choose colors by hue, saturation and lightness.
- Reorder colors by drag-and-drop.
- Supports two file formats: ".hex" and ".pal"
- Multiple options for importing external palettes (keep default palette, overwrite it, or try to match it)
Usage
The tool shows you four different views of the 64 colors in the current palette:
- at the top-left of the screen, the colors are shown in palette order (same as in sprite editor first tab);
- below, on the left, the colors are shown inside a circle picker: the angle correspond to the hue, and the distance from the center correspond to the saturation;
- in the middle the colors are shown as inside a square picker: the X axis correspond to the saturation, and the Y axis correspond to the lightness;
- finally, on the right is a "test zone", where you can use 24 paintable cubes to test color combinations.
To modify a color, you must first select it. You can do that either by clicking in the palette overview at the top of the screen, or by clicking directly on one of the color dots in the circle picker or in the square picker.
Once selected, some information about the color are displayed on the right of the palette overview:
- the color number;
- the hex code corresponding to the RGB values of the color;
- a padlock icon: if the padlock is closed, the color is "locked" and cannot be edited; click on the icon to lock/unlock it;
- an eye icon: if the eye is closed, the color is only shown in the palette overview; it is hidden in the circle and square pickers.
- a paint bucket icon: you can click on it to change the color background to the current selected color; click again to go back to a black background.
You can copy the current color by using Ctrl-C, and paste a copied color onto the current one by using Ctrl-V. This also works outside OkPal: the color is stored in the clipboard as a hex code ("#ffacc5").
There is five different ways to adjust the selected color:
- a small colored circle outside the circle picker allows you to change the hue of the color;
- a small colored circle inside the circle picker allows you to change at the same time the hue and the saturation;
- a small colored triangle below the square picker allows you to change just the saturation;
- a small colored triangle at the right of the square picker allows you to change the lightness;
- finally, a small colored circle inside the square picker allows you to change at the same time the saturation and the lightness.
Any change you make can be reverted by hitting Ctrl-Z for undo. Use Ctrl-Y for redo.
Once you have several colors in you palettes, you can reorder them in the palette overview: just drag one color onto another, they will swap their positions. Note that both colors must be unlocked.
Using the palette in cartridges
By default, the palette you edit is saved in the cart you're working on, alongside your sprite sheets and maps.
The default path is "/ram/cart/pal/0.pal"
In order to use a palette in your programs, you just need to copy it in memory:
poke4(0x5000, get(fetch"/ram/cart/pal/0.pal")) |
Loading and saving
If you only need one palette for your cart, you don't need to do anything special to save it. It is saved alongside the rest of your assets each time you hit Ctrl-S.
In order to create a new palette, use the '+' button at the right of the tabs and choose the name of your new palette, for example "1.pal". If you need to start from scratch for this new palette, use "Empty Palette" or "Picotron Palette" from the menu.
You can load a previously created palette by using "Open File" in the menu.
Importing and exporting
You can import and export palettes for use with external tools. Currently the only supported format is ".hex" files, which are simple text files with one line per color, represented by their RGB code in hex format (without "#" or "0x", just the hexadecimal numbers).
To import a palette, choose "Open File" from the menu, and select the ".hex" file. If this is the first time you open this external palette in OkPal, a dialog will appear to let you choose how to arrange the colors in the palette. You can either:
- Keep default Picotron palette in the first 32 colors, and put the imported colors in the last 32 slots.
- Completely remove the Picotron palette and import the whole palette, but reorder the colors to try to match the default colors.
- Or simply import the palette as is. Note that this will affect the interface and probably make it difficult to use the menu, the sprite editor and the map editor.
Changelog
2024-08-23: version 1.0.3 (release #okpal-6)
- added: add file icon to saved palettes;
- changed: can load and import palettes by
double-clicking in the file dialog (no need
to drag-and-drop anymore); - fixed: bug in BBS;
2024-05-03: version 1.0.2 (release #okpal-5)
- fixed: bug while using "+" button in Picotron
0.1.0g; - changed: disabled tabs in BBS, as it prevents
the cart from running;
2024-04-27: version 1.0.1 (release #okpal-4)
- fixed: picotron's palette was not locked in the
default file on first opening; - fixed: saving a ".pal" file from an imported
".hex" file was not working; - explain how to export to .hex in the manual;
2024-04-06: version 1.0.0 (release #okpal-3)
- propagate palette to sprite and map editors;
- undo/redo;
- reorder colors by drag-and-drop;
- import dialog;
- reorder imported colors to match default colors;
- added a manual;
- menu entries to initialize the palette and open
the manual; - flash padlock icon when trying to edit a locked
color; - shift-click paint-bucket icon to change the "white"
color used in the interface, and ctrl-click the
icon to change the "black" (useful when importing
external palettes);
2024-04-02: version 0.0.3 (release #okpal-2)
- Added the ability to change the background color (by clicking on the small paint bucket icon), and switched the default background to black.
- Added the ability to import ".hex" files (using drag and drop from the "Open File" dialog); to actually create the ".pal" file, you need to save.
- Improved the color pickers.
- Added the ability to copy/paste colors (using a hex string starting with #).
- Added the ability to show/hide individual colors (right click on a color in the palette).
2024-04-01: v0.0.1 (release #okpal-1)
- Added the ability to lock colors, to avoid accidentally modifying them. By default the first 33 colors are locked (click on the padlock to unlock)
- Added the ability to hide specific rows of color from the two color pickers.
- Added sliders to change the individual components (hue, saturation and luminance).
- Added the ability to select a color by clicking on their dot in the color pickers.
- Added a test zone, with 24 paintable cubes (click on a cube face to change its color).
27 comments
i missed how easy it was to tell what a color's numerical code was, so i made a picotron cart to list them out :) it doesn't do anything cool like copying them when you click on them, or reordering them to put like colors together... but it's better than counting by hand!
1 comment
.jpeg)
Is the education edition broken right now? I tried running the following:
INSTALL_DEMOS CD DEMOS LOAD HELLO RUN |
Then pressing ESC twice. But the editor doesn't show up. Am I doing anything wrong here?
4 comments
Import PNG images and generate optimal palette
Can import png to fit picotron default palette, custom palette imported through hex file, or custom palette generated for the png file.
For best results, reduce the png to 64 or fewer colors in an external program such as gimp. This isn't required, but will save you some time waiting for the palette to generate and will allow you to use dithering.
If the imported png has less than the "max colors" value and is set to generate palette, the generation step can be used and the image's colors can be used as-is.
The generated palette is also sorted to attempt to fit the current palette. Colors in the generated palette are moved to the location of similar colors on the loaded palette. For example, black will attempt to stay black, and white will attempt to stay white.
11 comments
