Sprites 2d Por Software

[Zaelsius]

 Aquí va mi máquina: PowerPC G4 1.5Ghz, bus 167Mhz, Virtual PC 7.0 + Windows XP Professional

La aplicación me peta tras el test 4.6(ver log), pero hasta ese momento funciona bien.

+----------------------------------------------------------+
¶           CRM32Pro Win32 v4.61 (build 1039)              ¶
¶               MegaStorm Systems © 2005                 ¶
¶            http://www.megastormsystems.com               ¶
+----------------------------------------------------------+

? TestSpeed v2.2

? Executing at Sun Sep 18 18:13:25 2005
? Running on Virtual CPU  - Family 6 - Model: 8  - MMX
? Selected normal code path.

? CRM32Pro successfully initiated.

? Test FillRect background - Number of sprites: N/A - Sprite: N/A
? 5 seconds of benchmarking
? 1298 total frames rendered
? 216.19 frames per second

? Selected normal code path.
? 800x600x16bits
? Screen is in system memory
? Sprite is in system memory
? Background is in System Memory
? Test 1.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 32
? 5 seconds of benchmarking - 1592 total frames rendered
? 265.29 frames per second

? Test 1.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 64
? 5 seconds of benchmarking - 1453 total frames rendered
? 242.05 frames per second

? Test 1.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 128
? 5 seconds of benchmarking - 1117 total frames rendered
? 186.07 frames per second

? Test 1.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 256
? 5 seconds of benchmarking - 726 total frames rendered
? 121.00 frames per second

? Test 1.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 512
? 5 seconds of benchmarking - 301 total frames rendered
? 50.02 frames per second

? Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 1600
? 5 seconds of benchmarking - 1026 total frames rendered
? 171.00 frames per second

? Selected 'MMX-I' optimized code path.
? 800x600x16bits
? Screen is in system memory
? Sprite is in system memory
? Background is in System Memory
? Test 2.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 32
? 5 seconds of benchmarking - 1486 total frames rendered
? 247.50 frames per second

? Test 2.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 64
? 5 seconds of benchmarking - 1341 total frames rendered
? 223.39 frames per second

? Test 2.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 128
? 5 seconds of benchmarking - 1032 total frames rendered
? 171.91 frames per second

? Test 2.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 256
? 5 seconds of benchmarking - 608 total frames rendered
? 101.20 frames per second

? Test 2.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 512
? 5 seconds of benchmarking - 210 total frames rendered
? 34.94 frames per second

? Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 1600
? 5 seconds of benchmarking - 993 total frames rendered
? 165.33 frames per second

? Selected 'MMX-II' optimized code path.
? 800x600x16bits
? Screen is in system memory
? Sprite is in system memory
? Background is in System Memory
? Test 3.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 32
? 5 seconds of benchmarking - 1495 total frames rendered
? 249.13 frames per second

? Test 3.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 64
? 5 seconds of benchmarking - 1333 total frames rendered
? 222.02 frames per second

? Test 3.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 128
? 5 seconds of benchmarking - 1042 total frames rendered
? 173.58 frames per second

? Test 3.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 256
? 5 seconds of benchmarking - 592 total frames rendered
? 98.65 frames per second

? Test 3.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 512
? 5 seconds of benchmarking - 213 total frames rendered
? 35.39 frames per second

? Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 1600
? 5 seconds of benchmarking - 1031 total frames rendered
? 171.66 frames per second

? Selected 'MMX-III' optimized code path.
? 800x600x16bits
? Screen is in system memory
? Sprite is in system memory
? Background is in System Memory
? Test 4.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 32
? 5 seconds of benchmarking - 1508 total frames rendered
? 251.12 frames per second

? Test 4.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 64
? 5 seconds of benchmarking - 1355 total frames rendered
? 225.80 frames per second

? Test 4.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 128
? 5 seconds of benchmarking - 1062 total frames rendered
? 176.94 frames per second

? Test 4.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 256
? 5 seconds of benchmarking - 601 total frames rendered
? 100.17 frames per second

? Test 4.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 512
? 5 seconds of benchmarking - 207 total frames rendered
? 34.37 frames per second

? Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 1600
? 5 seconds of benchmarking - 1045 total frames rendered

? 174.05 frames per second

