|
Wildcat by DMA [web]
[nfo]
|
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|||||||||||||
|
popularity : 65% |
|||||||||||||
alltime top: #2066 |
|
|||||||||||||
added on the 2015-11-24 14:47:26 by KK  |
||||||||||||||
popularity helper
comments
Great demo!!! Keep up the good work!! Music, gfx, style. I love it.
Awesome!
Amazing! Effects in this demo made some people speachless during the party :) Also great msx and flow! Lookig forward for "wildcat" release ;) All the best...
That wolfenstein looks amazing...
absolute amazing ass kicker ;) KK rulez! more! mooooooore!!
mein amiga!
sheriff: "Wildcat" was also "released" last saturday. :)
OMG! and this crazy speed in Wolfenstein effect! Massive!
Great! Welcome to the Amiga scene, KK! And congratulations on both releases. :)
Great demo, superb effects!
Well done KK, great demo and congrats on becoming father:) Go Wildcat go!
what blueberry said!
nice wolfenstein, great demo
What B&B said :) Congratz!
What a great firstie on Amiga. Amazing wolf-engine, but also digged the colourful blitter tornado. Loved it on the bigscreen. Your second best release in recent times.
lol, I guess congrats on upcoming "delivery", krzysiek ; D
I enjoyed this little demo!
Nice to see you on the Amiga as well - following the Jay Miner machines! :)
why not ks 3.1? my a600 is sad now :(
wysiwtf: I have no idea. I'm using Hannibal framework with Blueberry startup code and even the example demo in the framework doesn't work on KS 3.1.
As soon as fixed for the framework would be released I could incorporate that fix, but right now I'm complete n00b when it comes to Amiga system/kickstart-related issues.
As soon as fixed for the framework would be released I could incorporate that fix, but right now I'm complete n00b when it comes to Amiga system/kickstart-related issues.
that's great, whoot! works with KS1.2, which is all that matters :P
Some cool looking effects although not much of it was running in one frame.. Impressive Wolfenstein, the chaoszoomers were a not the best I've seen. Looking forward to more from you on OCS, please hook up with a decent pixel graphician though ;)
Kinda ugly but some proper code in there!
Very nice and a hell of a surprise! =)
Lovely, lovely zoomers. And the wolfenstein. And everthing else.
Very good demo. Great effects and good music. To fully happiness is missing only a few pixel arts.
Powerful demo with good pacing and a lot of action and a fitting tune. Even if the code is not optimized and framerate could be improved, it's still impressive code, "firstie" or not! I second the suggestion for getting a pixel artist on board next time, but that's a minor point overall.
You sure are a fast learner and a very productive person!
You sure are a fast learner and a very productive person!
Hey KK, I looked at this, and it seems that you are not setting DDFSTRT/DDTSTOP/DIWSTRT/DIWSTOP/BPLCON2/BPLCON3, and those are probably initialized differently in the various setups.
I found this by launching 2 instances of WinUAE - one working and one not working, and pressing shift+F12 to see in the debugger - you can see that those registers are different. The values you need for a 320x256 screen are
DIWSTRT($008e) = $2c81
DIWSTOP($0090) = $2cc1
DDFSTRT($0092) = $0038
DIWSTOP($0094) = $00d0
BPLCON2($0104) = 0
BPLCON3($0106) = $0C20
I'm not 100% sure the last two are needed, but these days I prefer to set all registers to cover myself. Try this and hopefully it helps (in the WInUAE debugger you could test it by directly writing to the registers with commands like this: W dff08e 2c81.w)
Other than that, really good job on the demo. I will check if my example demo has the proper setup, too.
I found this by launching 2 instances of WinUAE - one working and one not working, and pressing shift+F12 to see in the debugger - you can see that those registers are different. The values you need for a 320x256 screen are
DIWSTRT($008e) = $2c81
DIWSTOP($0090) = $2cc1
DDFSTRT($0092) = $0038
DIWSTOP($0094) = $00d0
BPLCON2($0104) = 0
BPLCON3($0106) = $0C20
I'm not 100% sure the last two are needed, but these days I prefer to set all registers to cover myself. Try this and hopefully it helps (in the WInUAE debugger you could test it by directly writing to the registers with commands like this: W dff08e 2c81.w)
Other than that, really good job on the demo. I will check if my example demo has the proper setup, too.
any chance to share the original protracker ?
@Hannibal: I'm doing exactly what you written. From init code:
I'm doing this once right after start of main demo function when system should be no longer running.
@asle: The module is in Retrokomp/Load Error downloads. It won Amiga Music compo at the same party. :)
link
Code:
BPLCON0 = 0x0201;
BPLCON1 = 0;
BPLCON2 = 0;
BPLCON3 = 0x0C20;
COLOR00 = 0;
COLOR01 = 0;
DMACON = 0x8000 | (1<<10); // blitter nasty
DIWSTRT = 0x2C81;
DIWSTOP = 0x2CC1;
DDFSTRT = 56;
DDFSTOP = 208;I'm doing this once right after start of main demo function when system should be no longer running.
@asle: The module is in Retrokomp/Load Error downloads. It won Amiga Music compo at the same party. :)
link
...........
KK, one blue sky idea without knowing the context of your code: where is custom? Usually that is another $dff000 to be added to all of the above values.
Another Amiga debut in 2015! Great code, nice music and a bit 'rough' graphics :) Good job and cool surprise in Danzig Demo Compo.
@noname: That is one of the possible future optimizations I was referring to - the demo uses full addressing for EVERY hardware access (except in startup/framework). I don't think I want to know how many cycles I'm wasting this way. :)
@slayer: Well, I did a lot of Amiga coding back in the time, but 99% of it was pure AMOS and I never got to proper low level HW programming back then.
@slayer: Well, I did a lot of Amiga coding back in the time, but 99% of it was pure AMOS and I never got to proper low level HW programming back then.
@KK
If it's your firstie demo then it's really great. You've got great potential mate :) I hope to see more from you in the future.
If it's your firstie demo then it's really great. You've got great potential mate :) I hope to see more from you in the future.
Oh yes!
I do not remember ever seeing a Wolfenstein clone that would work well as a part of a demo; it is not working for me here too. However, the use of background gradients to colour the noisy blitter feedback is daring and really makes this stand out and the music is pretty nice too.
KK, I tried to debug a bit further (this is kinda fun!) and saw that yes, your code actually does write to the proper registers
However, at that point the copper DMA is still enabled, and the system copper is still set, so the next frame the system copper runs, and it overwrites those values. Even though your vblank interrupt sets a new copper list, the system copper has already been started.
I imagine it works with some kickstarts because they set them to the same values you need. You could fix it by for example either
1. instead of setting the registers with the CPU, you could put it in a "setup" copper list and load that into COP1LC. It would automatically be kicked the next frame you run. Optionally you could kick it right away
2. turn off copper DMA before you set the registers, set your real copper, and then reenable the dma or
3. just set them in the first "real" copper list you have. That's what I have traditionally done
Side note: I see that after setting the copper (in dff080), you do clr.w dff088. Probably fine for you, but there are 2 details to know when you do this:
1. writing to cop1jmp/cop2jmp from the CPU is dangerous if the blitter is running because it can mess up the blitter destination.
2. The copper automatically starts at the beginning of each frame, so if you just set the copper pointer during the previous frame you don't need this
However, at that point the copper DMA is still enabled, and the system copper is still set, so the next frame the system copper runs, and it overwrites those values. Even though your vblank interrupt sets a new copper list, the system copper has already been started.
I imagine it works with some kickstarts because they set them to the same values you need. You could fix it by for example either
1. instead of setting the registers with the CPU, you could put it in a "setup" copper list and load that into COP1LC. It would automatically be kicked the next frame you run. Optionally you could kick it right away
2. turn off copper DMA before you set the registers, set your real copper, and then reenable the dma or
3. just set them in the first "real" copper list you have. That's what I have traditionally done
Side note: I see that after setting the copper (in dff080), you do clr.w dff088. Probably fine for you, but there are 2 details to know when you do this:
1. writing to cop1jmp/cop2jmp from the CPU is dangerous if the blitter is running because it can mess up the blitter destination.
2. The copper automatically starts at the beginning of each frame, so if you just set the copper pointer during the previous frame you don't need this
Thumb up for the speedy wolfenstein-routine
Yes! I wish there was more firsties of that quality. My personal favourite is the spectrogram effect under the textured cube. With more attention to graphics (logos, colors, palettes) and design (transitions, sync, flow) this could be a killer demo. Music is not my cup of samples, but it kinda fits the rough and understated visuals. And congrats on both releases!!! :-) Nice talking to you at the party.
Like damn how fast is that wolf part!
Very. You need gfx man though :) Music was okay
Very. You need gfx man though :) Music was okay
@Hannibal: Thanks for your findings. I'll definitely check it out. As for cop1jmp, we reached similar conclusions in this thread.
@jazzcat: That was the "rushy production" part. The logos were made with some "cool text" generators on the web, so they don't really count as real logos. ;) And it was nice talking to you at the party, too.
@jazzcat: That was the "rushy production" part. The logos were made with some "cool text" generators on the web, so they don't really count as real logos. ;) And it was nice talking to you at the party, too.
The graphics and music didn't really appeal to me, but the code is not bad at all. Therefore - thumb up!
Some great effects. Excellent coding. The design and music could be improved but it's a good demo regardless.
Amazing Wolf 3d on A500 ! It would have been an instant classic if it had some nice pixelart. Great anyway !
music
Totally enjoyable, great job :)
Decent.
good
Quite ugly but faaaast :)
Will you try AGA next time KK ? :)
This one is very F.A.S.T.! The music matches perfectly. Nice fresh effects which show that OCS has still its own charm. Thumb up for the good coding.
cool stuff!
On my BPPC060 A1200 (KS3.1) SetPatched to 3.9 is always working (but sometimes with good colors, sometimes with no colors (black screen) and sometimes with bad colors).
Great stuff !
Great stuff !
nice
Nice variations and combinations of classic amiga effects. And wolf engine, too.
3 effects are enough for everyone. Very good!
This is a pretty sweet Amiga intro. OCS and AGA mostly gets lame ass releases lately, and that makes it an outstanding release, however the length and the number of effects don't qualify it as a proper demo. Still a defo thumbup!
niceish.
OCS/ECS too slow for Wolf 3D? Very nice stuff in that demo!
Contrats KK for you firstie on the 3rd generetion VCS! I absolutely dig the feedback zoom effect.
Ah forgot to comment on this. Cool debut on amiga. The design aspect calls for more attention in the future, but there's a lot of promise in this :)
Great Wolf! Rulez! :)
Nice!
outch!
great demo
the wolfenstein part ruins it a bit for me, it's all deja vu and has an unoriginal visual style
the wolfenstein part ruins it a bit for me, it's all deja vu and has an unoriginal visual style
generally cool
but a bit oldschool fx like tornado zoomer, C2P, scroll
And nice to see A500 finally joined Wolfenstein 3D club. 10 years after ST ;)
but a bit oldschool fx like tornado zoomer, C2P, scroll
And nice to see A500 finally joined Wolfenstein 3D club. 10 years after ST ;)
ok
Great !!!
Cool demo
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 !
Sorry for delayed release - we had to debug this on a real machine.
The prod also will not run with Kickstart 3.1 (probably a framework bug).
Have fun!