Jump to content
LaunchBox Community Forums

Zombeaver

Moderators
  • Posts

    4,018
  • Joined

  • Last visited

  • Days Won

    54

Everything posted by Zombeaver

  1. For standalone, Alt + Shift + 1 configures player one controls and Alt + Shift + 2 for player 2. For RA it's just configured like any other core.
  2. And I take it this is one that you already ran through CDMage? Scroll down to the "Firmware/BIOS" section here to see what you should be using for the bios files. sega_101.bin is the Japan bios and mpr-17933.bin for USA. They need to be named exactly like that. The specific hashes are listed in that link. They should be in the base Mednafen directory (or firmware subdirectory) for standalone and the system subdirectory for RA.
  3. Derp. I was using unsafe_save_state = 1 instead of unsafe_save_states = 1. It's working now Thanks! It does indeed seem a bitty iffy though based on some testing.
  4. Not that I'm aware of. DOS art can sometimes be difficult to find general, let alone 3D boxes. There's a decent amount of box art between our DB and Mobygames, but not for 3D boxes. Emumovies doesn't appear to have any either.
  5. It was a joke haha. Actually, in my experience GOG's aren't even ideal in some cases. A lot of times they're using older versions of DOSBox which don't have all the features available in newer builds, sometimes they're using weird scaling options, none of them use Novert, etc. Sorry, that's probably not what you wanted to hear Often I don't use GoG's included .conf - I just install the game and then create my own and hook it into LB's instance of DOSBox instead of using what came with the install. I've got Crusader: No Remorse, King's Quest 7, and Tie-Fighter. I don't have Wing Commander Prophecy in my library but I have WC3, which should be the same or similar settings. I'll check out WCP and Strike Commander.
  6. That's possibly a bad rip or just a bad cue sheet. Open up the cue sheet in notepad and make sure it's directed to 1) the correct file name and 2) isn't in some specific subdirectory that came from the computer of whoever created the rip originally. The top line should say FILE "yourromfilename.BIN" BIN And not something like "L:\subfolder\that\doesn't\even\exist\on\your\computer\wrongfilename.BIN" BIN ePSXe basically just figures out what it should be even if the sheet itself is wrong - for Mednafen it actually needs to be correct.
  7. Nope, not unless you count GoG I make them myself. You can sometimes find some suggested tweaks in a game entry in the dosbox wiki, but I rarely use them. Some things are a matter of personal taste and some things are computer-specific so it might be difficult to have a definitive .conf for everyone for each game. I'm happy to help though, if you need any. I've got about 150 DOS games in my library.
  8. Yep, the md5s are listed in the link I included
  9. Honestly, most of them work with some pretty basic base settings. You might have to switch from 1200 to 500 or vice versa but that's about it. More often than not it'll work without much fiddling at all; as long as you've got everything squared away with a solid default configuration to start with. I get what you're saying though. Awesome, looking forward to it!
  10. As a pretty hardcore collector myself, I feel obligated to say "Don't do it man!" That being said, while it's true that VGPC can be a decent guide (I use it in both my purchase chart sheet and my full collection sheet and as a starting point when I'm looking for something in particular), you need to keep in mind that those prices are for individual games, not a lot. No one is going to pay individual prices for an entire lot because the entire point of buying a lot is to get games at a bulk rate. Personally, I don't pay VGPC even for single games, let alone a big lot. That purchase sheet is all from within the last year and the vast majority of it was bought game by game and I'm about 45% below VGPC overall. Your options are basically to either drop your lot price by a good bit or sell them off one by one. Or you could keep them, sell some plasma, and maybe find a job that you could carpool to.
  11. There are bad/incomplete dumps floating around the internet. Something else to keep in mind though is that there are separate ones per region as well (NA, PAL, and JPN) and you need them all if you play games from those regions. If you try to load a PAL game with only a NA bios, it won't work. They also need to be named correctly as noted in the bios section here http://emulation-general.wikia.com/wiki/Using_RetroArch As far as Mednafen, there are two versions - normal (software) and hardware. The hardware one allows upscaling but it's somewhat preliminary and you may run into some problems (especially performance wise). I use the normal one. Personally I think upscaling tends to make PSX games look weird/bad anyway.
  12. It could be a problem with your bios. If it's not properly recognizing the games (if it thinks it's an audio CD or just otherwise an unsupported disc) that's what it might indicate. It's possible that they're bad dumps of the games, but typically that would cause RA to just crash outright if you're using Mednafen.
  13. I like the idea here, but honestly this just seems overly complicated to me. Literally the only reason I've started using FS-UAE is to get away from this sort of thing. WinUAE has a lot more features than FS-UAE, but FS-UAE is easier to setup - especially if you're just using WHDLoad zips. I've used WinUAE for some time now and, prior to FS-UAE, my process was to load the adf(s) into WinUAE, adding disks to the swapper if it's multi-disk, and then saving it as a single .uae configuration file (named after the game title), then importing that configuration file as the "rom" in LB with WinUAE as the emulator. That works but it can be somewhat time consuming. There's nothing wrong with doing it like this at all, but I guess my perspective is that if I wanted to spend this much time getting things setup for each game I would just continue to use WinUAE because the only thing that I like more about FS-UAE than WinUAE is the simplicity/ease of use (which you're basically eliminating by going through all this); well, that and the interface is a bit nicer. If there was a way to quickly automate/streamline this process I'd totally be on board - but this seems like even more work than what I was doing with WinUAE
  14. Here's one for Atari 8-bit which, currently, is a custom platform but should be incorporated into the DB at some point, consolidating the current Atari 800 and Atari XE platforms and encompassing the entirety of the Atari 8-bit line of computers. Stealth is a game that's not super well-known but it should be because it rocks. It's on the C64 as well, but I think the 8-bit version is a bit better. Normal: Sketch:
  15. I tried that last night because I read about it elsewhere, but after adding that into the .ini the "save state" and "load state" menu options (accessed when hitting start on the 360 controller when in-game) are still greyed out. Am I missing something?
  16. You'll only have one "default" dosbox.conf so yes, you could put a custom one in the dosbox folder but it will be overwritten if you make changes to the conf via the LB UI, though it shouldn't happen just from updating LB. The best method is to just create .confs for each game. When you import the game, go to the DOSBox tab and where it says to use/browse to a custom .conf tell it to create one and then save it in the game's folder. It'll be created based on whatever you have in your default dosbox.conf in LB but this way you can individually tweak them per-game. There's no one-size-fits-all solution to .conf settings so individual .confs allow you get the best settings for each game.
  17. Yes, if you have bin+cue you should always be using the .cue - sometimes they'll "work" if launched directly from the bin but it often causes problems - often you'll lose music tracks as their location is specified in the cue sheet. Sometimes they just won't boot at all.
  18. Do a google search for "sega saturn region patcher srp 3.0 gold edition" Open the one that didn't work on it and see what region code it has listed on the right. If it's one of the pal ones, uncheck it and then click "U: North America" and then click "Let's patch your image" and then try it in Mednafen again.
  19. If it is a PAL game though you can region-patch it to change it to NA. I've done that with a few games and it works.
  20. Are you using a PAL game? It's not supported currently - just NA and JPN.
  21. So I was a little bit off here because it turns out there was an opening sequence that I was missing. It's kinda weird because it'll basically load either the game or the opening depending on the combination of disks you're using - 2 + 3 for the opening and 1 + 3 for the game. What I ended up doing is creating an additional app for the opening and using the normal launcher as the game. The normal launcher is directed to disk 1.dim and then with additional parameters of x68000 -flop1 %romfile% -flop2 "X:\Emulation\X68k\Roms\Aquales\Aquales (1991)(Exact)(Disk 3 of 3).dim" Then add in an additional app directed to mess64.exe with command line parameters of x68000 -flop1 "X:\Emulation\X68k\Roms\Aquales\Aquales (1991)(Exact)(Disk 2 of 3).dim" -flop2 "X:\Emulation\X68k\Roms\Aquales\Aquales (1991)(Exact)(Disk 3 of 3).dim" and titling it "Opening" I got Phalanx working and in its case Disk 3 by itself is the opening and 1 + 2 are the game. In this case, because the opening is just from one disk, I can just tell it to "Use emulator" in the additional app and direct it to the opening disk.
  22. So I was able to successfully get a 3-disk game to work. The game I experimented with was Aquales. It occurred to me that an actual x68k only has 2 disk drives so nothing should require more than that in order to simply get a game to boot and start properly. I tried just using -flop1 %romfile% -flop2 "[path\to\disk2].dim" but that didn't work. So then I thought "Maybe one of these is actually a save disk or something - let me try a different one" so I then tried -flop1 %romfile% -flop2 "[path\to\disk3].dim" And...it worked! So then I tried -flop1 %romfile% -flop2 "[path\to\disk3].dim" -flop3 "[path\to\disk2].dim" and that also worked. Whether or not it'll actually access that third disk when needed (for whatever it's needed for) I'm not sure - worst case scenario you could always select it when prompted via the MESS file selector and insert it into floppy drive 2. It does show all disks inserted in the selector though. x68000 -flop1 %romfile% -flop2 "X:\Emulation\X68k\Roms\Aquales\Aquales (1991)(Exact)(Disk 3 of 3).dim" -flop3 "X:\Emulation\X68k\Roms\Aquales\Aquales (1991)(Exact)(Disk 2 of 3).dim" I'm not sure if the weird disk order thing is some kind of common convention for this platform that I'm just not aware of or if it's just a fluke in this case, but if something doesn't work in the normal order, this would indicate that you might need to try a different order and seeing what'll boot. I've got some other games that are over 2 disks that I'm going to test out as well.
×
×
  • Create New...