|
VGA FLOOR CAST
[nfo]
|
||||||||
|---|---|---|---|---|---|---|---|---|
|
|
|||||||
|
popularity : 59% |
|||||||
alltime top: #11012 |
|
|||||||
added on the 2008-05-02 08:10:21 by rain_storm  |
||||||||
popularity helper
comments
Rather basic but non-ugly nevertheless. There's no reason to use floating point though, you could get it at lot smaller by using only integers.
added on the 2008-05-02 08:17:25 by Preacher 
A bit slow but nice. It could be done in 128b or something. Good that you moved from 32b intros to something bigger.
hmm. its ok, but when you consider that searchlight is the same size, its not so impressive. A piggy.
Thx for the mirror src well I guese this could be done smaller but fixed point math is a pain in the backside when it comes to division and I had already reached my target of 256b I will leave that for some other time
XOR EAX, [DWV]
Magic!
Magic!
meh. ugly and pointless.
freedir version!
Not bad.
rain_storm
Man, tell me, WHAT THE FUCK IS THIS?
Man, tell me, WHAT THE FUCK IS THIS?
Man, tell me, WHAT THE FUCK IS THIS?
I fully understand that there are your first steps in 256B introcoding, I fully appreciate that you go into creating such things instead of some moronic entertainment, but maybe would be good to think a bit before coding? You can operate Assembler - good. You had an idea - to code plane-based tiny intro in grayscale - great (just like me previous month). And you have done it - the result would be acceptable as 64B intro, let's say 128B in your case. I don't require y0bi skills, but your code is horrible. If you decided to make 256B, was it really hard to see other similar prods first, check their sources, draw some OBVIOUS conclusions, learn some BASICS about hard code?
Code:
FORY:FLD [DDYMIN]
FIDIV [DWY]
FSTP [DDW]
FLD [DDW]
FMUL [DDRESX]
FSUB [DDCAMY]
FSTP [DDV]
FLD [DDW]
FMUL [DDXMIN]
FADD [DDCAMY]
FSTP [DDU]
MOV WORD[DWX],0
FORX:FLD [DDU]
FISTP [DWU]
FLD [DDV]
FISTP [DWV]
MOV EAX,[DWU]
XOR EAX,[DWV]
AND EAX,0FFh
MOV [DWC],EAX
FILD [DWC]
FIMUL [DWY]
FDIV [DDRESY]
FISTP [DWC]
MOV EAX,[DWC]
SHR AX,2Man, tell me, WHAT THE FUCK IS THIS?
Code:
FLD [DDU]
FADD [DDW]
FSTP [DDU]
INC WORD[DWX]
CMP WORD[DWX],320
JB FORX
INC WORD[DWY]
CMP WORD[DWY],200
JB FORYMan, tell me, WHAT THE FUCK IS THIS?
Code:
DDRESX DD 320.0
DDXMIN DD -160.0
DDYMIN DD 100.0
DDRESY DD 200.0
DWX DW 00000
DWY DW 00000
DWU DD 00000
DWV DD 00000
DWC DD 00000
DDCAMY DD 0.000
DDU DD 0.000
DDV DD 0.000
DDW DD 0.000Man, tell me, WHAT THE FUCK IS THIS?
I fully understand that there are your first steps in 256B introcoding, I fully appreciate that you go into creating such things instead of some moronic entertainment, but maybe would be good to think a bit before coding? You can operate Assembler - good. You had an idea - to code plane-based tiny intro in grayscale - great (just like me previous month). And you have done it - the result would be acceptable as 64B intro, let's say 128B in your case. I don't require y0bi skills, but your code is horrible. If you decided to make 256B, was it really hard to see other similar prods first, check their sources, draw some OBVIOUS conclusions, learn some BASICS about hard code?
I think rain_storm is trying to improve his low size coding skills. this one is acceptable for me (piggy). I always prefer maybe not perfect but original code instead of stolen stuff. so, I disagree with Pirx at that point. first, follow rain_storm's way and learn it by yourself (of course you don't have to release all of your learning steps), then check how others do the magic.
i like antipatterns. thumb up
Pirx: chill down man, just because someone doesn't practice your fetish well doesn't mean you need to snap :D
I've a terrible admiration for this kind of little programs.
Thanks for let me thinking on how to do the same.
Thanks for let me thinking on how to do the same.
garg, some misunderstanding here I think. I'm composed, more than you can suspect. What is this comments forum for? Would be better if I just wrote "This is lame" and gave thumb down? Or maybe should I lie "Great 256B, well coded"? My comment fits perfectly to what the intro presents.
rain_storm, I hope you haven't take my uppercase words wrong. My intention wasn't to revile your work or insult you - on the contrary, I wanted to force you to code better. Your intro shows EXACTLY how 256B should NOT be done, it's kinda opposite to 256B essence. I noticed that with DBF guys you are still working on this prod, it's 2x smaller at the moment, so why you released it? Here is hard introscene, not "How to make loop in asm" school, and we already have too many bad intros around. Do you think releasing unfinished/unpolished/mommy-i-can-put-pixels prods is ok? Do you think there is space for sloppiness? Answer yourself. I wish you nice coding, and as much fun with tiny intros as I have.
rain_storm, I hope you haven't take my uppercase words wrong. My intention wasn't to revile your work or insult you - on the contrary, I wanted to force you to code better. Your intro shows EXACTLY how 256B should NOT be done, it's kinda opposite to 256B essence. I noticed that with DBF guys you are still working on this prod, it's 2x smaller at the moment, so why you released it? Here is hard introscene, not "How to make loop in asm" school, and we already have too many bad intros around. Do you think releasing unfinished/unpolished/mommy-i-can-put-pixels prods is ok? Do you think there is space for sloppiness? Answer yourself. I wish you nice coding, and as much fun with tiny intros as I have.
Quote:
Do you think releasing unfinished/unpolished/mommy-i-can-put-pixels prods is ok
Yes.
This wasnt running to mommy to show off to someone who cares. The last tiny code I released was months ago mommy has been getting alot of updates since then. But I agree that there is no room in 256b to get sloppy. I was very happy with myself this time and am still proud of this 256b version. I have been getting a lot of help over at DBF and I appreciate that forum, there are so many great coders over there that will take the time to help. hellfire was happy to show me where over 128 bytes could be shaved off this. And I thank him for taking the time to show me. It really made my coding look bad but it also showed me where I can improve myself. Next time I will come back better and smaller.
it looks good
i like it! motivational thumb!
Nice first 256b, but it could've easily been done in 128b...
...though I'm glad to see the DBF guys are still going strong and helping people improve and also that they've helped you fix your mistakes for next time :)
I look forward to your next prod, but for now, pig.
...though I'm glad to see the DBF guys are still going strong and helping people improve and also that they've helped you fix your mistakes for next time :)
I look forward to your next prod, but for now, pig.
we're all learning during whole life
gruik.
Could be done in 64b. See : Plain Monday by wamma, Meanwhile by wamma & asahikawa by yours truely
Could be done in 64b. See : Plain Monday by wamma, Meanwhile by wamma & asahikawa by yours truely
xor textures are always winners, however due to lack in the credits department( "c = (((u xor v) & 255)/resY)*y " ring a bell? :P) im gonna have to piggy it
Sorry mind I forgot with all the rush to get this out the door of course all credit goes to you for making this look good (a whole lot better than it originally was)
as pirx and rain_storm said
oh well (=
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 !