Odd shouldn't be necessary. Oh well. The best way to do this will be to actually uninstall the newest version, install the old one and then re-install the newest version. Don't want to attempt to register the old 1.1.xxxx files over the new ones cause that will cause problems going the other way.

 

Has anyone seen any issues with the "speed" column? I have a peak speak of 178 lol.. I may have hit 100 tops.

 

Apparently there are assembly references to DLL's specific to 1.1, files which don't exist in the 2.0 I noticed this while working on something else in my own code on another project.. When I looked at this one, it had the same dependency.

 

For a USDM EVO, you need to convert kph to mph. The data file looks like he labeled it as mph, but it's not correct.

 

Speed is definately off. Says I hit 138mph and I didnt even shift into 4th gear :/

 

Also the octane number is fubar from what I logged last night.. Stays at 100 and doesnt move. No more than 2 knock counts doing a 1-3rd pull multiple times. With 0.80 is reads 255.

 

The octane number is still working fine, but it's now be corrected to a 0-100 scale (think of it as a percentage if you want). It's unitless anyway. You can see it in the data.xml file: octane = "100x/255".

 

There are issues between cars in different markets. On a car from anywhere in the world the scaling is 2x with the unit km/h except for cars which have km/h to mph converters where the unit then becomes mph. The latter applies to the officially imported UK market cars.

 

I think the speed is off because it thinks your in two gears higher

 

The scaling in the speed definition in v0.9 is not for mph (even though its labeled as such). Change ...Eval="2x"... to ...Eval="1.24x"...

 

Ty!

 

thanks fred

 

np.

 

Fair enough.

 

Has everyone received their email link to download v0.9? Am I the only one still waiting?