Bug submission thread (for RetroArch 0.9.9)

Just installed the standalone to see (r537) and it shows the same issues in Castlevania adventures, perhaps less slowdowns though. F1 race hasn’t got the same problem but still has some strange artefacts here and there.

I watched some original gameboy footages on youtube and I’m not sure what to conclude. I can spot some “redraws” on the original hardware but Castlevania slowdowns and F1 race blinking line in the middle of the screen with Gambatte retroarch are definitely suspicious.

edit: not a bug, please ignore, sorry.

Mame2013 on Win64:

STV games (such as cotton2 or grdforce) aren’t working. Tried with Mame 150 (compiled 24/11/2013) and Mame 151 (15/12/2013).

I thought it worked in a previous version but I’m not sure anymore, I could be mistaken with Mame standalone (tried 150 and 151 and it’s working BTW).

First , for mame2013 use 0.151, the others are outdated (the last change on git for mame2013 0.151 is dated to Dec 02) Secondly , there is no pb with those SH-2 games , I’ve just re-tested them today (on win64 and on linux) , rebuild today the core from the current 0.151 git and they just works fine as expected.

Now maybe the problem is the mame2013 core you use .

Thanks for testing. I found the problem, my core is OK. It’s the Mame.ini I use where I specified a bios for the NeoGeo system. As the STV used different bios as well it’s trying to load the NeoGeo one, my bad. :confused:

Need to find a way to specify a bios per system now, sorry for that.

edit: OK, a simple neogeo.ini in retroarch folder works, that’s great. :slight_smile:

This one seems legit! :slight_smile:

Still Mame2013 on win64:

When you activate cheats via mame.ini and have access to overclock in in-game Mame GUI, some drivers have some strange default applied. I noticed:

-cps2 games have CPU overclock set to 74% (tested street alpha 3, alien vs predator) -toaplan2 games have Audio overclock set to 50% (tested Batsugun, Dogyuun)

Key config for gamepads (in this case 360 pad) seem to be messed up in MAME(2013), when configuring the buttons, the majority of them are correct as in ‘Joy 1 A’, ‘Joy 1 B’, ‘Joy 1 X’ etc but some of the like Left Trigger comes up as ‘TAB’, Right Trigger is ‘F11’, and L3 is ‘F2’ im not sure why this happens as all the rest of the buttons are correct.

Also from default in the normal MAME Emulator, driving games are setup from default to use the analog trigers for gas and brake pedals for driving games, yet this isnt the case in RetroArch MAME (2013) core.

Will these key configs be sorted out anytime soon?

@Tatsuya79 @lettucekl,

It’s not the place here for reports, it’s the Retroarch bug submission thread , and not specific to one core.

BTW , if you notice true bugs or legit feature request , the good place is to reports an issue on github.

@Tatsuya79 , Honestly , not sure that it’s a mame2013 core bugs, as far i know we don’t tweak any default drivers ( like changing default cpu overclock) . So certainly not a mame2013 port bugs.

@lettucekl ,

yes that are the defaults binding hard-coded for the OS that don’t have keyboard ( accessing menu without TAB in android with an overlay for example)


                input_device_item_add_pad (i,Buttons_Name[RETROPAD_L2], &joystate[i].button[RETROPAD_L2],(input_item_id)(ITEM_ID_TAB+0),retrokbd_get_state );
                input_device_item_add_pad (i,Buttons_Name[RETROPAD_R2], &joystate[i].button[RETROPAD_R2],(input_item_id)(ITEM_ID_F11+0),retrokbd_get_state );
                input_device_item_add_pad (i,Buttons_Name[RETROPAD_L3], &joystate[i].button[RETROPAD_L3],(input_item_id)(ITEM_ID_F2+0),retrokbd_get_state );
                input_device_item_add_pad (i,Buttons_Name[RETROPAD_R3], &joystate[i].button[RETROPAD_R3],(input_item_id)(ITEM_ID_F3+0),retrokbd_get_state );


Maybe we can found a way to permit to change the default binding by mame osd (but have to stay the default for android for example) . For now , i have no time to deal with, but you can always make an issue , maybe someone else will have time to look at it.

Oh OK sorry, thought it was about retroarch in general. And this bug seems to be in Mame standalone in fact, just tested. cps2 bug on 150 toaplan2 only in 151… strange.

