Foxconn e-bot Small Form Factor PC

Article Index

Real World Results with Wolfenstein and UT2004

Wolfenstein: Enemy Territory
OpenGL Quake Engine Gaming

To start our in-game testing, we ran through a batch of time demos with the OpenGL game Wolfenstein: Enemy Territory.  Wolfenstein: ET is a free, standalone multiplayer game that is based on the original Return to Castle Wolfenstein, that was released a few years back. It uses a heavily modified version of the Quake 3 engine which makes it a very easy to use benchmarking tool.  We ran the test using the "Fastest" setting at a low resolution of 640X480, using 16-bit color and textures.  Running this test with a higher-end graphics card, at these minimal settings, isolates processor and memory performance, without being limited by the graphics subsystem.

The frame rates we got with Wolfenstein - Enemy Territory clearly point out the advantages gained by the extra bandwidth afforded by the dual-channel setups.  The Foxconn e-bot put up respectable numbers, albeit at 640x460 with every setting turned down, but was still anywhere from 7 to 9 frames per second behind the other two systems.  Our performance delta is now looking at about a 7- 9 percent dropoff from the leaderboard.

Unreal Tournament 2004
DirectX Gaming Performance

Lastly, we did some benchmarking with Epic's Unreal Tournament 2004.  When we tested these systems with UT 2004, we ensured that all of them were being benchmarked with the exact same in-game settings and graphical options, and we dropped the resolution and detail levels to isolate CPU and memory performance.



More of the same occurred in Unreal Tournament 2004, although the Shuttle SB61G2 and Foxconn e-bot were much closer in framerates this time around.  The Epox ex5-320S placed well above the other two, at exactly eight frames faster than the e-bot.   This equated to the largest difference in any of our real-world tests; nearly a 10% difference from top to bottom.

 


Related content

Comments

Show comments blog comments powered by Disqus