There still things that can be added in the future but compatibility wise it is in a great place now and I'm really happy with it. Just took 8 months to cook Thanks for your help with it as well.I'm glad that your project is going well.
There still things that can be added in the future but compatibility wise it is in a great place now and I'm really happy with it. Just took 8 months to cook Thanks for your help with it as well.I'm glad that your project is going well.
No problem, mate. So far I feel like there's nothing that needs to be changed at this time, but if you need any small additions, then I'd be happy to help.There still things that can be added in the future but compatibility wise it is in a great place now and I'm really happy with it. Just took 8 months to cook Thanks for your help with it as well.
There are still some APv2 games out there, I never really exhaustively went through all of them. But I definitely found most of them...No problem, mate. So far I feel like there's nothing that needs to be changed at this time, but if you need any small additions, then I'd be happy to help.
Good job on the update.Version 1.2.2 (4/26/2023)
Changes:
- The Tonyhax International loader now does SetMemSize(8), SysInitMemory (0xA000E000, 0x2000), and InitDefInt(3). This makes it much more similar to how the real PSX BIOS boots games, and it fixes all known issues with booting games via the GameShark Code method.
- Fixed a race condition that rarely effected booting games via the flashed cheat cart and GameShark Code. The issue was that sometimes the console BIOS would execute CD commmands before starting the ROM too closely to when Tonyhax International would call the first CD INIT on startup. This issue also could happen in GSHAX, when a game was sending CD commands right before the GSHAX exploit would trigger and then starting the Tonyhax International loader. The issue previously manifested as being stuck on the first Initializing CD text forever.
- Updated GSHAX Tool to v2.0.1, which auto-calculates the MIPS assembly binary offset during code generation in the build step.
- Fixed an issue with the build.sh script due to missing template folders in the gshax directory since the last update.
- Improved documentation.
Ah yes, for the PS2 the video mode can not be set while in ‘PS1 mode’. The PS1 can set the video mode in comparison. The reason you need that VMODENEG is because it sets the video mode in ‘PS2 mode’ which works around the above issue.I've been silently (since post 2 in this thread) keeping up with all the improvements, but felt that it was about time I again thanked all involved.
From my own personal use case, I think that the only additional feature I could wish for (which isn't new, and has been a request since virtually release one of Socrams OG TonyHax) is the ability to trigger the PS1VModeNeg (on PS2) after the exploit launches (as an option on the exploit screen?) rather than prior to launching the entrypoint title. As I primarily use TonyHax to run my legit NTSC imports on a PAL PS2, anything that can be done to simplify the number of steps in the process would be welcome... but I'd been led to believe that it HAS to be done prior to launching the entrypoint title, because the title launched after the exploit 'inherits' the video mode settings of the entrypoint title. Maybe you can let me know if I'm understanding it correctly, and if not what the obstacles are that would prevent a videomode switching option within the exploit.
...and thanks again to all involved for maintaining and improving TonyHax!
Modchips are supposed to play games from other regions. You sure you got it installed correctly? And yes, Tonyhax International can be compiled as a disc image for all regions.Is the boot-cd version a PAL or NTSC disc? I've a PAL PS One (SCPH-102) with a MM3 modchip, so it can only boot PAL backup discs.
Yes, but the PAL PS One (SCPH-102) with a MM3 modchip is one of the exceptions. The SCPH-102 has a extra protection in the BIOS which is only bypassed with a more advanced modchip (Onechip or PSNee). But I only have a 12F629 PIC left which cannot be a Onechip but only a MM3. With a MM3 it can play backups, but only PAL ones.Modchips are supposed to play games from other regions. You sure you got it installed correctly? And yes, Tonyhax International can be compiled as a disc image for all regions.
PAL PSones have additional protection built into the BIOS. ONEchip and PsNee modchips connect to a couple BIOS pins and patch it to allow booting out of region games. Without the BIOS patch PAL PSones can only play PAL region games. Japanese systems starting with some SCPH-3000 models also have a similar region lock, but it hasn’t been bypassed by any modchips yet.
I already know that the PSone slim has additional protection. There's only the one ISO which uses a Japanese license file, so you will need to re-build the image using MKPSXISO with the appropriate license file for your region. I cannot share these files for copyright reasons, but those can be searched for on Google or found in a few PS1 games which accidentally have them in.Yes, but the PAL PS One (SCPH-102) with a MM3 modchip is one of the exceptions. The SCPH-102 has a extra protection in the BIOS which is only bypassed with a more advanced modchip (Onechip or PSNee). But I only have a 12F629 PIC left which cannot be a Onechip but only a MM3.
So the pre-build image in the ZIP is not a PAL one?
That was in a previous changelog but I had to reverse it. If you look at the latest versions when you boot them up they say ‘Remove FreePSXBoot memory card now” when it starts up after the freepsxboot exploit.Is the boot-cd version a PAL or NTSC disc? I've a PAL PS One (SCPH-102) with a MM3 modchip, so it can only boot PAL backup discs.
At this moment I use the 1.2.6 memory card version, but I want to free that card up for game saves.
Also, I've read in one of the changelogs that removing a FreePSXBoot card is not necessary when in slot 2, but that doesn't seem to be true for all games. The Crash Team Racing PAL and Harmful Park doesn't boot with the card still inserted. The first one just get stuck at a black screen, the second one boots but gets stuck at the loading screen.