Jump to content
LaunchBox Community Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


CDBlue last won the day on April 15 2019

CDBlue had the most liked content!

Community Reputation

69 Excellent

About CDBlue

  • Rank
    32-Bit GPU

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have neocd setup in my retroarch. Although I use FBNeo mostly for neocd (I have bin/img files) I have tested neocd and it worked for me. You are correct about the system/neocd folder needing to exist. For the record, these are the files I have in mine: 000-lo.lo neocd.bin neocd.srm (don't quite recall why this is in there) The best thing to do first is match the SHA1 hash values for the files you have with the ones recommended for the neocd core (as can be seen here - https://github.com/libretro/neocd_libretro) If they don't match then likely that's the issue. If they do match, then I'm not sure what else might be the cause, other than maybe bad chd dumps maybe
  2. Thx for the reply. I just saw updates and assumed it was changes to one the downloadable elements. Updating the text in the thread wouldn't need updates notes I guess heh. Thx for the clarification
  3. Liking this theme very much, nice job. One thing though, I noticed you updating this thread alot, but there are not notes as to what's being updated. Can you please add notes each time you update something so we know what's new/changed? Thanks
  4. yeah, to me I would say it still sounds like a parent/clone thing as I mentioned above. I would assume that it works from in Mame's UI because that is likely set to only show working roms (as it scans your rom folders and figures out which files are all there to make roms work, and will not show roms that don't have all the files needed). But importing into LB will import all roms, regardless if they have all the files needed to make them work or not... and it seems like some of those don't have all the files needed. The only thing I can suggest is to check to make sure you have a complete rom set, including all the bios, chd, sample files, etc. needed for all those roms to work (parents and clones).
  5. See below thread. It's an older thread for an older version of Cemu, but it should still be relevant.... esp. the part about the game files and how to import them into LB There's also an older video/tuturial that might be helpful as well:
  6. Out of curiosity, can you screenshot, and paste into this thread, the edit page for 1941 from within launchbox? Wondering if maybe when you imported the games into LB it made a clone the default file that it's trying to load, and that's missing files, while the parent would work properly. When in the Mame UI you likely have it set to only show working roms, so loading from within that UI would load a working parent (maybe)?
  7. Just out of curiosity. Where is your mame.ini file? Is it located in the root of your mame folder, or in the ini folder? If it's in the ini folder, try moving it to the root of your mame folder and see if that makes it work from within launchbox. If the games work in mame, as you said they do, it's gotta be some little disconnect with LB and the setup/folder locations I would expect.
  8. I believe the only emulator at the moment that does any decent job in emulating the Sega Naomi 2 boards is Demul (stand-alone/closed-source emulator)
  9. It's been a while since I used Desmume stand alone, but if I recall this might be a bug/issue that's been reported many times to the Desmume team. I believe most people suggest patching the code with a line that forces it to go black and then compiling the code (if I recall that is). which for most people is not likely going to happen. In the end I ended up using the Retroarch Desmume core which the last time I used it (a while ago) didn't suffer from that bug/issue.
  10. Hmm not sure there as I don't use the MAME core in retroarch as I prefer stand-alone MAME. However, it might be related to a newer option that was added recently (around version 1.7.7 I believe) which made it so you could select to have retroarch only close when you pressed escape twice. Check your settings and disable that option and see if that helps. Here's a video on where to set it:
  11. Hello fellow emulation junkies. Thought I'd post this here in case people don't stay on top of their emulators like some of us do... Retroarch just released its latest version, 1.8.2. Here's a link to the release notes page. https://www.libretro.com/index.php/retroarch-1-8-2-released/ One item of note, which I've been waiting for a long time for them to implement, is the following: CORE UPDATER: Add option to update all installed cores Now with one press of the button Retroarch will look at the cores you have in your cores folder, check the buildbot site, and if there's a newer version of that core available it will download and update your core file. Anyway, enjoy
  12. It really depends on what your system can handle. Unfortunately, PS emulation can be demanding when it comes to upscaling etc. I have a decent system and I have no issues with the below settings for the Beetle PSX HW core (I believe these are the only settings I changed in the core options): Renderer - Hardware (will only work with Vulkan or OpenGL video drivers - if your card cannot do these it will fall back to Software rendering, in which case upscaling is likely not going to work well, if at all)) Internal GPU resolution - 8x Internal Color Dept - 32bpp PGXP Operation Mode - Memory Only PGXP Vertex Cache - Off PGXP Perspective Correct Texturing - On The Libretro docs page has good information on the different settings and what they do. Worth a read if you're looking into tweaking the core options, etc. - https://docs.libretro.com/library/beetle_psx_hw/
  13. More importantly. do they run from within Retroarch directly? If not, then it's a bios/retroarch issue that needs to be looked at. If they run in Retroarch, then it's a config issue in LB/BB. You need to narrow it down first before looking to see what needs to be fixed
  14. I recommend trying to use the Bettle PSX HW vs just the Beetle PSX core if you can (unless you're going for a more authentic experience and not upscaling, etc.). The HW version of the core adds features such as PGXP Operation Mode, PGXP Vertex Cache and PGXP Perspective Correct Texturing that you can play with to make some major improvements with how the image looks (things line up better, less texture popping, etc.).
  15. They were correct. The K in the intel processors means that the cores are unlocked... meaning you can overlock them easily (as long as the motherboard supports it) But, overlocking is a tricky question to answer easily. Some games/emulators are single-core/thread bound, in which case having more speed for that core can make a difference if the stock speed of your processor is not allowing the emulator to run at 100% speed. However, that being said, the main thing to consider though when overclocking a processor is to make sure you have adequate cooling for the processor, as overclocking it can significantly increase the temperatures it generates. The stock processors coolers for intel for that era (and even now really) are not good for anything other than minor overclocking, which likely won't do much benefit for the most part. So, unless you have an aftermarket air cooler on your processor, or a AIO (water cooler) then I would not suggest tinkering with overlocking the processor as the tiny overclocks you might be able to get won't affect anything for the most part. Getting a decent GPU will benefit you much more than overclocking a processor
  • Create New...