Difference between revisions of "Memories"
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
| + | ==Tiny Megademo Framework== | ||
==History of tiny effects== | ==History of tiny effects== | ||
Sizecoders think in size categories. For MSDOS, these categories are 256b, 128b, 64b and 32b. These are the standards of one of the biggest demoscene archives, www.pouet.net. There is no 16b category, although many tiny effects can be implemented in 16 bytes. Almost of the effects of "Memories" have been coded and optimized by me before, and mostly the implementations were attempts to reduce an already existing effect in size, or do something similar in less size. Reducing the size in this case means, reducing it to the (one of the) next lower 2^N category. For example i might have seen an effect done in 33 to 64 bytes, and then reduced the size to 32 bytes or less. Almost everytime i moved an effect to a lower category, i submitted the resulting tiny program to a demoscene party which allowed remote entries in the 256b category. In this section i will introduce the effects and mention the origins and authors. | Sizecoders think in size categories. For MSDOS, these categories are 256b, 128b, 64b and 32b. These are the standards of one of the biggest demoscene archives, www.pouet.net. There is no 16b category, although many tiny effects can be implemented in 16 bytes. Almost of the effects of "Memories" have been coded and optimized by me before, and mostly the implementations were attempts to reduce an already existing effect in size, or do something similar in less size. Reducing the size in this case means, reducing it to the (one of the) next lower 2^N category. For example i might have seen an effect done in 33 to 64 bytes, and then reduced the size to 32 bytes or less. Almost everytime i moved an effect to a lower category, i submitted the resulting tiny program to a demoscene party which allowed remote entries in the 256b category. In this section i will introduce the effects and mention the origins and authors. | ||
===Array of chessboards=== | ===Array of chessboards=== | ||
| − | The origin of this effect is my own "Kasparov 16b" (https://www.pouet.net/prod.php?which=75912) apparently i "had this piece lying around, stuck at 17 bytes and not that beautiful, until i found a trick ;)" (quote from the release notes) There was a similar effect in 32 bytes before : "ew" by headcrash. (https://www.pouet.net/prod.php?which=17567) In this case, the design goal was to show "real" chessboards of 8x8 fields and recognizable dark and light squares, as well as the correct orientation of the single chessboards, meaning that the bottom left corner (a1) has to be a dark square. (source?) | + | The origin of this effect is my own "Kasparov 16b" (https://www.pouet.net/prod.php?which=75912) apparently i "had this piece lying around, stuck at 17 bytes and not that beautiful, until i found a trick ;)" (quote from the release notes) There was a similar effect in 32 bytes before : "ew" by headcrash. (https://www.pouet.net/prod.php?which=17567) In this case, the design goal was to show "real" chessboards of 8x8 fields and recognizable dark and light squares, as well as the correct orientation of the single chessboards, meaning that the bottom left corner (a1) has to be a dark square. (source?) For "Memories", the effect had to be reimplemented with another approach of writing to the screen to work with the framework, also the scrolling direction was changed to be different from the "scrolling tilted plane" effect. |
===Zooming circles=== | ===Zooming circles=== | ||
===Scrolling tilted plane=== | ===Scrolling tilted plane=== | ||
| Line 12: | Line 13: | ||
===Raycast bent tunnel=== | ===Raycast bent tunnel=== | ||
===Ocean night to day=== | ===Ocean night to day=== | ||
| − | |||
| − | |||
==Explaination of effects== | ==Explaination of effects== | ||
Revision as of 10:29, 18 April 2020
Contents
Introduction
Tiny Megademo Framework
History of tiny effects
Sizecoders think in size categories. For MSDOS, these categories are 256b, 128b, 64b and 32b. These are the standards of one of the biggest demoscene archives, www.pouet.net. There is no 16b category, although many tiny effects can be implemented in 16 bytes. Almost of the effects of "Memories" have been coded and optimized by me before, and mostly the implementations were attempts to reduce an already existing effect in size, or do something similar in less size. Reducing the size in this case means, reducing it to the (one of the) next lower 2^N category. For example i might have seen an effect done in 33 to 64 bytes, and then reduced the size to 32 bytes or less. Almost everytime i moved an effect to a lower category, i submitted the resulting tiny program to a demoscene party which allowed remote entries in the 256b category. In this section i will introduce the effects and mention the origins and authors.
Array of chessboards
The origin of this effect is my own "Kasparov 16b" (https://www.pouet.net/prod.php?which=75912) apparently i "had this piece lying around, stuck at 17 bytes and not that beautiful, until i found a trick ;)" (quote from the release notes) There was a similar effect in 32 bytes before : "ew" by headcrash. (https://www.pouet.net/prod.php?which=17567) In this case, the design goal was to show "real" chessboards of 8x8 fields and recognizable dark and light squares, as well as the correct orientation of the single chessboards, meaning that the bottom left corner (a1) has to be a dark square. (source?) For "Memories", the effect had to be reimplemented with another approach of writing to the screen to work with the framework, also the scrolling direction was changed to be different from the "scrolling tilted plane" effect.
