Thx very much for programming the Arma2FPS-Analyzer, the screenshots posted here look very good and sure give interesting feedback for all testers.
But I must be doing something wrong either in setup or in saving/getting back data / using the tool.
First of all this question: is it correct, that every time you want to use the tool you have to run setup.exe ? because I don't get info about any installation-path. so there isn't a resident .exe file except the setup.exe ?
my steps in detail:
-> I have copied the BM....pbo's in to Arma 2\missions\
-> I find these BM-missions in scenarios as expected and I can also run them
-> while running the BM-mission I have no other FPS-meter at OSD (I normally use FPS-meter of ATITrayTools)
-> the mission ends with the text '1-1-A 1 (langgis08) LOG SAVED'
-> I tab on desktop, let the tool's setup.exe (V2.0) run and ... I get a weird graph in "FPS over time": Y-Axis (fps) ranges from 0 to 80, x-Axis (time) ranges from 0 to 8889277 nearly totally blue as if all dots/pixels in the graph's area are set ... (?)
-> tried it with every BM-file, all the time same crazy results
here's the data logged in arma2.rpt (example): Spoiler:
>First of all this question: is it correct, that every time you want to use the tool you have to run setup.exe ?
No - after you have run setup.exe once, you will find the analyser under start/all programs/armafpsanalyser :-) Apart from that, everything is fine (and you shouldn't be breaking anything by running setup twice - it's just unnecesary).
I just tried the example data you sent and got a sensible output. Can you do the following ?
1) rename your arma2.rpt to oldarma2.rpt
2) Run another benchmark.
3) Start the analyser
If you still get garbage output, could you send me the new arma2.rpt file by email or stick it on download site somewhere and I will take a look at what is going on. If the problem has magically fixed itself, could you send me the oldarma2.rpt file instead ? I suspect a parsing error - possibly due to stoppring a benchmakr during its output phase but only the complete file will tell.
Seems to be a nice program, but I can't get it to work on my pc (Vista 64).
It fails with the following: Spoiler:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Single.Parse(String s, NumberStyles style, NumberFormatInfo info)
at WindowsFormsApplication1.Trace.readSubTrace(Stream Reader sr)
at WindowsFormsApplication1.Trace.read(StreamReader sr, Session ses, Int32 n)
at WindowsFormsApplication1.Session.read(StreamReader sr)
at WindowsFormsApplication1.Rpt.read(StreamReader sr)
at WindowsFormsApplication1.Form1.Form1_Shown(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnShown(EventArgs e)
at System.Windows.Forms.Control.InvokeMarshaledCallba ckHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Objec t userData)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallba ck(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallba cks()
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
Got some time to test this now, but i get the same problem as TheBarricade. When i try to start your app after running a bench an error notice come up with the exact same content as above. Initial run after install works ok.