Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > C64 Coding > AGSP - how to use sprite pointers for both sprites and char gfx
2013-06-10 08:47
Oswald

Registered: Apr 2002
Posts: 5127
AGSP - how to use sprite pointers for both sprites and char gfx

just wondering, would it be possible to change screen after sprite pointers have been loaded and before badline operation ? that would solve the problem of visible sprite pointers :)

badline + 8 sprites that is. there is maybe 1-2 free cycle with RMW but where in the line? cant find vic article with google.

or maybe one could write a multiplexer which only allows 7 sprites where critical.
 
... 20 posts hidden. Click here to view all posts....
 
2013-06-11 20:26
chatGPZ

Registered: Dec 2001
Posts: 11523
Quote:
which kind ? player - level, sprite-sprite, sprite char bullet?

i found player-background the most annoying. eg walking on ground that isnt flat. and managing edges properly so you either dont get stuck, cant walk into the background, and dont hoover in the air. YUCK. special cases galore :(
2013-06-11 20:55
doynax
Account closed

Registered: Oct 2004
Posts: 212
Quoting Groepaz
i found player-background the most annoying. eg walking on ground that isnt flat. and managing edges properly so you either dont get stuck, cant walk into the background, and dont hoover in the air. YUCK. special cases galore
Amen :(

You start out thinking you'll just implement a simple, generic, scheme. A height-map for every character type indicating where the ground lies.
But gradually you get bogged down in details of handling objects with width and height, diagonal tile transitions, fast movement, animation glitches, and so on.

Feel free to share any tips on doing this cleanly and/or efficiently, I could certainly use them.

One cute, albeit rather limiting, trick if you've got a separate collision attribute map is to manually extrude the edges ahead of time and pretend that the player is a point-size object.
2013-06-11 21:04
JackAsser

Registered: Jun 2002
Posts: 2038
Quote: Quoting Groepaz
i found player-background the most annoying. eg walking on ground that isnt flat. and managing edges properly so you either dont get stuck, cant walk into the background, and dont hoover in the air. YUCK. special cases galore
Amen :(

You start out thinking you'll just implement a simple, generic, scheme. A height-map for every character type indicating where the ground lies.
But gradually you get bogged down in details of handling objects with width and height, diagonal tile transitions, fast movement, animation glitches, and so on.

Feel free to share any tips on doing this cleanly and/or efficiently, I could certainly use them.

One cute, albeit rather limiting, trick if you've got a separate collision attribute map is to manually extrude the edges ahead of time and pretend that the player is a point-size object.


Brr yeah, classic problem. Extruding the edge is what we did in Pinball Dreams! Anyway, I can only recommend implementing the algo in a simulator in a higher level language that works flawlessly, then port to asm. It requires a great deal of fiddeling.
2013-06-12 00:43
chatGPZ

Registered: Dec 2001
Posts: 11523
one particular annoying thing to get working right was having platforms on which you can jump by standing under them and jumping up through the gfx. this creates some great deal of interesting problems, considering the player can move horizontally at the same time, or hits an enemy on the platform (which throws him down or something like that). very easy to miss something there and then you can suddenly walk through gfx or get stuck or warped up a dozen pixels (because you hacked another problem away like that...)
i think we solved a bunch of things by fixing the leveldesign around the engines shortcomings there ..... =)
2013-06-12 08:35
Danzig

Registered: Jun 2002
Posts: 446
Quoting groepaz
i think we solved a bunch of things by fixing the leveldesign around the engines shortcomings there ..... =)


Cheater! =)
2013-06-12 08:49
Stone

Registered: Oct 2006
Posts: 177
I don't think that's cheating at all. You can spend your entire life thinking up and fixing pathological cases. It's time consuming enough already to write an engine for the c64...
2013-06-12 15:14
chatGPZ

Registered: Dec 2001
Posts: 11523
Quote:
Cheater! =)

hehe. i think if you take a closer look at a couple of games... you will find out that all of them do it in one way or another =D
Previous - 1 | 2 | 3 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
WVL/Xenon
Didi/Laxity
Dane/Booze Design
Freestyle/Illusion
Exile/Anubis
Mike
Guests online: 170
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Codeboys & Endians  (9.7)
4 Mojo  (9.6)
5 Coma Light 13  (9.6)
6 Edge of Disgrace  (9.6)
7 Signal Carnival  (9.6)
8 Wonderland XIV  (9.5)
9 Uncensored  (9.5)
10 Comaland 100%  (9.5)
Top onefile Demos
1 Nine  (9.7)
2 Layers  (9.6)
3 Cubic Dream  (9.6)
4 Party Elk 2  (9.6)
5 Copper Booze  (9.5)
6 Scan and Spin  (9.5)
7 Onscreen 5k  (9.5)
8 Grey  (9.5)
9 Dawnfall V1.1  (9.5)
10 Rainbow Connection  (9.5)
Top Groups
1 Artline Designs  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Performers  (9.3)
5 Censor Design  (9.3)
Top Coders
1 Axis  (9.8)
2 Sailor  (9.8)
3 Lft  (9.8)
4 Graham  (9.8)
5 Crossbow  (9.8)

Home - Disclaimer
Copyright © No Name 2001-2025
Page generated in: 0.118 sec.