|
|
|||||||
| About Us | Register | FAQ | Members List | Calendar | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) | |
|
AI
![]() ![]() ![]() Join Date: Aug 2007
Location: System Server
Posts: 325
|
PCSX2 Game Statistics Index
This is an emulator performance index to track PCSX2 game performance and computer specifications. This is complementary to PCSX2 Game Troubleshooting Guide. Data compilation for FPS Prediction Subsection in progress => 43%. The theory behind this thread is to create a unified statistical analysis of the many data fields gathered from the Screenshots Thread and other sources to aid in the developers' and end-users' analysis of the emulated experience. For a practical example, the Specification to FPS analysis should help reduce the spawning of "Is this PC powerful enough to run game X at decent speeds" threads. The setup and layout are as follows: the first post (this post) will act as the primary indexing page whereas all future STATS posts or screenshots thread links will be linked to in an organized manner. That is, by means of categorizing each game in alphabetical order, and general articles in the respective order of importance. Each link will have by its side a brief detail of the peak FPS for the game, and the link to its corresponding KB article, if any. If the same title exhibits similar performance despite the region, then a single STATS article will be linked for all. If there is more than one STATS entry per game, an advanced STATS page will be made for that game. This STATS page may contains benchmark with specifications and settings to assist with performance expectations. By default, the setup will be such that individual games that have little data will be linked to the Screenshots post directly while those with more data can be analyzed specifically with specific STATS articles. For complimentary purposes, attached is the indexed Screenshots Thread, GameStats.xls with 437 manually made entries with fields of: GAME, REGION, STATUS, EMU_VERSION, OS, FPS_MENU_MIN, FPS_MENU_MAX, FPS_INGAME_MIN, FPS_INGAME_MAX, CPU_BRAND, CPU_MODEL, CPU_CLOCK, RAM, GPU_BRAND, GPU_MODEL PLUGIN_GS, PLUGIN_GS_VERSION, PLUGIN_SOUND PLUGIN_SOUND_VERSION, PLUGIN_CDVD, PLUGIN_CDVD_VERSION, Disable Forced ABS, EE/IOP Sync Hack, and REFERENCE. The data was collected manually from the first 420 posts in the screenshots thread. Posts without FPS were analyzed based on the screenshots: for those with few screenshots, the FPS_INGAME_MAX is the highest value for the ingame screenshots. Those with multiple appropriate screenshots were evaluated with minimum and maximum. Those without any FPS details were dropped. Posts of games with menu problems while having minimal data were dropped. Posts claiming "full speed" were not recorded, as this was a relative opinion. Multiple reposts were accumulated in the analysis. Quote:
Caution: Playable in the file adopts a different meaning than the one in the compatibility list. The meaning implies the game seemed to work fine for the player at the time of testing, which may not be a complete testing, unlike in the compatibility list. Due to the indexing, any posts in-between are welcomed as they will be disregarded when browsing through the actual index. The format is below the index. A sample report is shown below this post. Contribution will be much appreciated by anyone who finds a new means of analysis via a particular approach. Do not ask performance questions or report bugs here. This thread is for the access and creation of STATS articles. Use the appropriate forums instead. (Though suggestions for improvement would be appreciated.) Use the browser search feature (Ctrl+F) to find partial game names. --- INDEX General Performance Game-Specific--- If you wish to contribute, please follow the format below in order to keep the project organized. Have the post title be the name of the STATS approach. PHP Code:
To take responsibility to handle a sub-index: Have the post title be the name of the general category of study or the name of the game. PHP Code:
Last edited by GeominorAI; June 10th, 2008 at 05:50. Reason: Indexed STATS Article: "PCSX2 Overall Specification vs. Performance - CPU and GPU Power Matter" |
|
|
|
|
|
|
#3 (permalink) |
|
Insomniac in training...
![]() ![]() ![]() ![]() ![]() ![]() Join Date: Nov 2006
Location: Canada
Posts: 3,633
|
Wow, someone has a lot of time
. All I can say is kudos man. Not sure if it's necessary, but we haven't seen someone so enthusiastic about the project for awhile now .
__________________
Born free, riding free, living free. Always be free. Q6600 @ 3Ghz, 333x9 Gigabyte DS3R, Rev1.0 Patriot Extreme DDR2 PC-6400RAM BFG 9800GX2 @ stock |
|
|
|
|
|
#4 (permalink) |
|
AI
![]() ![]() ![]() Join Date: Aug 2007
Location: System Server
Posts: 325
|
To improve the effectiveness of the PCSX2 forum environment and to formulate useful data compilation, using the feedback the PCSX2 supporters have put forth throughout the years, to potentially help the PCSX2 team seemed to be beneficial for all.
__________________
Inspiron 1520 - Intel Core2 Duo T7500 2.2GHz - 2.0GB DDR2 RAM - Nvidia GeForce 8600M GT 256MB DDR2 600/485 Contribute to and review game troubleshooting Knowledge Base articles at the PCSX2 Game Troubleshooting Guide and PCSX2 Game Statistics Index. |
|
|
|
|
|
#6 (permalink) | |
|
AI
![]() ![]() ![]() Join Date: Aug 2007
Location: System Server
Posts: 325
|
Quote:
It took the entire day to get much of the latter half of the Screenshots Thread into Excel. It might have to wait until tomorrow to get some of the content up. The Game FPS Sub-Index post was put up temporarily in order to slightly fill the void.
__________________
Inspiron 1520 - Intel Core2 Duo T7500 2.2GHz - 2.0GB DDR2 RAM - Nvidia GeForce 8600M GT 256MB DDR2 600/485 Contribute to and review game troubleshooting Knowledge Base articles at the PCSX2 Game Troubleshooting Guide and PCSX2 Game Statistics Index. |
|
|
|
|
|
|
#7 (permalink) |
|
Registered User
![]() Join Date: Jul 2004
Location: oven
Posts: 67
|
Not trying to discount the awesomeness of this thread but...
Keep in mind some people are using frame limiting, therefore some peak numbers are not that accurate for the system spec. I am not sure if this is your intention, but unless you have standardized hardware, the numbers are meaningless and cannot be directly compared.
__________________
Computex was MEH ![]() Happy Core2 Family: Main:E84@4.05/98GTX NAS:Q66G0@3.0/76GT mATX:E84@3.6/88GTS and more. |
|
|
|
|
|
#8 (permalink) |
|
Registered User
![]() ![]() ![]() Join Date: Sep 2007
Location: Germany
Posts: 428
|
The numbers have a very big meaning.. If one user has 50/60fps on his machine it means
that game can be played fullspeed. There are many titles that, due to bugs, do not reach fullspeed on even the highest specs. GeominorAI: This thread prolly means a lot of work for you, i do hope you can keep it up
|
|
|
|
|
|
#9 (permalink) |
|
Registered User
![]() Join Date: Jul 2004
Location: oven
Posts: 67
|
That isn't what I am trying to say. If a user can get 60fps on some game on a say 3.6GHz Core2. What does it mean for someone with a 2.2Ghz X2? Nothing at all except that he'll run much slower than the guy with 3.6. If the numbers are normalized on a standard hardware, a rough performance number could be extrapolated. All you need is a multiplier. For example you normalized on a 2.0 C2D. And you got a 3.0 one. Use a 1.5 multiplier and you can get a rough number of your performance. Add a modifier for x2 architecture and you can extrapolate the rough numbers for X2s. (This is assuming no GPU bottleneck of course)
__________________
Computex was MEH ![]() Happy Core2 Family: Main:E84@4.05/98GTX NAS:Q66G0@3.0/76GT mATX:E84@3.6/88GTS and more. |
|
|
|
|
|
#10 (permalink) | |
|
AI
![]() ![]() ![]() Join Date: Aug 2007
Location: System Server
Posts: 325
|
Quote:
And yes, the peak-limit issue was noticed about a quarter way into the data entry. It was left that way to see how certain specifications stand out compared to the rest. At the point of actual analysis for the games, the peak will be trimmed at 60. In a semi-related note, the FPS on screenshots were generally floored before being entered into the spreadsheet. I have been working on a 3D-graphing setup on Excel for this thread. It should be up in the next few days.
__________________
Inspiron 1520 - Intel Core2 Duo T7500 2.2GHz - 2.0GB DDR2 RAM - Nvidia GeForce 8600M GT 256MB DDR2 600/485 Contribute to and review game troubleshooting Knowledge Base articles at the PCSX2 Game Troubleshooting Guide and PCSX2 Game Statistics Index. |
|
|
|
|
|
|
#11 (permalink) |
|
The Pest
![]() ![]() ![]() ![]() ![]() Join Date: Oct 2006
Location: Earth
Posts: 1,680
|
Good luck with it man. You do alot of nice things like this, which are very helpful to users who know how to search.
__________________
PC configuration Q6600 @ 3.4GHZ Stable,GeForce 8800 GT 512 MB GDDR3(Super-clocked) ,4GB PC8000(1000MHZ) RAM @ 950MHZ(5-5-5-15)(Waiting to tweak them eventually),Windows XP SP2 Professional(Vista 64 bit, Dual Boot),750GB 7200 RPM, 32 MB Cache Hard-drive(SATAII),24'' LCD( I know, sorry CRT'ers) HD 1080pi, DVI connected, 1920 x 1200 @ 60HZ),P35-DS3L Revision 2.0 @ 1.49V http://tinyurl.com/2zzzsr Use the Guide above to get PCSX2 to run properly. Has all you need to know to run PCSX2. Having trouble with a game? Check here: http://tinyurl.com/2cuzhx |
|
|
|
|
|
#12 (permalink) |
|
AI
![]() ![]() ![]() Join Date: Aug 2007
Location: System Server
Posts: 325
|
Thanks.
Optimistically, I will try to keep up with the ideas for new articles so that this thread can be kept at the surface of the thread pool. That way, even those who know not how to search can be helped as well.
__________________
Inspiron 1520 - Intel Core2 Duo T7500 2.2GHz - 2.0GB DDR2 RAM - Nvidia GeForce 8600M GT 256MB DDR2 600/485 Contribute to and review game troubleshooting Knowledge Base articles at the PCSX2 Game Troubleshooting Guide and PCSX2 Game Statistics Index. |
|
|
|