Great Emulator
#1
I have been following the emu scene casually since Zsnes came out, and I remember a few years back this emulator first came out. And most games were not playable, and those that were were lucky to do 1 FPS. Anyways, I downloaded this today and [with fps cap off], I recieve 250 fps on the FFX intro.

So great job on the emulator, its nice to see the PS2 is emulated so well now.

And for those wondering, I have a 4.2ghz E8500 C2D /w HD4850 [yep, overclocked to hell and back]. The games look great with the internal rez cranked up to 2000x2000 Tongue


Also i have a quick question, im using the Gsdx10 graghics plug in. Its working fine, however the hardware anti aliasing feature doesnt work. Im using the internal res as a workaround but there is still slight jaggy "crawling"...Is there anyway to force AA on, or is Internal res as good as it gets ?
Reply

Sponsored links

#2
AA should be working but depends on where you use it, works in FFX at least.

What setting did you use?
Core i5 3570k -- Geforce GTX 670  --  Windows 7 x64
Reply
#3
(06-29-2010, 01:36 AM)Shadow Lady Wrote: AA should be working but depends on where you use it, works in FFX at least.

What setting did you use?

I tried 2/4/6. Each setting above 0 crashed the app when I started it. Its no biggy though, Ive been messing with internal res more, and anything above 2k/2k and my Fps hits 50ish...So ill stick with 2k/2k. It looks great anyway.
Reply
#4
(06-29-2010, 01:53 AM)petepiate Wrote: I tried 2/4/6. Each setting above 0 crashed the app when I started it. Its no biggy though, Ive been messing with internal res more, and anything above 2k/2k and my Fps hits 50ish...So ill stick with 2k/2k. It looks great anyway.
FWIW, I experience identical symptoms. AA just crashes immediately for me...
Reply
#5
thats cause you use high internal res, try with lower
OS: Win 7 Ultimate x64 sp1, MoBo: Asus P5QD Turbo, CPU: Q6600 @ 3,0Ghz, RAM: Trancend 2x2gb 6-6-6-18 800 MHz, GPU: HD 4850 1gb.
Pcsx2: Always Latest
Reply
#6
(06-29-2010, 03:30 AM)iakoboss7 Wrote: thats cause you use high internal res, try with lower

YEah, too high internal res.


Why not go with 1920 by 1080 for 1080p resolution

then crank the AA up to 16 and you got yourself a game.
Reply
#7
Not sure if that was sarcasm, but it also crashes with native res and also with 512x512. It just always crashes immediately for me when AA>0.
Reply
#8
AA doesnt crash on me but it doesn't seem to do anything. Even at x12 there are no graphical or fps changes.
Reply
#9
The hardware AA works for me although takes a heavy toll on my 9600GT.
In FF12 I get steady 60FPS (only the normal flutuation) at most Rabanastre points minus a few where the FPS falls under 50 when AA=4, they are very specific points and depends on the visage angle and so on. Still even in these points the FPS increase to something like 55/56 at AA=2 and returns to steady 60 when AA=1 or 0.

Obviously the jaggedness is clearly reduced and it's not just resource wasting. Since the reports from crash to no visual changes I suggest anyone posting about it giving the complete configuration, mainly the Video card brand and drivers used.

Mine is:
AMD Phenom 2 X4 965 BE - OCed x18.5 and 205 refHT - what make it 2.792GHz per core
Mobo - ECS A790GXM-AD3 with 4GB 1333 RAM (Only indirectly OCed by the 205 refHT)
Nvidia 9600GT - OCed 720MHz core - 950GHz - 512MB VRAM

GSDX11/10 hardware mode with 1024x1024 - blend bbf and allow 8bit-texture (this can change)
-Texture filtering is total (not only the 3D)

The following applies to PCSX2 SVN 3339 but works on early versions experimented before.

Speed Hacks - Only INTC and Wait Loop detection (actually these are kept this way and touched only if the game presents some problem, I'm still to find one).

Sound - 5.1 with Hermit filter x1 default reverber.

External resolution, 1600x900 windowed/ 1920x1080 full screen.

One can experiment with internal resolutions and speed hacks since this game is reasonably tolerant with them.

PS: Forgot to mention I run this game in 16x9 mode.
The above overclock is very conservative and under stock cooling, probably this will change when entering the summer season or if I resolve getting bolder...

Edited: to change the external resolution spelling from 1900x600 to the correct 1600x900
Imagination is where we are truly real
Reply
#10
(06-29-2010, 06:33 AM)nosisab Ken Keleh Wrote: Obviously the jaggedness is clearly reduced and it's not just resource wasting. Since the reports from crash to no visual changes I suggest anyone posting about it giving the complete configuration, mainly the Video card brand and drivers used.

Mine is:
AMD Phenom 2 X4 965 BE - OCed x18.5 and 205 refHT - what make it 2.792GHz per core
Mobo - ECS A790GXM-AD3 with 4GB 1333 RAM (Only indirectly OCed by the 205 refHT)
Nvidia 9600GT - OCed 720MHz core - 950GHz - 512MB VRAM

GSDX11/10 hardware mode with 1024x1024 - blend bbf and allow 8bit-texture (this can change)
-Texture filtering is total (not only the 3D)


Yea it crashes for me aswell when set to native resolution or custom internal res, it doesnt matter. 2x AA+ 1920x1080 would be great if it worked on my end [just to remove jaggy shimmering].

Here are my specs for what its worth-

Cpu- Core 2 duo E8500, OCd to 4.2ghz
Mobo- P5b Deluxe
GPU- single HD4850 [overclocked slightly, but never had a issue for a year now]

GSDX11/10 hardware mode, I have it on 1920x1080 now. - blend bbf and allow 8bit-texture.

Im downloading a new set of ATI drivers atm, for a different reason though...My tv out refuses to work. But ill post again if it fixes the AA crash.
Reply




Users browsing this thread: 1 Guest(s)