they actually have options for individuals, IIRC. Just find the chips you want and request a free sample if they're available (sometimes they're not, but I've always found the chips I need).

You can get free samples from TI for some fairly powerful ADCs.

The ADC on the atmega/arduino chipset is notoriously slow, however. If you need speed, you might want to get a dedicated high-speed ADC (I generally use the SPI interface with an Arduino)

IIRC, greyscale was one of the things that made escheron so amazing in the past; it'd be a shame if you were to truly go down a pure b/w route. Still, it'd be an amazing game without pumped up graphics, and it's great to see it being worked on again

While (nojob):
    sleep(20)

The Binding of Isaac is a game with an incredible amount of complexity; you should probably figure out each and every detail before you actually start working on the project. As for your mockups, you might do with making the hearts smaller, but it looks fine to me.

There are built in commands to do this; rotC( is ShadeNorm(), and rotCC is Shade_t(). Note, however, that these are not recursive functions, so you can't chain them (like rotC(rotC(Pic1))).

Oh snap, I thought the screenshot was of a CSE. My bad, carry on!

Actually, I'd love to see tiles that aren't letters - It'd be a shame if developers used a full-color screen just for displaying monochrome ASCII characters

Yeah, I highly recommend getting Dropbox, so you can share your files across all computers as well as recover deleted files.

The problem I had wasn't with lines not clipping, it was how to do them in an extremely optimized manner. There are a couple routines lying around on the forums, but for my applications they're mostly too slow.

I've certainly thought about that, but I'm not sure if there'd be much of a benefit. I'd need to generate trapezoids at arbitrary angles (currently, each trapezoid is 6 lines or so). In the worst-case scenario, I'd be drawing probably upwards of 88 Rects() (think largest polygon at 45 degree angle). Of course, I might be able to optimize that by combining touching layers, but there aren't many of those in the randomized chunks.

EDIT: I didn't see the asm, but I have no idea how to do that

Your favorite game, coming to TI-84s everywhere. Someday.




To be fair, I'm not sure this is going to work out for a few reasons -
1) No clipped lines (although I'm sure runer's working on it )
2) Lines are inherently slow.

I've worked out all the logic needed to run the game engine, but I can foresee major problems with speed in the future. I'll probably be reaching out to a few people to help out with optimizing the code, but I want to make sure I have everything down first. If anyone can see straight off the bat anything I can do to make it faster, be sure to tell me!

Things I've already built into the engine:
1) Global rotation, distortion, and skewing (including altering the number of sides between 4, 5, and 6)
2) Player movement
3) Loading of chunks
4) Player collision

Things to do:
1) Create mappings of levels based on random chunks
2) Music???

shhhhhhh