Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Software Graphics

Interactive Raycaster For the Commodore 64 Under 256 Bytes 143

New submitter Wisdom writes "1bir (1 Block Interactive Raycaster) is a simple ray casting engine implemented only in 254 bytes to run on a stock, unexpanded Commodore 64. The name comes from the fact that on a C64 floppy disk, 1 block is equivalent to 254 bytes stored on a disk sector. In 254 bytes, 1bir sets up the screen for drawing, creates sine and cosine tables for 256 brads based on a simple approximation, casts rays into a 2D map that lives inside the C64 KERNAL ROM, renders the screen in coordination with KERNAL, evaluates 8-way joystick input and detects collision against walls. The ray casting core employs a brute force algorithm to determine visible walls, while the mapping portion supports both open-ended (infinitely looped) and traditional, closed maps. The source code in 6502 assembly is available, with extensive comments. A YouTube video showcases 1bir in a detailed manner with both kind of maps and more information, while a Vimeo video presents a shorter demonstration."
This discussion has been archived. No new comments can be posted.

Interactive Raycaster For the Commodore 64 Under 256 Bytes

Comments Filter:
  • kudos (Score:5, Informative)

    by excelsior_gr ( 969383 ) on Wednesday May 15, 2013 @04:30PM (#43734899)

    It is nice to see that in this world of plenty (at least as far as system memory and CPU speed goes) some people find joy in efficiency; and they go so far as to pull something like that off, just for the fun of it. Needless to say, the dude that did this is a real programmer [pbm.com].

  • by Anonymous Coward on Wednesday May 15, 2013 @04:31PM (#43734905)

    Dunno if the link was bad for anyone else, but here's the actual vimeo link [vimeo.com].

  • by Solandri ( 704621 ) on Wednesday May 15, 2013 @05:07PM (#43735205)
    The printer driver itself wasn't 500 MB. What happened was that some manager at HP decided tech support was wasting too much time (money) instructing people on how to navigate their byzantine support website to find and download the correct drivers for their printer. So they glommed the drivers for all of their printers into one big binary and told people to just download that.

    IMHO the real lesson from the HP printer drive fiasco is that if it's quicker and easier to find something on your website by doing a Google search for it, you need to redesign your website. HP eventually did that, and their site now lets you just type the printer's name and it'll take you directly to its download page.

"I've seen it. It's rubbish." -- Marvin the Paranoid Android

Working...