Ive already solved the my issue with this but I figured I'd give people a heads up cause I didn't see any posts on the matter. Now whether this problem is rooted in the math itself or just the specific purpose we were using it for I'm not sure. It did cause us a slight head ache so I figured Id post to spare others the pain. Here is a quick summary of what occurred:
Hero used ability which would kill the target unit and then add the remaining amount of life the target unit had on it before it was killed and add that total to the hero.
Game would crash right after.
The ability was designed mostly in triggers mainly the amount of life given to the hero unit. Now at first we thought the problem was the trigger doing the math for the life gain, however. As repeated testing and the debugger reveled with actually something different but related. Below follows what was actually causing the crash.
Previous to 1.5 in the trigger editor when you could select the precision of the decimal and the default was "Any Precision" which for all intents and purposes didn't appear to work. Now in 1.5 it is working and it was causing us a huge problem with our Custom UI. We had developed a custom stat bar for tracking life, shields, and energy. which had to do some simple math to calculate the change in the colored bar and the actual displayed number of life. My assumption is, now that Any Precision is actually working, a number would try and get added or subtracted to our stats bar number (IE not the bar itself but the numerical value displayed of amount of life) similar to 10/3 or any other infinite series and for some reason trying to display that number would cause the game to crash. I'm pretty sure it was the colored bar equation because we converted to integers.
The lesson I suppose I will take away from this is don't use the default values but there might be cases were people want to use the Any Precision so be forewarned.
EDIT: if anyone has trouble understanding what the hell I'm talking about I'll see if I can add some screenshots.
Ive already solved the my issue with this but I figured I'd give people a heads up cause I didn't see any posts on the matter. Now whether this problem is rooted in the math itself or just the specific purpose we were using it for I'm not sure. It did cause us a slight head ache so I figured Id post to spare others the pain. Here is a quick summary of what occurred:
Hero used ability which would kill the target unit and then add the remaining amount of life the target unit had on it before it was killed and add that total to the hero.
Game would crash right after.
The ability was designed mostly in triggers mainly the amount of life given to the hero unit. Now at first we thought the problem was the trigger doing the math for the life gain, however. As repeated testing and the debugger reveled with actually something different but related. Below follows what was actually causing the crash.
Previous to 1.5 in the trigger editor when you could select the precision of the decimal and the default was "Any Precision" which for all intents and purposes didn't appear to work. Now in 1.5 it is working and it was causing us a huge problem with our Custom UI. We had developed a custom stat bar for tracking life, shields, and energy. which had to do some simple math to calculate the change in the colored bar and the actual displayed number of life. My assumption is, now that Any Precision is actually working, a number would try and get added or subtracted to our stats bar number (IE not the bar itself but the numerical value displayed of amount of life) similar to 10/3 or any other infinite series and for some reason trying to display that number would cause the game to crash. I'm pretty sure it was the colored bar equation because we converted to integers.
The lesson I suppose I will take away from this is don't use the default values but there might be cases were people want to use the Any Precision so be forewarned.
EDIT: if anyone has trouble understanding what the hell I'm talking about I'll see if I can add some screenshots.