rec.autos.simulators

N2/ICR2 Benchmarks on 200 MMX

esetse

N2/ICR2 Benchmarks on 200 MMX

by esetse » Mon, 03 Feb 1997 04:00:00

Okay, I've finally got the data together for the performance of my new
200 MMX-based machine (with Rendition).  And the results are:

Chrisbench VGA          36.1 fps
Chrisbench SVGA         41.2 fps
Air Warrior bench       89.25 fps

Nascar 2 Tests - All cars, all textures, MIS
                         Min             Max
RENDDMA                 23.5            28.5
NASCAR2 (non 3D)        18.5            22.5

Note that the Rendition modes look much better than the basic NASCAR2,
so you are gaining quality and quantity!  Also note that NASREND was so
slow as to be unplayable for this particular test case (maybe 10 fps).

ICR2 (Indyfast) - All cars, all textures, MIS

Frame rate was 25-27 FPS on race start

Oh, and I adjusted PCI Latency to get over 90 on DMADIAG, and gained
about 1 fps over these numbers for both ICR2 and RENDDMA.

Configuration - Pentium 200 MMX CPU
                ASUS P/I-P55T2P4 Motherboard with 512K cache(Hx chipset)
                Intergraph Reactor Video (now Intense 3D I think)
                32 M EDO RAM
                Not overclocked
                Baseline PCI Latency - 32
                Increased PCI Latency - 56

Test Method - At Michigan at the end of a full field with 39 cars seen
front, 4 behind and 2 heard.  All textures on (using skids/paint on auto
to do the test).  Under yellow at the beginning of the pace lap,
evaluated the frame rate from the start/finish line to turn 2.  Same
method for ICR2 except used the frame rate counter to evuluate rate with
all textures on.


rec.autos.simulators is a usenet newsgroup formed in December, 1993. As this group was always unmoderated there may be some spam or off topic articles included. Some links do point back to racesimcentral.net as we could not validate the original address. Please report any pages that you believe warrant deletion from this archive (include the link in your email). RaceSimCentral.net is in no way responsible and does not endorse any of the content herein.