Bug submission thread (for RetroArch 0.9.9)

RetroArch General
#21

Thanks a mil :slight_smile:

#22

Android Version: all menus are really lag here. For example: If I click to go to Settings, will take 3~6 seconds. Also, overlays don’t work here.

Is really strange. I already formatted my entire smartphone. I have a Xperia S, running lastest sony firmware, 4.1.2.

Update: Ok, really strange, restarted the app again and now it’s working and without lag in menus. Not sure what happened!

#23

I’m afraid that is just Android for you - how laggy (or crappy) it will be depends on the vendor/carrier that loaded your device up with their own brand of ‘Stall/Lag City’ Javaware apps.

#24

Not a bug, we took this out.[/quote]

Can I ask why? Holding the wii remote power button to turn off the wii is standard functionality across the entire platform, including most (if not all) popular homebrew.

#25

Not a bug, we took this out.[/quote]

Can I ask why? Holding the wii remote power button to turn off the wii is standard functionality across the entire platform, including most (if not all) popular homebrew.[/quote]

Because it was about standardizing RGUI and not the Wii port. Not every platform is guaranteed to have a ‘shutdown’/‘remote power’ button at all - nor are we going to go to the effort of finding some kind of substitute for each and every platform. Therefore this stuff was removed because it is unneeded fluff that doesn’t scale.

RetroArch’s needs (and the uniformity of it running on every host system) is more important than whether or not this jibes with your particular pet peeve ‘homebrew scene’ and how ‘the other guys do it’.

#26

There is absolutely no need to take that tone with me. I asked “why?” in the most sincere way possible while providing anecdotal evidence to similar functionality. I know you’re having it out with the Wii homebrew scene (a scene that I am not part of, mind you) right now, but there’s no need to take it out on everyone who asks for some simple rationale as to why a feature was removed.

Clearly, I am no programmer, but is it really so difficult to include platform-specific functionality without “muddying the water?” I am asking this of any platform, not just the Wii. I’m also not asking that flippantly, as I realize it might come off like that. You may call it “unneeded fluff,” but I think that simple button press provides great functionality to already great homebrew.

#27

And my answer is still the same to you - this was about standardizing RGUI, and this ‘feature’ (if you can call it that) was an ill fit from a multi-platform perspective.

Smaller is better, and less additional fluff that serves no purpose is ultimately better in my book. And really, this ‘feature’ you think is so important was totally meaningless and unimportant. It won’t be coming back.

So I don’t consider it a bug and it won’t be added back.

#28

You have to see the poor logic in your argument claiming that the functionality is “totally meaningless and unimportant” while I’m sitting here and telling you it has use to me (and others, assumedly). I have no use for 80% of retroarch’s cores but I don’t say they’re useless fluff. They obviously have use to someone – just not me.

I can understand your point about standardizing RGUI (even if I don’t necessarily agree with it), but I refuse to accept your assertion that something has no value just because you personally see no value in it. And again, I respectfully ask that you stop speaking to me so derogatorily; we’re mostly adults here, let’s act like them.

And just to be clear, this isn’t pixel perfect, cycle accurate byuu-shit we’re talking about here; just simple functionality baked into the platform.

#29

Wii pallete issues.

prehisle.zip - Prehistoric Isle In 1930 and srumbler.zip - The Speed Rumbler.

#30

http://forum.themaister.net/viewtopic.php?pid=4674#p4674

What do you see in this post that you regard as ‘derogatory’?

Please stop cluttering up this thread with this nonsense. It’s gone. It has no purpose. This is final.

Now onto some real bug reports.

#31

I’ll look into that.

#32

Derogatory: showing a critical or disrespectful attitude

“And really, this ‘feature’ you think is so important was totally meaningless and unimportant.”

Your phrasing is entirely disrespectful. You could’ve phrased this statement a half dozen ways and not be nearly as condescending or inflammatory as you were clearly trying to be.

And then, as if that wasn’t enough, you lob a “Now onto some real bug reports.” into the mix, because mine clearly have no value.

I do apologize for cluttering this thread. Feel free to delete my posts – there’s no need to keep them up as they’ve reached their intended recipient. I would be happy to continue this discussion via PM, but I honestly don’t see the point as it seems we’ve reached an impasse.

Also, A “real” bug report for Wii: With video set to 4:3, when loading from Game History retroarch switches to either 4:3 stretched or 16:9 while the screen says “loading … .smc” then switches back to 4:3. Loading from file location does not exhibit this behavior.

#33

