Imprimir Página - Sprites 2d Por Software

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 15 de Septiembre de 2005, 04:23:46 PM

Hola pekenos hobbits,

necesito voluntarios para que probeis este test. Utiliza varios tamanos de sprites y 8 rutinas distintas optimizadas via ASM(MMX+SSE). Dura aproximadamente 6min en completarse, genera un .log que podeis o bien colgar aqui, o enviarmelo por correo.

Despues, lo metere en una hoja de calculo Excel y pondre aqui un pantallazo para que veais todos los resultados.

Para los que penseis..."que perdida de tiempo" deciros que estos test son para hacer un "fine tuning" de que rutina utilizar para que tamano dependiendo de la CPU y utilizando todo esto.. la mejora volcando sprites usando la CPU es bastante grande. Y los que me habeis leido un poco antes... lo de optimizar es casi por hobby... mola una vez terminado todo, pensar y pensar en como optimizar el sistema a nivel de instrucciones.

Test Speed Benchmark

Por cierto, la lib CRM32Pro.dll que incluye es de la proxima 4.60, no la utiliceis puesto que aun la estoy probando, me falta probar en linux unas cosillas, corregir un bug sencillote y agregar este "fine tuning" para subirla a la web.

Nada mas, espero vuestra ayuda!
Saludos

Título: Sprites 2d Por Software
Publicado por: jazcks en 15 de Septiembre de 2005, 06:01:16 PM

lo he probado en el curro, que corre menos que el caballo del malo :P

Código [Seleccionar]

 · TestSpeed v2.1

 · Executing at Thu Sep 15 17:51:58 2005
 · Running on INTEL processor - Pentium III - MMX - SSE
 · Selected 'MMX-II' optimized code path.

 · CRM32Pro successfully initiated.

 · Test FillRect background - Number of sprites: N/A - Sprite: N/A
 · 5 seconds of benchmarking
 · 203 total frames rendered
 · 33.78 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
 · 350 total frames rendered during 5 seconds
 · 58.21 frames per second

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

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

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

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

 · Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 236 total frames rendered during 5 seconds
 · 39.22 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
 · 353 total frames rendered during 5 seconds
 · 58.71 frames per second

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

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

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

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

 · Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 257 total frames rendered during 5 seconds
 · 42.81 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
 · 357 total frames rendered during 5 seconds
 · 59.39 frames per second

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

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

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

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

 · Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 257 total frames rendered during 5 seconds
 · 42.71 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
 · 352 total frames rendered during 5 seconds
 · 58.66 frames per second

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

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

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

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

 · Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 218 total frames rendered during 5 seconds
 · 36.32 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
 · 357 total frames rendered during 5 seconds
 · 59.39 frames per second

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

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

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

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

 · Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 222 total frames rendered during 5 seconds
 · 36.90 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
 · 361 total frames rendered during 5 seconds
 · 60.06 frames per second

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

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

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

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

 · Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 261 total frames rendered during 5 seconds
 · 43.38 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
 · 266 total frames rendered during 5 seconds
 · 44.22 frames per second

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

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

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

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

 · Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 259 total frames rendered during 5 seconds
 · 43.15 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
 · 348 total frames rendered during 5 seconds
 · 57.91 frames per second

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

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

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

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

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


 · CRM32Pro successfully closed.

Título: Sprites 2d Por Software
Publicado por: BeRSeRKeR en 15 de Septiembre de 2005, 06:18:55 PM

