▲ 440 ▼ Where it all began (media.piefed.world) submitted 1 week ago by The_Picard_Maneuver@piefed.world to c/memes@lemmy.world 51 comments fedilink hide all child comments
[–] The_Picard_Maneuver@piefed.world [S] 14 points 1 week ago (2 children) What did you play this on? It looks like Atari. permalink fedilink source parent hideshow 4 child comments replies: [–] prettybunnys@piefed.social 13 points 1 week ago (1 child) Looks like the chess game we had on our old “ibm compatible” permalink fedilink source parent hideshow 2 child comments replies: [–] defaultusername@lemmy.dbzer0.com 11 points 1 week ago* (1 child) That screenshot is specifically from the Atari 2600. You can tell because sprites that are next to each other are offset by one vertical pixel, which was a common effect used to help with hardware limitations. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago (1 child) IIRC, the 2600 didn't have a graphics processor. So, you had to "chase the ray" with CPU instructions, which made for some interesting limitations. permalink fedilink source parent hideshow 2 child comments replies: [–] defaultusername@lemmy.dbzer0.com 4 points 1 week ago (1 child) It has the TIA, which is as close to a picture processor (and also audio synthesizer) as you can get, but due to the 128 bytes of RAM, there was not enough RAM to form a framebuffer, hence the need to race the beam. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago Thanks for the clarification. I was too young to program the 2600. I started programming on PC-compatible. permalink fedilink source parent [–] Blue_Morpho@lemmy.world 3 points 1 week ago* Yes that's the Atari 2600. permalink fedilink source parent
[–] prettybunnys@piefed.social 13 points 1 week ago (1 child) Looks like the chess game we had on our old “ibm compatible” permalink fedilink source parent hideshow 2 child comments replies: [–] defaultusername@lemmy.dbzer0.com 11 points 1 week ago* (1 child) That screenshot is specifically from the Atari 2600. You can tell because sprites that are next to each other are offset by one vertical pixel, which was a common effect used to help with hardware limitations. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago (1 child) IIRC, the 2600 didn't have a graphics processor. So, you had to "chase the ray" with CPU instructions, which made for some interesting limitations. permalink fedilink source parent hideshow 2 child comments replies: [–] defaultusername@lemmy.dbzer0.com 4 points 1 week ago (1 child) It has the TIA, which is as close to a picture processor (and also audio synthesizer) as you can get, but due to the 128 bytes of RAM, there was not enough RAM to form a framebuffer, hence the need to race the beam. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago Thanks for the clarification. I was too young to program the 2600. I started programming on PC-compatible. permalink fedilink source parent
[–] defaultusername@lemmy.dbzer0.com 11 points 1 week ago* (1 child) That screenshot is specifically from the Atari 2600. You can tell because sprites that are next to each other are offset by one vertical pixel, which was a common effect used to help with hardware limitations. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago (1 child) IIRC, the 2600 didn't have a graphics processor. So, you had to "chase the ray" with CPU instructions, which made for some interesting limitations. permalink fedilink source parent hideshow 2 child comments replies: [–] defaultusername@lemmy.dbzer0.com 4 points 1 week ago (1 child) It has the TIA, which is as close to a picture processor (and also audio synthesizer) as you can get, but due to the 128 bytes of RAM, there was not enough RAM to form a framebuffer, hence the need to race the beam. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago Thanks for the clarification. I was too young to program the 2600. I started programming on PC-compatible. permalink fedilink source parent
[–] bss03@infosec.pub 2 points 1 week ago (1 child) IIRC, the 2600 didn't have a graphics processor. So, you had to "chase the ray" with CPU instructions, which made for some interesting limitations. permalink fedilink source parent hideshow 2 child comments replies: [–] defaultusername@lemmy.dbzer0.com 4 points 1 week ago (1 child) It has the TIA, which is as close to a picture processor (and also audio synthesizer) as you can get, but due to the 128 bytes of RAM, there was not enough RAM to form a framebuffer, hence the need to race the beam. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago Thanks for the clarification. I was too young to program the 2600. I started programming on PC-compatible. permalink fedilink source parent
[–] defaultusername@lemmy.dbzer0.com 4 points 1 week ago (1 child) It has the TIA, which is as close to a picture processor (and also audio synthesizer) as you can get, but due to the 128 bytes of RAM, there was not enough RAM to form a framebuffer, hence the need to race the beam. permalink fedilink source parent hideshow 2 child comments replies: [–] bss03@infosec.pub 2 points 1 week ago Thanks for the clarification. I was too young to program the 2600. I started programming on PC-compatible. permalink fedilink source parent
[–] bss03@infosec.pub 2 points 1 week ago Thanks for the clarification. I was too young to program the 2600. I started programming on PC-compatible. permalink fedilink source parent
[–] Blue_Morpho@lemmy.world 3 points 1 week ago* Yes that's the Atari 2600. permalink fedilink source parent