Not so much a bug as a feature request, there is no 6 button pad option on Mednafen PCE Fast making Street Fighter II Champion Edition pretty unplayable.

#34

#1. On the CPS2 core, loading a game from history with diagnostics enabled results in a code dump. Turning off diagnostics fixes this. Tested twice with SFA2 on Wii.

#2. Each time I restart the core my default input setup of Classic Controller reverts to Gamecube controller and has to be reset.

#35

PS3 - BUG #4:

Some menu info on screen disappear or get over other infos.

ex: in the resize mode, try putting a big viewport and you’ll see the caption space isn’t enough to fill all info.

ex2: the space where the selected core appear on menu screen get superimposed with other menu infos when these are big.

#36

I don’t know if you care about the 360 GUI, but I’ve seen two issues with it in this release:

Clicking on “Path Options” doesn’t do anything.

The menu randomly gets cut off (i.e one third of it is all black). Sometimes it happens right away when you start RetroArch, sometimes it happens after playing around in the settings or starting/changing games.

Just reporting this in case you’re interested. You can ignore it if you want.

#37

Android Version:

Already posted here: http://forum.themaister.net/viewtopic.php?pid=4489#p4489

I suspect that input is not detected/processed properly in libretro native code

On JXD S7300 there’s a joystick driver called “adc joystick”, the stock one, which is laggy and despite the name the two analog sticks work as a keyboard, that’s why a new driver was developed and put on Sxelrom, a custom firmware, named “noadc joystick”, it doesn’t get recognized automatically.

I, main developer of another custom firmware ,kept the same name to have automatic detection, but changed the driver so that instead of sending EV_KEY events it sends EV_ABS on axis X,Y, and this also does the other driver.

This seems to cause a problem: if I go in settings and manually bind the keys, it detects the analog stick properly and I’m able to set the 4 main directions, so the stick should work properly (and it does in other apps), but once a core is launched only up and left directions work. On my driver the absbit range for absolute axis x/y is 0-1023, so no negative values. Might this be the cause?

Finally, “tincore” is an IME that intercepts all the joystick events from sticks and buttons and forwards events to a virtual device, so if you set the axis to work as a key pressure instead of directly sending to libretro axis events, it works properly. For some cores using analog instead of keyboard would be better.

#38

Android Bugs - Xperia Play

#1. Gamepad not functioning, except for d-pad.

#2. Touching the bottom left part of the screen (slightly to the left of the words Sony Ericsson) causes emulation to crash and return back to the core selection screen.

Thank you for your time looking into this.

#39

I’ve noticed a few touchscreen-related bugs on RetroArch 0.9.9 on my Galaxy Note 2:

  1. Suspending/resuming the app causes the back button (which is a touch key on the Note 2) to not work. I see “sec_touchkey” printed to the screen when I press Back for the first time after resuming, but it doesn’t bring up the menu or exit the emulator like it’s supposed to.

  2. Same issue, but with any onscreen IME. I’m using something similar to Game Keyboard instead of RetroArch’s built-in controls. I see “Virtual” printed to the screen when I try to use it, but nothing else happens.

So, both the IME and the back button work as long as I never suspend the app, sleep the phone, or get a phone call, but whenever I have to resume RetroArch from the background for any reason, I’m unable to control it, and my only option is to force close it. :frowning:

  1. To use an onscreen IME, I have to press one of the IME’s buttons after starting a game and before pressing anything else. So for example, if I start a game and press a volume button before pressing an IME button, the IME is ignored. If “debug input reporting” is on in this case, I’ll see things like “Pad 1: 97, ac = 0, src = 0” printed to the screen when I use the IME, it just doesn’t control the game.

  2. Just a request since I’m on the subject… RetroArch already has “Input Method” and “report IME” options in its menu. It’d be nice if there was also an option to call up the IME whenever an emulator starts or resumes.

Ok, I’ll stop there. Thanks in advance

#40

Wii Bug - Possibly more general than just Wii?

Playing Seiken Densetsu 3, the screen seems to brighten and crisp up when I talk to people or nobody is moving. Like it’s briefly going hi-res. I’m not sure if this is related to this recent bug fix:

[SNES9x Next] Seiken Densetsu 3/Romancing Saga 3 no longer downsample to low-resolution for high-resolution modes on Xbox 1/Gamecube/Wii

If I change the filter to point instead of bilinear, the issue either disappears or becomes so minute that I can’t notice a change.

This can be tested in the first few minutes of gameplay with Duran as the main character.