Código [Seleccionar]


 · TestSpeed v2.1

 · Executing at Thu Sep 15 18:02:58 2005
 · Running on INTEL processor - Pentium 4(Northwood) - MMX - SSE
 · Selected 'K7 & K8' optimized code path.

 · CRM32Pro successfully initiated.

 · Test FillRect background - Number of sprites: N/A - Sprite: N/A
 · 5 seconds of benchmarking
 · 1578 total frames rendered
 · 262.96 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
 · 2741 total frames rendered during 5 seconds
 · 456.76 frames per second

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

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

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

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

 · Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1518 total frames rendered during 5 seconds
 · 252.92 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
 · 2588 total frames rendered during 5 seconds
 · 431.19 frames per second

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

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

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

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

 · Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1890 total frames rendered during 5 seconds
 · 315.00 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
 · 2613 total frames rendered during 5 seconds
 · 435.43 frames per second

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

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

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

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

 · Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1861 total frames rendered during 5 seconds
 · 310.11 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
 · 2718 total frames rendered during 5 seconds
 · 452.92 frames per second

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

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

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

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

 · Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1543 total frames rendered during 5 seconds
 · 257.17 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
 · 2750 total frames rendered during 5 seconds
 · 458.26 frames per second

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

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

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

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

 · Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1519 total frames rendered during 5 seconds
 · 253.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 6.1 - Number of sprites: 100 - Sprite: 16.bmp - Scanline: 64
 · 2647 total frames rendered during 5 seconds
 · 441.02 frames per second

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

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

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

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

 · Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1812 total frames rendered during 5 seconds
 · 301.90 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
 · 2655 total frames rendered during 5 seconds
 · 442.50 frames per second

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

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

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

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

 · Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1802 total frames rendered during 5 seconds
 · 300.23 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
 · 2697 total frames rendered during 5 seconds
 · 449.50 frames per second

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

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

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

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

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


 · CRM32Pro successfully closed.

Título: Sprites 2d Por Software
Publicado por: josepzin en 15 de Septiembre de 2005, 06:26:32 PM

Te lo envié por email.

Título: Sprites 2d Por Software
Publicado por: Flint en 15 de Septiembre de 2005, 06:44:18 PM

Código [Seleccionar]

· TestSpeed v2.1

 · Executing at Thu Sep 15 18:33:36 2005
 · Running on INTEL processor - Pentium 4(Prescott) - MMX - SSE
 · Selected 'K7 & K8' optimized code path.

 · CRM32Pro successfully initiated.

 · Test FillRect background - Number of sprites: N/A - Sprite: N/A
 · 5 seconds of benchmarking
 · 2236 total frames rendered
 · 372.54 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
 · 3305 total frames rendered during 5 seconds
 · 550.83 frames per second

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

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

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

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

 · Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1792 total frames rendered during 5 seconds
 · 298.52 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
 · 3418 total frames rendered during 5 seconds
 · 569.67 frames per second

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

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

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

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

 · Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 2388 total frames rendered during 5 seconds
 · 398.00 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
 · 3409 total frames rendered during 5 seconds
 · 568.07 frames per second

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

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

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

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

 · Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 2370 total frames rendered during 5 seconds
 · 394.93 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
 · 3452 total frames rendered during 5 seconds
 · 575.33 frames per second

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

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

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

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

 · Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1833 total frames rendered during 5 seconds
 · 305.50 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
 · 3442 total frames rendered during 5 seconds
 · 573.57 frames per second

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

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

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

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

 · Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1822 total frames rendered during 5 seconds
 · 303.62 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
 · 3409 total frames rendered during 5 seconds
 · 568.07 frames per second

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

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

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

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

 · Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 2289 total frames rendered during 5 seconds
 · 381.37 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
 · 3445 total frames rendered during 5 seconds
 · 574.17 frames per second

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

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

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

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

 · Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 2283 total frames rendered during 5 seconds
 · 380.50 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
 · 3457 total frames rendered during 5 seconds
 · 576.17 frames per second

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

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

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

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

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


 · CRM32Pro successfully closed.

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 15 de Septiembre de 2005, 07:01:45 PM

Sois la leche!!! que rapidez!!! (ole)

veo que tengo varios emails mas esto de por aqui... he visto asi a grosso modo Pentium3, Athlon, Duron, Pentium4(un prescott que me viene de perlas!)... voy a merendar algo y ver un poco de X Files(uno que es un friki) y despues recolecto todas las estadisticas, ajusto la lib a todo lo que me habeis dicho y a ver si el release es para mañana(con un poco de suerte).

