Jump to content
LaunchBox Community Forums

gibbawho

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by gibbawho

  1. Sorry, didn't see this until now. But ofcourse. Gladly. For now, this post is edited to reflect.
    Want me to package a text file with it or something? Or would editing the post on youtube suffice? Whatever works for you.

  2. 5 hours ago, Flyojumper said:

    Yes I am aware of that. I can't comment on other setups it breaks, but in the case of dex incompatibility (the one setup that it breaks that I am familiar with), once in Dex mode outputting the video to an external monitor or TV, you just cannot open any app that is considered as a launcher, whether it is currently set as your launcher or not.

    I'll take this as another example of the lesson i'm always learning, that my lack of imagination in thinking of problem scenarios seldom means they don't exist :D

    • Like 1
    • Haha 1
  3. 17 hours ago, Jason Carr said:

    I have thought about that, but the problem is the development and administrative overhead that is introduced in having to maintain two releases. We have multiple systems that would need semi-significant coding updates in order to support it. And yes, we could provide just a custom one-off download, but ultimately that risks messing up things like metrics and such, so unfortunately it's not an easy problem to solve.

    Oh right. I wasn't even considering telemetry and such. Well I guess just put me down as a supporter of the attempt :)
    I'll keep with my hack solution for now. I wish android keymapper apps didn't break in most emulators or this whole thing wouldn't even be an issue.

    PS - Always a pleasure to get a response from ya, Jason. Best frontend ever... And i've been around.

    • Game On 1
  4. Thanks. I read it. This is slightly different though. I'd only be talking about a side build for people who want that. Specifically not in the general consumption build. Like a "grab this one if you want it" thing. Which is normally something that'd be ridiculous to ask for, maintaining 2 builds for a minor use case, but in this case its like not even really code base changes. Just the apk manifest. And since they don't go through play store ... thats one hurdle gone. I've gone in and hack edited mine to do this anyway.. but its a pain with updates.

    Btw just a side note.. and off topic, really, because its not even what I'm asking for but.. you know you don't have to use a launcher app as your launcher right? Like ... it just functions like any other app if you don't make it your launcher. Gestures and buttons will still treat it separate and home will still take you to your launcher. It will ask if you want it to be your default launcher but you only have to say no once i'm pretty sure.

  5. Its essentially 2 lines in the android manifest and would make my life a hell of a lot easier.

    <category android:name="android.intent.category.HOME" />
    <category android:name="android.intent.category.DEFAULT" />
  6. Yeah i downloaded his set and checked them out. his bezels are all mame bezels. while you can use them in retroarch in the sense that you can use any mame feature in retroarch, they aren't actually using the retroarch overlay system and can only be used when a mame core is loaded. They are awesome. I wish retroarch's overlay system could do such things. i'd have a ball making bezels. I just don't have much interest in making mame bezels or i'd be doing it already.

  7. 8 hours ago, Retro808 said:

    His bezels are for use in Retroarch.

    his retroarch bezels have turning handlebars?
    i don't see the ones in the video turning. the bezel in that video is for mame, anyway.  with my understanding of retroarch's overlay system (which very well may be lacking, so i'd love to know how, if so) that wouldn't really be possible except maybe some gif trickery. that can totally be done in mame bezels, though. i want to find whichever ones you're talking about and dig into them to learn if its true.

  8. I was messing around with RetroArch's overlay system and made this cool little animated bezel for gba. The buttons visually "press" on the screen when you hit your controller buttons. You can also click the overlay buttons to control your game, which I assume means you could potentially use it as touch controls on a mobile device but I don't know why you'd want to. Enjoy!

    original gba photo by hydef

    Download here: https://mega.nz/file/8ssVzIgR#J8xo28OP_JMAYfBWcHHL3k2PQfbu7gX_fhPMBV7uKb4

    gba-bezel.thumb.jpg.71a64da64af119504650237da5852699.jpg

     

    ADDED:
    Replace the background.png in the package with this one if you don't want the shine across the screen:
    background.thumb.png.e002e32f08fa0b2e60e7ec64bb43f113.png

    • Like 2
  9. 1 hour ago, Lordmonkus said:

    Retroarch Mame for non arcade is a pain in the ass but here is a thread that might be of some help to you.

     


    Thanks so much! Found exactly the useful tips i needed there and got it working!

    • Like 1
  10. I'm not sure if this is a noob question or not, but its definitely making me feel like a noob. I'm trying to set up Casio PV-1000 in Launchbox through Retroarch's Mame core and I'm having trouble. Here's my setup, what I've run into, and what I've tried so far.

    First of all.. I have my roms set up with a softlist (pv1000.xml)

    My RetroArch/System/mame/roms/ folder and the pv-1000 folder inside can be seen in the screenshots below.

    mame01.thumb.png.bdae977203a4889427b8de5d4a9699fc.png  mame02.thumb.png.14292b85e9814d9c90e3f729a2d256f4.png

    You'll notice the zip files and bin files therein are named properly as per the attached XML softlist.

    When I attempt to launch a game I am greeted with this screen:
    retroarch01.thumb.png.746458aaecbee89b06d51b3113e95b6b.png

    I can then navigate to the correct rom from here:
    retroarch02.thumb.png.c704020373d82344980ee0ce5c390a28.png

    And it seems to load just fine:
    retroarch03.thumb.png.755cce3ae8161fbe9db19f50bf119909.png

    Now, if i exit retroarch, any time I attempt to launch any PV-1000 game it will load into whatever rom I last successfully loaded through the mame interface. Unless I empty the cart slot in mae and THEN exit, in which case I will be greeted once again with the first screen next time I launch a game.

    So the retroarch mame core can clearly see and load the game just fine. There's something about my setup that seems to not be telling the retroarch mame core to launch any game.
    I've provided some screenshots of various pertinent settings in launchbox and the retroarch mame core options:
    launchbox01.thumb.png.17d949943e6f07d68c6174830b382120.png  launchbox-emulator01.thumb.png.63058a2594c5e65366f24cd2274b9272.png  launchbox-emulator02.thumb.png.7de1a3dae6c9610888931c19b0f1c346.png  

    retroarch-settings01.thumb.png.56f34476910a8efe6ea07272e69516eb.png


    Are there any glaring errors anyone can see in my set up? This system has been an unusual thorn in my side. Any help I can get would be much appreciated.

    pv1000.xml

  11. Oh man. This gets my imagination going on what this means for the mobile app features. *excited wiggle*
    If this means what i think it means.. yes. 1000x yes. This is the direction I want to see!

    • Like 2
×
×
  • Create New...