RomRaider

Was editing some XML and deliberately put in a bogus expression in the real expression field. When opening a map, RomRaider did not alert me to that the real and byte calculations conflict. I know I've seen that error message before, so it was working at one point in time. Tried a different XML file (Braden's 5-23) and put in an obvious error, but still did not recognize it. Also made sure that the error checking was selected in settings. Also tried older versions 2.73, 2.72 with the same result.

I think I figured out the problem. It looks like the expression checker takes the first z value on the ROM in a particular table and uses that value to check the expression and reverse expression's validity. The problem is, if the first value is zero then it nevers catches the problem, depending on the formula, because the end result is zero for both fields. For example, the I noticed this with the ignition correction table. I can put whatever I want in the real expression field and it doesn't pick it up.

I'll get this fixed in the next version.

Ok, the validation wasn't getting called on 3D tables (but it was in their axiis). Fixed. I also made some changes to the validation method for floats which could potentially cause some problems but I haven't run in to any. This will be in the next release, I'll do as much testing as I can before then.

Edit: Forgot to mention -- all it actually does is plug in an arbitrary value (it's 5) and calculate back and forth to make sure the result is 5. And now, with floats, it's actually making sure the result is within .001 of 5. There's where the potential problem could come in.

Great. If the float thing gets to difficult, I would just leave it out as most of the values are straight values from the ECU, except where we want to convert psi or engine load and it is usually a simple equation.