Ah, alguno de los que me mando mail(puede ser Ager?) creo que el del Duron ponia que se veia todo muy distorsionado... pero todos los test?? o algunos?? es posible que el Duron al no tener MMX+(como lo llama AMD) ni SSE casque en algun test... pero en todos?? no creo...pero mejor pregunto :P

Y una cosa que se me olvido postear, si podeis, ponerme que micro teneis y su velocidad... puede que mi rutina de deteccion falle con alguno

lo dicho, luego vuelvo con mas!!

A ver si se anima algun Athlon64 que no hay ninguno....

Título: Sprites 2d Por Software
Publicado por: josepzin en 15 de Septiembre de 2005, 07:07:18 PM

En mi pc, la pantalla quedaba en negro y se ve un cartel de fuera de sincronismo o algo asi (que lo pone el mismo monitor).

Micro: Intel ® Pentium ® 4, CPU 3.00GHz... creo que eso es todo.

Título: Sprites 2d Por Software
Publicado por: [EX3] en 15 de Septiembre de 2005, 07:13:21 PM

Citar· TestSpeed v2.1

· Executing at Thu Sep 15 18:42:52 2005
· Running on AMD processor - AthlonXP - 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
· 337 total frames rendered
· 56.17 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
· 595 total frames rendered during 5 seconds
· 99.05 frames per second

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

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

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

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

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 349 total frames rendered during 5 seconds
· 58.17 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
· 556 total frames rendered during 5 seconds
· 92.65 frames per second

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

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

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

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

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 527 total frames rendered during 5 seconds
· 87.82 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
· 584 total frames rendered during 5 seconds
· 97.30 frames per second

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

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

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

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

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 505 total frames rendered during 5 seconds
· 84.07 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
· 571 total frames rendered during 5 seconds
· 95.07 frames per second

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

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

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

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

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 361 total frames rendered during 5 seconds
· 60.11 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
· 620 total frames rendered during 5 seconds
· 103.21 frames per second

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

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

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

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

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 369 total frames rendered during 5 seconds
· 61.43 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
· 616 total frames rendered during 5 seconds
· 102.58 frames per second

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

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

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

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

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 417 total frames rendered during 5 seconds
· 69.40 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
· 647 total frames rendered during 5 seconds
· 107.82 frames per second

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

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

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

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

· Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 447 total frames rendered during 5 seconds
· 74.36 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
· 571 total frames rendered during 5 seconds
· 95.09 frames per second

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

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

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

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

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

· CRM32Pro successfully closed.

Salu2...

Título: Sprites 2d Por Software
Publicado por: Flint en 15 de Septiembre de 2005, 07:16:23 PM

Información del micro:

