Strange, Apollo 13 works on my side.
Could you post your core options file for the core?
I even re-downloaded the rom from a different source and it still won’t load
mame_alternate_renderer = "disabled"
mame_altres = "640x480"
mame_auto_save = "disabled"
mame_boot_from_cli = "disabled"
mame_boot_to_bios = "disabled"
mame_boot_to_osd = "disabled"
mame_buttons_profiles = "enabled"
mame_cheats_enable = "enabled"
mame_current_mouse_enable = "disabled"
mame_current_skip_gameinfo = "disabled"
mame_current_skip_nagscreen = "disabled"
mame_current_skip_warnings = "disabled"
mame_current_videoapproach1_enable = "disabled"
mame_lightgun_mode = "none"
mame_mame_paths_enable = "disabled"
mame_media_type = "rom"
mame_mouse_enable = "disabled"
mame_read_config = "enabled"
mame_saves = "game"
mame_softlists_auto_media = "enabled"
mame_softlists_enable = "disabled"
mame_throttle = "disabled"
mame_write_config = "disabled"
NAME | SIZE | BIOS | STATUS | MERGE | REGION | OFFSET | OPT | CRC | SHA1 |
---|---|---|---|---|---|---|---|---|---|
10_07 | 4096 | good | maincpu | 0 | no | 63d0deaa | d5de99d5e0ee08ec2ebeef7189ebac1c008d2e7d | ||
tapollo13.svg | 643176 | good | screen | 0 | no | e2dac162 | 4089fa485579d2b87ac49b1cf33d6c2c085ea4c5 |
default.cfg
<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
<system name="default">
<input>
<port type="SERVICE">
<newseq type="standard">
JOYCODE_1_RZAXIS_NEG_SWITCH
</newseq>
</port>
<port type="UI_CONFIGURE">
<newseq type="standard">
KEYCODE_TAB OR JOYCODE_1_ZAXIS_NEG_SWITCH
</newseq>
</port>
</input>
</system>
</mameconfig>
tapollo13.cfg
<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
<system name="tapollo13" />
</mameconfig>
You must be using a different core because mine doesn’t have some of the core options like the ones about the mouse and the nag screen.
The rest of the options are the same as mine.
ATM i am on my win7 pc. I will test it later on linux and the pi3
[EDIT] Windows core is from 19.10.2019 15:31, linux is newer ( 20.10.2019 08:36 )
OK i think i found what’s going on here.
I noticed in the standalone that the artwork files are different between the games that work and the ones that don’t. The ones that don’t work in RetroArch have some additional bezel around the screen. The ones that work don’t have this. I deleted the artwork file and now Apollo works.
Now i just have to figure out why this happens.
Is your Windows core from the buildbot? I downloaded mine today and has the same date but it doesn;t have the no-nag options.
RA core updater, so yes.
After playing with the artwork file i discovered, that the screen
element is causing the crash
<screen index="0">
<bounds x="742" y="292" width="433" height="320" />
</screen>
Any way i could edit this file so it can be fixed?
I still don’t get why my core has less core options than yours XD
I’m using the Windows 64bit build. Downloaded today.
In the artwork.zip there is the default.lay
where every element is defined.
I played around deleting on element after another until the game worked.
Don’t know why the screen element is causing the problem
[EDIT] my mame options:
Ok that’s my options as well. I was confused by your previous post where you seemed to have extra options.
I fixed the artwork files like this:
I deleted the “unit” and “backdrop” png files and then replaced the code with this:
<mamelayout version="2">
<element name="Background">
<image file="Background.png"/>
</element>
<view name="Handheld_Artwork">
<overlay element="Background">
<bounds x="742" y="292" width="433" height="320" />
</overlay>
<screen index="0">
<bounds x="742" y="292" width="433" height="320" />
</screen>
<bezel element="Background">
<bounds x="742" y="292" width="433" height="320" />
<color alpha="0.1" />
</bezel>
</view>
</mamelayout>
So far the ones i fixed work. I only care about the background, for bezels i can use a different overlay from the overlays menu.
Thanks for your help my man.
I think the settings you mentioned are only in the retroarch-core-options.cfg
In mame2003 for example you can enable/disable those settings in the Quick Menu:
mame_current_skip_gameinfo = "disabled"
mame_current_skip_nagscreen = "disabled"
mame_current_skip_warnings = "disabled"
Yeah these are the “no-nag” options. Not all versions of the cores have them. Whoever makes the core has to put them there, it’s like a custom version of MAME so it doesn’t “nag” you with those messages.
214 core doesn’t have these options.
Uups, you’re right. I deleted the retroarch-core-options.cfg
and in the fresh generated one those settings are gone.
Must be a remaining of an older core
@Sivarticus: sorry for abusing your thread.
If you wish i will ask a moderator to split the off-topic chatter into a new thread.
That was my bad actually, i started the off topic
Nah you’re good. It’s all kinda related anyway.