MegaLogViewer 2.81 update doesnt work??
Thread Starter
Junior Member
Joined: May 2007
Posts: 220
Total Cats: 0
From: Mountain View, CA
MegaLogViewer 2.81 update doesnt work??
I went to open MegaLogViewer just now and it prompted me to update, so i did. Now it says "fatal exception ocurred. program will exit". Is this happeneing to anyone else? How do I fix it DIY?
Reply
0
0
Any way to disable that message every time it starts? I just don't feel like updating, for reasons like this. What I have now works fine, and if I hear about a cool new feature in an update I'll go find the update myself.
Reply
0
0
Reply
0
0
http://www.msextra.com/viewtopic.php?t=26499
Reply
0
0
too lazy to read but other than that msg trying to get you to register are there any improvements in the software?
i don't like the fact that i can no longer use Ctrl O to open a file. It's a bitch to move that cursor around while driving.
i don't like the fact that i can no longer use Ctrl O to open a file. It's a bitch to move that cursor around while driving.
Reply
0
0
Added built in help files and viewer.
VE Analyze now has adjustable cell change resistance setting.
plus some background stuff.
Where in 2.80 from a feature stand point it got help and a new advanced VE Analyze setting, more happened under the covers. I have been migrating everything over to lightweight components, from peered components. This is two things for integration with the new tuning app, but also for faster startup times and smaller memory footprint. The problem is, peered components and lightweight components sometimes don't play well together. So in 2.81, everything will be based on a lightweight Component. It is all looking good right now, so I just need to tie up a few loose ends and TEST this time.
VE Analyze now has adjustable cell change resistance setting.
plus some background stuff.
Where in 2.80 from a feature stand point it got help and a new advanced VE Analyze setting, more happened under the covers. I have been migrating everything over to lightweight components, from peered components. This is two things for integration with the new tuning app, but also for faster startup times and smaller memory footprint. The problem is, peered components and lightweight components sometimes don't play well together. So in 2.81, everything will be based on a lightweight Component. It is all looking good right now, so I just need to tie up a few loose ends and TEST this time.
also MLV is now classified as Shareware. it's $10, but considering how easy this guy has made it to tune and the effort he's put in, it's worth it.
Reply
0
0
Agreed, it's well worth it-- Phil busts his tail and has made one of the best datalogging and VE tweaking apps available for any EMS and he's not stopping there, it's going to go alot further I think....
__________________
Jerry a.k.a. 'FoundSoul'
DIYAutoTune.com
'91 Miata BEGi S3 GT2560 w/ MSPNP - 14.1psi - 253whp, 232wtq
'95 Miata n/a
A few other cars....
Jerry a.k.a. 'FoundSoul'
DIYAutoTune.com
'91 Miata BEGi S3 GT2560 w/ MSPNP - 14.1psi - 253whp, 232wtq
'95 Miata n/a
A few other cars....
Reply
0
0
I don't know about you guys but I can't ever get MLV to tune my fuel VE worth a crap it also destroys my table no matter how long the datalog is or how much i filter out.
Reply
0
0
it works brilliant for me. I need to do a tad of manual smoothing afterwards, but nothing major. If anything the smoothing just makes the graph look nicer, and not a lot else
Reply
0
0
I have good afr targets setup, it still looks like crap, it makes cells sometimes dangerously lean, others too rich, i'll have cells within 1-2 ve units apart and it will adjust them so that two cells next to each other will go from 65-78 between two cells.
Reply
0
0
Jim
Reply
0
0
That's hte interesting part of it all. I leave all inrichments turned off when attempting to the fuel map. Maybe I need to focus my datalogs on certain parts of the map. I'll keep messing with it all i suppose.
Do you turn EGO off?
Do you turn EGO off?
Reply
0
0
Actually, the author has noted that the VE analyzer DOESN'T actually need the enrichments and corrections turned off. The correction/enrichment levels are in the log, so they are compensated/accounted for in the analysis.
Reply
0
0
