Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
I have to ask. . .why do my fps drop?
#11
Yeah that game is supposed to be complete hell to run.
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply

Sponsored links

#12
(07-18-2014, 11:49 PM)Blyss Sarania Wrote: Just FYI with an FX 6300 @ 4.2 Ghz I have been able to run any game I tried at full speed in PCSX2. Including demanding titles like Shadow of the Colossus. Some of them required a lot of tweaking, but I got them all running full speed. Although I haven't tried BGLaughA and even people with a 3570k say it crawls for them.

sure.
but you're comparing piledriver with bulldozer...
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply
#13
Yeah, I know. I was specifically referring to his comment about AMD not being able to hack it.

Also, taking into account the higher turbo speed of the 6300 VS the 6100, at the same clock speed, there is about a 150 point difference in Single threaded performance. From that I can guesstimate a 6100 at 4.6 would be equivalent to a 6300 at around 4.3Ghz.

Bulldozer sucks, for sure, but for most non super demanding games, a 6100 should be able to eek out enough performance for a good experience, especially around 4.2Ghz. Even with a 4770k I imagine BG : DA will struggle.
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply
#14
If fezzer has the game, maybe he can test it on his 4770K
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#15
I think it was Topken who said it struggled for him on 3570k... not sure. Whoever it was said they got like 30 FPS on that chip.
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply
#16
yeah, those games run like hell on pcsx2.
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#17
Baldur's Gate is probably badly optimized on pcsx2.
pcsx2 doesn't run any game well, mostly only the most popular games.

Main Rig: i7-3770k @4.5ghz | 16GB DDR3 | Nvidia GTX 980 TI | Win 10 X64
Laptop: MSI GT62VR | i7-6700HQ | 16GB DDR4 | Nvidia GTX 1060 | Win 10 X64

Reply
#18
(07-19-2014, 12:06 AM)Blyss Sarania Wrote: I think it was Topken who said it struggled for him on 3570k... not sure. Whoever it was said they got like 30 FPS on that chip.
possibly something throttled in machine!(3570k) or maybe pcsx2 cant able to run game correctly due to lot's of bugs while gsdx trying to render this game! or maybe 3570 cant able to handle this !
Core i3 9100f 3.6Ghz
RAM=8GB
nvidia GT 1030
pcsx2 version-1.3.1  


Still surfing with Browser?, Try the pcsx2 forum App !
Reply
#19
Thanks for all the great info. One last question, (because I am ignorant of the EMU), I seem to get better performance, fps, if I run my GS in hardware mode, but I get half screen distortion, pixelation, etc. but the game runs super good. What might I do to correct the problem? Versus running in software mode. . .I am still amazed that my PS2 slim, which was $120 new, can't be emulated by a $700 custom build with a new and strong video card. . .are their demons housed within the Sony chipset configuration? Anyways, thanks again.
Reply
#20
Unfortunately, nothing. BG : DA is one of the games that use the "Snowblind engine" and none of these games currently work in GSDX hardware mode.

As I said above, your machine should emulate most game at playable speed. This is a special case though. But for the "demons" you spoke of, look here:

Quote:A lot of people seem to compare PS2 emulation to the other consoles such as Gamecube and PSX. Why are they faster? well the simple fact is the consoles are much simpler than the PS2, thus less code, bandwidth and development time is required.

This is a list of the things the emulator needs to emulate, i shall compare to the PSX.

EE (Emotion Engine) core = The PS2's main processor which runs 8x faster than the PSX processor with registers twice the size (128bits) although in general cases only 64 bits are used, where the PSX uses 32bits as a general rule. The other difference is the R5900 (EE) has many extra instructions, multimedia instructions and extra co processors which aren't in the PSX, so we have a processor that's 8x faster and at least 3 times more complex.

IOP (In Out Processor) core = This is identical to the PSX core, it is the same chip with a few extra dma channels, it is also clocked 3mhz higher than the PSX but we can assume its basically the same chip.

VUs (Vector Units) = The PS2's equivalent to the graphics engine on the PSX, it is seen as an extra processor (yes another one) although the PSX one was 4 times slower than the VU and also the VU has its own memory and run independently from the main CPU where as the PSX one is cpu dependent. This is the main reason for the slow 3d games on PCSX2, intense vertex processing done by the game using 4 32bit vertex's which makes up the 128bit floating point registers that it contains. This unit also processes textures and 2d information on a part of the unit called the VIF which unpacks texture data and sends it to the GS.
Oh, did we mention there's 2 of these units (VU0 and VU1)?

SPU2 (Sound Processing Unit 2) = This is literally, the SPU found on the PSX but doubled, so there is now 2 of them to handle

GS (Graphics Synthesizer) = This is the PS2 version of the GPU, which does a similar job, but has the ability to do anti aliasing and all sorts of other fancy things, although some were rarely used, this does all the vertex/texture mapping that you see on the screen.

SIF = Now this didn't appear on the PSX, it connects the IOP to the EE and is used to transfer data between the 2, as the DVD, sound etc is situated on the IOP side, pretty much laid out as the PSX was. Although its function seems simple, its required that we emulate it which takes extra time as expected.


These are the main, intensively used parts of the PS2 which are used in the emulator, as you can tell from the comparison that the PS2 is much more complex than the PSX and requires a lot more time. To add insult to injury on the real machine a lot of work will be done asynchronously, so say while the VU is doing something the processor will be doing something else, but unfortunately we cant do this, so we have to run 1 and pause the rest, when that's done let something else do the work and so on, and running all that processing power on a single CPU is very very intensive work. Now take all that and throw on at least FIVE times the requirements due to the emulation needing to process the original data and convert to ix86

As time goes on we find quicker ways to do things and optimize the code, but until we can run games at high speeds, enjoy the fact you can even run a PS2 game on your PC and continue to show your support

Also, look here for other games you will have trouble with:
http://forums.pcsx2.net/Thread-LIST-The-...sive-Games

Aside from games on that list, you should be fine.
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply




Users browsing this thread: 1 Guest(s)