![]() If you disable fast boot, boot your ISO for your changer app, then boot your game through there via swapping discs and not resetting or dragging in ELF files, I would consider that working as intended. this allowed those previously mentioned games to work. On PCSX2, when you full boot, this process is repeated, this is why some games needed full boot in 1.6 and older to not crash, because they try to read the same memory you are trying to modify with your launcher app.ĭuring the 1.7 cycle we fixed this in Fast Boot by HLE'ing the region parameters syscall so it reads the information directly from the NVM file instead of the memory, which is not how the PS2 would normally do it, but Fast booting is basically hacking past the BIOS to make the boot process quicker. Your app then overwrites that memory to make it think a different language is selected. ![]() You boot the system, it loads the BIOS, which reads the NVM information in to memory which can be accessed by the Get Region Params syscall, then you boot your game/app or whatever. This is not like it should behave at all. If I directly launch HWC_Language_Selector.iso, then swap, then launch the game, it will not work. The only way it works on PCSX2 dev-1921 is launching the BIOS with no disc, then set HWC_Language_Selector.iso as disc, launch it, then swap the disc (to let's say European God of War II) and then select a language and launch the game. So, yes, it is doable.Īs for the dragging and dropping, I don't know what to do, because fixing that might completely break language selection for normal games, and standard PS2 behaviour for booting games trumps some 3rd party app that hacks the language. In this case, drag and drop should be like launching an ELF as system update (mc?:/B?EXEC-SYSTEM/osd-?.elf) on real hardware. Can you not do the same work flow as on a real machine? if you could set up a memcard to boot your app then full boot in to that, then boot your game from there, I expect it would work. Well if you drag and drop an ELF, PCSX2 will reset and completely skip the BIOS and the subsequent NVM loading, since you can't drag and drop on a real console, PCSX2 will assume you're booting something else and start again. Meaning you can use software like XEB+ to change the language to the one you desire (and it will keep set until the case scenario mencioned above) or, you can even use XEB+ as System Update, letting it take care of the OSD init and the language configuration, instead of letting the OSD do the job. Real hardware works this way: On coldboot, it sets the language (vanilla OSDSYS, FMCB or other software that does init the OSD), then it is not changed again, unless you reload OSDSYS or the osd***.elf (system update). ![]() Here's my answer: Games like "Silent Hill Saigo no Uta" (SLPM-65098) has languages locked, but you can unlock them by setting a different OSD language, let's say. also, you might want to ask too "Well, Japanese games only supports Japanese or English, why use another language on a Japanese console?" In emulation, this also applies as we must use the BIOS from the hardware we own. Using a software like XtremeEliteBoot+, people can unlock more languages. ![]() My OSD language will be Japanese or English as these are the only two languages I can select on the OSD. Usual case scenario: I imported a Japanese console and I am from let's say. Why is your language in your OSD different from your language anyway? Windows 10 (64bit) If Linux - Specify Distro Expected BehaviorĪfter changing the language, the next ELF launched by the app who changed the language should keep the language set by the app, not the one set by the OSDSYS. Then, just boot and ELF or game from there. No public homebrews does this ATM, but you could easily code one and do: That way it will not void the changes made by software who changes the language, for example XtremeEliteBoot+ Reproduction Steps I advise to PCSX2 only set the language once you manually launch an ELF or a game, after that, no matter how many times you change the ELF, don't change the language unless it is done via the PCSX2 menu itself or via drag and drop. ![]() This is certainly a regression, since I tested PCSX2 1.1.0 and that does not happens there. If an application changes the language, as soon as you load another ELF (like launching a game, for example), the emulator sets the language back to the one configured on the OSDSYS, voiding any changes made by the previous application. ![]()
0 Comments
Leave a Reply. |