PS2 OPL - GrimDoomer fork Merge - Logic Check

[GamerGhosts]

I'm getting ready to do my own personal PS2 FAT build and I was very curious why some of the features from the GrimDoomer fork of OPL haven't made it back to the upstream. There are two hard drive interface specific features I'd be interested in:

- Having an exFat partition and being able to put .zso on the drive and being done. The goal would be space saving and convenience. My understanding of the current version of OPL is that there is zso support, but it has to be installed like a partition and the requirements of those partitions ends up not saving any physical drive space. Am I understanding this correctly or is there still a lot of space saving to be had with the current implementation?

- If the above isn't possible, the ability to have larger than 2TB hard drives so that full partitions can be installed and ultimately size won't be an issue any more. My understanding is that this limitation still exists in the main branch.

I should premise by that I'm not a PS2 Developer, but have developer and GIT experience. Looking at the fork, it appears as if everything can be merged from upstream safely. Is there any reasons I shouldn't go down that path and start testing what will be a very popular build (latest OPL + GrimDoomer features)

 

[El_isra]

I'm getting ready to do my own personal PS2 FAT build and I was very curious why some of the features from the GrimDoomer fork of OPL haven't made it back to the upstream. There are two hard drive interface specific features I'd be interested in:

- Having an exFat partition and being able to put .zso on the drive and being done. The goal would be space saving and convenience. My understanding of the current version of OPL is that there is zso support, but it has to be installed like a partition and the requirements of those partitions ends up not saving any physical drive space. Am I understanding this correctly or is there still a lot of space saving to be had with the current implementation?

- If the above isn't possible, the ability to have larger than 2TB hard drives so that full partitions can be installed and ultimately size won't be an issue any more. My understanding is that this limitation still exists in the main branch.

I should premise by that I'm not a PS2 Developer, but have developer and GIT experience. Looking at the fork, it appears as if everything can be merged from upstream safely. Is there any reasons I shouldn't go down that path and start testing what will be a very popular build (latest OPL + GrimDoomer features)

Probably because the EXFAT HDD and APA HDD modules cant co-exist. same issue than UDPBD Network stack: its not in upstream due to conflicts with SMB.

OPL Has been getting harder and harder to deal with (on the UI code)

I think the future is neutrino. only thing we're missing is a fool-proof launcher.

 

[GamerGhosts]

Thank you for the insightful reply El_isra (and for all your contributions!). I've also come across neutrino and was surprised it hasn't gotten more press. It would be cool if the UI didn't have worry about the data backend at all, even in pulling the list of games. Maybe it could have some query functionality added to it to help with that (ie: list all files on backend - embed game id in filename, UI takes it from there and launches with correct parameters)