pouët.net

wertstahl information 429 glöps

• general:
• level: user
• personal:
• first name: Sebastian I.
• last name: Hartmann
• portals:
• csdb: profile
• cdcs:
• cdc #1: Seven Sins by Scoopex [web]
• cdc #2: Der Brockhaus by Setrox [web]
• cdc #3: Sin-intro 2 by Thrust

• demo Commodore 64 spaceout by Offence [web]
• kewl!
• rulezadded on the 2013-11-11 00:49:59
• invitation Amiga OCS/ECS Datorstam - Datastorm 2014 Invitation by Spaceballs [web] & Up Rough [web]
• very nice, consistent and exceptional design. this has a very strong feeling and thus rulez.
• rulezadded on the 2013-10-17 21:09:20
• invitation Commodore 64 Datastorm 2014 Invitation by Genesis Project [web]
• <3
• rulezadded on the 2013-10-17 11:17:14
• cracktro Commodore 64 Iridis-Alpha by Dynamic Duo
• <3 + what zartan said!
• rulezadded on the 2013-10-07 01:43:19
• demo Commodore 64 Fogyish by Samar Productions & Arise
• fast-paced!
• rulezadded on the 2013-10-06 21:37:49
• demo Commodore 64 In Thorn by Sabath
• fx put in context!
• rulezadded on the 2013-10-06 21:35:08
• intro Commodore 64 Simpletro by Flood
• don´t get me wrong, i intended to be encouraging. you can actually use the the idle/main loop to do alot of things that are not time critical and usually you would interrupt whatever the main loop is doing with things that need to happen at a certain time. therefore irqs.
  if you have found many productions using an useless main loop, you are right: thats not an optimal way.
  i am very interested in what you come up with, next :-)
• isokadded on the 2013-09-24 23:03:40
• intro Commodore 64 Simpletro by Flood
• +1 for the beginner´s effort.
  -1 for the fact that you´re lucky that it works.
  
  you have an idle loop jmp c0c1 at c0c1 but you never reach it.
  
  infact, i really wonder where your idle loop is going after all.
  
  since after the cli, you´re normally in the idle loop. but you continue straight into the interrupt routines (see c055 --> this jsr returns (possibly just an init) and then continues into the irq routine!)
  
  you are lucky that somehow the idle strain (the line of operation, that you interrupt by your interrupts) seemingly never reaches your jmp $ea7e!
  because else you would end up with a nice crash.
  
  what i find really interesting is how it can get lost. the idle loop must be stuck somewhere in your interrupt routines which is then constantly interrupted by the irq and just just reaches a dead end.
  
  to see what i mean, write in line c055 JMP $c132
  ask yourself: where does the rts go, that then returns from $c132?
  --> that is your idle loop.
• isokadded on the 2013-09-24 22:05:56
• demo Commodore 64 The Awakening by Covenant
• i really had questionmarks above my head about the lovelessness of the linking
• isokadded on the 2013-09-16 22:11:53
• demo Windows Apocalypse When by Fairlight [web]
• yeah! strong moments of : wtf - which reality is this?!? :-)
• rulezadded on the 2013-09-15 19:45:46