Well the map file to texture is a DirectX command so I'm not really sure what is going on there. You basically have three factors...
The file size which probably has the least impact since .jpg's and .png's are generally compressed. Most likely any memory used (for loading, and work space) is released once decoded.
The color depth and screensize of the source (aka the file).
The color depth and screensize of the destination. Color depth = 16bit RGB. Screensize matches the source file, pretty much.
I'm not sure what the OS (xbox) / DirectX does with the actual texture. Whether it keeps it in memory and then just blits it to the screen memory, or how that works. So this may or may not be a factor.
I only personally ran into memory issues twice..
1. Some hi-res Box/Art for the Odessey2.
2. Some hi-res manual sacans for the Odessey2.
One of them seemed more an issue of the actual dimensions of the image and not how much memory it used. But I'm not really sure since it was DirectX that was rejecting it and it was not exactly giving me a whole lot of details on why it rejected it.
What was disconcerting about the above mentioned scenario was that it was happening with the O2 emulator which is not exactly a memory hog.
To be honest HQ artwork is gonna have diminishing benefits (I'll leave it to the math experts cause I'm lazy). But you figure at SD you are at 640x480 and the boxart is only gonna take up a small portion of that unless you stretch it to the full screen. Then the next two highest up are 720p and 1080i. So you get a little more detail. But 1080i REALLY pushes the performance and memory of the Xbox.
In fact some people may consider HQ box-art about as pointless as others may consider titles screens, dual previews, movie previews, and the synopsis.
I wouldn't worry to much about title screen size anyways. Most emulated systems don't really go any higher than 320x400 anyways.
daleswanson brought up a good point. Could there be a way that the emu could just auto save the configurations for new roms if you enter the game by pressing B? I really don't care for my own setup now since I've pretty much got all the saves done, but I could see how this could be valuable for new people who dont' have the Xtras or don't take the time to FTP over the thousands of saves I'll be uploading. I was wondering if that'd be difficult to code in?
Pressing B at the games select screen, exits you out to the main menu. Not sure what your getting at here. Sure we could add an option in the "General Options" menu to "Use configuration defaults on unconfigured games" or something like that. Then the user could just press "X" to "Force the configuration screen to come up" if the above added option was set to "Yes".
I've been wanting to work on some means of transferring configurations easily way back since I started Atarixlbox. But it never came to fruition and the computer based emu's seem to be the only ones that need it the most. So I figured the point was kinda moot unless someone was willing to sit down and make configurations.
It is likely, however, that something may come into existance on my work with winuaex. If waal comes thru with his configurations. Now I just got to get over all these nice little muscle aches created by the nice little flu I caught. This post has been edited by madmab: Nov 1 2009, 03:58 PM