[Krackers87]

before i reinstalled windows i was having that bug on XP, the button was on the keyboard, tried switching it, no avail.

[bottomfan]

A test exe perhaps?

[Beowulf]

Impressive!

[penguin]

Originally posted by Gravaton
tmp is an int, and the problem SEEMS to be that, on my system, at the end of this block eax is equal to a number around 33,000,000.  This, when moved into tmp (which is a regular int) gets taken to be a negative number of about -9,000,000.  And at that point everyone gets all sad.  The solution I've found is to turn tmp into an unsigned int (as there's no way any of the system timer functions would EVER be returning a value less then zero according to MSDN specs), and also turn the "now" variable (in code/ship/afterburner.cpp line ) for the afterburner into an unsigned int as well.  This worked.

Are you sure you didn't drop a couple decimal places?  Why would 33M roll over to -9M ?  I'm confused.  If it was 3300M rolling over to -900M I would understand:

Code: [Select]

3,300,000,000 (unsigned) = 0xc4b20100
 -900,000,000 (signed)   = 0xca5b1700Nice catch, in any case  Now check it to make sure it doesn't break anything else  

For example, see if any timing-related sexps get hosed, make sure beams don't stay on for 5 minutes (ow), make sure the HUD clock seems reasonable...

[Gravaton]

Hmm, you're right, the numbers do seem a little off.  Sorry I haven't been exactly around, school re-started and ate my soul for a bit  I'll take a look at things tonight and get some more exact figures.

[Kazan]

penguin: he rounded ... but the bug totally makes sense

i wish i would have been reading this thread a long time ago -- the moment i noticed a time_get_milleseconds() i figured it was a sign problem

[penguin]

Originally posted by Kazan
penguin: he rounded ... but the bug totally makes sense

Heh, the rounding I get, it was the two order of magnitude (33M vs 3.3G) that puzzled me.  A number like 33M would be the same, regardless of whether it's signed or not.

To pick a nice round (hex) number:
0xc800 0000 == (unsigned)  3,355,443,200 == (signed) -939,524,096.

And you're right -- makes sense; signed vs. unsigned is a major PITA.

[Rga_Noris]

erm... just out of curiosity, how goes work on this? This problem seems like a big one to me, especially because I suffer from it. I'm a WinXp Pro user, and this is greatly cramping my FS2ing...

--Rga

[karajorma]

Have you tried the compatability options fix from my FAQ? It never really worked well for Win2k users but it solved the problem for most XP people.

[Rga_Noris]

Yeup. Still all buggered up.

--Rga

[Goober5000]

Wait for someone to post a build.  I think Phreak put this in recently, but we have to check if it's correct.

[Taristin]

I'm win2k and have never _ever_ had a problem with my afterburners. Hell, I use them instead of my primary thrusters.

[karajorma]

Originally posted by Raa Tor'h
I'm win2k and have never _ever_ had a problem with my afterburners. Hell, I use them instead of my primary thrusters.

If you're on about my above comment I was talking about the fix never solving the problem on 2K not that everyone on 2K has the problem.

[Admiral Nelson]

Is there any chance of this making it into the 3.6 build???

I don't think that there has been a build posted with this fix in place?

PLEASE PLEASE PLEASE??

[Kazan]

it's already in.....

[Bobboau]

look at any of the recent builds in the recent build forum, I think they should all have it in.

[Admiral Nelson]

Yes, this was my moistake, I had an older build selected in the launcher. The afterburner bug is indeed fixed in the march 5th build.  

Thanks very much!

[Darkhill]

-nevermind-

[Bobboau]

there is a table defind max AB speed wich generaly is well above the max cruiseing speed (though Silent Threat showed that wasn't required (Loki))

[Darkhill]

Once again, I should look around more before I post.  The craft I was using had no afterburners installed.  I took the afterburner key increasing my speed as the burners actually working.  Beat me with a stupid stick.