that looks cool, how does sub-pixel animation work?

Sorry, but it sounds to me like you've been trying only for a short while. Please don't be too impatient. What exactly is the problem? If you want me to tutor you a bit, I'm game, just contact me by private message, we can set up a meeting over IRC or skype or something.

I answered his post before I read yours.  Thankyou for those sprite opcodes you told me about.  I would like to be tutored!

I've looked through many tutorials of high-level languages and non of them tell me any stuff I need to know in making games, nor breaks it down remotely enough.  Hello World? why would I need to know this? I can easily type Hello World in note-pad and get the same result.

If they make these high-level programming languages to make things easier than assembly, why don't they have opcodes such as:

DISPLAY SPRITE: coordinates (123,201), size: 32x32, sprite number 53, 12 frames, 12 fps
COLLISION DETECTION: sprite 17, sprite 15, effect 75
MOVE SPRITE: 5 pixels left, 4 pixels up

Why can't anyone make a language with opcodes like that? because THAT would make video games easy to program.


How exactly would you guys know if assembly really is harder than high-level without knowing assembly?  Does anyone here know both assembly and high-level?  I'm starting to get a feeling that people only think assembly is hard because high-level is hard, and they hear other people saying high-level is much easy compared to assembly, and they think omg!

How do high level languages work?  All the opcodes in assembly are like "MOVE A,B" which moves A into B, and "ADD A,B" which adds A into B.  All the assembly opcodes speak for themselves.  For high level opcodes you have instructions like "int" and "def" and "segren" and "felneb," what the heck do those supposed to do?

thankyou everyone for the advise!