Tetsujin 28 Gou Ps2 Iso Game
I've been toying around with FF XII on PCSX2, I initially got PCSX 1.2.1 or something like that and was quite satisfied with how the game looked. Wanted to get shaders working and got PCSX 1.4.0 and can't geem to get the anti-aliasing to work on the text/menu items in game.
Could someone point me in the right direction on what settings are affecting this or how to get the anti-aliasing to work on text too? No matter which settings I change doesn't seem to have an impact on how the text looks. I tried setting all the settings to the same I had them with 1.2.1, but the text is still super fuzzy and grainy. I've been toying around with FF XII on PCSX2, I initially got PCSX 1.2.1 or something like that and was quite satisfied with how the game looked. Wanted to get shaders working and got PCSX 1.4.0 and can't geem to get the anti-aliasing to work on the text/menu items in game. Could someone point me in the right direction on what settings are affecting this or how to get the anti-aliasing to work on text too? No matter which settings I change doesn't seem to have an impact on how the text looks.
Ps2 Iso Game Download
I tried setting all the settings to the same I had them with 1.2.1, but the text is still super fuzzy and grainy. Due to a sudden nostalgia, I'm desperately trying to get a 'patched' Winning Eleven (don't know now as I quit playing soccer games basically, but those were actually a thing some 10+ years ago) under PCSX2, with miserable results.:- By the way, I don't think that qualifies as piracy since I own the original, japanese game on which the patched version is based on. Background: the patched version runs flawlessly on a modded PAL PS2.
Now, I know little to nothing about the PS2 boot process, but there's a thing I've just discovered: a small file on the game disc, named system.cnf apparently tells the OS which file has to be loaded for the game to start. And here comes the first weird thing: despite running on the modded PS2 as I said before, on further investigation I discovered the system.cnf file of this patched version actually asks for a file that doesn't exist!
So (obviously I guess) PCSX2 complains and immediately fails to boot the game. Then, with a Hex editor I modified the iso (and in turn that system.cnf) to reflect the actual content of the disc, namely the bootable file. Now, boot process goes a little further and PCSX2 doesn't complain anymore, but the emulated system just displays a (corrupted) logo first, then goes back to the console browser menu, the one with the memory cards and the disc icons. Any suggestions?
Tetsujin 28 Gou Ps2 Iso Gamecube
^^ hmm, ok, solved. Not knowing what else to do, I desperately extracted the non-working iso to a directory, put the system.cnf of the original, unpatched WE7 International in here and renamed, then added the patched (?) main executable to the iso directory. Then I re-created the iso and. Tah-dah, this time it booted flawlessly on PCSX2. ^^ I hadn't tried this before because I thought the iso structure was hardcoded so I was worried that the aforementioned process would totally destroy the (virtual) disc.
Tetsujin 28 Go
Nobody responded to you and you probably aren't paying attention anymore so maybe this is fruitless, but the short answer is that it varies from game to game. On my old system, which was a Core 2 Duo with 2gb of RAM and a Radeon 6870, I could run games like Kingdom Hearts and the PS2 Remake of NiGHTS at full speed. DBZ Budokai 3 and Maximo would almost get full speed, and something like Burnout 3 would chug along at 15fps. I rebuilt my whole system last month (4th gen Core i5, 16gb of RAM, Radeon 7860 or whatever) and I get full speed in a lot more games, but there's still stuff that's beyond me. Burnout 3 sometimes starts stuttering, for example. I don't even dare try games like Snake Eater. There's that lists optimal settings for each game and known problems with emulation.
It'll give you a good idea whether or not you'll be able to run something or if it's even supported (Burnout 3 has some rendering problems, for example).
Comments are closed.