Jump to content
LaunchBox Community Forums

dragon57

Members
  • Posts

    1,107
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by dragon57

  1. Some of your items are addressed in this thread:

    As to your 'to zip' or 'not to zip' is user preference, but you have to realize how some things will be affected by either choice. I personally 7-zip all my console roms, but many find it easier to just have no of the small console roms compressed as large disk drives are pretty cheap these days. There is no right or wrong here.

  2. While the TV surround can cause a very slight clipping if you don't use a shader to match the round corners like CRT-GEOM (the intent of that TV surround), what you are seeing is way more than you should have. What does your lay file look like for this game? Here is mine.

    <!-- bezel.lay -->
    <mamelayout version="2">
    <element name="bezel">
    <image file="bezel.png" />
    </element>
    <view name="Bezel Artwork">
    <element ref="bezel">
    <bounds left="0" top="0" right="16" bottom="9" />
    </element>
    <screen index="0">
    <bounds left="4.625" top="0" right="11.375" bottom="9" />
    </screen>
    </view>
    </mamelayout>

    image.thumb.png.5a465172d579186a26303f23eb0dafc8.png

  3. 27 minutes ago, Kleigkarath said:

    I did the install through launchbox, not the Github.  But I can look over there and see if I can update through that.

     

    LaunchBox pulls from the same Github, so updating with LB should be fine.

  4. Note: the MAME bezels were just updated a couple of weeks ago. Depending on the age of your files, you may want to reinstall them.

    Here is my lay file:
    <!-- bezel.lay -->
    <mamelayout version="2">
    <element name="bezel">
    <image file="bezel.png" />
    </element>
    <view name="Bezel Artwork">
    <element ref="bezel">
    <bounds left="0" top="0" right="16" bottom="9" />
    </element>
    <screen index="0">
    <bounds left="4.625" top="0" right="11.375" bottom="9" />
    </screen>
    </view>
    </mamelayout>

    • Like 1
  5. 7 hours ago, Headrush69 said:

    Retroarch can drag options in from so many places due to overrides, configs, etc.

    To really compare you should turn on debugging for Retroarch and see exactly what is being read, set, etc.

    Totally agree. Retroarch has a ton of tweaks you can do, but unless you have lived and breathed Retroarch/Libretro over time and understood those tweaks as they evolve, it can be difficult for users to figure things out in a simple way.

    Keep giving us data and info and I am sure this can be figured out.

  6. 18 hours ago, stonev said:

    Thank you so much for this reply and for making me feel like I’m not going crazy! Not about this, anyway. I 100% appreciate your desire to not go into details regarding your potential solution. But just to make sure we’re on the same page, are you also observing the following oddities:

    1. Saving by content directory doesn’t affect all users. Before posting here, I searched online to see if others were experiencing the same problem and I couldn’t find anything. I also asked a buddy to test and he had no problem with the content directory remap working as advertised.
    2. This doesn’t affect saving remaps by core or by game. I’ve tested and those work fine for me.
    3. There seems to be a LaunchBox-specific aspect to this issue. As I mentioned, when I launch content directly through the LaunchBox-installed version of RetroArch, everything works fine. Those settings persist as long as I’m using RetroArch directly, but they do not carry over when launching through LaunchBox (I naively assumed that the correctly named remap file in the designated directory would be the solution, but it’s not). The core and game remaps do persist regardless of how I load content. I am particularly flummoxed by this aspect of the problem because it counters my (again, naive) notion that LaunchBox is simply a very nice front end to run other applications. In this instance, at least, LaunchBox seems to be applying its own logic and over-ruling RetroArch’s.

    Again, I totally appreciate your reticence to go into detail. I appreciate even more your coming up with a potential solution and your work on the Bezel Project (which is soooo awesome)! But - to the extent you’d feel comfortable - I’d appreciate your thoughts on my 3 observations.

    I have seen a number of people who say behavior seems to change when launching Retroarch from LaunchBox versus launching from Windows. Not always, but usually it is related to what is defined in the command line arguments for the Retroarch Emulator section. Have you checked to see how LaunchBox is launching Retroarch? I doubt that command line is basically blank.

  7. This has been a bane to all users of Windows Retroarch and the cores that support more than one system. I work on the Bezel Project team and am well aware of this issue and I am currently working on a solution to this. My testers have told me my latest method works well for them and I hope to roll this out in my Bezel Project Windows app very soon. While my efforts address the issue you bring up more widely than just for bezels, my bezel solution should address what you are stating. I have reached out to the LaunchBox team about integrating my new method, but I can't say more than that at the moment. I have no timeline yet for broad release. Just know a potential solution is forthcoming.

  8. All, an updated themed and system art bezel pack for MAME has just been released. This builds on the original MAME sets that were targeting an older Retropi build. These updates attempt to provide a bezel for every 'working' game MAME supports as of the 0.270 release. If you happen upon a game that is missing a bezel, please go to Github for the particular repo in question and open an 'issue' ticket with what is being requested.

    Also, the issue where the Bezel Project app for Windows disables the overlays setting in Retroarch has finally been identified and should be fixed. A new build of the app (V1.1.13) has been uploaded. Existing installations of the app should reinstall this new release as it contains a new file required for MAME. The app has better support for native MAME installations for games that use more than one monitor for its display. If you want to know when a new version of the app is released, follow this post as I will be announcing it here. You can also watch the repository on Github: https://github.com/thebezelproject/BezelProject-Windows

    Finally, the game list required for LaunchBox has also been updated.

    • Thanks 1
  9. You have two options in my mind. 1. Do some manual pixel offset measuring in a graphics program using those bezels in question, then edit the MAME lay file for the same bezels, then you should be good. 2. Go into the MAME Tab section with the bezel showing and modify the video graphics settings to get the MAME viewport to fit the bezel transparent display port section.

  10. That indeed is the correct flow. #3 is a big pain point for our Bezel Project. I plan to see what I can do about that sometime coming up. All the old requested bezel repos for consoles/system will be done very, very soon (probably a week). Then the plan is to hit every repo for outstanding issues and see if a bullet point structure will alleviate the problem of using a core for multiple systems.

     

    • Thanks 1
  11. It sounds like you have a core cfg file saved with menu_show_overlays set to false. You will have to force save an updated core cfg file inside of Retroarch after changing this to true, or manually change the value inside the questioned cfg files (make sure Retroarch isn't running if you manually edit anything).

  12. 1 hour ago, Kevin_Flynn said:

    After moving to a database, are all data changes required to go through the front-end? What happens to our old method of updating via XML files in the data folder?

    I assume if you want to look at the insides, you just use one of the SQLite tools to lookup and edit the tables. I am sure this is not supported, but I have played around inside of the LaunchBox.Metadata.dB file (never do this with LB or BB running and make a backup first) and had success editing areas/data myself. This is the one I use:
    image.thumb.png.aab47cd60ea7fa2db9d3df7813643843.png

  13. EmuMovies has pretty good coverage for the older cartridge-based systems, but you will find some holes here and there. As I've seen with most sites with manuals, the coverage tends to go down as you approach newer system files.

    I just re-checked for the Atari cartridge systems and most are available on EM. Commodore 64 shows 973 manuals. Your mileage may vary depending on what games you have in your collection.

  14. 43 minutes ago, dukenukem008 said:

    I am able to log in on the website without issue..its just saying "unable to login to emumovies" it must be some strange bug thats only effecting a few and ive changed my password and that didnt work either..

    Just logging in to the web site isn't enough. That is why I mentioned getting through to an admin on their forums to have their side of things using your EMid verified would be the next step. The way LB connects is purported to use a different way of authentication than just logging in to the EmuMovies web site. A LB dev can correct me if I am wrong.

×
×
  • Create New...