Nistune Forums

Hello ..

I have recorded a log, but when I replay it the TP-Load-Graph is either flat or out of sync with what actually happened (see load 95 in picture). - any ideas?

All sorts of weird log replays happen.

as a habit the first thing I do when replaying them is;
1. close log record/player first
2. reopen it,
3. browse for the file (even if its listed as the file at the start when you fire up log player and then veiw it.

if you mess with it via playing it faster, or slower or move the redline marker around too much,
scroll back and forth or simply play it twice, you get different results and it all becomes a mess.

Sometimes in some strange world you even get remnants of previous runs attached to consecutive log files.
I wish I could replicate as Matt would love this. The weird thing is that it disappears after a restart of log player or Nistune.

I notice this when logging a drag car which only has two events in it. Burnout and the 1/4run. often when simply reviewing the log file without reloading it the graphs are screwy and mess with my knowledge of what really happened.
I get two burnouts or two runs. The time seems off also. I rub my eyes then rememeber to restart log player and start again. Seems ok but a little confidence is lost in the logs accuracy.

Hello bachig24u,

Thanks for the reply!

Yeah, it's a bit odd that I get a TP-Load of 95 whereas the graph for TP-Load remains flat.

I think the log is a very very useful feature but maybe the log-software needs a rewrite.
The whole navigation in the log-player is a bit clumsy anyhow.
It must be complicated to code this ...

I hope that Matt will find a solution to the issue.

Maybe it would be possible to use Nistune's logs with LogWorks in a way?
http://www.innovatemotorsports.com/support.php


What car do you run on the 1/4?

Cheers from London,
Andrew

I've done a lot of work on the navigation part of the log player last week. The trick is making the scroll bar line up with the actual log bar. Otherwise things get out of wack and its messy

So when you move the scroll bar it syncs with the log (and then back with the scroll bar if the log is paged forward/backwards). Moving the red line also adjusts the point on the scroll bar which makes is even more complicated.

Closing and reopening the log player reinitialises the class and all its variables. It may be necessary for me to reset some of these when opening the new log. I'll try those out and see what happens with opening/closing multiple log files.

I wont be rewriting the class but just trying to improve it at this stage so its more usable

Thanks Matt,

That would be helpful since I the log is a very useful tool.

One feature I'd very much like to have would be to go to the peak (maximum) of a logged item.

For example if you have a larger log you would be able to jump to the TP-Max of your session.
(That's what I often do)

Or how about some statistics? I mean show min and max for all logged items?
(would be very useful as well)

Torque wrote:Hello bachig24u,

Thanks for the reply!

Yeah, it's a bit odd that I get a TP-Load of 95 whereas the graph for TP-Load remains flat.

I think the log is a very very useful feature but maybe the log-software needs a rewrite.
The whole navigation in the log-player is a bit clumsy anyhow.
It must be complicated to code this ...

I hope that Matt will find a solution to the issue.

Maybe it would be possible to use Nistune's logs with LogWorks in a way?
http://www.innovatemotorsports.com/support.php


What car do you run on the 1/4?

Cheers from London,
Andrew

Yeah, I've never been able to get my head around programming at great depths so I'm glad to be able to let some one know who does!! Mr Matt Nistune.
I'm usually running Holden Commodore/Calais Turbo '88' VL' Series. RB30 6cyl Engines. We had some great success with Nistune that can really embarrass those who use Motec/Haltec/Microtec etc. We have drivability those cars can only dream of in less than a quarter of the time.