ps2homebrew
[ISSUE]: VMC doesn't seem to work in 1.2.0 beta
Checks
- [X] I have checked existing OPL issues for duplicates and found none
- [X] I am using either OPL latest stable version, or archived version or OPL beta version
Describe the issue
Corrrectly used the VMC option on games to create both a specific and generic VMC image and formatted. Settings saved and game loading (with a Loading Config) prompt. Game loads - no memory card inserted in slot 1.
I have double checked the VMC folder - both .bins exist as well as opening the CFG and can see $VMC_0=generic_0.
Yet it doesn't work.
I have seen other reports of OPL previously creating "bad" images and users were met with an error. I see no message other than a config loading and then the game.
edit. I have tried running the same game from USB and a created VMC on there and it works and saves. This seems specific to HDD.
Games are partitions as per PFS Batchkit and VMC is created in +OPL/VMC/.
Console model
SCPH-39000 (NTSC-J)
OPL version / revision
OPL Beta 1.2.0 / 2082 & 2087
In which device(s) have you experienced this issue?
HDD
Context and extra information
Driv3r [SLUS_205.87] Burnout 3 [SLUS_210.50] but seems to be all games
seems this might technically duplicate https://github.com/ps2homebrew/Open-PS2-Loader/issues/1216 but I added more details! :P
Weird, it works for me
I tested it with Freestyle Metal X which I have installed on my HDD. Using v1.2.0-Beta-2087-be25d81
Some proof:
Oh that's strange!
Are you using dvd iso images or partitions from HD installer?
Oh that's strange!
Are you using dvd iso images or partitions from HD installer?
HDL partitions since the HDD was in usual APA format
Oh that's strange! Are you using dvd iso images or partitions from HD installer?
HDL partitions since the HDD was in usual APA format
OK.. That's weird. To add a bit of added detail. I've got a official network adaptor upgraded to SATA. With a WD 2TB 3.5" disk.
Other than that I can't see why mine isn't working..
@vrooze, try OPL Beta 1.2.0 2049.
Tried. No dice. Just claims no MC present. No idea why...
I would try to check the HDD with HDDChecker
@vrooze, try OPL Beta 1.2.0 2049.
Tried. No dice. Just claims no MC present. No idea why...
I would try to check the HDD with HDDChecker
Ok this this is interesting.
The "release" version detects my 2TB as 1TB. The check stops at 5% then errors out after about 10 mins The Optimise just randomly stops soon after starting.
The Beta versions (as well as AKuHAK's from his fork) just don't load. They make my OSSC lose sync a few times and drop me back at the OSDSYS.
Random bump from ages ago.
I figured out randomly today that my +OPL partition was 4096MB. I recreated it as +OPL2. as 2048MB, copied all the data from old one to it. Deleted old then renamed new to +OPL.
VMC now works perfectly!
Wonder if either my +OPL was corrupt somehow and creating a new one fixed something. Or if it was because it was >2048MB
Either way. It works now. I'm happy :)
Random bump from ages ago.
I figured out randomly today that my +OPL partition was 4096MB. I recreated it as +OPL2. as 2048MB, copied all the data from old one to it. Deleted old then renamed new to +OPL.
VMC now works perfectly!
Wonder if either my +OPL was corrupt somehow and creating a new one fixed something. Or if it was because it was >2048MB
Either way. It works now. I'm happy :)
I had this same issue and your fix of recreating a smaller partition fixed it for me as well. This was on OPNPS2LD-v1.2.0-Beta-2194-a626d98.
Random bump from ages ago. I figured out randomly today that my +OPL partition was 4096MB. I recreated it as +OPL2. as 2048MB, copied all the data from old one to it. Deleted old then renamed new to +OPL. VMC now works perfectly! Wonder if either my +OPL was corrupt somehow and creating a new one fixed something. Or if it was because it was >2048MB Either way. It works now. I'm happy :)
I had this same issue and your fix of recreating a smaller partition fixed it for me as well. This was on OPNPS2LD-v1.2.0-Beta-2194-a626d98.
Glad it helped!
Certainly better than trying to buy/find memory cards all over the place! :D
@vrooze If everything has been resolved, could you please close this issue?
Random bump from ages ago.
I figured out randomly today that my +OPL partition was 4096MB. I recreated it as +OPL2. as 2048MB, copied all the data from old one to it. Deleted old then renamed new to +OPL.
VMC now works perfectly!
Wonder if either my +OPL was corrupt somehow and creating a new one fixed something. Or if it was because it was >2048MB
Either way. It works now. I'm happy :)
Confirming this works with the latest OPL snapshot. Games now detect my VMCs. I have recreated it as 512MB as that seems to be enough for art and apps
This still a thing? Sure I closed this ages ago unless the above reply reopened it?
Going to close it again but @Jaajees is this possible to fix in opl itself? It allows you to create larger partitions but the VMC gets created corrupt with over 2GB.
Not a top priority as 2GB is probably plenty big enough for most cases but should probably be looked at at some point 😀.
N.B. I'll leave you to close once you see this. The issue isn't 'fixed' in definition of done sense but a viable workaround exists.
@vrooze There is no record of this issue being closed, you probably just thought it was closed.
As shown in the project's Read-me: If not found a config file, a 128Mb "+OPL" partition will be created. You can edit the config if you wish to use/create a different partition. All partitions created by OPL will be 128Mb (it is not recommended to enlarge partitions as it will break LBAs, instead remove and recreate manually with uLaunchELF at a larger size if needed).
In other words, an external means will be required to change the main OPL partition.
Problems can only be closed by the person who opened them or who manages that project, I do not have such ability