New Crysis WARHEAD Benchmark Tool BETA

hmm, that would be great for DX9 vs DX10, gamer vs enthusiast, ect setting comparisons.

 

Please add support for the Steam version of Warhead. For 32-bit windows the executable is located at:
C:\Program Files\Steam\steamapps\common\crysis warhead\Bin32\Crysis.exe

And for 64-bit windows it is located at:
C:\Program Files (x86)\Steam\steamapps\common\crysis warhead\Bin32\Crysis.exe

Better yet please just add the ability to specify a custom executable location.

 

you tried verr 0.8?

 

It gives an error about the .NET framework, but I already have 3.0 installed, which includes everything from 1.1

 

I don't think 3.0 includes 1.1. Same thing is happening for me, I have 3.5 isntalled, and it wants me to install 1.1 (which i really dont want to do)

 

LOL , made my day

 

New build 0.09 available

Thanks

Thank you, very good results!

Time of day option added. 0 means timedemo's default time of day.

I'll add the option to capture screenshots at certain frames in a future build.

Since build 0.08 the program will ask for game's installation path if the registry don't have that information. Did you tried that latest build?

Well, you'll need .NET framework 1.1 runtime in order to run the benchmarking tool.

Sorry, as stated above .NET Framework 1.1 runtime is needed.

:roll:

 

Works great THX...

Did notice it showed DX10 at the bottom even though it was a DX9 run.

You should of lobbed some nades in the video or shot at a mine something

 

nice work.

is there a standard or preferred setting for your ranked benchmark
comparison and can u post the url or the ranked top10 list here?

my gtx280 sli can do whatever setting it is and its not even overclocked
yet hehe

regards
wombel

 

USFORCES

omfg...those 280s really show there beastyness in this game...

 

Running the latest version:




Happens a few seconds after I hit execute, while Steam is starting Warhead up. Maybe just that Steam returns some wrong value when the benchmark app calls warhead, and then the app looks for the logfile, that doesn't exist yet. (you're just using a streamreader/filestream or similar and not checking if it is a valid stream?)

Maybe add a way to manually hit "read in logfile, run next test"?

Exception info:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not find file "c:\program files (x86)\steam\steamapps\common\crysis warhead\Game\Levels\avalanche\framebuffer.log".
File name: "c:\program files (x86)\steam\steamapps\common\crysis warhead\Game\Levels\avalanche\framebuffer.log"
at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize)
at System.IO.StreamReader..ctor(String path, Encoding encoding)
at FBWHTool.Form1.showTime(String _map, String _special, String _mode, String _res, String _aa, String _runs, String _api, String _hora, Boolean lastRun)
at FBWHTool.Form1.OnShowtime()
at FBWHTool.Form1.timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.Callback(IntPtr hWnd, Int32 msg, IntPtr idEvent, IntPtr dwTime)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
FBWHTool
Assembly Version: 0.1.0.0
Win32 Version: 0.1.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/FRAMEBUFFER%20Crysis%20WARHEAD%20Benchmark%20Tool/FBWHTool.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
RegexAssembly3_0
Assembly Version: 0.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.85.5.452
Win32 Version: 0.85.5.452
CodeBase: file:///C:/Program%20Files%20(x86)/FRAMEBUFFER%20Crysis%20WARHEAD%20Benchmark%20Tool/ICSharpCode.SharpZipLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

 

is it possible to post the source so we can compile it in .NET 3?

 

I didn't need to install the Net frame work with Vista.

 

Hi there,

I just downloaded the tool, about 10 minutes ago and installed it.

This is what I get after I exit Crysis Warhead:


When I execute, Crysis starts in 1920x1200 despite the 1280x800 I selected and no demo/benchmark is run.

Any ideas?

Patrick

 

Yeah !! I see ..

Thanks guy :banana:

 

version 0.10
Vista 64

Three bugs:

I installed game under XP, so I have to manually point benchtool to crysis folder. The path isnt saved.

DX10 mode is run in window-mode. Vista64

Benchtool failed during bench, saying:
E:/games/Crysis WARHEADGame/config/cvargroups not found.
Strangely it failed during second loop.

Notice the red text. Needs to be /Crysis WARHEAD/Game/. I made an according folder and copied cvargroups in to it. Tool has been running fine since.

#0 Thank you for the tool Appreciate your work.

 

Same bug I posted, its getting a return, I'm guessing with the steam version (calling Crysis.exe with steam may return prematurely, causing the tool to look for the framebuffer data before it exists.)

Can I get source, so I can step through the bug?

Also, I think that .net 1.1 comes with Vista - but I'm not 100% on that. Windows update should offer it, either way.

 

Hm, I don't have the steam version so that can't be te problem and I assumed .net3.5 or whatever it's called is completely backward compatible with earlier versions.

Anyway, .net 1.1 is installed including .net 1.1 hotfix kb929729.

btw. about the source, do you mean the entire text of my bug window?

 

Thank you for posting the entire error, as stated in Known Issues the tool doesn't work with Steam version, looks like Steam's Crysis executable works in a different way, I'll try to fix in a future build.

Sorry, right now I'll not post the source code.

Hi Patrick, please browse to "C:\Program Files (x86)\Electronic Arts\Crytek\Crysis WARHEAD\Game\Levels\avalanche" and check if framebuffer.tmd file is there. 1280x800 is a supported screen resolution by your display driver?

Crysis will start at resolution you defined in the game, the FBWHTool will not change game configurations, that's why the game starts in 1920x1200 regardless the resolution you choose in the testrun.

You're welcome.

Fixed the missing backslash on path, sorry about that and thanks for pointing it out.

The tool will only look at CVarGroups if you choose Ranked benchmark mode, it will hash the game's .cfg files so the results can be compared to a non-modified game.