pouët.net

Feedback: self-voting is lame and this "demo" should've been left unreleased as there is nothing interesting to see. The code is also not exactly good to put it mildly. Try harder! :)

for first prod

First prod + Amiga + OCS
+ having the balls to pack the .S of your first-timer with it: Welpenschutzupvote.
But i f you want to show something to others that is not exactly a demo you'd release somewhere but more a tryout and want to get (kinda instant) feedback: Try the IRC. ;)

Perhaps we need a new category: Stuff we want feedback on but which is not really worth looking at for the majority of people.

Thumb up for making a demo and countering StingRay's bitter response. Don't listen to the old farts! Make shit you want to make and release all of it here please! :)

Thumb up for the effort. And do more ((=

Here's some feedback on your code: Get rid of all the magic numbers! Use symbolic names for registers, OS routines etc., or you will run into problems when you try to do a bigger project. :)

I know this as we all had to start somewhere and were proud of our first "demo" achievements. :) However, once you gain more experience you will realise that what you created here is a very simple effect and has not much to do with a "real" demo. Friendly advise: Try and experiment but keep the results of these experiments on your HD no matter how tempted you are to show your stuff to the world. After a while of creating these "trial and error" screens you'll be able to create a much more interesting demo/intro, trust me on that one! :)



Some hints:

First of all, get a proper startup-code as your current one will not work when your code is started from non-native screens due to missing WaitTOF() and LoadView() calls. Use a spare address register for the custom base ($dff000) and use indirect addressing [f.e. move.w #0,$dff1fc move.w #$c00,$dff106 etc. -> lea $dff000,a6 move.w #0,$1fc(a6) move.w #$c00,$106(a6)], this will create faster and shorter code. Use local labels instead of global ones when you only need to access the label in a sub-routine (POINTBP: -> .POINTBP), advantage is that you can use the same label names and won't get a "double symbol" error, i.e. you don't need to think of a new name for a common label such as "LOOP" all the time.

Using symbolic names for the hardware registere is good advice too but once you know the registers by heart you can read the code without problems without using "proper" symbol names. :) It's a matter of taste IMHO, I find it much more convenient to use the plain hardware addresses, other people prefer to use the symbolic names.

What okkie said

Ok firsty, not much to see or listen, could have been better with more work to make it an intro, it looks like a test routine. But +1 for source.

something that would've been better left unreleased

Nothing special indeed. My firstie looks worse. So motivational thumbs ;)

Every legend has its beginning!!

What sensenstahl and magic have just said!
Keep kickin'!

Well, it's cool that the firstie is on Amiga :)

Thumbs up for firsty.

glop

keep going :)

motivational thumb

Agree with mr. Norris. Keep on going :)

OK for a first attempt.

Just moving left & right, no music, no graphics - nothing! Get me wrong but just uploading stuff which has nothing to do with demo stuff isn't okay.

Other people trying hard to get something nicely together and spend quite some time... and get just thumbed down because it was 100 times seen, and you? Well, consider yourself lucky...

I'm not thumb down.. it can be considered as some support/motivation. But seriously, don't place here a copperbar next week, okay?

seems you didn't improve much

Must be a joke, no!

1st prod.

Try again.