(http://img108.imageshack.us/img108/139/informacionmicro2ev.jpg)

Título: Sprites 2d Por Software
Publicado por: Xam en 15 de Septiembre de 2005, 08:44:44 PM

Citar
· TestSpeed v2.1

· Executing at Thu Sep 15 20:32:53 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
· 1131 total frames rendered
· 188.41 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
· 1573 total frames rendered during 5 seconds
· 262.08 frames per second

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

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

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

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

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 983 total frames rendered during 5 seconds
· 163.75 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
· 1576 total frames rendered during 5 seconds
· 262.67 frames per second

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

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

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

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

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1192 total frames rendered during 5 seconds
· 198.67 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
· 1577 total frames rendered during 5 seconds
· 262.79 frames per second

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

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

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

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

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1189 total frames rendered during 5 seconds
· 198.10 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
· 1584 total frames rendered during 5 seconds
· 263.87 frames per second

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

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

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

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

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 993 total frames rendered during 5 seconds
· 165.42 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
· 1583 total frames rendered during 5 seconds
· 263.79 frames per second

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

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

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

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

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 993 total frames rendered during 5 seconds
· 165.50 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
· 1587 total frames rendered during 5 seconds
· 264.50 frames per second

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

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

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

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

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1161 total frames rendered during 5 seconds
· 193.47 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
· 1588 total frames rendered during 5 seconds
· 264.53 frames per second

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

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

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

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

· Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1172 total frames rendered during 5 seconds
· 195.20 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
· 1583 total frames rendered during 5 seconds
· 263.83 frames per second

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

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

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

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

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

Aquí tienes un AMD64 3400+ ClawHammer (1Mb L2 cache, Single Channel).

Título: Sprites 2d Por Software
Publicado por: AgeR en 15 de Septiembre de 2005, 08:58:04 PM

Sí, me petan todos los test.
Duron 800, 384 mb de ram, TNT2 (va a ser por la gráfica) últimos drivers, WinME.

Título: Sprites 2d Por Software
Publicado por: Pogacha en 15 de Septiembre de 2005, 10:41:30 PM

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

· TestSpeed v2.1

· Executing at Thu Sep 15 17:32:22 2005
· Running on INTEL processor - Pentium 4(Northwood) - MMX - SSE
· Selected 'K7 & K8' optimized code path.

· CRM32Pro successfully initiated.

· Test FillRect background - Number of sprites: N/A - Sprite: N/A
· 5 seconds of benchmarking
· 1028 total frames rendered
· 171.30 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
· 1486 total frames rendered during 5 seconds
· 247.58 frames per second

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

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

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

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

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 951 total frames rendered during 5 seconds
· 158.42 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
· 1453 total frames rendered during 5 seconds
· 242.13 frames per second

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

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

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

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

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1061 total frames rendered during 5 seconds
· 176.80 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
· 1448 total frames rendered during 5 seconds
· 241.29 frames per second

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

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

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

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

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1056 total frames rendered during 5 seconds
· 175.85 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
· 1499 total frames rendered during 5 seconds
· 249.71 frames per second

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

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

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

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

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 927 total frames rendered during 5 seconds
· 154.42 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
· 1495 total frames rendered during 5 seconds
· 249.13 frames per second

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

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

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

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

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 927 total frames rendered during 5 seconds
· 154.47 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
· 1517 total frames rendered during 5 seconds
· 252.83 frames per second

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

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

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

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

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 998 total frames rendered during 5 seconds
· 166.22 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
· 1519 total frames rendered during 5 seconds
· 253.08 frames per second

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

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

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

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

· Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 989 total frames rendered during 5 seconds
· 164.70 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
· 1500 total frames rendered during 5 seconds
· 250.00 frames per second

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

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

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

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

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

· CRM32Pro successfully closed.

Título: Sprites 2d Por Software
Publicado por: Gunmaster en 15 de Septiembre de 2005, 10:50:50 PM

Citar· TestSpeed v2.1

· Executing at Thu Sep 15 21:40:42 2005
· Running on INTEL processor - Pentium 4 (4)- MMX - SSE
· Selected 'K7 & K8' optimized code path.

· CRM32Pro successfully initiated.

· Test FillRect background - Number of sprites: N/A - Sprite: N/A
· 5 seconds of benchmarking
· 1504 total frames rendered
· 250.67 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
· 2197 total frames rendered during 5 seconds
· 366.04 frames per second

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

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

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

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

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1300 total frames rendered during 5 seconds
· 216.67 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
· 2179 total frames rendered during 5 seconds
· 363.11 frames per second

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

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

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

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

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1552 total frames rendered during 5 seconds
· 258.54 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
· 2067 total frames rendered during 5 seconds
· 344.50 frames per second

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

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

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

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

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1544 total frames rendered during 5 seconds
· 257.29 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
· 2091 total frames rendered during 5 seconds
· 348.50 frames per second

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

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

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

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

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1337 total frames rendered during 5 seconds
· 222.72 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
· 2144 total frames rendered during 5 seconds
· 357.27 frames per second

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

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

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

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

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1376 total frames rendered during 5 seconds
· 229.26 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
· 2193 total frames rendered during 5 seconds
· 365.38 frames per second

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

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

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

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

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 1623 total frames rendered during 5 seconds
· 270.50 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
· 2227 total frames rendered during 5 seconds
· 371.17 frames per second

Título: Sprites 2d Por Software
Publicado por: tewe76 en 15 de Septiembre de 2005, 11:07:00 PM

Código [Seleccionar]

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

 · TestSpeed v2.1

 · Executing at Thu Sep 15 22:52:38 2005
 · Running on INTEL processor - Pentium II - MMX · Selected 'MMX-II' optimized code path.

 · CRM32Pro successfully initiated.

 · Test FillRect background - Number of sprites: N/A - Sprite: N/A
 · 5 seconds of benchmarking
 · 48 total frames rendered
 · 7.93 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
 · 52 total frames rendered during 5 seconds
 · 8.59 frames per second

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

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

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

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

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

 · Selected 'K7 & K8' optimized code path.
 · 800x600x32bits
 · Screen is in system memory
 · Sprite is in system memory

Qué corto me ha salido el log, ¿no?

Título: Sprites 2d Por Software
Publicado por: [EX3] en 16 de Septiembre de 2005, 05:54:45 AM

Cita de: "tewe76"Qué corto me ha salido el log, ¿no?

Es que esta incompleto, no esta terminado, fijate en el final del resto.

Salu2...

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 16 de Septiembre de 2005, 12:16:01 PM

Ayer se me jodio Internet en casa(gracias Auna, una vez mas me estas dando el servicio que te pago! :angry: ) y no pude hacer nada, voy a hacer unas cosillas en el curro y me pondre con todo esto. He visto que ya hay test de todas las CPUs asi que de lujo!

hay dos fallos por ahi...uno de vosotros tenia el log partido (porque intentaba ejecutar una rutina con instrucciones que no conoce el micro... lo retocare para poder ejecutarlo en el PentiumII) y lo mas jodio es Ager que no ve nada :S... luego os digo mas

muchisimas gracias a todos por "participar"!!! (ole)

PD: si fuera millonario, os regalaba a todos una PSP :P

Título: Sprites 2d Por Software
Publicado por: josepzin en 16 de Septiembre de 2005, 04:53:24 PM

Cita de: "TheAzazel"PD: si fuera millonario, os regalaba a todos una PSP :P

hee???? MALEDETO!! yo creía que al menos había de obsequio una de las nuevas GP32X... :'(

http://www.gpx2.com http://www.gp32x.com

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 16 de Septiembre de 2005, 07:07:34 PM

Bueno, analizados los resultados.. necesito saber algunas cosillas...

AK47,jacks,Berserker,EX3 y Pogacha: que micro y que velocidad?

Gunmaster: que micro y velocidad y ademas... se te colgo? porque el log no esta completo...

Tewe: te enviare una version especial para el PentiumII...

josezpin y Ager: quereis hacer de conejillos de indias?? si es asi... podeis empezar por bajarlos el SpacePong de mi web(ocupa poquito) y con el configurador, probar distintas cosas: modo software, hardware, ventana, pantalla completa, etc.. y me decis que sucede....

De momento, esto es todo amigos!!!
En cuanto solucione algunos bugs que habeis encontrado y rellene con la informacion que falte, subo el Excel y sus graficos para que lo veais.

Talugooo

Título: Sprites 2d Por Software
Publicado por: Douch en 16 de Septiembre de 2005, 07:49:11 PM

Ou!. Vaya, ahora que le iba a meter la "zarpa" parece que has eliminado el archivo de la web. ¿Es el mísmo benchmark que tienes anunciado en tu web, el de los conejitos rosas? (glSDL Benchmark v1.1).

Título: Sprites 2d Por Software
Publicado por: jazcks en 17 de Septiembre de 2005, 01:48:59 AM

el mio era un pentium 3 a 600mhz, creo que el bus a 133.

tb lo he probado en casa, pentium4 2.4Ghz, 800 ht

Código [Seleccionar]


 · TestSpeed v2.1

 · Executing at Sat Sep 17 01:37:56 2005
 · Running on INTEL processor - Pentium 4(Northwood) - MMX - SSE
 · Selected 'K7 & K8' optimized code path.

 · CRM32Pro successfully initiated.

 · Test FillRect background - Number of sprites: N/A - Sprite: N/A
 · 5 seconds of benchmarking
 · 1617 total frames rendered
 · 269.50 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
 · 2292 total frames rendered during 5 seconds
 · 382.00 frames per second

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

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

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

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

 · Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1436 total frames rendered during 5 seconds
 · 239.21 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
 · 2223 total frames rendered during 5 seconds
 · 370.50 frames per second

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

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

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

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

 · Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1713 total frames rendered during 5 seconds
 · 285.40 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
 · 2227 total frames rendered during 5 seconds
 · 371.17 frames per second

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

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

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

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

 · Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1690 total frames rendered during 5 seconds
 · 281.62 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
 · 2290 total frames rendered during 5 seconds
 · 381.67 frames per second

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

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

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

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

 · Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1445 total frames rendered during 5 seconds
 · 240.71 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
 · 2288 total frames rendered during 5 seconds
 · 381.27 frames per second

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

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

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

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

 · Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1448 total frames rendered during 5 seconds
 · 241.25 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
 · 2219 total frames rendered during 5 seconds
 · 369.83 frames per second

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

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

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

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

 · Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1662 total frames rendered during 5 seconds
 · 276.86 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
 · 2224 total frames rendered during 5 seconds
 · 370.67 frames per second

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

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

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

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

 · Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
 · 1650 total frames rendered during 5 seconds
 · 275.00 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
 · 2293 total frames rendered during 5 seconds
 · 382.10 frames per second

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

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

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

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

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


 · CRM32Pro successfully closed.

Título: Sprites 2d Por Software
Publicado por: [EX3] en 17 de Septiembre de 2005, 06:28:21 AM

Cita de: "TheAzazel"AK47,jacks,Berserker,EX3 y Pogacha: que micro y que velocidad?

AMD Athlon XP, 1533 MHz (5.75 x 267) 1800+

Sigue asi, te lo estas currando mucho ;)