I got a Wii U Pro Controller plus this Mayflash adapter and when it’s in Xinput mode whenever I start RetroArch it doesn’t work and is set as Device Disabled in RGUI’s Input Options. I can get it to work by changing it to “N/A (Port 0)”, but I have to do that every time I start RetroArch. It happens whether autoconfig is on or off, and having input_player1_joypad_index = “0” in my config doesn’t help with this controller.

If I set the adaper to dinput mode it doesn’t have that problem, but I’d like to use xinput for rumble and the ability to use the Home button.

Edit: False alarm. I reverted to lordashram’s last build and this doesn’t happen there. I think it was just a problem with my own compile of retroarch.exe.

Green beret mame rom version. 078 will not boot on mame core of RR v1.0.0.2 for ps3? Black screen freeze after the copyright mame screen. Anyone else have this issue?

I just bought a new iPad mini 2 Retina(7.0.6), downloaded retroarch with a Final Fantasy VII ROM and everything was running fine. I never close the app, I just leave it running in the background, however, on more than one occasion the app has crashed when I’ve tried to re-enter it(by double pressing the home button and selecting retroarch from the screen of open apps). It feels like I have tried everything but once this initial crash occurs there is nothing I can do to get the app running again. I’ve tried fully closing the app, changing the date and re-initializing, crashes. Rebooted my iPad, changed date, crashes. Removed all roms/files, rebooted, changed date, crashes. The only solution is to delete the app and re-download but it takes days for me to do this because whenever I try to download the app from Emu4ios it tells me ‘retroarch could not be downloaded at this time’. It’s a complete nightmare. I just want to play some of my old favorite games and I cant. There has to be a solution, these issues have been driving me crazy for the past 2 weeks so if anyone has any info that can help me please reply! I’ve almost given up

My issues:

1 Crashes when I try to re-open from the background and then crashes everytime after that on start-up so the app has to be deleted and reinstalled.

2 Can’t download retroarch through Emu4ios(gets it from github), get pop up ‘retroarch cannot be downloaded at this time’

@RedKing The non-jailbreak version isn’t supported by us, and we don’t have anything to do with its production or distribution. Sorry :frowning:

We can usually help with simple usage problems with it, but not bugs like that, which are probably related to the enterprise cert loophole thing.

Thanks for your quick reply.

I have since jail broken my ipad on 7.1.1 using Pangu and downloaded your official version of retroarch. However, I’m having a problem with crashing every time I try to load a psx ROM. I’ve downloaded the schp1001.bin and placed it into the .retroarch system folder and changed ‘user’, ‘group’, ‘world’ to ‘read’, ‘write’, ‘execute’ and I’ve moved the .bin file to var/mobile/documents/ROMs/PSX and it’s still crashing when it tries to load the ROM. Any tips mate?

Also, RetroArch runs gba ROMs no problem.

Cheers

From the RGUI menu, if you go to ‘core options,’ does it say that the BIOS is found? That really shouldn’t be a deal-breaker in the case of pcsx-rearmed, though, since I think it has a HLE BIOS fallback… Have you made sure your cue file points to the correct stuff (filename’s may be case-sensitive, etc.)?

Do you mean the initial RGUI(load core, load content, frontend) or the in game RGUI? If it’s the latter I can’t access that because the ROM makes retroarch crash before I can access it, if it’s the former could you elaborate on how to navigate to check the BIOS? I appreciate your feedback btw, I’m a JB/RetroArch noob and any info helps me to learn.

Cheers

Also, what do you mean by cue file pointing to the correct place? The cue file is all lower case and in the ROMs folder(with the FFVII bin file)

Yeah, I meant the in-game menu, but it’s probably not the issue, really, as I mentioned, since it should have the HLE BIOS fallback. For the cue file, open it in a text editor and its contents will probably be in all-caps, which isn’t an issue in Windows, where most of those cue files were originally made, since its filesystems aren’t case-sensitive. Filesystems that are case-sensitive can get thrown off by having an all-caps cue and lead-cap or no-cap filenames.

Is it possible to disable “full path” messages on screen? For example when I load/change a shader I don’t know what I am loading since name is left outside the screen. I made the font smaller but it’s already too small.

Also aspect_ratio_index = “5” (1:1 PAR) for the Sega Genesis core is broken. It shows 8:7 for most of the games which is fine, but also another esoteric ones (5:7) depending on shader.

Custom aspect ratio only allows for resolution values, and not ratio values (4:3 or 1.33, 5:4 or 1.42, etc)