Jump to content
LaunchBox Community Forums

tycho1974

Members
  • Content Count

    37
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by tycho1974


  1. 5 hours ago, Jason Carr said:

    This is good to know, @tycho1974. I wish I had a solution for you, but sadly I don't. I haven't done any extensive testing with sideloaded Retroarch 32-bit vs. from the Play Store and controls, though. It may be worth trying some older (and/or newer) versions to see if all versions are affected by any bugs like that. It's not uncommon for Retroarch to put out official versions with bugs.

    Interesting tidbit about the official releases with bugs. I can say that I just got the APK from the Retroarch website, so I'm assuming it's the latest version.

    I did some further testing, and I discovered that the only way for my D-pad to function properly was to manually edit the bindings; specifically, I had to remap the "analog" stick inputs for left, right, up, and down to the D-pad instead of the left analog stick. The existing D-pad bindings do nothing in my testing, and my "Analog to Digital Type" setting does nothing when changed. I hope this helps anyone who is having this same issue...

    • Like 1

  2. So I followed ETA Prime's tutorial on loading my MAME games into Android, and apart from exporting my entire 10,000+ file romset, it worked great. My problem is that Retroarch 32-bit is pretty janky about controls, and I can't seem to fix it.

    I use the "official" Retroarch app to run all my other emulated games (NES, SNES, Genesis, PS1, etc), and input works flawlessly, using the D-pad for movement controls. But when I use Retroarch 32-bit to play my arcade games, the program insists on forcing me to use the analog control stick for basic UDLR movement. This is even before connecting a controller - the input OSD has to be switched over to left analog stick in order for me to be able to control movement in all games. I've gone into the settings and poked around, but nothing I do seems to make the app use regular D-pad inputs for movement. The same holds true after I connect a controller. Has anyone else run into this? This behavior has been consistent since first installing and running Retroarch 32-bit.


  3. After a couple of days of testing, I'm really liking where LB on Android is, especially out of the gate. The emulator setup and configuration is similar to the experience on my Windows machine (trial and error but rewarding when completed), and I'm impressed that so many features are working.

    That being said, I have some questions that I was wondering if other users have come across, and while I know that some of these are emulator specific, the LB community is pretty knowledgeable about these things, so maybe someone can help.

    Playstation Emulation
    Using Retroarch+PSCX-Rearmed

    • I noticed that when exporting out of LB, some of my PSX roms didn't make the journey. The files that launch (on my main Windows LB build) from a .pbp or .bin transferred fine, but any file that used a .cue or .m3u didn't. I had to manually add the .iso and .m3u files to the LB folder before I copied the whole thing to my device. Games that use .m3u include Metal Gear Solid 2 (2 discs) and the Final Fantasy games, and a .cue-based game would be something like Wipeout 3, in which the music track information resides in the .cue.
    • On the subject of Wipeout 3, while the game did successfully launch and run in Retroarch, none of the CD music was audible. I have verified that the game does in fact work with the CD audio on my computer, and I'm not sure what I need to modify to get it working correctly on my Android device.
    • Related to that issue: Currently, I cannot specify which file LB needs to launch. So in other words, I'd like to configure LB to use the .cue file to launch Wipeout 3, instead of the .iso. Are there plans to include such an option?

    Dreamcast Emulation
    Using Retroarch+Flycast

    • More of a comment than a question: I had to manually add the BIOS files to my Retroarch folder in order to get these games to work. Same goes for PS1 games. Really, just add all the BIOS files you have to the /system folder in your Retroarch folder.

    Retroarch General

    • Is there a way to use custom overlays/bezels? I was able to somehow load my PS1 bezel, but I could still see the controller button overlays. As far as I can tell, there's no way to just have the bezel, and not the overlay. Anyone know of a solution?

    I had other questions, but I can't think of them right now. Suffice to say that this is a fantastic start, and I can't wait to see what other features come on down the road. Thanks!

    • Like 1

  4. Tycho's BigBox DOS Intro

    View File

    I just spent about two weeks adding my old DOS games to my BigBox build, including creating individual dosbox.conf files for each game, keybinding changes for modern gamepad support, and Roland MT-32 emulation for all my favorites (Sierra adventure games represent!) and I figured I'd make a special startup video that focuses on DOS games. Enjoy!

    Runtime: 30 seconds
    Resolution: 1920x1080
    FPS: 30
    Filesize: 19mb
    Music: Extreme - Play with Me

    Now if you'll excuse me, I'm going to watch The Goonies again...


     


  5. Tycho's Arcade Startup (Version B)

    View File

    Yeah, I'm addicted to making these startup videos. This one's got a focus on arcade games and an 80s style logo stinger (version B).

    Update: An alternate version of this intro, with the MAME logo subsituted for the BigBox logo, is located here.

    Runtime: 30 seconds
    Resolution: 1920x1080
    Filesize: 20Mb
    Music: Dance with the Dead - "Screams & Whispers"

    I hope you like it! And if you feel the inclination, let me know if you prefer version A or B (the only difference is the logo stinger at the end).


     

×
×
  • Create New...