Salu2...

Título: Sprites 2d Por Software
Publicado por: Gunmaster en 17 de Septiembre de 2005, 09:41:37 AM

Cita de: "TheAzazel"Gunmaster: que micro y velocidad y ademas... se te colgo? porque el log no esta completo...

Sí...lo dejé terminar pero no me salia del programa y estuvo andando unos 10 minutos y estaba mosqueado hasta que lo reinicié :(

Por cierto...

P. IV 550J, 3400 Mhz (17 x 200)

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 18 de Septiembre de 2005, 02:00:17 PM

Cita de: "Douch"Ou!. Vaya, ahora que le iba a meter la "zarpa" parece que has eliminado el archivo de la web. ¿Es el mísmo benchmark que tienes anunciado en tu web, el de los conejitos rosas? (glSDL Benchmark v1.1).

Lo elimine porque ya tenia bastantes resultados pero he dejado alli otra copia para ver si los errores que aparecieron...quedan suprimidos

No es el mismo test, el otro comparaba glSDL, modo software, directdraw y direct3d todos en modo 2D. Este ultimo test es puramente por software, tiene utilidad en CPU antiguas... segun he visto en los graficos en algunos casos se dobla el rendimiento asi que bastante bien (ole)

Bueno, pues he dejado el test en:
SpriteSpeed 2D

Los cambios son...reorganizacion del orden de las rutinas...(para permitir funcionar bien a los PentiumII y similares), una nueva rutina con copia SSE-2, por ahora no tiene utilidad pero para el futuro port a 64bits(tanto en linux como windows) sera la utilizada ya que MMX y similar..en modo 64bits no existen jeje.

Y bueno, deciros que estaria bien probarlo en estas CPUs(el resto ya esta bien surtidito :P):
-Pentium MMX
-Pentium II
-Cualquier derivado del K6
-Pentium 4 Willamette (es que no quedan de estos??)
-Algun Pentium 4 Prescott mas...
-Algun Athlon64(cualquiera de sus versiones) mas...

Ah, es probable que algun dia lo refine mas(mas o menos como el glSDL-Benchmark) con salida html y demas cositas y lo coloque en la web a vista de todos... pero me tendra que entrar la inspiracion...

Título: Sprites 2d Por Software
Publicado por: nsL en 18 de Septiembre de 2005, 02:29:46 PM

Oi que necesitabas un prescott mas ;)

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

