Official 2 byte thread!
well there is no 5.10 for 88590013 
but in 88590015 the MUT (40 or 41) is already programmed with 1byte load, u just need a recent version of evoscan and it will *just work*

but in 88590015 the MUT (40 or 41) is already programmed with 1byte load, u just need a recent version of evoscan and it will *just work*
So we just buy evoscan and with your version 5.10 of the 88590015 rom, the load we be accurately logged? When does one have to change the 1byte mod number of 1.2 in the version 5.10 of the 88590015 rom?
yeah:
- run v5.10 or above of my mods
- get evoscan
- if evoscan hasn't already got the 1byte load entry then add it
- log accurately
the 1.2 needs to match it both evoscan formula and in the rom, it just is a multiplication factor that limits the maxload evoscan will see ie:
1.0 = 255 max load
1.1 = 280 mad load
1.2 = 306 max load
1.3 = 331 max load
1.2 should be good enough for 99% of users
- run v5.10 or above of my mods
- get evoscan
- if evoscan hasn't already got the 1byte load entry then add it
- log accurately

the 1.2 needs to match it both evoscan formula and in the rom, it just is a multiplication factor that limits the maxload evoscan will see ie:
1.0 = 255 max load
1.1 = 280 mad load
1.2 = 306 max load
1.3 = 331 max load
1.2 should be good enough for 99% of users
Somebody please confirmm the right codes for 1 bite and 2bytes mut table for 88840017and for 88840013 also.
V6 seems to have others values than al\lupo confirm at the start pages of this thred.
Give me please correct values for stock rom for both rom versions
Thanks
V6 seems to have others values than al\lupo confirm at the start pages of this thred.
Give me please correct values for stock rom for both rom versions
Thanks
Last edited by Danieln; Apr 17, 2009 at 09:38 AM. Reason: 88840013 and 88840017



