You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the problem was Games with long titles in which 2 or more discs/games have the same beginning 17 characters in the title i.e. Shadow Hearts 2 - Covenant [Disc 1]
&&
Shadow Hearts 2 - Covenant [Disc 2]
expected behaviour
I expected... There wasn't necessarily an issue with the program itself, but rather the naming convention causing issues elsewhere. When the games are created as partitions on the PS2 hard drive, only the first 17 characters are visible. This causes OPL and applications accessing these partitions to get confused and not recognize 1 or more of the partitions with similar name (first 17 chars). In order to get around this, the naming convention in the database for these games should be updated as follows: [Disc 1] Shadow Hearts 2 - Covenant
&&
[Disc 2] Shadow Hearts 2 - Covenant
Issue
the problem was Games with long titles in which 2 or more discs/games have the same beginning 17 characters in the title i.e. Shadow Hearts 2 - Covenant [Disc 1]
&&
Shadow Hearts 2 - Covenant [Disc 2]
expected behaviour
I expected... There wasn't necessarily an issue with the program itself, but rather the naming convention causing issues elsewhere. When the games are created as partitions on the PS2 hard drive, only the first 17 characters are visible. This causes OPL and applications accessing these partitions to get confused and not recognize 1 or more of the partitions with similar name (first 17 chars). In order to get around this, the naming convention in the database for these games should be updated as follows: [Disc 1] Shadow Hearts 2 - Covenant
&&
[Disc 2] Shadow Hearts 2 - Covenant
Program version
version 3.6.0 revision 1
Windows version
Windows 11
Relevant log output
No response
In which package have you experienced this issue?
64 bits
other checks
The text was updated successfully, but these errors were encountered: