Closed skmp closed 5 years ago
The touchscreen gamepad only hides if you press the face buttons, the start button or the dpad on the external gamepad, it remains visible if you just press the lt and rt buttons or move the stick, you can see the input of the lt and rt buttons that way, press on the touchscreen to make it visible then just press lt and rt buttons on gamepad.
On screen control isnt visible. It still there, i can control normaly, just dont see any buttons. I'm using Xperia xz premium and newest build on playstore.
Delete the buttons.png in the folder you chose as your "home folder" in reicast settings and then restart.
ok i moved the home folder to internal storage and it worked thanks.
It should be in a subfolder named "data" Launching a game should recreate the file, but may require quitting and launching again (but only one additional time)
Using latest beta 91dda19 if you enable the option enable microphone in input settings you get a black screen when launching any game, I already made sure reicast has the Android microphone permission enabled in Android app settings but it still happens, Seaman is now unplayable.
The microphone has to be configured to a controller, which is currently not available without a physical controller present in port 2. We appreciate your patience while a workaround is added.
But Seaman requires the microphone to be connected to the first controller (A) in expansion socket 2 and right now the 2 VMUs of the first controller cannot be modified, making the game unplayable. Also it appears the extra vmus are not working even with a second gamepad attached on Android, I select them on the input menu but they don't appear on the bios ui:
As you can see it detects the second controller but not the vmus.
I dunno what to tell you. I only did the UI portion of the new controller support. You'll probably need @baka0815 to check that over.
It's possible if they are being defaulted to "None" and later changed, the existing device has to be deleted first. I would think the controller setup code should override that, though.
Tested 97c5b9e but toggling the option enable microphone in input settings still causes a black screen when launching any game or bios. I made sure the mic permission is on in Android settings but still happens, anyone else with the same issue? it should be easy to reproduce. Also tested with 3 different gamepads but the extra vmus don't get enabled even when selecting them in input settings.
https://github.com/reicast/reicast-emulator/commit/1619d856633e49a9d6b8a5e76baa1bdbbff4b76a#diff-aefc745393e658c01ab2b0be044819beL387 https://github.com/reicast/reicast-emulator/commit/fa3c3cd94d85e160af2b1e71a8ceb91ae5e7c272#diff-aefc745393e658c01ab2b0be044819beR407
Honestly don't know what to tell you there.
https://github.com/reicast/reicast-emulator/pull/1317 should restore functionality.
Well, I don't have Seamen to verify the mic works, but setting VMUs in other ports is fixed. It shows a blank in the BIOS for A-2, so I am assuming it at least gets the mic there. Just not sure if it still attaches with the new way of configuring it.
Is it safe to assume the microphone works again?
Thanks a bunch man, I will test if it works when I get the update through the playstore.
Just tested it and everything works perfectly now! Enabling the mic in settings no longer causes a black screen and it does work on Seaman, the extra vmus are working correctly now too:
Pretty good job guys, you rock.
Hi good day. I have problems with Android 8.1.0, the emulator is not able to run when starting a game
now on Android 6.0.1 if it starts, all right until I start playing resident veronica code. before I played normal, now it seems that I had jumps of images.
Yes, when walking, you skip images or show lag. before it did not happen.
I hope the comments serve
Android 6.0.1 GPU adreno 330- 578 mhz
Thank you
Xiaomi Mipad1 ,android 7.1 (linage 14.1),Tegra K1.
Can't load any game with any Bios. If i try to load game,only bios loaded,or program crashed. Sorry for bad english
That is typically the result of a bad ROM, most likely in CDI format.
@cthulhu1990 use GDI versions and verify with TOSEC or redump.org.
Bug report: On latest beta 8c93ba0 everytime after opening the emu settings or the input settings and going back the bios files appear instead of your game list:
should be easy to reproduce.
The issue was resolved around 15 minutes ago. https://github.com/reicast/reicast-emulator/pull/1353
Just updated it but it is still happening on 81056d3
Until the most recent changes are published, all of the menus work fine. It is only when using the hard back button that was effected.
latest release reicast_r8.1-6-g93affdd7 can't locate or read any games what happened
😢
@Emulatorer Nobody was doubting you. Check the reference between your posts.
@Abandonedcart OK tnx waiting for the fix 😅
I still get the black screen issue that other people were having when trying to launch the BIOS or a game. I'm using a custom ROM Oreo on a Galaxy S5.
Unfortunately, that one doesn't have as easy of a fix. It appears to be a memory mapping issue.
Device : Samsung Galaxy grand prime Os : Android KitKat 4.4.4 APK version : r8.1 from play store After pressing ( About ) option the app freezes .
The biggest issue I have is: 1) Either the game list fails to load from over a network share, usually takes about 4 force closes to resolve. 2) If the game list doesn't load, nothing else loads either (Settings, PG Settings, About, etc)
Details: nVidia Shield: 7.1.0(29.6.259.0) APK: 8.1 from Play Store
@delize Unfortunately, the emulator is not really tailored to support network filesystems and that isn't really a priority at the moment. The Shield does support up to 256 GB sdcards, though.
Major bug on latest beta: when you enter the touchscreen gamepad editor if you try make any button bigger it gets all distorted on Android 7:
Just the latest beta did this? Or did the one before it do it, too?
Not sure about the previous one because it didn't detect the bios but the resizing works fine in latest master 00ecf2f.
The betas are built automatically from master. Looks like there is nothing to do here then.
Not anymore apparently, latest beta version from playstore is r8.1-11-geacbae5b and the latest master still r7 00ecf2f: http://builds.reicast.com/
the bug is present in latest playstore beta but not in that master build.
And the changes are already submitted to resolve that.
Nice job mostly fixed but if you make the dpad big the right button goes all to the right:
The specific code for that was more or less reverted to the way it was (for years). Are you actually trying to make the dpad that size to use it or was that just to find an issue? If it is just to find issues, it probably won't be addressed right away. After all, it doesn't seem like there is a lot of demand to make the dpad 1/2 the screen width in the last 3 years given the lack of reports about it.
Updated to latest beta:
But Reicast now crashes or closes itself when pressing reicast settings on Android 7.
Interesting. It was build against and tested on two Android 7 devices.
Tried uninstall and install again but still can't enter the reicast settings, here is a quick video of the bug: https://youtu.be/d4E8Ak2-nd4
Updated to latest beta, sadly I still get the same settings bug so I can't configure the directories to play. Anyone else experiencing the same bug?
Updated to latest but bug is still there here is a log:
i have the issue with this emu, The house of the dead 2 Verify failed, not only HOTD but the others too
issue spaces
Blackmann91: Yeah same here i can't go to config because a bug
House of the Dead 2 fix: https://github.com/reicast/reicast-emulator/commit/af5931c214a03fafd51005aae86db156b1de31ce
Android Beta opt in
Feedback
http://chat.reicast.com (#reicast)
(Original post follows)