· TestSpeed v2.2

· Executing at Sun Sep 18 14:21:00 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
· 1366 total frames rendered
· 227.55 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 - 2106 total frames rendered
· 351.00 frames per second

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

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

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

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

· Test 1.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1149 total frames rendered
· 191.50 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 - 2116 total frames rendered
· 352.61 frames per second

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

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

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

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

· Test 2.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1178 total frames rendered
· 196.30 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 - 2114 total frames rendered
· 352.33 frames per second

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

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

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

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

· Test 3.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1180 total frames rendered
· 196.67 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 - 2077 total frames rendered
· 346.11 frames per second

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

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

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

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

· Test 4.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1331 total frames rendered
· 221.83 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 - 2077 total frames rendered
· 346.05 frames per second

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

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

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

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

· Test 5.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1377 total frames rendered
· 229.46 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 - 2112 total frames rendered
· 352.00 frames per second

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

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

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

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

· Test 6.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1195 total frames rendered
· 199.17 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 - 2110 total frames rendered
· 351.67 frames per second

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

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

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

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

· Test 7.6 - Number of sprites: 100 - Sprite: BlitSurf - Scanline: 3200
· 5 seconds of benchmarking - 1174 total frames rendered
· 195.60 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 - 2032 total frames rendered
· 338.55 frames per second

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

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

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

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

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