? Selected 'MMX-IV' optimized code path.
? 800x600x16bits
? Screen is in system memory
? Sprite is in system memory
? Background is in System Memory

[zupervaca]

 ahi va mi contribucion tio  ;)

Código [Seleccionar] Expand

+----------------------------------------------------------+
¦           CRM32Pro Win32 v4.61 (build 1039)              ¦
¦               MegaStorm Systems (c) 2005                 ¦
¦            http://www.megastormsystems.com               ¦
+----------------------------------------------------------+

· TestSpeed v2.2

· Executing at Sun Sep 18 19:32:38 2005
· Running on INTEL processor - Pentium 4(Prescott+) - MMX - SSE
· Selected 'P4 Prescott+' optimized code path.

· CRM32Pro successfully initiated.

· Test FillRect background - Number of sprites: N/A - Sprite: N/A
· 5 seconds of benchmarking
· 2018 total frames rendered
· 336.33 frames per second

· Selected normal code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 1.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2980 total frames rendered
· 496.67 frames per second

· Test 1.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2676 total frames rendered
· 445.85 frames per second

· Test 1.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1912 total frames rendered
· 318.61 frames per second

· Test 1.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 1118 total frames rendered
· 186.24 frames per second

· Test 1.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 406 total frames rendered
· 67.55 frames per second

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1723 total frames rendered
· 287.17 frames per second

· Selected 'MMX-I' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 2.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2973 total frames rendered
· 495.50 frames per second

· Test 2.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2631 total frames rendered
· 438.43 frames per second

· Test 2.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1935 total frames rendered
· 322.50 frames per second

· Test 2.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 1023 total frames rendered
· 170.44 frames per second

· Test 2.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 341 total frames rendered
· 56.80 frames per second

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1737 total frames rendered
· 289.40 frames per second

· Selected 'MMX-II' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 3.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2979 total frames rendered
· 496.42 frames per second

· Test 3.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2630 total frames rendered
· 438.33 frames per second

· Test 3.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1932 total frames rendered
· 322.00 frames per second

· Test 3.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 1029 total frames rendered
· 171.47 frames per second

· Test 3.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 339 total frames rendered
· 56.42 frames per second

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1735 total frames rendered
· 289.17 frames per second

· Selected 'MMX-III' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 4.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2847 total frames rendered
· 474.50 frames per second

· Test 4.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2456 total frames rendered
· 409.33 frames per second

· Test 4.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1782 total frames rendered
· 297.00 frames per second

· Test 4.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 934 total frames rendered
· 155.56 frames per second

· Test 4.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 331 total frames rendered
· 55.13 frames per second

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 2067 total frames rendered
· 344.39 frames per second

· Selected 'MMX-IV' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 5.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2852 total frames rendered
· 475.33 frames per second

· Test 5.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2454 total frames rendered
· 409.00 frames per second

· Test 5.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1779 total frames rendered
· 296.40 frames per second

· Test 5.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 937 total frames rendered
· 156.01 frames per second

· Test 5.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 342 total frames rendered
· 56.91 frames per second

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 2063 total frames rendered
· 343.78 frames per second

· Selected 'MMX-V' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 6.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2978 total frames rendered
· 496.25 frames per second

· Test 6.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2629 total frames rendered
· 438.17 frames per second

· Test 6.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1930 total frames rendered
· 321.56 frames per second

· Test 6.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 1013 total frames rendered
· 168.72 frames per second

· Test 6.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 334 total frames rendered
· 55.52 frames per second

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1784 total frames rendered
· 297.23 frames per second

· Selected 'SSE-2' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 7.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2968 total frames rendered
· 494.58 frames per second

· Test 7.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2613 total frames rendered
· 435.43 frames per second

· Test 7.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1904 total frames rendered
· 317.33 frames per second

· Test 7.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 985 total frames rendered
· 164.17 frames per second

· Test 7.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 328 total frames rendered
· 54.61 frames per second

· Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1715 total frames rendered
· 285.69 frames per second

· Selected 'K7' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 8.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 2831 total frames rendered
· 471.83 frames per second

· Test 8.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 2451 total frames rendered
· 408.50 frames per second

· Test 8.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 1816 total frames rendered
· 302.57 frames per second

