Jump to content
LaunchBox Community Forums

kidloser0426

Members
  • Posts

    22
  • Joined

  • Last visited

kidloser0426's Achievements

8-Bit Processor

8-Bit Processor (3/7)

1

Reputation

  1. I’ll look into a new graphics card. Until then, I’ll settle for nes through genesis consoles and the game boy stuff. Since I know all of those consoles work with my current setup, I’ll just turn my focus towards getting launchbox set up with RA. Thanks again for the help. After getting comfortable with the software, I think the next step will definitely be drawing up plans for a stand alone cabinet and venturing into the territories of setting the cabinet up with an arcade control panel and all of that fun stuff.
  2. Onboard graphics I think? I’m not quite sure. All I know is, I bought this pc two years ago refurbished to build a home recording studio. Then, a better computer came to me for that, so this one has been collecting dust. Figured I’d put it to use. It’s an old Dell optiplex 760 if that helps. I’m not quite sure how to check otherwise. This is all a pretty big learning experience for me. I’m updating RA at the moment to see if that fixes my video driver issues. I’ll keep you posted
  3. Awesome. Thank you. Any word on if the RA update would fix the issues I'm having with the "gl" video driver?
  4. Also, if that stands true for N64, does it mean the same for MAME and similar emulators?
  5. What specs are you asking about? Drivers, video cards, etc?
  6. Tried switching back to gl, and it crashes again. Will the new update of RA fix this?
  7. Ok. So..... the Genesis roms are still loading perfectly. The new roms I'm trying, Nintendo 64, aren't being recognized by retroarch. I've tried both mupen64plus and pralleln64 cores. Is there something wrong with these cores? Should I update retroarch and try again? The rom files I'm using are .z64 files, which mupen64plus claims to run the best. With mupen, I get a message saying "no content found". With parallel, it goes to start the game up, then crashes. Any help would be greatly appreciated.
  8. SUCCESS!!!!! I found that changing the video driver to "d3d" works great on my system. Genesis games are loading just fine, and retroarch has stopped crashing all together. On to the next tutorial!! Thank you guys for all the help and suggestions. I'll keep you posted on my progress, and any of the guaranteed snags I will hit along the way.
  9. I’ll give it a shot and let you know how it works out.
  10. How would I go about changing that? Again, sorry for all the questions. I’m new at this. I feel I may have bit off more than I can chew on this first project. Haha. Maybe I should get my feet wet programming a raspberrypi? Thank you for any and all help/tips.
  11. Changing the video driver helped a bit. I was able to load a rom at one point. Although, it was at the cost of the very nice, fluid menu screen set up on retroarch. Upon switching the video driver back to “gl” the program crashes much more often now. I am no longer capable of choosing the option of exiting retroarch. It just crashes whenever I try and exit out of it, or make changes in the menu screens, or really click on anything for that matter. Could this be a Windows 10 issue? I wish I could revert to an older os, but 10 was on this pc that I bought refurbished 2 years ago, so an older os is unavailable. Maybe a reinstall of retroarch will work. Or, I’ll try downloading the oldest possible version of retroarch I can get for my pc, which I think is 1.6.7. I’ll post updates tomorrow. Thanks for the help everyone!!
  12. The exe loads. I load the core, browse to my roms, click on the one I try to load, then it crashes
  13. Nope. Just trying to load it through retroarch. Could the issue be that I’m using the latest version, 1.7.0? I also have retroarch stored in the emulators folder under launchbox. Could that be the issue? Although, every attempt I’ve made has been through retroarch.exe.
  14. The roms still won't load through retroarch. I moved all of the bios into the "system" folder under retroarch. Was that a mistake? Although, I tried running a game before that and it was a no go. I feel like I had to have missed something in the tutorial, but I've gone back and double checked every step twice. I go to start up the game, and it crashes. Any suggestions would be awesome. I've hit a wall at this point.
  15. Is that a pretty standard recommendation for all rom sets?
×
×
  • Create New...