Bitmap loading

[Zaknafein]

Ok I have a question about loading bitmaps into your game from disk. I'm designing an adventure game that loads a new bitmap background for each screen.

Here's the code I'm useing ScreenArray is an array of strings that store the names of the bitmaps that make up background pictures.

frmSprites.picBackground.Picture = LoadPicture(App.Path & "\Dat\Bak\" & ScreenArray(LocX, LocY) & ".bmp")

There is a noticable delay loading new screens when you first start the game, however once you go to a certain screen it always loads faster if you need to go back to it again later even though it goes through the same reloading process again. Does anyone know how I can speed this process up right from the start of the game?

[Sastraxi]

It's stored in memory once you load it, for the remainder of your program, until you delete it (how, I don't know, but I haven't looked into it). You won't be able to speed this up as there is no faster way to load from the disk. Maybe there is, but this might be lost with the overhead of programming it in VB. I suggest just letting your users know there's going to be a wait.

[Zaknafein]

Well I would like to know the exact dynamics of how it works, because unlike memory dc's you can perpetually load new bitmaps into a picture box as the program runs over and over again without running out of memory. So at some point I assume it replaces memory locations with new bitmaps, the fact that I can't fully understand how it does this is what bothers me.

[Sastraxi]

Well I'm pretty sure 90% of the time is seek time, and that Windows has an internal handler, keeping seek points in memory to oft-used files. Thus, it would be faster loading it the second time.

But, I do fully agree with you. I hate not understanding how something works

[dogfish227]

one thing that may sped up the process is to have all your pictures in one file and have the top,left of where each is and then just load them to the pic boxs once and from then on always get them useing there location in that one picture to do this you will have to use bitblt or several set pixel calls if you dont already know this you can learn it or just do it another way.

for this youll need another picbox to store the pics in.

this may be faster but if you have alot of picture and they arent all used alto it may actually be slower im not shure

[Zaknafein]

Well that would produce one long load time at the start as oppose to many short ones, that would be preferable except that it would cost a huge amount of memory to hold that many backgrounds at once. They are 600X480 and there are around 100 of them. thats 64000 pixels by 480 pixels. I'm trying to keep it down to 32 megs minimum system requirements I doubt 32 megs could hold that much graphical information at once.

[dogfish227]

yeah for your situation(when you have lots of pictures) thats probally not the best way to do it

[Steven8]

A Picturebox will support .jpg's and they are a fraction of the size. Just Convert your .bmp's to .jpg's. Maybe that'll help since it won't take up as much memory.

[Valkan]

Originally posted by Steven8
A Picturebox will support .jpg's and they are a fraction of the size. Just Convert your .bmp's to .jpg's. Maybe that'll help since it won't take up as much memory.

I don't think so, Sure it will take less space on the disk, but once the jpg will be loaded (decompressed) it will probably take as much space in memory as the bitmap used to create the jpg.

As for the loading thing... could it be possible that using the LoadImage API and then blitting it to your picture box be faster? When you use vb's LoadPicture, vb as to convert your image into an iPictureDisp object and then setting it to the Picture object of the PictureBox ( wich i'm pretty sure is something that slows down the process of having your picture inside your picture box.)

If i'm wrong... well i really don't know what you could do. I can only say that using tiles to create your backgrounds (unless they are to much different one from another) would have been a bether way and would have really reduce the size of the bitmaps you need to load.

- Valkan

[Zaknafein]

Thanks for all the replies. What I've found to be the best method (although it may sound kind of dumb, is just to initalize the game by having all the backgrounds load into the picture box one after another. That way as Sastraxi said:

"Windows has an internal handler, keeping seek points in memory to oft-used files. Thus, it would be faster loading it the second time."

Without wasteing memory windows gets the idea that it might have to find that file again soon so the seek time drops down significantly, because it seeks through those files first. 100 bitmaps doesn't put a dent in the efficiantcy of this but I imagine a really huge amount like 10,000 would. But I dont' need that many so problem solved for now.

[Sastraxi]

Just to let you know, as you get farther along in your programming, you'll realise how useful Tile Engines really are. You'd never have this problem

[Zaknafein]

Yeah but my game is similar in nature to the old sierra or lucas arts adventure games. Every background is hand drawn and compleatly unique so I can't really get away with using tiles.