Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
wiki:benchmarking_for_batocera [2022/07/11 11:13] – [Games to test] added clarification footnote about compiling shaders atariwiki:benchmarking_for_batocera [2024/08/07 06:58] (current) – [Games to test] add low end ps3 games atari
Line 8: Line 8:
   * Running the game off the internal drive. Network shares or external drives may have unrelated storage speed access issues that negatively affect games.   * Running the game off the internal drive. Network shares or external drives may have unrelated storage speed access issues that negatively affect games.
  
-For Batocera's benchmarking purposes, it's really only necessary to see whether a game is running at full-speed or not. There is no ambiguity with this sort of system and is easy to understand by all. You can enable the FPS counter by going to **SYSTEM SETTINGS** -> **DEVELOPER** -> **SHOW FPS COUNTER** and turning it on.+For Batocera's benchmarking purposes, it's really only necessary to see whether a game is running at full-speed or not. There is no ambiguity with this sort of system and is easy to understand by all. 
 + 
 +You can enable the FPS counter by going to **SYSTEM SETTINGS** -> **FRONTEND DEVELOPER OPTIONS** -> **SHOW FPS COUNTER** and turning it on.
  
 ===== What is considered "full-speed"? ===== ===== What is considered "full-speed"? =====
  
-  * For a 60 FPS game, anything between 57 to 60 FPS without noticeable stutters (more than half a second) would be considered full-speed. Micro-stutters (less than a 60th of a second) can usually be explained by hardware configuration and slightly less-than-optimal default settings, and should be ignored. +  * For a 60 FPS game, anything between 57 to 60 FPS (95%) without noticeable stutters (more than half a second) would be considered full-speed. Micro-stutters (less than a 60th of a second) can usually be explained by hardware configuration and slightly less-than-optimal default settings, and should be ignored. 
-  * For 50 FPS games (like PAL region games), the same but anything between 47 to 50 FPS instead. +  * For 50 FPS games (like PAL region games), the same but anything between 47 to 50 FPS (95%) instead. 
-  * For games that run easily at full-speed, try increasing the rendering scale by an integer multiplication. Things like x2 resolution, x3, x4, etc. until you reach the setting where emulation is no longer full-speed. For systems where upscaling the rendering resolution is not possible, just write down "Full-speed" instead.+  * For games that run easily at full-speed, try increasing the rendering scale by an integer multiplication. Things like 2x resolution, 3x, 4x, etc. until you reach the setting where emulation is no longer full-speed. For systems where upscaling the rendering resolution is not possible, just write down "Full-speed" instead. For systems where the highest rendering resolution still runs at full-speed, write down "Max" (consider removing such systems from the benchmark if the high-end game runs at full-speed with "Max" rendering).
   * Consider the speed of the game running during its regular gameplay, not during menus or transition screens. On that note, sometimes the "first area" of a game is significantly easier to render than other parts, be sure to move into other areas to make sure.   * Consider the speed of the game running during its regular gameplay, not during menus or transition screens. On that note, sometimes the "first area" of a game is significantly easier to render than other parts, be sure to move into other areas to make sure.
