Please, can someone explain this screen shot? It is paused on the state following the state shown, with that subsequent state selected in the debug log window. HitObjScale and OwnScale are not changed in any way after the action shown. EvadeDistance is not changed in any way either. (The Float Operator action immediately following the offending action, which you can see the top of, divides EvadeDistance by another value and stores it in a different variable entirely.) Debug flow is on.
Foolishly attempting to think logically, I disabled all the actions following this offending action, and miraculously it showed the correct answer: 2.6... Encouraged, I re-enabled one action at a time, until - heart sinking - I found myself with all of them back on again and the correct answer still showing: 2.6... Angry, uncertain and paranoid now, I reran the scene with all the actions still checked: back it was to 1.6...
I need to be able to trust the damn thing to add numbers correctly. Right now, I am just about ready to sandpaper Unity and Playmaker from drive and brain, kiss goodnight to the Cheshire Cat and run away to sea.