Re-tool the Aurora

[dstojkov]

Ugh, another idiot who doesnt undetstand how the engine works.

Are you speaking of yourself ?

[FunkOff]

Hi,


Actually aurora should have RateOfFire = 0,6 instead of 0,66

0,6 * 40 = 24 like other tank

0,66 * 40 = 26.4

regards

Ugh, another idiot who doesnt undetstand how the engine works.

Could you enlighten me? I would like to understand why we have to do all these gymnastics to get the aurora to work right.

I cba to type it out on my phone, later when i get home.

[IceDreamer]

Ugh, another idiot who doesnt undetstand how the engine works.

Are you speaking of yourself ?

He's talking to you. RateOfFire = 0.6 in the case of the Aurora gives it 23.53DPS, not 24.

1/0.6 = 1.666666666 Firing Interval >>> Rounded up to 1.7 (Engine works in 0.1s Ticks)
DPS = Damage/Firing Interval = 40/1.7 = 23.5294117 >>> Rounded to 23.53 (Engine rounds damage to 2DP)



OT: @PilOt - How low can you put the TurnRate without the responsiveness of the unit noticeably declining? Find out and put it to that

[dstojkov]

0,1 ticks mhh ....

Well i didn't pay attention to that my mystake then

still

1/0,66 = 1,5115151.... which rounded to the 0,1 ticks will in act be a 1,6 periode

so that 40 / 1,6 = 25 DPS

P.S : will have a better lock at this for my mods ....

[IceDreamer]

Current DPS is 26.67

1/0.66 = 1.51515151 Firing Interval >>> Rounded down to 1.5
DPS = Damage/Firing Interval = 40/1.5 = 26.666666666 >>> Rounded to 26.67


Don't worry about these mistakes, it took me two years and troubleshooting by DeadMG and Mithy (Supcom's two best ever mod coders) before I understood how DPS was calculated once you include racks, multiple muzzles, and various other rarely used quirks of the engine, and we now have nobody around with anything LIKE the coding expertise of those two.

[FunkOff]

Thank you for explaining, Shadow.

[dstojkov]

1/0.66 = 1.51515151 Firing Interval >>> Rounded down to 1.5

This is what I doubt ... the rounding up yes make sense ... actually don't even think there is a rounding process this is a simple test the like > or < so that this rounding down ... mhh ... not that I don't believe you but that sounds odd to me. I will make some test and see what really happens here

Will give some feedback when I will have finished my tests ... means this evening

[IceDreamer]

1/0.66 = 1.51515151 Firing Interval >>> Rounded down to 1.5

This is what I doubt ... the rounding up yes make sense ... actually don't even think there is a rounding process this is a simple test the like > or < so that this rounding down ... mhh ... not that I don't believe you but that sounds odd to me. I will make some test and see what really happens here

Will give some feedback when I will have finished my tests ... means this evening

It rounds down in this case. For a long time, people thought it only rounded up, as how can a game engine move backwards in time, or know to round something before it happens? However, Mithy investigated the phenomenon of RateOfFire set to 3 giving a real-time rate of fire of one shot every 0.3 seconds, not 0.4, which didn't tally with that theory. He tested by getting the engine to display a message every tick, slowing game-time down, then timing the shots.

After confirming, he and DeadMG investigated other units. I am certain any unit who's Firing Interval is in the .01 -> .33 range will have it rounded down to X, and I am 95% sure that the rounding is in fact bog-standard mathematical rounding, where anything less than the .5 is rounded down, and vice versa. The lua engine does actually support the math function 'Round', after all, and the suspicion is that the engine itself has this command written in.

[Ze_PilOt]

I've found a better fix for the handling, the turn rate is reverted to 120. Also added a nice subtle wobble effect.

[dstojkov]

it tested it

1,45 to 1.54 wil be rounded to 1,5 ( rof from 0,66 to 0,68 )

The rounding has taken place before the thread start ...

the 0,1 is also used for beam ...make sense