While using the snes emulator, 9 times out of 10 I can’t see the stock controller/overlay when I load up my Rom. I have a galaxy s3. I know this is a documented problem but I was hoping/told that I could get some help on these forums.
@Tanuki Does this happen with many shaders or particularly with the mdapt shaders? If specifically mdapt (and a few others), we tracked the issue down in another thread: the input vertex attributes don’t like ‘half’ and will crash. If you change those 'half’s to 'float’s, mdapt should work without crashing. I don’t know if this will work for all shaders, but it’s likely since the only difference between the halfs and floats is precision.
@hunterk Beautiful! This seems to have done the trick. SABR gave me the same problem and seems fixed as well =) Thanks!
Humm, I need to update common-shaders to only use float in vertex.
On Wii, .9.9
Loading two patched games in a row (translations in my case) without restarting retroarch in between results in some peculiar behavior. Most of the time, the game doesn’t really boot at all. Sometimes you get through a few opening intros and it dies then. I tried it with a couple different games, so it doesn’t seem specific to any one patch.
Not really a big deal though… just restart RetroArch.
Briefly mentioned this in the android thread…
Seems to be an issue with shaders on Nexus 4 and 2013 Nexus 7; all of them just give a black screen with audio. S4Pro and Adreno 320 combination bug.
Core diagnostics enabled in FBA doesn’t seem to be reliably taking me to the settings/debug/bios/test menu, whatever you want to call it (unless I’m just missing the boat on how to do it)
Would need device testing - either an outside dev who has access to these things and wants to help out on fixing the bug in RetroArch Android, OR the vendor/whatever gifting a device to us like others have done.
It’s really starting to look like (based on my experience with Shield so far) we do have to pre-configure some settings here and there on a per- device basis to make sure things run decently out of the box - I’d feel a lot better about the Android port if we really had a plethora of devices we have proof-tested this on so we can be absolutely confident in telling people ‘turn this and this feature on - set refreshrate to such and such - turn off GPS/mail syncing/Play Store updates whatever and it will run great’).
And well - some devices will simply be non-salvageable and compromises will have to be made - but when you’re dealing with this many hardware configurations and vendors to begin with, that’s kinda unavoidable.
So far the ‘gifting’ option seems to have been well-received - let’s hope this continues because we are not going to go down the road of Kickstarters or ‘donate here’ buttons at any point in time. This is not a money venture for us and we are not going to be living off other people’s cash like others have done.
(Wishful thinking here…) I hope the new Nexus 7 would be a device that you could focus a lot of developmental resources on, since it’ll probably sell very well and is free from carrier bloat and will always run the latest Android OS. Hopefully one lands in one of the RetroArch teams hands soon.
Wii, .9.9
Don’t think this is specific to Wii, and it’s not really a bug, but I was wondering if anything can be done about the input options menu. While it works fine for the snes, nes, gameboy, etc, things get a little weird with genesis since the menu uses a generic XYAB button scheme but the Genesis uses either ABC or ABCXYZ.
Also, and this may be more specific to Wii, but input options don’t seem to function for me correctly when switching cores. IE, set it to classic controller, switch to gen core, switch back to snes9x core. The classic controller input will continue to work but if you enter the input options you’ll find the option has reset to gamecube controller. If I keep messing around with device option the whole thing will just gum up. It’ll get stuck on a certain device and I have to keep jamming left or right and eventually it’ll change.
Not sure if I can explain it any better than that… it’s just kinda wonky.
I tested RetroArch on a Huawei Y300 phone (Android 4.1.1). There are a couple of problem which make it pretty unusable on this device.
But first a suggestion: please add the ability to move it to the SD card! On devices with a small amount of internal storage, the 90MB+ occupied by RetroArch is a lot.
Tapping a touchscreen button causes the press to be registered, but not the release. So at the RetroArch menu if I tap down, the arrow keeps on moving down, cycling through all the menu options. I can stop it moving by tapping right.
The touchscreen controller overlay image doesn’t appear initially. However if I return to the launcher then switch back to RetroArch the overlay does appear then.
@mark_k Moving to SD card probably won’t ever be an option due to the way the program works. However, you can open the apk file like a zip and delete the cores you don’t want/need before installing.
OK
I have a windows 7 64 bit I use retroarch PC
I have a big problem with snes9x NEXT
-
snes9x NEXT is not good for résolution , because the integer scale is not full screen (1600x900) , contrariwise bsnes and snes9x (normal) is in full screen , no problem
-
Crop overscan with snes9x NEXT bug , because if the box is not checked there are problems on the screen , garbage color
it is important to correct, because snes9x NEXT works very well on small computer , bsnes is slower (but i love bsnes)
thanks
The first issue is known at least, snes9x next reports the wrong resolution. The second issue makes sense in that case.
Using retroarch 0.9.9.6 on android. On the mame 0.78 core there are sound problems in games made by Irem.
Chalk it up to it being a MAME version from 2003.
The current google play version has the following issues on my devices
- Screenshots appear as black images
- In-game fonts are rendered as black boxes if auto-load of states is enabled (tested nestopia, gambatte, fba, s9x-next)
Also I hope you were able to take a look to the mappings of my weird DS3 that gets detected as “Gamepad 0”
This has been fixed and will be in the next version
PS3 Rogero CFW 4.46 v 1.01:
Service Mode with L1, L2, R1, R2, + Start buttons for CPS1 games: you can see the test menu (Example: SF 2 Hyper Fighting), but not make any changes because CPS1 motherboards relied on dip switches.
RetroArch v0.9.9 has an audio pop noise right after a rom is selected and the game is booting up: example MvsC1.
Cant remove Right Analog Stick command: Fast Forward when pressing down.
Bug report for the PC version (0.9.9 x64)
Cannot use automatic updater. When I select “check version”, it tells me, “download was not completed” and does nothing. I have tried redist, full and slim builds, I could’ve sworn there was a 0.9.9.6 for the PC…maybe there isn’t, but the fact of the matter is the download feature on RetroArch isn’t working 