Commander X16

Thank you guys! I appreciate that. I'm working on yet another version of this with a more dynamic galaxy, a less fancy interface... and frankly, more interesting. This one has a lot of "capability" and I learned a lot writing it, but ... but I am bored with it. It doesn't have the neat fea...

Splash 1.0.png Travel the space lanes in your free trader... discover a thousand worlds in Imperial space... and avoid the pirates. Fly dozens of starship types and pick your own crew. This is a very 1980's-style retro simulator of Free Trader operations in the Traveller universe. The getting start...

There's more. If you have more than two inputs to a neuron, then you need to normalize the weights. That means summing the squares of the weights, taking the square root, inverting, and then multiplying the result by each weight to give a relative weighting. But that looks like a new technique (201...

Minifloats I would prefer to steal someone else's minifloat code (and have been looking at examples lately); unfortunately minifloats on the 6502 really ought to be in assembly language, and I'm not too keen on doing that. Maybe I can approach it by writing very elementary and memory-focused C. Tha...

I'd suggest breaking it up into semi-independent but inter-compatible modules. In this way, you could work on them independently and release them separately. This has the benefits of 1. accomplishment 2. reducing complexity 3. more likely to be bottom-up code projects But you already know this, beca...

Here's my first attempt at a "real" cellular automaton: the Hodgepodge machine, from Scientific American around 1989 or so.

Written in C with CC65. Faster than BASIC, slower than assembly.

As an initial diversion I coded up a starter CA for myself in BASIC. I really need to move this to C to get some speedup.

When my mood swings to machine learning, I think about implementing things on the X16. I SHOULD be implementing cellular automata (CA) or genetic algorithms (GA) first. CA are fun and easy. They work on a grid of byte values, which is usually displayed on the screen as pixels or characters. A CA pro...

So I got a small execution speedup by removing the % and the two calls to INT(). I also created a couple of indexes to determine the pixel color, but I didn't use anything sophisticated. 10 PA=$FA00 20 VPOKE 1,PA+ 0,0 :VPOKE 1,PA+ 1, 0 30 VPOKE 1,PA+ 2,0 :VPOKE 1,PA+ 3, 0 40 VPOKE 1,PA+ 4,0 +$0F:VPO...

Would the demo run slightly faster if all the variables were floating point? I.E. no A% N% S% and so on?