Threaded Mode | Linear Mode

ZiNgA BuRgA · 19/02/2011 05:17 PM

Sorry, I forgot about the -ps3 switch - thanks for picking that one up :).

The tex_psn.gim seems to be using standard 32-bit colour.
Can you try converting the tex_psn.png with the following?

Batch Script

gimconv -ps3 --format_style psp -N tex_psn.png -o tex_psn.gim

The above is giving me byte exact output for me...
If it works, would you mind trying it again without the "-N" switch?
(By the way, I don't have a PS3 so IDK what GIM formats it supports)

DXT5 is compressed colour if you're wondering: http://en.wikipedia.org/wiki/S3_Texture_...4_and_DXT5

Thanks!

mugi · 19/02/2011 05:56 PM

success ^.^

"gimconv -ps3 --format_style psp -N tex_psn.png -o tex_psn.gim" «-- works !
""gimconv -ps3 --format_style psp tex_psn.png -o tex_psn.gim" «-- doesn't work

i could hug you now :)
...custom interfaces psp style here i come !

ZiNgA BuRgA · 19/02/2011 06:04 PM

That's interesting, thanks for trying.
If this is the case for all images, you can edit GimConv.cfg, find:

Code:

option -ps3 {
	format_style = ps3
	format_endian = big
}

Replace with:

Code:

option -ps3 {
	pixel_order = normal
	format_endian = big
}

And it should work with Rcomage fine.

Thanks :)

mugi · 19/02/2011 06:13 PM

I'll do that and see what happens with future edits then :)

edit: tested with said changes to the cfg and it works like a charm :)

mugi · 21/02/2011 10:58 AM

Ran into another thing with ps3 RCO's today...

this thing i can get around of, but it requires me to write changes that are unnecessary.
it's about a little conflict with the contents of an XML file and the XML file parser..

here's what happens when you open and then save unmodied English.xml of sysconf_plugin.rco and try to recompile.

Quote:Text/English.xml:1469: parser error : Opening and ending tag mismatch: Notices line 1469 and Text
	
<Text name="msg_remember"><Notices></Text>
	
^
Text/English.xml:2121: parser error : expected '>'
</TextLang>
^
Text/English.xml:2122: parser error : Premature end of data in tag TextLang line 3
^
Warning: Can't parse XML file Text\English.xml.
Warning: [line 87] Text entries not specified! Assuming no entries.

im sure you can see that the problem is that sony used <Notices> as a text string and since such tag doesn't exist in the xml itself it confuses the poor parser that then b0rks itself.

is there a sensible way around this or do i just change the <Notices> to [notices] or something to get over with ?

sorry for double post too.

ZiNgA BuRgA · 21/02/2011 02:47 PM

:/
Rcomage is meant to convert anything which contains a < or > character into CDATA sections.
So the code should've been something like:

XML Code

<Text name="msg_remember"><![CDATA[<Notices>]]></Text>

I'll have to take a look at it at home.

mugi · 22/02/2011 11:53 AM

good luck dealing with that :)
I'll just change the string to something else in the meantime to get around with experimenting with the said RCO some more.

...in the meantime, here's what i use the product of your skill to do.
im getting the hang of editing the XMB now :)

huge bad quality pic warning:
http://projects.kotoba.free.fr/poo poo/Valokuva0148.jpg

ZiNgA BuRgA · 23/02/2011 03:05 AM

I'm not getting what you're getting.
You sure you didn't do any editing, including loading it into something like Notepad and saving without doing any changes?

I'm getting this:

XML Code

<Text name="msg_remember">＜Notices＞</Text>

Note that Sony is using ＜ instead of < (unicode version of the sign, which is different and not part of XML syntax).

mugi · 23/02/2011 08:44 AM

well, as far as i know i never opened it, but can try again and see.
I'll take a peek at it on hex editor to see how the symbol behaves.

err...i did open it but never modified or saved it.
weird though, it seems to work now if just extracted, not saved, and the weirder part is that i tested saving it on hex editor and checked afterwards that the hex for the symbol didn't change from unicode to standard so it should have worked... it didn't -.-

oh well, I'll just change it to [notices] :P

on a semi related note.. have you ever tried taking a peek at ps3 sprx files ?
I've now rebuilt every rco from flash0 and i can't seem to find the main icons of XMB anywhere. thre's no icons, and no default p3t themefile either....
they might be in prx's or then there's something else going on here. The prx's also contain attributes for certain things in XMB such as image dimensions and movement, spacing, scroll and whatnot settings of icons which i'd love to get my hands on.

i can provide you with 3.55 decrypted prx's if you need some and are willing to take a peek

ZiNgA BuRgA · 23/02/2011 04:45 PM

(23/02/2011 08:44 AM)mugi Wrote: err...i did open it but never modified or saved it.
weird though, it seems to work now if just extracted, not saved, and the weirder part is that i tested saving it on hex editor and checked afterwards that the hex for the symbol didn't change from unicode to standard so it should have worked... it didn't -.-

Maybe your hex editor is trying to interpret it as ASCII?
I know, for example, UltraEdit does try to revert to a textual input if you give it a text file.

(23/02/2011 08:44 AM)mugi Wrote: on a semi related note.. have you ever tried taking a peek at ps3 sprx files ?
I've now rebuilt every rco from flash0 and i can't seem to find the main icons of XMB anywhere. thre's no icons, and no default p3t themefile either....

PRXs are compiled code, so it's not going to be easily manipulated like RCOs.
I don't have a PS3 so I haven't looked in those files, no, and probably won't due to aforementioned reason.
Good luck on finding the icons though. You can try searching for references to "GIM" in the PRX files if you believe they're in there.

Threaded Mode \| Linear Mode [PSP] Rcomage v1.1.1 - new RCO manipulation tool
Author	Message