· CRM32Pro successfully closed.

Enhorabuena por el trabajo (ole)

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 18 de Septiembre de 2005, 02:53:54 PM

Gracias nsL... por lo que por ahora faltan:

-Pentium MMX
-Pentium II
-Cualquier derivado del K6
-Pentium 4 Willamette (es que no quedan de estos??)
-Algun Athlon64(cualquiera de sus versiones) mas...

Título: Sprites 2d Por Software
Publicado por: josepzin en 18 de Septiembre de 2005, 04:25:34 PM

De donde bajo el SpacePong?

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 18 de Septiembre de 2005, 04:31:17 PM

Cita de: "josepzin"De donde bajo el SpacePong?

Desde la web:

MegaStorm

y muchisimas gracias por probarlo!!! mira que lo he probado en muchos sistemas.... debes ser un betatester cojonudo jeje

Título: Sprites 2d Por Software
Publicado por: josepzin en 18 de Septiembre de 2005, 05:06:31 PM

He bajado el juego, y me da este error: "Error al iniciar la aplicación porque no se encontró CRM32Pro.dll. La reinstalacion de la aplicación puede solucionar el problema"

Fui nuevamente a tu web y bajé eso del CRM32pro, lo instalé y seguía el problema. Al final probé copiando el archivo "CRM32Pro.dll" a la carpeta donde está el juego y funcionó.

Info que muestra el Setup:
Processor: GenuineIntel
Memory: 1021
DirectX: DIrectX v9.0
MMX: Available

Algunas observaciones:
-En modo "Ventana" me pone solo aceleracion por Software.
-En modo "Ventana" siempre queda a 800x600. Cuando lo pongo a 1024x768 igual queda a 800x600.
-En modo Fullscreen tanto a 16/32bs de colores me queda el monitor fuera de frecuencia. (cartelito de la pantalla)
-Apenas arrancar hace un ruido raro, y luego aparece el menu con la musica.

Ya sobre el juego en sí:
- La música que se reinicia cada rato es un poco "molesta"...
- El menú tendrías que ordenarlo un poco mejor. queda un poco disperso asi y le vendria bien algun icono o boton. Me parece.
- Igual, sobre el sonido se tendria que poder desactivar solo la musica.
- Cuando aparece la pelotita, lo hace muy de repente y de la nada.
- Igual cuando se sale de la pantalla, a veces "desaparece" antes de salir.
- A la pelotita le falta algun brillo como que gira o algo asi.

Espero que te sea util. :)

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 18 de Septiembre de 2005, 05:26:59 PM

Uhmm... para solucionar eso de que falta la .dll... agregare en todos los ejecutables todas las lib necesarias...asi sera menos engorroso.

