(10/04/2015 06:43 PM)ZiNgA BuRgA Wrote:  You're mostly correct in your understanding.

Rcomage doesn't have a GIM parser yet, so it can't figure out what settings to use.  It currently just makes a guess from what the RCO file is - it doesn't know anything about the GIM.

A possible solution is as you mention - parse the GIM file and write the settings to the XML file.  Then the compile process would need to read in the settings and generate the correct GIM file.

A limitation of that though, is that conversions may not work so nicely as GimConv doesn't support all of them.

//--------------------------------------------------------
//  Rcomage options
//--------------------------------------------------------

	//  GIM formats used by OFW RCO's

option -pspbpp8 {				// First most used GIM format in PSP
	format_style = psp
	format_endian = little
	image_format = index8
	pixel_order = faster
	limit_image_width = 512
	limit_image_height = 512
	output_sequence = off
}
	
option -ps3bpp32 {				// First most used GIM format in PS3
	format_style = psp
	format_endian = big
	image_format = rgba8888
	pixel_order = normal
}

option -ps3dxt5 {				// Second most used GIM format in PS3
	format_style = psp
	format_endian = big
	image_format = dxt5
}

	//  GIM formats supported by CFW RCO's

option -pspbpp4 {
	format_style = psp
	format_endian = little
	image_format = index4
	pixel_order = faster
	limit_image_width = 512
	limit_image_height = 512
	output_sequence = off
}

option -pspbpp16 {
	format_style = psp
	format_endian = little
	image_format = rgba5551
	pixel_order = faster
	limit_image_width = 512
	limit_image_height = 512
	output_sequence = off
}

option -pspbpp16a {
	format_style = psp
	format_endian = little
	image_format = rgba4444
	pixel_order = faster
	limit_image_width = 512
	limit_image_height = 512
	output_sequence = off
}

option -pspbpp16p {
	format_style = psp
	format_endian = little
	image_format = rgba5650
	pixel_order = faster
	limit_image_width = 512
	limit_image_height = 512
	output_sequence = off
}

option -pspbpp32 {
	format_style = psp
	format_endian = little
	image_format = rgba8888
	pixel_order = faster
	limit_image_width = 512
	limit_image_height = 512
	output_sequence = off
}

This completes all ?, in some way are making uneeded the "convenient options"
Note are divided in 2 groups, the GIM formats used in OFW are placed at top to give them some kind of preference, because the "First most used GIM format in OFW" for each console can be considered the default
This way is posible to use them from the rcoxml:

For PSP the default image type="pspbpp8"
The user can replace the type manually by: pspbpp4, pspbpp16a, pspbpp16p, pspbpp32 (to change image quality)

<RcoFile UMDFlag="0" rcomageXmlVer="1.1" type="psp" minFirmwareVer="1.5">
	<MainTree name="sysconf_plugin_about">
		<ImageTree>
			<Image name="tex_about_psp_WW_0" src="Images\tex_about_psp_WW_0.png" format="gim" type="pspbpp8" compression="zlib" unknownByte="0" />

For PS3 the default image type="ps3bpp32"
The user can replace the type manually by: ps3dxt5 (for the images that needs it)

<RcoFile UMDFlag="0" rcomageXmlVer="1.1" type="ps3" minFirmwareVer="unknownId0x130">
	<MainTree name="xmb_plugin">
		<ImageTree>
			<Image name="tex_loading_icon" src="Images\tex_loading_icon.png" format="gim" type="ps3bpp32" compression="zlib" unknownByte="0" />

(10/04/2015 06:43 PM)ZiNgA BuRgA Wrote:  Also, it may be possible to swap types - at least on the PSP, where most (all maybe?) firmware GIMs are 8-bit (indexed), but can be replaced by 32-bit (8888) and they work fine (provided you don't hit the internal memory limitations).  I don't have a PS3 to test with, so I don't know what GIM types could be swapped.

(10/04/2015 06:43 PM)ZiNgA BuRgA Wrote:  The UMDFlag and minFirmwareVer attributes, I don't really know about.  They are values in the RCO file which seem to correspond with versioning, but I don't fully understand them.  'minFirmwareVer' was used because I map the values in the RCO file to PSP firmware versions:

C Code

1 2 3 4 5 6 7 8 9 10

switch(rco->verId) { case 0x70: fputs("1.0", fp); break; case 0x71: fputs("1.5", fp); break; case 0x90: fputs("2.6", fp); break; case 0x95: fputs("2.7", fp); break; case 0x96: fputs("2.8", fp); break; case 0x100: fputs("3.5", fp); break; //case 0x107: fputs("ps3", fp); break; default: fprintf(fp, "unknownId0x%x", rco->verId); }

---

So I've seen a 0x107 for PS3 RCOs, I suppose some may be 0x130 and maybe something else.  It may correspond with a particular firmware version, I don't know.

			default: fprintf(fp, "0x%x", rco->verId);