· Test 8.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 1063 total frames rendered
· 177.11 frames per second

· Test 8.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 376 total frames rendered
· 62.62 frames per second

· Test 8.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 2123 total frames rendered
· 353.83 frames per second


· CRM32Pro successfully closed.


micro: p4 dual core 3ghz, ram 1giga 533mhz, windows xp (tengo varios procesos de fondo rulando siempre como el antivirus, el detecto del nokia, bluetooth, etc, pero no creo que baje mucho el rendimiento por ellos)

editado: tengo el servicio de directx en modo debug, ¿pero usas software con lo que no tiene importacia no?

[TheAzazel]

y esto...a esto no le encuentro explicacion  :blink: ... has probado poniendo modo hardware+doublebuff, hardware sin doublebuff y solo software? en todos te pasa lo mismo?? que tarjeta grafica tienes???

Tengo una GeForce FX 5700. Lo que sucede es como si intentara usar un modo grafico con un barrido vertical mayor del que soporta el monitor (Philips 107E). Lo mismo me hacia el test de Sprites.

Esas mejorillas... lo mismo algun dia me inspiro(tu ya me has dado las ideas asi que... solo es aplicarlas) pero como es un simple ejemplo y los graficos son mios(se notara no? jaja) pues tampoco voy a darle mucha prioridad...


Lo del barrido...pufff... me tiene asi  :blink: , si es que no es nada del otro mundo...activa un modo 800x600 y no tiene nada que hacer con la frecuencias... puede ser el monitor? ende luego que yo lo flipo...no te han pasado cosas similares con otro soft?

esto va camino de un expediente X.... se me ocurre hacer un programita y que te vaya probando varios modos... pero con eso solo veriamos cuales te funcionan...no porque el que falla...lo hace... a ver si se me ocurre alguna cosa....

y no me cansare de darte las gracias!  (ole)  

[TheAzazel]

 @Zaelsius: para estar emulando.... la cosa va bastante rapida... y te peta justo cuando empiece a utilizar prefetch via SSE, porque solo te emula MMX, nada de SSE. Pero si señor, unos resultados curiosos!

@zupervaca: bien! otro prescott y de los nuevos! (el dual core me imagino) y lo del modo depuracion... no creo que afecte mucho, todo es por software(aunque ya sea por soft o por hard, al utilizar directx algo influira), de todos modos lo que me interesa son las variaciones de unos a otros en tu misma maquina, no comparar estos con otras maquinas... por lo que tus test me son perfectamente validos para discriminar que rutinas van mejor.


Como veo que los equipos que faltan:

-Pentium MMX
-Pentium II
-K6 y derivados
-Athlon64

pueden ir para largo... ya los incluire en alguna mini actualizacion de la lib, voy a compilar los paquetes y probar todo que funcione y para mañana actualizo la web y subo todos los resultados.

Gracias por perder unos minutos de vuestro tiempo!!!
Buenas noches

[Douch]

 Micro: Athlon XP 1400 (1600+)
Ram: 768 MB
Windows XP SP2

+----------------------------------------------------------+
¦           CRM32Pro Win32 v4.61 (build 1039)              ¦
¦               MegaStorm Systems © 2005                 ¦
¦            http://www.megastormsystems.com               ¦
+----------------------------------------------------------+

· TestSpeed v2.2

· Executing at Mon Sep 19 01:25:24 2005
· Running on AMD processor - AthlonXP (A) - MMX - SSE
· Selected 'Athlon' optimized code path.

· CRM32Pro successfully initiated.

· Test FillRect background - Number of sprites: N/A - Sprite: N/A
· 5 seconds of benchmarking
· 205 total frames rendered
· 34.08 frames per second

· Selected normal code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 1.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 317 total frames rendered
· 52.81 frames per second

· Test 1.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 333 total frames rendered
· 55.44 frames per second

· Test 1.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 278 total frames rendered
· 46.30 frames per second

· Test 1.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 159 total frames rendered
· 26.37 frames per second

· Test 1.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 45 total frames rendered
· 7.33 frames per second

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 253 total frames rendered
· 42.12 frames per second

· Selected 'MMX-I' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 2.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 365 total frames rendered
· 60.80 frames per second

· Test 2.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 337 total frames rendered
· 56.03 frames per second

