Yeah, it could be paging in from a single large bitmap, I did not think of that!
I''ve implemented a tile based engine and it looks like this will be fine so I''m happy now.
Loading large background graphic
Hi, can you guys clue me in, what is paging?
and what is it in programming terms... i''m a real newbie and need a lot of help, sorry.
and how would you scroll a large bitmap ... larger than screen size if movement was 360?? If you have any examples with a simple source, i would most appreciate it..
thanx~
If all jobs and hope fails... you can still program porno games. There are never too many perverts...
and what is it in programming terms... i''m a real newbie and need a lot of help, sorry.
and how would you scroll a large bitmap ... larger than screen size if movement was 360?? If you have any examples with a simple source, i would most appreciate it..
thanx~
If all jobs and hope fails... you can still program porno games. There are never too many perverts...
My god, this is an old thread. I thought it was a new one, until I saw my name on one of the replies 
Paging, in computer terms, is the act of bringing in data from some sort of external source to a local source as it''s needed. This is generally used in the context of virtual memory, where some of your allocated memory is stored on disk, and ''paged in'' to RAM when you need it, as RAM is faster than your hard disk.
In this context, paging would be loading in the bitmaps as you approach their area, rather than having them all in memory at once.
Scrolling large bitmaps, small bitmaps, is all the same really. Your screen is basically a camera that shows a small portion of the overall world. Therefore you calculate which part of the world you should be seeing by working out the screen''s offset from the world''s origin. From here, you can work out which tiles (whether these tiles are 32x32 or 800x600) need to be onscreen, and draw them, clipping to your screen or play area.
Paging, in computer terms, is the act of bringing in data from some sort of external source to a local source as it''s needed. This is generally used in the context of virtual memory, where some of your allocated memory is stored on disk, and ''paged in'' to RAM when you need it, as RAM is faster than your hard disk.
In this context, paging would be loading in the bitmaps as you approach their area, rather than having them all in memory at once.
Scrolling large bitmaps, small bitmaps, is all the same really. Your screen is basically a camera that shows a small portion of the overall world. Therefore you calculate which part of the world you should be seeing by working out the screen''s offset from the world''s origin. From here, you can work out which tiles (whether these tiles are 32x32 or 800x600) need to be onscreen, and draw them, clipping to your screen or play area.
alright... are there any examples?? especially in DDraw...
and how fast would scrolling a huge bitmap be?? for say a P2 400 64 Mb ram..no3D card btw... damn..
and how fast would scrolling a huge bitmap be?? for say a P2 400 64 Mb ram..no3D card btw... damn..
Im pretty sure that Baldurs Gate is using tiles...
check these site:
"Baldur''s Gate: File Format Hacking Project"
http://www.ugcs.caltech.edu/~jedwin/baldur.html
and:
"Infinity Explorer"
http://infexp.sourceforge.net/
check these site:
"Baldur''s Gate: File Format Hacking Project"
http://www.ugcs.caltech.edu/~jedwin/baldur.html
and:
"Infinity Explorer"
http://infexp.sourceforge.net/
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
