Difference between revisions of "Talk:Long Integer"
Jump to navigation
Jump to search
imported>DragoonWraith (this is on an object, not a global or quest) |
imported>Timeslip (does oblivion store integers as floats?) |
||
Line 10: | Line 10: | ||
1017072517</pre> | 1017072517</pre> | ||
As you can see, when I add the last number in, it changes the last digit for no apparent reason. It does not change it consistently, so I can't just account for the change. I assume this is due to memory issues, but the maximum number I reach is 1326262626 and the minimum is -1326262626, which is well within the limitations written on this page. What gives? | As you can see, when I add the last number in, it changes the last digit for no apparent reason. It does not change it consistently, so I can't just account for the change. I assume this is due to memory issues, but the maximum number I reach is 1326262626 and the minimum is -1326262626, which is well within the limitations written on this page. What gives? | ||
:I know that in esm/esp/ess files ''all'' variables and gmst's are stored as floats, even if they're defined as integers. Maybe it stores integer script variables as floats in game too, and you're seeing the normal rounding errors suffered by floats? [[User:Timeslip|Timeslip]] 15:10, 15 August 2006 (EDT) |
Revision as of 14:10, 15 August 2006
Dragoon Wraith TALK 12:45, 15 August 2006 (EDT): I'm having issues with longs that are above 10^8 (or less than -10^8). They are longs on an object, and so these numbers should work. My math looks something like this:
13 + 2500 2513 + 70000 72513 + 17000000 17072513 +1000000000 1017072517
As you can see, when I add the last number in, it changes the last digit for no apparent reason. It does not change it consistently, so I can't just account for the change. I assume this is due to memory issues, but the maximum number I reach is 1326262626 and the minimum is -1326262626, which is well within the limitations written on this page. What gives?
- I know that in esm/esp/ess files all variables and gmst's are stored as floats, even if they're defined as integers. Maybe it stores integer script variables as floats in game too, and you're seeing the normal rounding errors suffered by floats? Timeslip 15:10, 15 August 2006 (EDT)