Author Topic: Loading vs paging in (Read 1909 times)

Wanderer · **on:** May 08, 2008, 02:44:14 am

Quote

I have some questions about graphics files and FS.. I have not earlier coded well anything graphics related on language at the level of C/C++ so i have no real knowledge how this should be handled... But as i was browsing the code to check how 'stuff is made' i noticed that almost all hud bitmaps are paged in. When I wrote the coloring and bitmap thing with the radar images didn't really do this. Still in my tests the radar bitmaps worked quite nicely after initial setbacks. Also on a brief glance it seemed like scripted bitmaps would rely on only bm_load and unload stuff. So what is the catch? Especially with FS that is.

I have so far asked about this from people i have come across in the IRC and also from Karajorma and Goober but haven't got any definitive answers yet. I started looking at this when Backslash asked about this but i misunderstood his question.

Wanderer · **Reply #1 on:** May 11, 2008, 02:57:41 am

So... No takers?

Nuke · **Reply #2 on:** May 11, 2008, 04:37:51 pm

i get that too, did all the coders take a vacation or something?

WMCoolmon · **Reply #3 on:** May 11, 2008, 11:18:47 pm

My understanding is that _load just loads the bitmap's info, page_in loads the actual content. They're still automatically paged in on use, but if they first appear during a mission they will slow things down (if they're big, or a large number have to be loaded in at once.)

Wanderer · **Reply #4 on:** May 14, 2008, 09:40:29 am

Ok.. Thanks from the information... I take i could add a page in function for those and page in (and out) the ship images alongside rest of the radar stuff. Though given the small size of the images used in radar thingye that probably shouldn't cause problems in any case.