|
Neon Station by Digimind
[nfo]
|
||||||||
|---|---|---|---|---|---|---|---|---|
|
|
|||||||
|
popularity : 72% |
|||||||
alltime top: #295 |
|
|||||||
|
||||||||
added on the 2008-03-02 15:09:17 by Digimind  |
||||||||
popularity helper
comments
überkrass
rulez added on the 2008-03-02 15:13:02 by 0rel 
O___________O
WHAT THE FUCK ARE YOU ON
WHAT THE FUCK ARE YOU ON
excellent stuff
Quote:
1520 <GargajCNS> HOLY
1520 <GargajCNS> FUCKING
1520 <GargajCNS> SHIT
woah, this is _good_
How is that possible?
@_____________________@;;
Awesomeness!
Awesome!
Very incredible!
Generations ahead.
Nice!
![[self-ban]](https://content.pouet.net/avatars/intro.gif)
well, this is cool, but you're sure there isn't any room for a better palette?
O_O
what gargaj said....
smooth
wtf?!?!
Purely amazing.
speechless
WOW kick ass stuff !
This MAN should look for a girl.
indeed
ftw!? FAKE!
crashed my machine on exit. But fuck yeah!
shimmering neon lights
wow
FUCK THE WHAT???
massive wtf
also.. what's next? portal in 1k? :D
just wow
ugly colours but roxx for 256bytes
Wow! Amazing!!!
I'm really surprised! It really RULEZ!
I'm really surprised! It really RULEZ!
What am I supposed to run this on? The compatible version works under XP, but the actual demo doesn't run under dosbox.
zomg
the normal version works fine under winxp sp2 for me...
both versions works fine under winxp sp2 for me...
I'm speechless...
whoa
Unreal!
bah, fucking to having 64 bit instruction sets it my CPU.
really amazing again
impossible!
definately ROOLZ!
after 5 minutes watching i gave the .exe a shot and it appeared windowed....and holy cow,thats looking so damn smooth.!
thanX a lot for theZe bytes.! :)
thanX a lot for theZe bytes.! :)
WOOOOOOOW
what *.* said.
We go into a club, and there we start to dance.
#%%¤&"%¤&
ace! makes me wanna go 256b :)
noooooo fucking way!!!!!!
Oh! That's great!
holy crap
WTF?! O_o
Gulp!
I can't believe it :)
...
.....
WHAT THE FUCK?
I literally just wached this with my jaw hanging open. I'm not even exagerating. I cannot believe it. Digimind for president!
I literally just wached this with my jaw hanging open. I'm not even exagerating. I cannot believe it. Digimind for president!
It's starting to get ridiculous.
!!!MUST BE IN ALL TIME TOP!!!
What - no music? This sucks! Second Reality is much better than this!
Just kidding, here's the thumb :)
Awesome!
Just kidding, here's the thumb :)
Awesome!
holy shit rulez
bbut
Incredible !
Wtf!
just fucking sick..
fuuuuck.
ubercool.
oharaaa
Wtf O________________o
holy shit, that's crazy
You have distilled magic bytes!
ouééééééé
impressive
Ok, the 256b category can`t be bettered, now go do some 4k`s Digimind :)
fuck..
So... when does mentor release his 256b compressor :-)
Very nice 256b, even the motion path is outstanding.
Very nice 256b, even the motion path is outstanding.
incredible 256b!
wow! 0_o Digimind, you crazy! )
!
mmm, descent 256b ..
Bit o' blue, for the dads! Bit o' blue!
this is madness
coder demo
i give it up
nuff said
Total!
good
awesome
Even with some kind of changing cameramovement... awesome! Definately a new step in the quarter kB category.
rox.
R0X0R
fugly colors for solid code.
fugly colors for solid code.
fucking amazing. okay, you're allowed to make a progress bar in your 4k executable graphic. but only you.
Yep, this goes straight into the classic 256b category. Probably joint no.1 with tube for me.
O_O'...
fuck yeah!
very nice and also thank you for putting that compatible version in there (vista alert)
The best 256b intro so far!!
hmm... In fact seems that this is the 1st 256b providing 4dof 3D rendering (Pirx or other: correct me if I'm wrong)
Anyway: FTW, here's another thumb
Anyway: FTW, here's another thumb
Incredible..!
Awesome! Totally awesome.
@Broderick: Nah, an FD-tunnel would also be 4dof actually (i.e. roll+pitch+yaw+z-movement), but I get what you mean.
@Broderick: Nah, an FD-tunnel would also be 4dof actually (i.e. roll+pitch+yaw+z-movement), but I get what you mean.
wow
Awesome.
(The compatible exe works in wine, yay.)
(The compatible exe works in wine, yay.)
Fuck yeah =)
cool 256 bytes!
fuck it, for ten minutes I tried to write a decent comment here, but I'm totally out of words.
uhmmm.. sick!
after watching it again i must correct myself: this is FUCKING sick!
(and superb cam movement and no rendering artifacts at all!)
(and superb cam movement and no rendering artifacts at all!)
I don't get this... Insane..
this feels like doom
Amazing! This is a masterpiece!
fuck
neon?
this prod rulez
wtf dude, u on crack?
wow! unfortunately I cannot give this one more than one thumb up ...
Nice.
Ten thumbs.
Just awesome! :)
hngg..
I don't get the sizecoding hype.
have you tried to do sizecoding yourself ? or remake a popular 256b to see what size you get ?
No, because I don't get the point when it doesn't look like a demo.
It's ok if you don't get it. Others do. Go watch the Popular demo :)
You're such a nifty smartass.
Phuck, the guy is right - it doesn't look like a demo. Lets cry all together.
Damn, how come i thumbed this one up, it just contains 1 effect..
i don't know how or what
Tantronix, maybe it's taste (I don't think) or simply a vision of what should be exciting. Demos can be amazing on many levels, but I'll always love "impossible", mind blaster stuffs and even silly world records :P
what gargaj and src said.
cool stuff ;)
this can't be real!
Sooooooooo cool
nice musicdisk! even for 256 bytes..
jokin that really kicks.. alot..
übercoolex!
impossible! how can this be happing?!
!
should be in alltime top
actually, this is 255, not 256 bytes!
this production is the first thing i worship in the morning
unbeliveable!
This is so awesome!
I love the intertwined constants at the beginning (0.503 = good enough 1/2 for you? ;)), I love how there was 6 bytes left for blue, I love the maze generation (every block that the cam visits+refection), I love the coordinate cycling in BX/BP and the DDA hit check... it seems so... obvious now ;-)
You can save 1 byte by using "sbb di,di" at 156h (where you set DI according to the block coords) -- carry is set on both calls from BL cycling. I think you can also get rid of some of the "inc bx"'s by using "sbb bl,bh" instead and somehow preserving carry, but that's a pain.
What happens when [102h] (the timer) becomes >8000h again? No one watches that long? :D
What's the cause for snow? Quantization errors at 1B8h? Nice idea tho.
Thanks for the neat effect and hours of disassembling fun.
I love the intertwined constants at the beginning (0.503 = good enough 1/2 for you? ;)), I love how there was 6 bytes left for blue, I love the maze generation (every block that the cam visits+refection), I love the coordinate cycling in BX/BP and the DDA hit check... it seems so... obvious now ;-)
You can save 1 byte by using "sbb di,di" at 156h (where you set DI according to the block coords) -- carry is set on both calls from BL cycling. I think you can also get rid of some of the "inc bx"'s by using "sbb bl,bh" instead and somehow preserving carry, but that's a pain.
What happens when [102h] (the timer) becomes >8000h again? No one watches that long? :D
What's the cause for snow? Quantization errors at 1B8h? Nice idea tho.
Thanks for the neat effect and hours of disassembling fun.
rrrola:
thanks for minireview
> You can save 1 byte by using "sbb di,di"
sure, but I usually stop optimizing when size-limit is reached :)
> What happens when [102h] (the timer) becomes >8000h again?
well, it does precalc again and then intro continues
> What's the cause for snow? Quantization errors at 1B8h?
I'm not really sure... maybe these dots are sparks from high voltage needed for neon extraction
> Thanks for the neat effect and hours of disassembling fun.
now imagine few days of assembling fun when first highly optimized version turned out to be 330+ bytes without any obvious ways to remove more than a few bytes so I seriously considered giving up the project :)
MASSIVE WIN!
I think I had too much coffee
WOW!
But the "compatible" version is faster, and does not contain the snow pixels that the .com does.
Seems like the screen shot is from the compatible version. Feels a bit like cheating.
Don't get me wrong, I am very impressed by this intro!
But the "compatible" version is faster, and does not contain the snow pixels that the .com does.
Seems like the screen shot is from the compatible version. Feels a bit like cheating.
Don't get me wrong, I am very impressed by this intro!
Very impressive!
insane!
Fake, must use some hidden routines in gm.dls...Wow!! This is programmer's pr0n just like tube!!!
The COM becomes a slideshow when running it in DOSBox, but it still rules.
mic_:
By default DOSbox runs real-mode .com programs in slower mode. You can speed it up by setting following values in DOSBox.conf:
By default DOSbox runs real-mode .com programs in slower mode. You can speed it up by setting following values in DOSBox.conf:
Code:
core=dynamic
cycles=max
>> This MAN should look for a girl.
yep
yep
speechless
Ovechkin 60 goals so far.
Sincerely:
Digimind one man fan club Finland :)
Sincerely:
Digimind one man fan club Finland :)
fucking awesome!
I thought Tube was the best I've ever seen. Years later... there is Neon Station :)
/me imagine a 512 bytes Neon Station with the cube texture mapped with Tube's texture :)
This is just incredible!
Amazing 256bytes
CDC anyone?
256b... wow
very impressive!
Lovely 256b!!
Killer!
Compatible version runs in wine => mega rulez!1
Way to go, Digimind!
All fake i tell ya. It uses DirectX built-in textures!!11 :)
This shit pwnz like hell. Absolutely brilliant.
It can't be real! Congrats!
Digimind is now my idol, most impressive demo this side of 1k. If only I could make sense of the disassembly, no surprise that it gets a thumb up
Cool! I only want to understand idea of source code. What is it? Raytracing or special trick? I have not seen more impressive stuff. Demo in natural meaning - code has been made very optimal!.... AND the maze even have a texture, moving camera for the path. 256b - rulez, actually :)
abnormal
Lots of artifacts, so-so colours... but it's a 3D maze in 256b wtf!
really nice!
O_o
Excellent
Good!
christ
Ruuuuuuuleeeeeeeeeeeeeeeez!!!
Truly amazing. Thank you for attaching compatible executable version.
Wow... Amazing, how can this fit in 256b?
wow!
Awesome!
Ouch !
Eh, wth!
what iq said.
Digimind/rrrola: Could one of you masterminds maybe share his sources with us? That would be extremely cool.
Although probably us mortals won't grasp how it works anyway. :)
i find two questions particularly intriguing:
-how is the maze generated? seems fairly complicated, with multiple layers, tunnels, corners and such.
-how is camera movement calculated? i figure it's maybe quite simple: constant-speed y-rotation, y pos maybe just goes up and down at fixed speed, and x/z movement is also cleverly constructed in some way.
camera path does seem to vary slightly with each iteration. it never touches the wall anyway which i find particularly amazing.
incredible piece of work.
Although probably us mortals won't grasp how it works anyway. :)
i find two questions particularly intriguing:
-how is the maze generated? seems fairly complicated, with multiple layers, tunnels, corners and such.
-how is camera movement calculated? i figure it's maybe quite simple: constant-speed y-rotation, y pos maybe just goes up and down at fixed speed, and x/z movement is also cleverly constructed in some way.
camera path does seem to vary slightly with each iteration. it never touches the wall anyway which i find particularly amazing.
incredible piece of work.
Re: sources.
Even first c++ version is unreadable due to optimization, so short explanation would be better.
Re: rendering.
There is not much choice for 3D with a free camera in 256b world, so raytracing is used.
Re: camera movement.
Camera position is a Lissajous 3D curve with 2 sinewaves. Camera direction is calculated as a derivative of position to always look forward.
Re: maze generation.
There were no bytes left for maze generation so I had to reuse camera movement code. I just initialized 3D array to mark all cubic cells as non-empty. Then during precalculation I send the camera through this array for thousands of iterations and mark each visited cell as empty. Since camera path varies slightly with each iteration, it clears a lot of space. In this way there is also a nice property during rendering that camera never touches the wall - automatically.
Even first c++ version is unreadable due to optimization, so short explanation would be better.
Re: rendering.
There is not much choice for 3D with a free camera in 256b world, so raytracing is used.
Re: camera movement.
Camera position is a Lissajous 3D curve with 2 sinewaves. Camera direction is calculated as a derivative of position to always look forward.
Re: maze generation.
There were no bytes left for maze generation so I had to reuse camera movement code. I just initialized 3D array to mark all cubic cells as non-empty. Then during precalculation I send the camera through this array for thousands of iterations and mark each visited cell as empty. Since camera path varies slightly with each iteration, it clears a lot of space. In this way there is also a nice property during rendering that camera never touches the wall - automatically.
sick !
^-^b
sick
o_Ô
really awesome prod from Russia! ))
What one would call awesome
great for 256b
Can't believe I haven't seen it yet, this demo is amazing!
some day, when l grow up, i want to be able to do stuff like this!
for mother russia!
WOW!
+1
*boing*
Rulez. Found sources somewhere. Appreciated.
I am Gobsmacked Koala :D
oO
Shame, doesn't work in DOSBox or XP.
Wow!
Very nice!
Quote:
by Digimind:
Re: sources.
Even first c++ version is unreadable due to optimization, so short explanation would be better.
Re: rendering.
There is not much choice for 3D with a free camera in 256b world, so raytracing is used.
Re: camera movement.
Camera position is a Lissajous 3D curve with 2 sinewaves. Camera direction is calculated as a derivative of position to always look forward.
Re: maze generation.
There were no bytes left for maze generation so I had to reuse camera movement code. I just initialized 3D array to mark all cubic cells as non-empty. Then during precalculation I send the camera through this array for thousands of iterations and mark each visited cell as empty. Since camera path varies slightly with each iteration, it clears a lot of space. In this way there is also a nice property during rendering that camera never touches the wall - automatically.
Very nice!
Oh. Forgotten thumb, of course.
WTF
Wow
simply rockz!
yuh
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !