Official Soldat Forums
Soldat Talk => Need Help? Report Bugs! => Topic started by: Mexer on May 06, 2010, 02:49:53 pm
-
(http://img188.imageshack.us/img188/3711/16195135.jpg)
Happens when I start soldat right at the welcome screen.
As far as I know, 2426997368 IS a valid integer value. What's his problem ?
-
Not that it fixes your problem, but integer is up to 2147483647, so 2426997368 is not a valid integer value.
try rebooting PC.
-
yeah... you gotta reboot to fix this one, happens every now and then.... and it really sucks -.-
(I'm not sure if it's because of the computers run time... since you can convert time into ticks of computers run time... however, the ticks should restart as it reaches the maximum value)
-
Can't be time, Major, if my calculations are correct. You'd have to have the process running for 414 days before that would occur... anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
Although, your guess is as good as mine (mine being a color value somewhere being read into the game is too big).
-
Can't be time, Major, if my calculations are correct. You'd have to have the process running for 414 days before that would occur... anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
Although, your guess is as good as mine (mine being a color value somewhere being read into the game is too big).
It could be the windows timer which is in milliseconds from when you started the computer and then its more lik 24 days of uptime to reach that.
-
Can't be time, Major, if my calculations are correct. You'd have to have the process running for 414 days before that would occur... anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
Although, your guess is as good as mine (mine being a color value somewhere being read into the game is too big).
It could be the windows timer which is in milliseconds from when you started the computer and then its more lik 24 days of uptime to reach that.
Who would keep running system for over 24 days? Probably only hosting companies.
-
Can't be time, Major, if my calculations are correct. You'd have to have the process running for 414 days before that would occur... anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
Although, your guess is as good as mine (mine being a color value somewhere being read into the game is too big).
It could be the windows timer which is in milliseconds from when you started the computer and then its more lik 24 days of uptime to reach that.
Who would keep running system for over 24 days? Probably only hosting companies.
this laptop has been up for 2 months.
-
Can't be time, Major, if my calculations are correct. You'd have to have the process running for 414 days before that would occur... anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
Although, your guess is as good as mine (mine being a color value somewhere being read into the game is too big).
It could be the windows timer which is in milliseconds from when you started the computer and then its more lik 24 days of uptime to reach that.
Who would keep running system for over 24 days? Probably only hosting companies.
this laptop has been up for 2 months.
Ok, I'm taking then my words back. :)
-
Who would keep running system for over 24 days? Probably only hosting companies.
Um, I did Lol
-
Can't be time, Major, if my calculations are correct. You'd have to have the process running for 414 days before that would occur... anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
Although, your guess is as good as mine (mine being a color value somewhere being read into the game is too big).
It could be the windows timer which is in milliseconds from when you started the computer and then its more lik 24 days of uptime to reach that (which was 24 days I think..).
ya, I remember I calculated how long the computer could be running before the ticks goes above the maximum integer value.
it might even have been because of that soldat error (cuz at that time I ussualy had the computer running untill windows crashed, poweroutage, or having bad headaches).
-
anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
I feel the need to highlight this point again in light of recent posts.
:P
-
anyway, it would say 2147483648 is an invalid Integer if that was the case (the problem would occur just as you go over).
I feel the need to highlight this point again in light of recent posts.
:P
integers ranges from -2147483648 to 2147483647
nvm, I think I missunderstood that statement ;o
-
You did. I was saying that if it was a time variable that was getting too big, you'd get the error occurring just as it overflows, not 2 million units afterwards.