· Test 2.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 278 total frames rendered
· 46.25 frames per second

· Test 2.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 164 total frames rendered
· 27.33 frames per second

· Test 2.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 45 total frames rendered
· 7.43 frames per second

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 263 total frames rendered
· 43.69 frames per second

· Selected 'MMX-II' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 3.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 360 total frames rendered
· 59.88 frames per second

· Test 3.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 332 total frames rendered
· 55.26 frames per second

· Test 3.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 281 total frames rendered
· 46.78 frames per second

· Test 3.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 166 total frames rendered
· 27.64 frames per second

· Test 3.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 49 total frames rendered
· 7.86 frames per second

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 260 total frames rendered
· 43.33 frames per second

· Selected 'MMX-III' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 4.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 371 total frames rendered
· 61.76 frames per second

· Test 4.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 363 total frames rendered
· 60.49 frames per second

· Test 4.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 332 total frames rendered
· 55.20 frames per second

· Test 4.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 267 total frames rendered
· 44.50 frames per second

· Test 4.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 138 total frames rendered
· 22.86 frames per second

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 289 total frames rendered
· 48.15 frames per second

· Selected 'MMX-IV' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 5.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 373 total frames rendered
· 62.13 frames per second

· Test 5.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 363 total frames rendered
· 60.42 frames per second

· Test 5.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 337 total frames rendered
· 56.06 frames per second

· Test 5.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 264 total frames rendered
· 43.99 frames per second

· Test 5.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 143 total frames rendered
· 23.73 frames per second

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 290 total frames rendered
· 48.25 frames per second

· Selected 'MMX-V' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 6.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 357 total frames rendered
· 57.69 frames per second

· Test 6.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 312 total frames rendered
· 51.90 frames per second

· Test 6.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 215 total frames rendered
· 35.77 frames per second

· Test 6.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 149 total frames rendered
· 24.75 frames per second

· Test 6.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 45 total frames rendered
· 7.26 frames per second

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 223 total frames rendered
· 37.17 frames per second

· Selected 'K7' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 8.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 5 seconds of benchmarking - 345 total frames rendered
· 57.43 frames per second

· Test 8.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 5 seconds of benchmarking - 305 total frames rendered
· 50.74 frames per second

· Test 8.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 5 seconds of benchmarking - 158 total frames rendered
· 26.32 frames per second

· Test 8.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 5 seconds of benchmarking - 111 total frames rendered
· 18.44 frames per second

· Test 8.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 5 seconds of benchmarking - 42 total frames rendered
· 6.70 frames per second

· Test 8.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 244 total frames rendered
· 40.59 frames per second


· CRM32Pro successfully closed.

[AK47]

 Saludos
Mi maquina es un Athlon 1.4 GHz con 768 MB de ram

[_Grey]

 Bueno, con bastante retraso, pero ahi va:

Athlon64 3000+ (2Ghz)
1Gb
WinXP SP2

+----------------------------------------------------------+
¦           CRM32Pro Win32 v4.6x (build 1030)              ¦
¦               MegaStorm Systems © 2005                 ¦
¦            http://www.megastormsystems.com               ¦
+----------------------------------------------------------+

· TestSpeed v2.1

· Executing at Wed Sep 21 05:18:13 2005
· Running on AMD processor - Athlon64 - MMX - SSE
· Selected 'AthlonXP' optimized code path.

· CRM32Pro successfully initiated.

· Test FillRect background - Number of sprites: N/A - Sprite: N/A
· 5 seconds of benchmarking
· 1569 total frames rendered
· 261.37 frames per second

· Selected normal code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 1.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2301 total frames rendered during 5 seconds
· 383.44 frames per second

· Test 1.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 1866 total frames rendered during 5 seconds
· 311.00 frames per second

· Test 1.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1398 total frames rendered during 5 seconds
· 232.96 frames per second

· Test 1.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 743 total frames rendered during 5 seconds
· 123.71 frames per second

· Test 1.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 206 total frames rendered during 5 seconds
· 34.15 frames per second

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1203 total frames rendered during 5 seconds
· 200.43 frames per second

· Selected 'K7 & K8' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 2.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2321 total frames rendered during 5 seconds
· 386.77 frames per second

