[Iss Mneur]

Having just loaded a Diaspora mission >50 times with a debug build and having to click through the warning about missing the interface art for GR640 twice with every mission I have a proposition.

I realize that just removing the Warning is probably the fastest way stop FSO from complaining about these assets missing, but is this a problem?  Does anyone actually use this resolution?  Should this be a game_settings.tbl flag?  Should I just downgrade the Warning to a log message?

If we do go the game_settings flag route, it would be a flag that basically makes FSO forget that GR640 exists.  It could pick GR1024 as the lowest resolution.

[z64555]

I use it with FSO in windowed mode.

I find it especially useful when some CTD's freeze up WinXP to a point where I can't kill FSO's process. 

I do support going the game_settings flag route, however.

[mjn.mixael]

I know command line flags are generally not recommended anymore.. but might this be a case for a 'Dev Tools' command line flag?

[Iss Mneur]

I use it with FSO in windowed mode.

I find it especially useful when some CTD's freeze up WinXP to a point where I can't kill FSO's process. 

I do support going the game_settings flag route, however.

Hmm, so you would not be able to debug something like Diaspora, which has no GR640 data anywhere?

I know command line flags are generally not recommended anymore.. but might this be a case for a 'Dev Tools' command line flag?

I don't think this is appropriate for a dev tool, because because in cases like Diaspora there is no GR640 data anyway.  Though if enough people say that they do use the resolution, that could change things, and make it such that Diaspora has "bad data" by not having the GR640 stuff.

[z64555]

I use it with FSO in windowed mode.

I find it especially useful when some CTD's freeze up WinXP to a point where I can't kill FSO's process. 

I do support going the game_settings flag route, however.

Hmm, so you would not be able to debug something like Diaspora, which has no GR640 data anywhere?

I wouldn't be able to debug a full mission or campaign of mods such as Diaspora, if that's what your getting at. Framerates in retail builds (on this old laptop) are painful enough as is. 

[mjn.mixael]

The only reason I thought a command line would be best in this case is because this 'feature' seems only useful during debug. Though as I thought through it more, game settings made sense too.

[Nuke]

i once was able to run freespace in a window that was smaller than most icons. it was amusing.

[Dragon]

Would that be possible to resize the main interface files to 640x480? Not exactly the most optimal solution, but I think it'd work with today's computers. I think it'd work as default behavior in case 640x480 files aren't found.

[Iss Mneur]

Would that be possible to resize the main interface files to 640x480? Not exactly the most optimal solution, but I think it'd work with today's computers. I think it'd work as default behavior in case 640x480 files aren't found.

While probably the best solution, the problem is that in order to implement the feature, FSO would have to learn how to resize images, which as far as I know, would require another library, though someone more familar with the graphical capabilities of FSO would probably be able to comment with more authority.

[Nuke]

what about just throwing together a command line util to scale down all the images for you.

[chief1983]

Uhm, I kinda figured it already scaled up pretty well, even to non-4:3 resolutions.  I always wondered why scaling down a bit would be any trickier (and it's not, as 1024x720 now uses the 1024x768 interface art, which means it's being scaled down, not up).