Carnivol
01-22-2007, 05:51 AM
Okay, so I'm sitting here and fiddling with a game's text, but, there are some minor obstacles/curiosities I kinda either need to sort out, want to sort out or would just make things easier for me;
#1;
When saving/loading, the game seems to call strings that're stored in the PSP's firmware.
How/where can I change what system language set it should take these strings from ? (Is this stored in a default place, like a value in one of the common files between all UMDs that I can just quickly change a value in)
Or is there any other way to force another language ? (Without editing the actual firmware)
Why this?
Well, game was originaly in one language, I've edited majority of text into another, having save/load/network related strings show up in original language creates... confusion and a feel of incompleteness.
#2;
I don't know how plug-ins for 3.03 OE-B works, and what features they can bring me, but is there one that lets a folder on the Memstick act the same way as an ISO in the ISO folder does ? (or evt act as a mounted UMD. I seem to recall this feature was in a UMD launcher. But if I've understood things right, these don't behave properly in 3.03 OE)
Why this?
Everytime I do a change and want to check it out in the game, it requires me to compile an ISO, label it with a date/ID and transfer it to the UMD.
If I just could copy the altered files quickly over on the Memstick and skip the procedure of building and transferring a full ISO everytime, it would greatly improve efficiency + not de-moralize me from bothering with certain time consuming and pixel perfect matters.
#3;
If I edit a boot.bin (not eboot.bin), is there any way to load this from a memstick (evt. also on a non-homebrew enabled firmware), with all original UMD referances intact (so it'll basicly still require the UMD to work, as everything besides the main executable must be fetched from the game's original UMD)
Why this?
Well, if the final work could run in co-existance with the original UMD, it'd be perfect in so many ways~
pre-thanks to anyone who can give me useful answers/help
#1;
When saving/loading, the game seems to call strings that're stored in the PSP's firmware.
How/where can I change what system language set it should take these strings from ? (Is this stored in a default place, like a value in one of the common files between all UMDs that I can just quickly change a value in)
Or is there any other way to force another language ? (Without editing the actual firmware)
Why this?
Well, game was originaly in one language, I've edited majority of text into another, having save/load/network related strings show up in original language creates... confusion and a feel of incompleteness.
#2;
I don't know how plug-ins for 3.03 OE-B works, and what features they can bring me, but is there one that lets a folder on the Memstick act the same way as an ISO in the ISO folder does ? (or evt act as a mounted UMD. I seem to recall this feature was in a UMD launcher. But if I've understood things right, these don't behave properly in 3.03 OE)
Why this?
Everytime I do a change and want to check it out in the game, it requires me to compile an ISO, label it with a date/ID and transfer it to the UMD.
If I just could copy the altered files quickly over on the Memstick and skip the procedure of building and transferring a full ISO everytime, it would greatly improve efficiency + not de-moralize me from bothering with certain time consuming and pixel perfect matters.
#3;
If I edit a boot.bin (not eboot.bin), is there any way to load this from a memstick (evt. also on a non-homebrew enabled firmware), with all original UMD referances intact (so it'll basicly still require the UMD to work, as everything besides the main executable must be fetched from the game's original UMD)
Why this?
Well, if the final work could run in co-existance with the original UMD, it'd be perfect in so many ways~
pre-thanks to anyone who can give me useful answers/help