How does MSX & ColecoVision Co-Exist in BlueMSX?

TPR

@folly In my /opt/retropie/configs/coleco here is the retroarch.cfg:
#Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "/opt/retropie/configs/coleco/"

quit_press_twice = "false"

core_options_path = "/opt/retropie/configs/coleco/retroarch-core-options.cfg"
#include "/opt/retropie/configs/all/retroarch.cfg"

and my retroarch-core-options.cfg in /opt/retropie/configs/coleco
bluemsx_auto_rewind_cas = "ON"
bluemsx_cartmapper = "Auto"
bluemsx_msxtype = "ColecoVision"
bluemsx_nospritelimits = "ON"
bluemsx_overscan = "disabled"
bluemsx_vdp_synctype = "Auto"
bluemsx_ym2413_enable = "enabled"

I cannot figure out why it keeps loading as an MSX machine.

TPR

The only way I can see to get around this right now is to make an .opt file for every single ColecoVision ROM I have that specifically calls out the system type as ColecoVision.

Folly

@tpr

I checked mine and your log.

mine does this instead :
[INFO] [Core Options]: Saved core options file to "/opt/retropie/configs/coleco/retroarch-core-options.cfg"

TPR

@folly Yes, this is what is contained in that .cfg file in that folder:

#Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "/opt/retropie/configs/coleco/"

quit_press_twice = "false"

core_options_path = "/opt/retropie/configs/coleco/retroarch-core-options.cfg"
#include "/opt/retropie/configs/all/retroarch.cfg"

Folly

@tpr

Indeed, very strange.

Don't have a solution right now.

TPR

@folly Just for fun I removed that "press_quit_twice" thing and I'm still getting this in my runcommand log:
[INFO] [Core Options]: Saved core options file to "/home/pi/.config/retroarch/config/blueMSX/blueMSX.opt"

I can't figure it out either. I don't think I've ever run into an issue like this before.

TPR

@folly Thanks for at least looking into it. I think at this point I'm just going to make a separate game options file for every single ColecoVision ROM. That's the only fix I can think of at the moment that will at least get this working.

Folly

@tpr

Yes, that is the only option for now.

Perhaps someone else has an idea how to fix this.

dmmarti

@tpr Do you have a file in this folder?

[INFO] [Remaps]: core-specific remap found at /opt/retropie/configs/coleco/blueMSX/blueMSX.rmp.

saw that in your verbose log.

If so, delete it and see if that fixes it.

TPR

@dmmarti Let me go look...

TPR

@dmmarti Damn... I do. Let me rename that now and see if it helps.

Folly

@tpr

Indeed my log doesn't refer to a remap file.

TPR

@dmmarti Nope. Didn't fix it. It also removed the ColecoVision specific remap for controls I had made. So I don't think that's the culprit.

TPR

Here's what's also interesting. Some of my ColecoVision ROMs boot with FBNeo and even when I look at the runcommand log for those it's also pulling the config from the FBNeo config folder and not the coleco folder:

[INFO] [Core Options]: Saved core options file to "/home/pi/.config/retroarch/config/FinalBurn Neo/FinalBurn Neo.opt"

Folly

@tpr

Do you perhaps have wrong settings in /opt/retropie/configs/all/retroarch.cfg ?

Above is just a guess, seems we are on a dead end.

TPR

@folly I can check....

TPR

@folly Here's the retroarch.cfg in /all/
https://www.dropbox.com/s/h4j6yhod2z92sin/retroarch_main.cfg?dl=0

Folly

@tpr

The config looks good.

Perhaps it's an idea to update RetroArch.

TPR

@folly Ha! Updating RA is actually where all these problems started! :P I just updated last night.

Folly

@tpr

Ok, then it could be an issue in the RetroPie-Setup.

To be continued......