En modo ventana, solo esta disponible el modo software, eso es correcto...lo de 800 y 1024 ya era un pequeño bug, en realidad, solo se soporta 800, luego la otra opcion la he deshabilitado en el setup.
Lo del ruido raro...es un trueno :P jeje, debe de salir un trueno y un minilogotipo con las letras MS o algo asi, despues un fade y ya salta el menu.
Y en el menu hay botones eh? si pasas por encima de cada opcion se iluminara y si clickeas tambien jeje o te refieres a otra cosa?
Lo de la musica que se repita pues si, tienes toda la razon... a ver si añado mas variedad aunque como solo es un ejemplo tampoco lo cuide mucho en ese aspecto.
Anoto lo de opcion de sonido/musica por separado...no habia caido en eso...

- Cuando aparece la pelotita, lo hace muy de repente y de la nada.
sip, es algo que esta corregido en la v1.04 que subire o esta noche o mañana...

- Igual cuando se sale de la pantalla, a veces "desaparece" antes de salir.
esto no lo sabia...lo mirare a ver...

- A la pelotita le falta algun brillo como que gira o algo asi.
tiene un pequeño(isimo) efecto de brillo... pero no se nota mucho jeje

-En modo Fullscreen tanto a 16/32bs de colores me queda el monitor fuera de frecuencia. (cartelito de la pantalla)
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???

Por lo demas, muchas gracias...como sigas asi...te vas a ganar la PSP.... anda que no has visto cosillas.....

Título: Sprites 2d Por Software
Publicado por: josepzin en 18 de Septiembre de 2005, 06:08:01 PM

Cita de: "TheAzazel"Lo del ruido raro...es un trueno :P jeje, debe de salir un trueno y un minilogotipo con las letras MS...

jeje, era la otra alternativa que se me había ocurrido... :)

CitarY en el menu hay botones eh? si pasas por encima de cada opcion se iluminara y si clickeas tambien jeje o te refieres a otra cosa?

Es que esa pantalla de menu la veo bastante floja, no se bien como explicarlo, pero da la sensacion de que hay textos desparramados por alli.

Citar- Igual cuando se sale de la pantalla, a veces "desaparece" antes de salir.
esto no lo sabia...lo mirare a ver...

Es raro, no se si te lo describí bien lo que hace. Es como si quedara congelada en el borde unos instantes y luego aparece de nuevo al centro de la pantalla.

Citartiene un pequeño(isimo) efecto de brillo... pero no se nota mucho jeje

Para mejorar el efecto, yo le pondría un pequeño motion blur (o un par de bolitas que vayan por detras apenas visibles)... O que dejen un rastro de particulas. Creo que sería mas vistoso.

Citary 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.

Título: Sprites 2d Por Software
Publicado por: Zaelsius en 18 de Septiembre de 2005, 06:50:26 PM

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.

Citar+----------------------------------------------------------+
¶    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

Título: Sprites 2d Por Software
Publicado por: zupervaca en 18 de Septiembre de 2005, 07:41:00 PM

ahi va mi contribucion tio ;)

Código [Seleccionar]

+----------------------------------------------------------+
¦           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?

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 19 de Septiembre de 2005, 12:40:03 AM

Cita de: "josepzin"
Citary 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)

Título: Sprites 2d Por Software
Publicado por: TheAzazel en 19 de Septiembre de 2005, 12:47:08 AM

@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

Título: Sprites 2d Por Software
Publicado por: Douch en 19 de Septiembre de 2005, 01:38:33 AM

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

Citar+----------------------------------------------------------+
¦ 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.

Título: Sprites 2d Por Software
Publicado por: AK47 en 19 de Septiembre de 2005, 08:44:37 AM

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

Título: Sprites 2d Por Software
Publicado por: _Grey en 21 de Septiembre de 2005, 05:29:52 AM

Bueno, con bastante retraso, pero ahi va:

Athlon64 3000+ (2Ghz)
1Gb
WinXP SP2

Citar+----------------------------------------------------------+
¦ 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.

Foros - Stratos

Proyectos => CRM32Pro => Mensaje iniciado por: TheAzazel en 15 de Septiembre de 2005, 04:23:46 PM