|
-
May 13th, 2001, 10:42 AM
#1
Thread Starter
Lively Member
Size of a game
Hi all of you.
I have a simple question: If I have a lot of surfaces I'm blitting into will this affect the size of my game?
Thank you.
-
May 13th, 2001, 10:44 AM
#2
transcendental analytic
yes, but in considerably more on memory usage, and also more important than the size of the executable.
Use  
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
-
May 13th, 2001, 11:03 AM
#3
Frenzied Member
Surfaces have a small fixed overhead, I don't know how much but I shouldn't think more that a kilobyte, and then there is the actual image data. If you have a 32-bit surface at 800x600, it will be 32*800*600 bits of image data, or 4*800*600 bytes, which is 1875 Kb, or a little over 1.8 Mb. That has to be stored somewhere, either in system memory or video memory, depending where you specify it should and where there is room for it at runtime. If you have lots of large surfaces at high colour depths, you will use up a lot of memory with textures, so if you have lots of textures to load in your game (like more than 10 megabytes maybe, you decide what's acceptable though) you may want to load the surfaces as they're needed and unload ones you don't need while the game is running.
Harry.
"From one thing, know ten thousand things."
-
May 13th, 2001, 12:08 PM
#4
Thread Starter
Lively Member
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote