EvoScan v0.98 Now with Power & Torque Graphing - Map Tracing completed also!
Everybody complaining about not getting .98 Would you rather have it now and it be full of bugs and cant do what you want it to do. Or be Patience and wait for it to be finished 100% and be bug free? I am excited for .98 also but I would rather it be complete first
I talk to Hamish once in awhile, I know how busy he is, plus he and myself are also helping John Banks with his development efforts by getting the new live tuning protocol supported. I'm certain that is part of the delay.
I just purchased it today since I needed a logger right away, I thought I was just buying the 97 version and I could then upgrade to the newer version whenever. After buying and downloading it, I found it is the new 98 version anyway? So I guess he just hasn't changed the link on his site yet, woohoo! I've got the new version, now I just have to figure out how to use it, lol.
"Trigger data-logging with WOT"
what a good idea, I just implemented it for v0.98, done..
I have 10 beta testers testing and providing feedback on a more complete v0.98, so just a few more days, a lot of v0.99 features are slowly sneaking into v0.98 too at this rate, like 2byte logging support for those that have figured out how to mod their ROMs already. For those that want easy patching the MODs will need to wait for v0.99, and for realtime tuning.
Any other good ideas out there?
what a good idea, I just implemented it for v0.98, done..
I have 10 beta testers testing and providing feedback on a more complete v0.98, so just a few more days, a lot of v0.99 features are slowly sneaking into v0.98 too at this rate, like 2byte logging support for those that have figured out how to mod their ROMs already. For those that want easy patching the MODs will need to wait for v0.99, and for realtime tuning.
Any other good ideas out there?
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
I'd like to see some options so we can pick what we want to trigger logging. For example:
TPS @ 95% or higher + Knock above 3 Count or whatever your threshold preference is.
also it would need to go back a bit to record the moment this occurred or it would be missed.
TPS @ 95% or higher + Knock above 3 Count or whatever your threshold preference is.
also it would need to go back a bit to record the moment this occurred or it would be missed.
As far as I know .98 is still being worked out. Also he stated that he has been away on business. Give him a break, I am sure people here probably have .97 somewhere saved. As long as you have your key you purchased it should work fine. I am not at home, so I cannot send it to you, but I will gladly send you .97 as long as you have your key.
i have .97, i downloaded it the same night i paid for it.
cheers!
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
how do you know you're not on the e-mail list? as far as I know, no e-mail has been sent regarding .98 because it's still in testing. This has been covered several times in this thread. Seems like alot of people are skipping to the end to rant without reading a thing.
again this has been covered b4, when you pay for it in paypal you are taken to a page with your serial number and a link.
if you want .97 then change the URL (in the link) to .97, otherwise grab the test version of .98.
if you want .97 then change the URL (in the link) to .97, otherwise grab the test version of .98.
I am NOT posting this to complain, but I thought I'd include this to help out "Evo4Mad" with debugging.
When using the HP/TQ graphing function in version .98, EvoScan crashes with the following error:
*********************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at Dundas.Charting.WinControl.AxisScale.c()
at Dundas.Charting.WinControl.AxisScale.get_Crossing( )
at Dundas.Charting.WinControl.AxisScaleBreakStyle.c(A xisScaleSegmentCollection )
at Dundas.Charting.WinControl.AxisScaleBreakStyle.a(A xisScaleSegmentCollection )
at Dundas.Charting.WinControl.ChartAreaAxes.a()
at Dundas.Charting.WinControl.ChartAreaAxes.a(Boolean )
at Dundas.Charting.WinControl.ChartArea.ReCalc()
at EvoScan.frmChart.cmdCalcPower_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
*********************
I have verified that this error occurs on multiple computers/installations of EvoScan/log files, etc.
This may already be on this list of fixes when .98 is officially released, but I thought I'd try to help out any way I can.
Thanks
When using the HP/TQ graphing function in version .98, EvoScan crashes with the following error:
*********************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at Dundas.Charting.WinControl.AxisScale.c()
at Dundas.Charting.WinControl.AxisScale.get_Crossing( )
at Dundas.Charting.WinControl.AxisScaleBreakStyle.c(A xisScaleSegmentCollection )
at Dundas.Charting.WinControl.AxisScaleBreakStyle.a(A xisScaleSegmentCollection )
at Dundas.Charting.WinControl.ChartAreaAxes.a()
at Dundas.Charting.WinControl.ChartAreaAxes.a(Boolean )
at Dundas.Charting.WinControl.ChartArea.ReCalc()
at EvoScan.frmChart.cmdCalcPower_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
*********************
I have verified that this error occurs on multiple computers/installations of EvoScan/log files, etc.
This may already be on this list of fixes when .98 is officially released, but I thought I'd try to help out any way I can.
Thanks




