Jump to content
LaunchBox Community Forums

Lordmonkus

Members
  • Posts

    11,556
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by Lordmonkus

  1. It is not because it is not in the No-Intro rom set that I have, I don't know if there has been an update made to the No-Intro SNES set or not. If someone knows if it has been included and can give me the exact name of the rom I will gladly add it to the batch file and upload it. The nice thing about these batch files though is that it is a good base set to start out with and easy to modify to add or remove any games you want or don't want.
  2. Yup, pure personal preference. To me the scaled up clean pixels blows the details of the art out and doesn't look how it "was intended". There's an argument to be made that the original artists took CRT characteristics into account when they made their sprite art to give extra details that couldn't be there in the sprite itself. Luckily though we have so many options now to suit personal preference.
  3. Well to be perfectly honest this isn't a "Launchbox problem" it's just something that the emulator doesn't allow for, the vast majority of emulators out there either have a command line option or a toggle to set to load in fullscreen. Even Byuus original BSnes and Higan emulators allow for this for most builds and those that don't will allow an AHK script to toggle it "F11".
  4. I'm just not a fan of the "more modernish high resolution" packs, I like the ones that are more like 16 bit upgrades personally. I changed the shader I use and that helped the performance.
  5. I just had a look at the Donkey Kong one, not too bad looking for a "hi rez" pack but not one that suits my tastes. It was also a major performance hit because of how much it bumps the resolution up.
  6. I am completely stumped on this one. I can get the official builds of Higan, Byuus latest BSnes and other versions of BSnes to fullscreen but this one just doesn't want to play nicely. I tried AHK scripts and stuff but nothing worked, I would suggest contacting the devs maintaining this fork and ask them if there is a way or just use one of the other builds.
  7. My first guess is that the game requires either the dual shock or normal non analog stick controller in the emulator, this is something that can be toggled on the controller, I just can't remember how right now so check the emulators documentation.
  8. Try this, turn on Fullscreen Exclusive in Settings > Configuration > Video
  9. Boxes for some upcoming MSU releases. All my covers can be found on my Google Drive for easier download here: https://drive.google.com/open?id=1IF0pmvUlnYM_rrrjuZMJi4YuWz3EjocS
  10. Yes, you can. Yes, it's actually critical you do so.
  11. You can add your own platform, just go to the bottom of the list and click twice in an empty box and type in the name, make sure it's named exactly like how you have it in LB.
  12. I'm not gonna say you can't ask but I also doubt you will find someone willing to do it for you. I will say this though, I highly recommend you learn to do it on your own. Start small with simple systems and emulators, we have tons of guides here on the forums in written form and videos on the YouTube channel walking you through what you need to know. Learning to do it for yourself will teach you how it all works so when something goes wrong you will know how to fix it easily, it really isn't that difficult.
  13. No, and do not link to these kinds of sites, selling pre packaged emulation setups with roms and emulators is illegal and not allowed here.
  14. Updated the SNES batch file, I shamefully did not have Super Mario World in it for some strange reason.
  15. Double check your Associated Platforms for Retroarch, make sure you have a Game Boy platform and calling the correct core.
  16. Thanks for pointing that out @CDBlue, I had totally forgotten about that.
  17. To be perfectly honest i'm not sure, I think Mame generates its mame.ini file in the ini folder by default but I always manually generate a mame.ini file manually with mame64.exe -cc as the very first step whenever I do a new Mame install which generates the ini file in the main folder. I even put that in my Mame for Noobs guide.
  18. Yeah, it's a weird issue with Mame not being able to read the config file when being told to load from a frontend. We have no idea why it has this issue but it's a common one so that's how I knew to tell you to do that.
  19. Move your mame.ini file from the /ini folder to the main Mame install folder (where your Mame executable is).
  20. All I can tell you based off what Google shows when I put in that error message is what has been said here already, your disk images are bad. None of my PS2 games give this error at all.
  21. Try changing your CDVD plugin. https://forums.pcsx2.net/Thread-Path-IsoFileSystem
  22. On your next system, preferably a popular one like the SNES or Playstation, try importing only boxart (front and back) and gameplay images, you will find it goes much much faster. Of course it could be the server was being slow for whatever reason at the time but I can tell you with great certainty that grabbing fanart will slow the scraping down immensely, some of those images are large png format. Over the last few days I have been putting together a streamlined install of LB, importing and scraping only boxart and screenshots and it didn't take all that long to do. I also only have a 12 Mbit internet connection.
×
×
  • Create New...