Agozer

Good news, although I have to confess that it's been ages since I've been stoked about a new Mortal Kombat game. Kratos fits perfectly in a bloody game like MK, though.

- FAS is borked - ACP password (I know, I'm a broken record) There was something else as well, but I can't remember what it was.

Well... - Combine the Arcade subforums into one. - Combine the Sega subforums into one - Combine the "General X" subforums into one - Same with Nintendo stuff and perhaps Playstation (with the exception of the Wii and the PS3) - Put Wii, PS3 and X360 under "Next Generation Consoles" or something like that - or rather, "Current Generation" - Does anyone truly care about MUGEN?

This whole turmoil surrounding Assange has reached astoundingly ridiculous levels regardless of what one actually thinks of the guy. I'm begininng to think that these girls spotted Assange at some party, realized who he was, and decided to get their 15 minutes of fame one way or another.

Did you lol at the ending credits? Yes, very much. Damn, that was awesome. A bit of a throwback to old(er)-school gaming. I think that it was a great detail to actually see the faces of the developers.

I sorta kinda figured you'd run into this since the archive is 7-zipped. Both WinZip and WinRAR can work with 7-Zip archives, or if you're feeling adventurous, download and install the official 7-Zip Archiver (Google it).

We have very nice and picturesque snow over here. There's a lot of it though, so I suspect that commuters and public transport are going to having a rough time tomorrow. But yeah, snow doesn't suck over here.

From the official homepage, naturally: http://www.vba-m.com/ It's bundled with a vba-over.ini file that already has lots of settings for various games, including Pokemon games. Don't know if LeafGreen's in there though

Console ROMs are dumped using specialized backup units (i.e. copiers) that are connected to the console in question, and then dump the contents of the cart to a ROM image. Said units also often feature a floppy disk drive, and thus ROM images can also be played on the copiers. There are some exceptions, like the units designed for the SNES games, since many games use proprietary custom chips by Nintendo (S-DD1, SA-1, etc.), which some copiers don't support. The copiers often come with the needed software to perform the dump. Dumping ROMs from arcade boards is an entirely different matter, seeing how there aren't (or weren't, I don't know what the situation is now) any specialized kits for doing it. This force the dumpers to not only come up with the hardware solutions, but also software solutions created from scratch, usually one for every piece of arcade hardware. As the games and their protections grew more complex, the dumping hardware and software had to be redone. This is the main reason why proper romsets and their emulation for hardware like the CPS-3, Model 2, the Neo-Geo etc. took so long. With optical media, there really isn't much to it, with the exception of the GameCube, which in itself isn't much of an exception anymore either. As for writing emulators and making them work... I'm not the expert since I've never done anything like that. Anyway, developers either get official hardware documentation detailing memory addresses/areas, graphics creation and start recreating that in ASM or C, but this is very rare. In many cases, someone in "the community" takes upon him/herself to see how a running game interacts with the hardware and arduously documents every bit of detail, probably having to again write specialized software to track changes in memory and how/where data behaves and moves when a game is using the hardware. With the documentation, a developers creates the emulators core, which at first contains the very basic necessities of the emulated hardware. This core itself won't boot any games, but can be tested with various Test ROMs, Demos and self-created test programs to see if the core does the very basics right. Then it's off to emulate graphics, sound, inputs and what have you, to the point when you can see/hear/control something. Then it's just fine-tuning and going over the documentation again, until the devs have something that would be considered a working emulator.

Just as a reminder, you risk getting banned should you post any torrent links here. As for this: Are you sure that wasn't a PS2 emulator of sorts? Like you said before, PS2 emulation seems to work on your computer a lot better. Dreamcast emulation, on the other hand requires lots of processing power and a decent graphics card (both which you seem to lack, judging by your problems) to run even remotely smoothly and without graphics glitches. For the most part anyway.

Still ancient. Use VBA-M. Anyway, create a new text file, for example. Type in what you need to. Just remember to save it as vba-over.ini and not vba-over.ini.txt (which will happen if you're not careful). Or, if you are really feeling helpless and stupid, and what the easy way out, just make a copy of vba.ini, clear it of content and rename the copy as vba-over.ini.

Managed to clear a particularly nasty bit in Dead Space. The game was just sitting around for months because that bit got on my nerves too much. My faith in the game's awesomeness has been restored.

Checking that box really does noting unless you have a separase IPS file with the same name as your ROM in either the Save folder or the ROM folder, I forget which one. vba-over.ini works exactly like it was written in the first post in that other tread. 1. Create an empty file and name it vba-over.ini (not vba-over.ini.txt or some other stupid shit like that). Place it in VBA's main folder. 2. Open it in Notepad (or whichever text editor you use) and type in or paste the lines that correspond to the game you have: i.e. if you have LeafGreen: Pokemon LeafGreen (U) [BPGE] flashSize=131072 The first line is the filename, without the extension. This needs to match your ROM, for obvious reasons. The second line is the Game Code, which can be found by loading a game and choosing File --> ROM Information. The last line is the savetype specification. Most Pokemon games seem to use flashSize=131072, but don't expect it to work for all games. If the game uses the Real Time Clock to measure time, the line rtcEnabled= is also present (just so we're on the clear, LeafGreen doesn't use the RTC, to my knowledge anyway). 3. When you're done, save the changes. P.S. i don't remember if I asked this, but what version of VBA are you using? Don't tell me it's 1.7.2 or something ancient like that.

Perfect guard and the ensuing criticals have always been very strict with their timing in Onimusha. I'm torn on whether that's a good or a bad thing. I think Capcom tweaked the timing to be a bit less unforgiving in Dawn of Dreams, but not by much. Is PGing too easy in LOS or just right? P.S. Where the hell is my PS3 Onimusha game? We got Sengoku Basara Samurai Heoes, but that's not same thing.

Vanquish. I'm close to the end, but it's been good times.

If you don't know that you have an IPS patch, then you most likely don't. IPS patches can be separate files, which the emulator patches into the game on the fly during emulation (soft-patched), or the IPS patches might have been added the the actual ROM image before hand with an external patcher tool (hard-patched). Like I said, if you don't know, assume that your game is not patched in any way. Then again, you could always ask your friend for confirmation.

The first Mortal Kombat movie was definitely good. The second, not so much, but I still got a kick out of it. I personally think that taking the middle ground is almost always the most effective method story-wise, although that doesn't guarantee that the movie will be any good. Sticking to the original story is no good if the story of the source material is no good in any conceivable manner --- Just winging it and not giving a fuck about the original story can lead to the existing fanbase denouncing the movie outright.

In short, no.

What most likely happened here is that the save type VBA emulates was wrong for the very beginning; if the emulated save type if different from what the game expects it to be, the saving process will fail spectacularly. Even if you set the correct savetype in the emulator right now, you'd have to start the game from scratch. The savestate you used to save your game still contains data that tells the game that the savetype used is something unknown to it -- despite the emulator is emulating it correctly.

If the emulator gives you a "write state" message or something similar, you are using savestates, which is not the same thing as using the game's own "proper" save feature. Given your responses, I don't think you've saved in-game properly at any moment during your gaming hours. Save states are not a viable alternative to actual in-game saves (although they can be used as such), and can sometimes be quite volatile and unreliable. Now, what exactly does the game say when you beat the Elite Four? Does it try to save your progress automatically and failing at it, or what? And what exactly do you mean by "i was wondering if there is actually a way to be able to continue after beating the elite four in leaf green", and how exactly does this "save problem" of yours manifest itself?

They make reality TV out of everything these days. Bam Margera "getting married" is no exception.

I don't know enough about Pokemon to tell you what's supposed to happen after you beat the Elite Four, but if you truly have a genuine save problem, read this: http://www.1emulation.com/forums/index.php?showtopic=17613 It's sticked and all. In this very subforum.

Like so many have said before me, the true potential in Demon's Souls comes from the "feature" that allows you or others to join a game in progress and help out, or on the flip side, invade a game and slaughter whoever was playing.

Hahahah, that's just wrong. In all fairness though, I'm amazed that you've had the patience to get that far.

Well, you should at least try one of those and see if saving and loading native saves and save states works without a hitch. Of course, you should also try your old save and see if those emulator pick it up. Just remember to rename the save file to match your ROM.