|
Atari coding BBS
Re: x+y + offset in screen |
Posted by: nerve
|
Mar,10.2009-13:22
|
wiztom: i should probably consult a cycle table and do some profiling, but as there is no barrel shift on 68000 one has to take into account the extra cycles for the shifts. However this stuff is getting vague now - i really need to refresh it!
gloky: this used to be one of my fave things to mess about with on the ST back in the mid 90s... you can do some neat stuff by enlarging the table to say 320x200, let it contain both offsets and a pixel, and with smc you can get down to just a couple of instructions after setup.
Why you say?
For fun damnit! :)
Another approach, favoured by some other scandinavians and better for cached cpus, are filling these offsets into jumptables. The more RAM you are willing to waste, the less setup code...
-Kåre (tired but sober:) )
|
[All messages in this thread] [Start new thread]
Topic
|
Posted by
|
Date
|
x+y + offset in screen
|
gloky
|
Mar,08.2009-17:19
|
Re: x+y + offset in screen
|
Randy
|
Mar,09.2009-13:19
|
Re: x+y + offset in screen
|
nerve
|
Mar,09.2009-14:03
|
Re: x+y + offset in screen
|
gloky
|
Mar,09.2009-18:58
|
Re: x+y + offset in screen
|
gloky
|
Mar,09.2009-19:04
|
Re: x+y + offset in screen
|
gloky
|
Mar,09.2009-19:21
|
Re: x+y + offset in screen
|
wiztom
|
Mar,09.2009-22:09
|
Re: x+y + offset in screen
|
nerve
|
Mar,10.2009-13:22
|
Re: x+y + offset in screen
|
wiztom
|
Mar,10.2009-23:13
|
Re: x+y + offset in screen
|
glokyy
|
Mar,10.2009-22:58
|
Re: x+y + offset in screen
|
gloky
|
Mar,10.2009-23:00
|
Re: x+y + offset in screen
|
h3rrv
|
Mar,11.2009-11:08
|
Re: x+y + offset in screen
|
gloky
|
Mar,11.2009-17:41
|
Re: x+y + offset in screen
|
nerve
|
Mar,13.2009-12:44
|
Re: x+y + offset in screen
|
Defjam
|
Mar,15.2009-23:23
|
Re: x+y + offset in screen
|
nerve
|
Mar,16.2009-14:31
|
Re: x+y + offset in screen
|
gloky
|
Mar,21.2009-14:49
|
What's the anti-troll code? That's your personal code to be able to add comments and messages on the dhs.nu site.
Don't have a code or forgot it? Fix it here.
|