That makes sense but imagine the logic behind trying to find runs in that ...

 

thats why I thought the TPS filter was there, to sort out anything <99%

 

Easy. Sort by TPS, and then by Time. All of the full throttle runs will be at one end of the log file, so you delete everything else, and then you can separate each run out from there. Unless that somehow screws up the formatting of the csv that I'm not aware of.

 

I just start evoscan, do a pull then stop evoscan. 1 WOT per log.

 

well each run is read from one file ... if I did that Id have to reserve colors for infinite runs in 6 files. So each file could technically over run my color buffer. I have to hand pick colors to graph by because other wise it looks like trash. Plus the logic is a little more hairy than that because Ive seen cars come off a few points on the TPS and still be at WOT. Just an oddity that doesnt allow me to just chop the file up on deviation from max on TPS. Its just a logistics nightmare that just doesnt seem worth it at this point in time.

If that makes no sense I blame it on the 3 hours of sleep and clinicals today ...

 

Same here. I do take longer logs for looking at cruise and part throttle stuff, but I don't try to load them in this program.

 

indeed, there's some responsibility on the end user to make useful logs. the program is likely not ever going to be able to account for every type of log.

"I've been idling for hours and ran that log through but can't find the horsepower"

 

Thank you mellon. This program already holds your hand a lot of the way ... but there are just some things it cant or wont handle due to purposeful design limitations.

 

I am having a problem getting VDR to plot HP/TQ properly for OpenPort standalone logs. I have attached my two logs, one from OpenPort and one from Evoscan both logging 3rd gear. As you can see from the attached graph VDR is puking on the HP/TQ calculations from what it appears to be due to the time column in the OpenPort log. If I overlay the <LogEntrySeconds> from the Evoscan log over <time> in the OpenPort log it all looks great, even though they both span ~8 seconds total per log. Thanks in advance!

Here are the files and graph, vBulletin wouldn't let me link them again.

https://www.evolutionm.net/forums/8681406-post93.html

 

Wont let me open the logs.zip file ... send em again.

 

great program, easy to use, I was having an issue loading up, but it seems ok after I did the repair option

 

Does it just not open or does it open but is minmized in your task bar? Read the solution above for this bug. I have this fixed in 1.0.7 but its not ready for release.

 

Well, I knew it had to be something simple. I thought I was running the latest version of VDR at home but apparently I wasn't. I loaded up my logs at work to send over to you and they looked fine! I know, I know, but thanks for the response Brad!

 

Keep in mind this is way different than VDR. Written by two diff people. This is Virtual Dyno (VD).

Glad you got your issue fixed. 1.0.7 made progress today i made it past my hurdle. Ill keep yall posted.

 

Sorry about the VDR. Anyhow, I got home and updated my VD and it still didn't work for like 30 minutes and then all of a sudden it kicked in and started plotting correctly.