I also took a look and couldn't find any info. If you want to take a leap of faith, once you buy the assets there's metadata files including individual glyph sizes and kerning info so you could find all the ones that fit your project
I took a look at what's a part of my car controller[1] if you want some inspiration. A lot of these wouldn't make sense in an F-Zero type game
- Wheel modifiers (which wheels are on road, grass, boost tiles, etc)
- Control loss when airborne
- Slow turning when at low speed (a bit different from yours since the impact drops to zero very quickly)
- Speed / accel penalty when hitting a wall
- Visually rotating the car (this is what happens when a player presses the turn key but the actual velocity rotation is handled separately)
- Boost handling
- Nudge the car to the side a little if it's trying to turn but is blocked by a wall
- Acceleration, friction, breaking, and drift-breaking
- Corrective side force (basically an extra friction perpendicular to velocity like you have)
- Artificial speed limit (alternatively, you can include a drag component which applies a force proportional to the square of speed, but I've found it hard to get this feeling good in the past)
- Velocity rotation to align velocity direction and visual direction. This is a minor effect - it's mostly handled by the other physics
- Gravity
- Out of bounds checks
I think you've got the main pieces already. What's more important is understanding what you want your game to feel like and continuously tweaking until you get there
My .p8 file just has `#include driftmania-min.lua` and I do all the code edits in an external editor on that file. By splitting it out you remove the conflicts from modifying code and audio/graphics at the same time
Ah, you must be entering a race from the pause menu. PICO-8 controls are arrow keys, Z, and X (emulating old school consoles with limited input options). There's a level select screen just off the title menu
I worked at JPL for two years in college and helped with flight hardware testing a few times (probably in the same clean room this story took place in, albeit several years later). I can definitely see how a mistake like this could get made. A few stories I remember hearing from those days:
1. Bending pins from trying to insert a connector incorrectly
2. Running a full day of testing but forgetting to set up data recording
3. Accidentally leaving a screwdriver next to the hardware inside a thermal vac chamber in an overnight test
PICO-8 is really fun! I've released two games with it and I'm working on my third. For the third one I'm trying to push the edge of what the limitations permit, which adds quite a bit of complexity to an otherwise straightforward engine. You are only allowed a certain amount of tokens (~2k lines of code), characters, and compressed cart space. Maximizing the use of these limits requires a lot of tricks!
Workday | Senior Software Engineer, Distributed Systems | Full-time | San Mateo or Pleasanton, CA | Onsite (remote until August)
Workday is a leading provider of enterprise cloud applications for finance and human resources. I'm leading the Distributed Systems & Cloud Services teams within Workday Prism Analytics. We build the infrastructure behind our self-service analytics stack, which is a core driver for Workday's growth. If you're interested in helping us scale up our distributed systems, please apply at: