The new proposed "VM2" from Chris at DreamMods.net

[fafadou]

The content of the VM2 itself, I have no saves in my µsd card for now only an empty VMU.

[chrisvcpp]

That is strange. Have you tried to use "Restore a local VMU file" button?
This way you can upload a .VMU file (dump) to the internal memory.
Then, you can use either "View memory contents" or "Backup to a local VMU file" for making sure that the GUI reads properly from the device.
Also, as a side note, make sure that you are using the proper file format : the VM2 works with full VMU dump files (128KB). Otherwise, if you try to view the contents of the internal memory using VMU Explorer, the application will show an error!
If you still have issues, you can take some screenshots of what you see as not working, and direct p.m. to my email address.
Furthermore, you can check this guide on how to properly handle the VM2 memory, use VMU Explorer to build .VMU dumps, etc.:
https://www.youtube.com/watch?v=g24Jmy7mo-A

[fafadou]

Thanks for sharing this very helpful video, and for helping me.

I can manage my VM2 via the dreamcast bios menu, so everything is good.
And I create some vmus on the µsd card, I did the update so everything is fine

Do you have planned some other updates ?
Like for example manage the dreamcast overclocking, I believe the crystal is faster than 7.2MHz required for saving with an overcloked dreamcast. It would be nice !

[ArcadiaDC]

Hi! My VM2 won't connect to my Dreamcast. I'm using GDEMU with openmenu, but it works fine for my regular VMU's.

When I go to the regular main menu to manage the VMU's, it works when I only have the standard VMU inserted, but when I plug in the VM2 the regular VMU disappears, and when I only use the VM2 nothings shows up.

I tried factory reset twice, the first time I reset it and then updated the firmware and it didn't show in the DC. The second time I tried to reset it to use an older firmware to see if it was a problem with the new FW, but it was stuck in "Factory Mode" so I had to update it. And again, it didn't connect to the DC.

I usually use a StrikerDC but have tried this with the regular controller too.

[chrisvcpp]

Hi.

At the moment, the StrikerDC does not support the VM2 (or any other 3rd part memory), so this is something to be expected.

Now, I assume you have also tried with an OEM wired controller, correct?
If so, what you described sounds like a power issue with either the controller itself, or with your console's controller port PCB.

You can try with another controller to check whether it's a controller issue.
Otherwise, your Dreamcast controller port PCB might need a repair, like fuse replacement.

Here's a trick you can do : plug the VM2 into USB. Then plug it to the controller and see whether the VM2 shows up on the Dreamcast BIOS..

[ArcadiaDC]

Hi.

At the moment, the StrikerDC does not support the VM2 (or any other 3rd part memory), so this is something to be expected.

Now, I assume you have also tried with an OEM wired controller, correct?
If so, what you described sounds like a power issue with either the controller itself, or with your console's controller port PCB.

You can try with another controller to check whether it's a controller issue.
Otherwise, your Dreamcast controller port PCB might need a repair, like fuse replacement.

Here's a trick you can do : plug the VM2 into USB. Then plug it to the controller and see whether the VM2 shows up on the Dreamcast BIOS..

Charging the VM2 while placing it in the dock of an OEM controller did nothing, I will try it in my spare DC tonight to see if my main DC's controller port PCB is broken, like you said.

You said "at the moment", is using StrikerDC with a VM2 possible through VM2 firmware update or is it completely to do with the StrikerDC?

While the wireless version seem to able to be updated through its dock, the wired version I have probably don't have that capability.

[chrisvcpp]

I see. Yes, please try with your spare DC as well, since you have this option.

I said "at the moment" because Retro Fighters are working on making their StrikerDC to work with the VM2.

The wired version already works with the VM2, AFAIK, so no need to do anything there..

[ArcadiaDC]

I see. Yes, please try with your spare DC as well, since you have this option.

I said "at the moment" because Retro Fighters are working on making their StrikerDC to work with the VM2.

The wired version already works with the VM2, AFAIK, so no need to do anything there..

So I tried my spare DC yesterday and had no problems, so it's probably the controller PCB in my main DC that's the problem, like you said.

I'll probably fix it by replacing the fuse so I've ordered some fuses, but I tried switching places with the PCB's but discovered that even though they're both PAL VA1, weirdly enough the spare one had the metal fan and heat sink, while the main DC had the black plastic fan and they are not cross compatible due to them having different connectors. The one with the metal heat sink was made in Indonesia I believe, while the one with the plastic fan was made in Japan.

Either way, thanks for troubleshooting this for me.

[chrisvcpp]

Great, glad that it's sorted out.

If your controller PCBs have different fan connectors, then for sure one of them is VA0.
A 3PIN fan (metal or plastic) is VA1/VA2 while a 2PIN fan is VA0 (and always metal).

[ArcadiaDC]

Great, glad that it's sorted out.

If your controller PCBs have different fan connectors, then for sure one of them is VA0.
A 3PIN fan (metal or plastic) is VA1/VA2 while a 2PIN fan is VA0 (and always metal).

Correct me if I'm wrong, but doesn't the "1" next to "PAL" indicate VA1?