|
It makes me shake by Spice Boys [web]
[nfo]
|
||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|||||||||||||||
|
popularity : 60% |
|||||||||||||||
alltime top: #4984 |
|
|||||||||||||||
added on the 2007-04-01 08:38:31 by evil  |
||||||||||||||||
popularity helper
comments
<moredhel> no STE: fullscreen, Fullscreen Big Scroll, Rasters, and 8khz music
<moredhel> and big sprite
<moredhel> still makes me shake :)
<moredhel> and big sprite
<moredhel> still makes me shake :)
by the way- it says "FUCKINGS TO TITAN" in the scroller... wish i could thumb this up again!!!!1 :)
gr00vy
Yep nice screen
nice screne
Thanks for the fuckings :)
Well, I somehow like it. If I can find the time, I will try port it to my Atari XL. Atari rulz, no matter what the suffix is ;-)
thumbs up for moredhel. hope me smokes more weed and watches dis demo!
who is that pretty girl ?
wow, she is so beautiful :)
wow, she is so beautiful :)
All my favorite effects in one screen! Top Stuff!!
nice...
spiceboys rule the oldschool!
btw.
scanned babe > manga babe
just so you know
scanned babe > manga babe
just so you know
ahahahha. "uberdemo with c2p fullscreen dualplayfield blablablala" ;)
Nice :) And it has a cube \o/
boobs
nice one.
Fine Stuff :D more !!!
well done!
cool, the first really good one by the spiceboys!
nice one :)
Would have been a nice addition if the picture of the girl used 8 colors per scanline instead of 8 colors in total.
I haven't checked the prod in a debugger nor with a TOS <1.6.
If this is really a STe prod, it is straightforward to code and ~70% of the CPU is unused. Not that it is a bad thing since the prod still look nice.
I haven't checked the prod in a debugger nor with a TOS <1.6.
If this is really a STe prod, it is straightforward to code and ~70% of the CPU is unused. Not that it is a bad thing since the prod still look nice.
nice intro
far too cool screen for being made by a fakegroup
That's one smooth babe, i say. ;)
STF or STE ?
If it's STE, absolutely no work involved...
If it's STF on the other hand it's a respectable effort.
I reserve the (rulez) or (piggy) for when somebody will clearly state if it's STE or not :)
If it's STE, absolutely no work involved...
If it's STF on the other hand it's a respectable effort.
I reserve the (rulez) or (piggy) for when somebody will clearly state if it's STE or not :)
the spice boys website says it's STE...
Dbug: this demo was meant as a joke for Moredhel, nothing more :)
dbug: no work to get an STe to display overscan? i beg to differ. (that is, maybe i'm missing some of the ste features?)
Dbug:
It is STe, why do you think I added it as STe otherwise? :)
It uses hardware scroll in the intro, dma sample playback (25kHz) in the mainpart and screen address counter writes for the split parts.
It's only made to practise synclock coding a bit, and get Moredhel to shut up. He (Moredhel) has been incredibly annoying the last months shouting over and over that me nor Keops can code a "total fullscreen with dual playfields and wiztom quality replay". So I did it here. It has the Spiceboys label just cause it's not very serious.
And to sum up; yes it was some effort as it's my first release using this kind of coding and I had to study some hardware bits I've never done in earlier prods. If I had to do it again it would of course be a lot easier now that I know where the hurdles are. I would estimate about 50% of the CPU is free, or nop nop nop nop ;-)
It is STe, why do you think I added it as STe otherwise? :)
It uses hardware scroll in the intro, dma sample playback (25kHz) in the mainpart and screen address counter writes for the split parts.
It's only made to practise synclock coding a bit, and get Moredhel to shut up. He (Moredhel) has been incredibly annoying the last months shouting over and over that me nor Keops can code a "total fullscreen with dual playfields and wiztom quality replay". So I did it here. It has the Spiceboys label just cause it's not very serious.
And to sum up; yes it was some effort as it's my first release using this kind of coding and I had to study some hardware bits I've never done in earlier prods. If I had to do it again it would of course be a lot easier now that I know where the hurdles are. I would estimate about 50% of the CPU is free, or nop nop nop nop ;-)
earx: Granted, doing overscan on STe isn't trivial but it is much easier to do hardscroll/split and play a sample using the DMA on STe than doing synch scroll in overscan and replay a sample on STf
p01:
Overscan on STf is exactly the same as STe.
Playing an STf sample in overscan isn't really tricky either as you already have a static interupt. We chosed STe audio here because the Wiztom replay Moredhel refer to is STe. Somehow Moredhel belives that the Braindamage music uses some magic fast tracker player from Wiztom, when it is in fact just DMA samples.
Using syncscroll instead of hardscroll would be harder, no doubt and decrease the visible scanlines by 5-7 lines more. But seeing it already uses STe audio, it seemed pointless to decrease the resolution and complicate things further.
And finally, I'm not sure the splits can be made on STf. Total 208*69*2 bytes to copy each vbl (clear+data) which is about 28k. Also don't forget that there are 4.3kbyte/vbl colour copies, 1kbyte/vbl cube copy, 1kbyte/vbl scroller copy and 416x5 roxl (can be prerendered I know, but it isn't). So in total it would be 35k data just to copy, nah I'd say it's probably not doable on STf when there are 274 synclocked scanlines, and 273 of these do overscan.
Overscan on STf is exactly the same as STe.
Playing an STf sample in overscan isn't really tricky either as you already have a static interupt. We chosed STe audio here because the Wiztom replay Moredhel refer to is STe. Somehow Moredhel belives that the Braindamage music uses some magic fast tracker player from Wiztom, when it is in fact just DMA samples.
Using syncscroll instead of hardscroll would be harder, no doubt and decrease the visible scanlines by 5-7 lines more. But seeing it already uses STe audio, it seemed pointless to decrease the resolution and complicate things further.
And finally, I'm not sure the splits can be made on STf. Total 208*69*2 bytes to copy each vbl (clear+data) which is about 28k. Also don't forget that there are 4.3kbyte/vbl colour copies, 1kbyte/vbl cube copy, 1kbyte/vbl scroller copy and 416x5 roxl (can be prerendered I know, but it isn't). So in total it would be 35k data just to copy, nah I'd say it's probably not doable on STf when there are 274 synclocked scanlines, and 273 of these do overscan.
Heheh.
This intro needs bouncing big scroll(Dim screen).
Yeah, next time i'll be even more annoying so my swedish friend can code another Moredhel intro ;)
Time to roll a ciggy.
-Moredhel Boozing Society (MBS)
This intro needs bouncing big scroll(Dim screen).
Yeah, next time i'll be even more annoying so my swedish friend can code another Moredhel intro ;)
Time to roll a ciggy.
-Moredhel Boozing Society (MBS)
I didn't know about the Moredhel arguments. :) One must be brain damaged to not figure the music in Braindamage is a bunch of samples played with the DMA. At best they are unpacked on the fly but that's definitely not a tracker.
No need to split. Consider the black-ish parts as sprites displayed (sp?) on top of the overscan pic, for the next frame only parts of the "sprites" must be reverted to original picture.
- The big 'sprite' is 384x70 = 13440 bytes ( if done in 4 bpl, 10080 bytes if done in 3 bpl )
- The scroll can be rendered on a single bpl and is 384x5 = 960 bytes.
- At most 40 scanlines ( rough estimate ) of the original pic must be reverted = 7680 bytes.
I have no idea how much time it takes to play a sample on STf :\
Not that I have the skills to do it but it seems possible on STf.
No need to split. Consider the black-ish parts as sprites displayed (sp?) on top of the overscan pic, for the next frame only parts of the "sprites" must be reverted to original picture.
- The big 'sprite' is 384x70 = 13440 bytes ( if done in 4 bpl, 10080 bytes if done in 3 bpl )
- The scroll can be rendered on a single bpl and is 384x5 = 960 bytes.
- At most 40 scanlines ( rough estimate ) of the original pic must be reverted = 7680 bytes.
I have no idea how much time it takes to play a sample on STf :\
Not that I have the skills to do it but it seems possible on STf.
Just to avoid any misunderstanding, I'm not dissing the prod or the work behind. This intro did make me shake. I'm just curious to figure if it is doable on STf.
p01:
Yes you can optimize the clearing by using the highest movement speed as max. But it wouldn't be as flexible then.
Besides it is 416 width, not 384 (some emulatorcrap only shows 384 so I guess that's why you did that calcul). And you need to clear the scroller bg, which is 9 lines. STf sample can use more or less speed depending which quality you want. 4-bit 16kHz replay is quick, one move.l (an)+,(an) per scanline should do the trick.
Anyway, time to code something decent and forget about this crap.
Yes you can optimize the clearing by using the highest movement speed as max. But it wouldn't be as flexible then.
Besides it is 416 width, not 384 (some emulatorcrap only shows 384 so I guess that's why you did that calcul). And you need to clear the scroller bg, which is 9 lines. STf sample can use more or less speed depending which quality you want. 4-bit 16kHz replay is quick, one move.l (an)+,(an) per scanline should do the trick.
Anyway, time to code something decent and forget about this crap.
And I forgot to add; there might be a little memory issue on STf, if it should still run in 1MB. The chick is 200k in size, if you should be able to clear it, you need a second copy in memory.
Also, the sample player above means one long per sample, on STe it's one byte per sample. So I think it would be 800k sample data instead of 200k. So the replay has to be made slower to optimize the size. Something like move.b #9,(an) ; move.b (an)+,2(an). And at this rate, registers becomes a valueable resource too, limiting movem data copy a lot, hence slowing down the graphics copy a lot.
Ok, that was all. Now back to Qed :)
Also, the sample player above means one long per sample, on STe it's one byte per sample. So I think it would be 800k sample data instead of 200k. So the replay has to be made slower to optimize the size. Something like move.b #9,(an) ; move.b (an)+,2(an). And at this rate, registers becomes a valueable resource too, limiting movem data copy a lot, hence slowing down the graphics copy a lot.
Ok, that was all. Now back to Qed :)
Oh, my calculations were based on the screenshot.
Since when demos are flexible ? :p
No need to clear the scroll bg, set half of the colors to black, the others to the color used by the scroller at each scanline. Just like the 8px pattern.
Depending on when the copies are done, you might not need to swap screens.
Thanks for the insights.
Since when demos are flexible ? :p
No need to clear the scroll bg, set half of the colors to black, the others to the color used by the scroller at each scanline. Just like the 8px pattern.
Depending on when the copies are done, you might not need to swap screens.
Thanks for the insights.
and if the CPU times allows it you can copy the parts of the chick that will be overwritten by the sprite. So you save ~180k
Cool to see nice girlz in overscan :)
I want more d'elle ! Muhahaha...kuf...kuf...hahaha !
very decent stuff! maybe its easy, maybe its hard - but the shaded cube does look good.
Hopefully a taste of great things to come on the STe.
Yop, that makes me shake!
Too bad it was released under fake name...
Too bad it was released under fake name...
Maybe that intro should be converted to CPC+ hahahaha. :D
Dope!
What gwEm said.
<3 Boobz & Kubez <3
=)
yeah well, not enough variations
Yeah, i managed evl to code an intro against me.
I was succesfull. However, this one misses Dim's Big & Bouncing overscan scroller. Maybe of lack of coding?
Im waiting for v2.0 with bouncing....no tits but with a Dim's style.
I was succesfull. However, this one misses Dim's Big & Bouncing overscan scroller. Maybe of lack of coding?
Im waiting for v2.0 with bouncing....no tits but with a Dim's style.
k
One screen that rocks ! =)
rulers gonna rule
Technically superb. I'd like to see more using DMA, scrolling, overscan, etc..
Cool!
what's with atari prods, girls and clichés?
I approve.
Like it!
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 !
Youtube video