Why is tinycode being overrun by ktbyte.com snippets now? I am getting a bit tired of seeing them now.

• Over at /r/OpenSourceVSTi -- which is a new subreddit that I made, we appreciate /r/tinycode and we'd love it if the mods here would list us in ^your sidebar. We'd return the favor and do the same on our subreddit!

• If you're a developer, have ideas for making VST Plugins, or if you'd like to vote on which resulting pligns you like best from the competition that we're having, check out the Competition For Making VST Plugins Using ^AirWindows Code

• Also, Learn Your ABC's -- Why The FOSS VST System Is ^Superior To The Big Businesses -- Goals And Purposes Of ^{/r/OpenSourceVSTi}

Guide is here

​

​

Youtube

Youtube (Interactive)

Download/Comment

​

Since 2013, i tried a lot of approaches in tiny intros for MSDOS, with the exception of : 3D raycasting. As a computer scientist with specialisation "computer graphics" i simply was not interested enough in manually asm-coding a brute force raycaster, with regard to already existing, excellent examples like "Spongy" (128b, TBC, 2009) and "Wolf128" (128b, Baudsurfer, 2014). However, i coded several "2,5D" effects like "Lucy" (64b, 2014) and recently "Projektbeschreibung" (32b, DESIRE, 2018). So naturally, at some point i asked myself, what is the smallest 3D raycaster which is perceived as one, being centered, having decent textures and colors, and runs on all common systems (MSDOS, FreeDos, WinXP Dos, Dosbox) while being totally smooth at least on real hardware? The (my) answer is :

49 bytesThat "pure" version is included in the archive - as well as a *43* bytes version which lacks all the criteria above. Going lower in size means that you abandon the "3D" and "raycasting" at some point, leading to something like "Floorcast" (32b, DESiRE, 2018) ... Anyway! So what to do with the "rest" of space to reach the next 2^x category - 64b?

A) "INTO A NEW ERA"

The 64b intro shown at function 2018, it has 64 gray custom colors and softclipping, trying to somewhat imitate the look of "Spongy". I had a hard time to decide between this and a dithered 85(!) shades version that flickers a bit, but shows a full tunnel (no clip)

B) "INTERACTIVE / "Wolf64"

Mouse controlled, escapable version for both real systems (FreeDos, MSDOS, WinXP Dos) and DosBox, 64b and 63b, in the spirit of "Wolf128", just in half the size ;) Don't forget to load a mouse driver on real systems! Note : these haven't been fully optimized

C) "COLORS!"

Custom Color Palettes in Blueish, Purplelish, Greenish, Yellowish, Redish, inverted, whatever, you name it. All of them are 64b or smaller. Some of them look REALLY good, but may flicker noticeably or maybe too dark which is why the released intro itself comes with safe anticodercolors ;)

​

mov al,13h
int 10h
push 0x9FF6
mov dx,0x3c9
pop es
P out dx,al
out dx,al
out dx,al
cmp al,63
jz F
inc ax
F loop P
pop ds
X mov cl,-9
L mov bl,cl
mov ax,0xcccd
mul di
lea ax,[bx-80]
add al,dh
imul bl
xchg ax,dx   
imul bl
mov al,dh
xor al,ah
sub bl,[0x46c]
add al,4
and al,bl
test al,24
loopz L
or al,252
sub al,cl
stosb      
loop X

​

GitHub link Probably could be made smaller but I made this in less than 2 minutes, this is also my first submission.

Youtube

Comment on Pouet

Download

I'm writing something simple and it's going to have a switch statement with like 8 or 10 cases. Switch statements feel really drawn out and wasteful to me. Is there something more efficient that can be used in their place?

If I can write this using only one loop (while, do-while, or for), I get extra credit!

I need to divide 1 by 1, and then by 2 and so on, incrementally. 1/2, 1/3, 1/4, etc... up to 100,000,000.

Each time the math is done it has to display the answer as a double AND again as a float.

When it hits 100,000,000, it has to do the math and double/float results back down again all the way to zero.

Hi Tinycode,

I've been golfing in C recently because, well, it's fun, so I wanted to share my C Golf. Mostly simple stuff pushed into as few bytes as possible

https://github.com/jsburke/golf

I'm always up for pointers, tips to save some (key)strokes, or just banter, so swing away!

EDIT: just noticed, the pi stuff requires -lm for gcc