Jump to content

Agozer

1Emu Veteran
  • Posts

    19,930
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Agozer

  1. Supposedly the 64-bit version of MAME is faster on 64-bit operating systems, but it's not like I have any hard evidence of it. Most widely used derivative MAME builds are 32-bit only. At least the last time I checked.

     

    As for reading material, the FAQ on the official MAME site explain a few basics about the vanilla, command line-driven MAME: http://mamedev.org/devwiki/index.php?title...Asked_Questions. Another fairly good place for info here: http://strategywiki.org/wiki/MAME

     

    More reading material can be found on Google without too much effort, and with decent search terms. You can also ask for specifics here if you feel like it.

  2. Just because some parts of the forums are inactive, doesn't mean that we don't keeps tabs on them.

     

    Anyway.

     

    Press F11 for the Neo-Geo Test Menu (this is covered in Kawaks' documentation). Look for and entry about Soft DIP Settings, then select the game. You should see a list of various options pertaining to that particular game. Make our changes and Press C enough times to go back and exit to the regular game. Note that if you have the 'Censored' version of he game to begin with, no amount of fooling around with the DIP settings will enable fatalities.

     

    The above might also apply if you keep the emulator in Console mode instead of Arcade. I'm not entirely sure about that, since I rarely play in Console mode.

  3. You could actually put some effort into posting in the appropriate forum section. Moved.

     

    To answer your question, download the official Samurai Shodown V Special romset (Set 1 to be exact). It has fatalities. I the fatalities aren't enabled from the get-go for some reason, they can be enabled from the Neo-Geo's internal game settings. All the current Neo-Geo emulators support this set, starting from MAME. No, do not ask where to downlosd the romset.

  4. Are you using the very regular, command-line driven MAME or one of its derivatives, with a GUI? Because by the sound if it, you have the official 64-bit "Windows" MAME, which functions mostly via command-line only.

     

    This setup is definitely not ideal if you truly are as new to emulation as you claim to be. A much friendlier alternative would be to download a plain x86 build (i.e. 32-bit) of say, MAME Plus, which has a neat graphical user interface. This makes fiddling with MAME's global emulation options much easier, including enabling/disabling triple buffering and refresh rate sync, and vsync.

  5. I use my Ps3 daily. If not for gaming, then for videos. Plus, Mass Effect 2 is released in a few days. I'm not that interested (yet anyway) about possible ways run run homebrew and backups on my PS3.

     

    P.S. The PSN Store isreally great. My only gripe is that the EU PSN doesn't get nearly as many offers as the US, especially when it comes to PSOne Classics. Aside from a few Final Fantasy titles and Vagrant Story that I already own on disc, the rest of the offerings are more or less mediocre shit.

  6. No, there are no alternatives to the bundled plugins. At least not to my knowledge. I don't think there are any settings that would affect one loud beep. Changing the sound buffer setting only applies if the sound is scratchy or skips.

     

    All I can think of is that DEmul doesn't know how to properly emulate the game, the game is somehow corrupt, or the beep is a trait of the BIOS/Flash you use (being corrupt or something else). maybe DEmul doesn't like your audio hardware. I'm just speculating, though. Having said that, what does the console window say? Anything relating to sound?

  7. It doesn't matter which folder the VMS is in, since the one you created is the active one (i.e. its filename is in the box under Port A in the VMS Manager). Sure, if you want some consistency, put it in the memsaves folder, but you have to re-select the file in the VMS manager afterwards.

     

    Sorry, can't say tell you anything about the loud beep. Google it, it has happened to other people, I'm sure. It might have to do with the Dreamcast hardware itself rather than the game or the emulator, but I'm just guessing here.

  8. Let's review a bit.

     

    1. You open up the VMS Manager, Click edit next to the first slot in Port A.

    2. You click Create Vms, give a filename of your choice and click Save.

    2b. Click Format Vms. Shouldn't really do much since there aren't any data to format. For shits and giggles.

    3. Close the Vms editor with OK. The filename you gave now occupies one space in the VMS list under Port A.

    4. You start the game, but the game still insists to clear blocks.

     

    Are we on the same page here?

     

    Anyway, if the game still goes on and on about freeing slots, try Formatting the VMU/VMS via the Dreamcasts internal VMU Manager, if possible.

  9. "Not enough memory block space" message in-game means that the VMU/VMS has not been either hooked up or formatted. Make sure that the is at least one VMS set up for Port A in Plugin settings. Then use Demul VMS Manager to create a new VMS file for use (Edit --> Create, give name, Save, Format, OK).

     

    If the Dreamcast menu always asks to reset date and time, your Flash file (dc.flash under nvram directory) is corrupt. Delete it and try again.

    When I go to VMS Manager>Edit>Create, then I type a name and hit Okay it does nothing. Nothing gets added to the list. Am I doing something wrong? Trust me I just spent 10 minutes looking on Google before asking, lol.

     

    Okay, I read that somewhere else. I'll have to find a new dc.flash. I can't seem to find it on it's own so I guess I'm going to have to download another pack just to get it :/

    That "list" you speak of lists the VMS data that's been saved onto the VMS (that is, game saves). If you just created and formatted one, of course the list is going to be empty. Like a I said earlier, click OK, and see that the VMS' filename shows in the VMS Manager under Port A.

     

    Just delete dc.flash and see if Demul agree to run without that file present. If so, then Demul creates dc.flash based on the info it finds in your BIOS files. If not, then you need a proper Dreamcast flash file present, and Demul then creates dc.flash based on the data in the other flash file. Sorry for being vague and indecisive, but it's been a really long time since I've had to think about this stuff.

  10. "Not enough memory block space" message in-game means that the VMU/VMS has not been either hooked up or formatted. Make sure that the is at least one VMS set up for Port A in Plugin settings. Then use Demul VMS Manager to create a new VMS file for use (Edit --> Create, give name, Save, Format, OK).

     

    If the Dreamcast menu always asks to reset date and time, your Flash file (dc.flash under nvram directory) is corrupt. Delete it and try again.

  11. If any given game won't boot but shows the audio screen, that's usually a dead-on indicator that the disc image you have really isn't selfboot. Well, usually, as there are some oddball exceptions. Since you're using gdrDemul, I have to ask: have you burned the Ecco disc image to a CD-R or are you using a virtual drive? If you have the game on CD-R, are you sure you've burned it properly?

     

    It would be less hassle for you if you'd use gdrImage plugin instead, and use that to mount the disc image file directly and play using that. No need for physical media.

  12. For starters, use a nullDC version that isn't old as hell. 1.0.3 is what most people use if they favor nullDC. Demul is also a [perhaps better] option. If your disc image is selfboot (like most should be, at least those that have been properly ripped), you don't need to mess around with a bootdisc. Anyway, you've said nothing about the plugin setup you use, specifically the GD-ROM plugin in use.

     

    By the looks of it, the Utopia bootdisc messes nullDC up completely.

  13. This has nothing to do with DSEmu. Moved.

     

    You need to st No$Gba to emulate the correct savetype. The current selected savetype is wrong, i.e. not the one that the game expects, hence the message.

×
×
  • Create New...