· Test 2.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 1963 total frames rendered during 5 seconds
· 327.11 frames per second

· Test 2.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1277 total frames rendered during 5 seconds
· 212.76 frames per second

· Test 2.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 685 total frames rendered during 5 seconds
· 114.09 frames per second

· Test 2.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 208 total frames rendered during 5 seconds
· 34.62 frames per second

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1483 total frames rendered during 5 seconds
· 247.17 frames per second

· Selected 'Pentium 3' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 3.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2322 total frames rendered during 5 seconds
· 386.94 frames per second

· Test 3.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 1938 total frames rendered during 5 seconds
· 322.89 frames per second

· Test 3.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1295 total frames rendered during 5 seconds
· 215.80 frames per second

· Test 3.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 700 total frames rendered during 5 seconds
· 116.55 frames per second

· Test 3.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 211 total frames rendered during 5 seconds
· 35.13 frames per second

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1429 total frames rendered during 5 seconds
· 238.13 frames per second

· Selected 'MMX-I' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 4.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2322 total frames rendered during 5 seconds
· 387.00 frames per second

· Test 4.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 2012 total frames rendered during 5 seconds
· 335.33 frames per second

· Test 4.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1341 total frames rendered during 5 seconds
· 223.50 frames per second

· Test 4.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 708 total frames rendered during 5 seconds
· 117.98 frames per second

· Test 4.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 218 total frames rendered during 5 seconds
· 36.21 frames per second

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1267 total frames rendered during 5 seconds
· 211.06 frames per second

· Selected 'MMX-II' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 5.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2118 total frames rendered during 5 seconds
· 353.00 frames per second

· Test 5.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 1995 total frames rendered during 5 seconds
· 332.39 frames per second

· Test 5.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1395 total frames rendered during 5 seconds
· 232.38 frames per second

· Test 5.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 684 total frames rendered during 5 seconds
· 113.96 frames per second

· Test 5.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 221 total frames rendered during 5 seconds
· 36.83 frames per second

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1266 total frames rendered during 5 seconds
· 211.00 frames per second

· Selected 'MMX-III' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 6.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2224 total frames rendered during 5 seconds
· 370.60 frames per second

· Test 6.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 2267 total frames rendered during 5 seconds
· 377.71 frames per second

· Test 6.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1772 total frames rendered during 5 seconds
· 295.28 frames per second

· Test 6.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 1018 total frames rendered during 5 seconds
· 169.55 frames per second

· Test 6.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 430 total frames rendered during 5 seconds
· 71.62 frames per second

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1601 total frames rendered during 5 seconds
· 266.79 frames per second

· Selected 'MMX-IV' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 7.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2170 total frames rendered during 5 seconds
· 361.61 frames per second

· Test 7.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 2240 total frames rendered during 5 seconds
· 373.33 frames per second

· Test 7.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1834 total frames rendered during 5 seconds
· 305.62 frames per second

· Test 7.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 812 total frames rendered during 5 seconds
· 135.33 frames per second

· Test 7.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 308 total frames rendered during 5 seconds
· 51.24 frames per second

· Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1606 total frames rendered during 5 seconds
· 267.53 frames per second

· Selected 'MMX-V' optimized code path.
· 800x600x32bits
· Screen is in system memory
· Sprite is in system memory
· Background is in System Memory
· Test 8.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
· 2266 total frames rendered during 5 seconds
· 377.67 frames per second

· Test 8.2 - Number of sprites: 100 - Sprite: 32.bmp - Scanline: 128
· 1810 total frames rendered during 5 seconds
· 301.62 frames per second

· Test 8.3 - Number of sprites: 100 - Sprite: 64.bmp - Scanline: 256
· 1430 total frames rendered during 5 seconds
· 238.21 frames per second

· Test 8.4 - Number of sprites: 100 - Sprite: 128.bmp - Scanline: 512
· 667 total frames rendered during 5 seconds
· 111.06 frames per second

· Test 8.5 - Number of sprites: 100 - Sprite: 256.bmp - Scanline: 1024
· 186 total frames rendered during 5 seconds
· 30.87 frames per second

· Test 8.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1319 total frames rendered during 5 seconds
· 219.80 frames per second


· CRM32Pro successfully closed.