-  * For games that don't run at full-speed, note down the **average FPS** for that system (this is very subjective, but do what you feel is the best representation of the performance). Some users may still find a "mostly full-speed" game acceptable to play.+  * For games that don't run at full-speed, note down the **average speed in percentage** for that system including the FPS in parenthesis (this is very subjective, but do what you feel is the best representation of the performance, some users may still find a "mostly full-speed" game acceptable to play).
   * For games that are otherwise fine on other systems but crash/fail to render anything/other major issue, put down N/A and add a [[wiki:syntax#footnotes|footnote]] indicating the issue.   * For games that are otherwise fine on other systems but crash/fail to render anything/other major issue, put down N/A and add a [[wiki:syntax#footnotes|footnote]] indicating the issue.
  
Line 25: Line 27:
   * 03:38 - **Atomiswave** This would be considered full-speed, despite the graphical issues. Theoretically, this could be fixed by using the proper drivers/settings in the emulator.   * 03:38 - **Atomiswave** This would be considered full-speed, despite the graphical issues. Theoretically, this could be fixed by using the proper drivers/settings in the emulator.
   * 04:03 - **N64** This would be considered full-speed (he did not test upscaling in this example).   * 04:03 - **N64** This would be considered full-speed (he did not test upscaling in this example).
-  * 04:54 - **PSP** This would be considered "x3". +  * 04:54 - **PSP** This would be considered "3x". 
-  * 06:22 - **Gamecube** For low-end games, this would be considered "x1". For high-end games, due to the drop down to 50 FPS, this would not be full-speed.+  * 06:22 - **Gamecube** For low-end games, this would be considered "1x". For high-end games, due to the drop down to 83% (50 FPS), this would not be full-speed.
   * 07:38 - **PS2** This would not be full-speed, as hacks/alternative regions needed to be utilized to achieve such a speed. Benchmarking should only consider performance at default settings.   * 07:38 - **PS2** This would not be full-speed, as hacks/alternative regions needed to be utilized to achieve such a speed. Benchmarking should only consider performance at default settings.
  
-For older systems that might be running a Nvidia card, do try to get the official Nvidia drivers working. If it's really old, you may have to use the [[https://wiki.batocera.org/supported_pc_hardware#legacy_nvidia_drivers|legacy build]]. If the CPU/motherboard is too old for even that, you may have to use an even older version of Batocera (such as **5.26**).+If running a version of Batocera before **v35**, for systems that might be running a Nvidia card, do try to get the official Nvidia drivers working. If it's really old, you may have to use the [[https://wiki.batocera.org/supported_pc_hardware#legacy_nvidia_drivers|legacy build]]. If the CPU/motherboard is too old for even that, you may have to use an even older version of Batocera (such as **5.26**).
  
 ===== Games to test ===== ===== Games to test =====
Line 65: Line 67:
     * **GameCube/Triforce/Wii**((Special exception here, you should always notate this as GameCube/Wii as their system requirements are similar if not identical; there are a lot of GameCube games which are tougher to emulate than Wii games.))     * **GameCube/Triforce/Wii**((Special exception here, you should always notate this as GameCube/Wii as their system requirements are similar if not identical; there are a lot of GameCube games which are tougher to emulate than Wii games.))
       * Low-end GameCube/Triforce/Wii (Mario Kart Double Dash)       * Low-end GameCube/Triforce/Wii (Mario Kart Double Dash)
-      * High-end GameCube/Triforce/Wii (Auto Modellista/F-Zero GX)((Notably, Star Wars Rogue Squadron III: Rebel Strike is not here as it performs so poorly as to be misrepresentative of how the emulator performs in other demanding titles.))+      * High-end GameCube/Triforce/Wii (Metroid Prime 2: Echoes/Super Smash Bros. Melee/Auto Modellista/F-Zero GX)((Notably, Star Wars Rogue Squadron III: Rebel Strike is not here as it performs so poorly as to be misrepresentative of how the emulator performs in other demanding titles.))
     * **3DS**((Indicate whether you are testing with or without shaders already being compiled in a footnote. Results can vary greatly if the emulator is processing shaders for the first time.))     * **3DS**((Indicate whether you are testing with or without shaders already being compiled in a footnote. Results can vary greatly if the emulator is processing shaders for the first time.))
       * Low-end 3DS (Super Mario 3D Land)       * Low-end 3DS (Super Mario 3D Land)
Line 77: Line 79:
       * High-end Wii U (Breath of the Wild)       * High-end Wii U (Breath of the Wild)
     * **PS2**     * **PS2**
-      * Low-end PS2 (Monster Hunter/Tekken 5/Sonic Riders/Sonic Riders: Zero Gravity/Beatmania/Kingdom Hearts) +      * Low-end PS2 (Monster Hunter/Tekken 5/Sonic Riders/Sonic Riders: Zero Gravity/Beatmania/Marvel vs Capcom 2: New Age of Heroes) 
-      * High-end PS2 (God of War/Gran Turismo 4)+      * High-end PS2 (God of War/Gran Turismo 4/Shadow of the Colossus)
     * **Xbox**     * **Xbox**
       * Low-end Xbox (Jet Set Radio Future)       * Low-end Xbox (Jet Set Radio Future)
-      * High-end Xbox (Burnout 3: Takedown)+      * High-end Xbox (Halo: Combat Evolved, Burnout 3: Takedown)
     * **PS3**     * **PS3**
-      * Low-end PS3 (Hatsune Miku Project DIVA F)+      * Low-end PS3 (Hatsune Miku Project DIVA F/Hard Corps: Uprising/Castlevania: Lords of Shadow)
       * High-end PS3 (Red Dead Redemption/GTA V/Sonic Unleashed/God of War 3)       * High-end PS3 (Red Dead Redemption/GTA V/Sonic Unleashed/God of War 3)
 +    * **Xbox 360**
 +      * Low-end Xbox 360 (Hexic)
 +      * High-end Xbox 360 (Sonic Unleashed)
  
 Here's an example benchmark for reference: Here's an example benchmark for reference:
Line 91: Line 96:
  
 ^ CPU ^ GPU ^ High-end N64 (Goldeneye 007) ^ High-end PSP (Midnight Club: L.A. Remix) ^ Low-end Dreamcast (MvC2) ^ High-end Dreamcast (Sega Rally 2)  ^ High-end GameCube/Wii (Auto Modellista) ^ Low-end PS2 (Sonic Riders: Zero Gravity) ^ High-end PS2 (God of War) ^ Low-end Xbox (Jet Set Radio Future) ^ High-end Xbox (Burnout 3: Takedown) ^ ^ CPU ^ GPU ^ High-end N64 (Goldeneye 007) ^ High-end PSP (Midnight Club: L.A. Remix) ^ Low-end Dreamcast (MvC2) ^ High-end Dreamcast (Sega Rally 2)  ^ High-end GameCube/Wii (Auto Modellista) ^ Low-end PS2 (Sonic Riders: Zero Gravity) ^ High-end PS2 (God of War) ^ Low-end Xbox (Jet Set Radio Future) ^ High-end Xbox (Burnout 3: Takedown) ^
-| Intel Core i3-4350 | Nvidia GTX 750Ti | Full-speed | x10 | Full-speed | 40FPS | x5 | x2 | x1 | x4 | N/A((The game runs, but only renders a black screen.)) |+| Intel Core i3-4350 | Nvidia GTX 750Ti | Full-speed | Max | Full-speed | 67% (40 FPS) | 5x | 2x | 1x | 4x | N/A((The game runs, but only renders a black screen.)) |
  
 You can also view the already existing benchmark tables at [[:choose_a_desktop_computer#benchmarks|the "Choose a Desktop/Benchmarks" page]]. Some of the older benchmarks use a different format, but contributions for older versions of Batocera are still accepted. You can also view the already existing benchmark tables at [[:choose_a_desktop_computer#benchmarks|the "Choose a Desktop/Benchmarks" page]]. Some of the older benchmarks use a different format, but contributions for older versions of Batocera are still accepted.
Line 103: Line 108:
 {{:wiki:screenshot-2021.10.09-20h53.32.jpg?640|}} {{:wiki:screenshot-2021.10.09-20h53.32.jpg?640|}}
  
-In order to activate it, simply change the **HEADS UP DISPLAY** to "PERFORMANCE" in either the **MAIN MENU** -> **GAME SETTINGS** or that system's specific **ADVANCED SYSTEM SETTINGS**.+In order to activate it, simply change the **HEADS UP DISPLAY** (in the **DECORATIONS** submenu) to "PERFORMANCE" in either the **MAIN MENU** -> **GAME SETTINGS** or that system's specific **ADVANCED SYSTEM SETTINGS**.
  
 {{:wiki:heads_up_display_option.png?640|}} {{:wiki:heads_up_display_option.png?640|}}
  • wiki/benchmarking_for_batocera.1657537987.txt.gz
  • Last modified: 4 years ago
  • by atari