Bullet Trajectory?

The game's gravity pulls the bullet downward, so I'd imagine it is parabolic.

The bullet is also dramatically deaccelerated by air resistance.

[NL]Freshmeat said:

Thanks for the answer.

I am deeply impressed.

Honestly, I thought that the sheer amount of calculations for this kind of realism would kill off any processor, esp. with lots of full-auto fire.

Demosthanese, are you implying that the game uses a non-analytic approach? Or is it more along

y=-a*t^2 (gravity)
x= b*ln t (resistance)

For a fast approximation?

-Freshmeat

Click to expand...

The resistance is something the team has little control over, as it is a product
of the level in the variable of terminal velocity. Any object going faster than
what the level assigns as terminal velocity is slown down gradually (apparently
why the 40mms don't behave properly). Gravity affects the bullets in the
same way it affects the player or a flak shell in Vanilla UT.

I doubt that it uses the distance formula. I'd imagine that every unit of time,
the game subtracts or adds to the velocity of the pawn, and the position is
altered based on the speed.

Want another way to see it?

"Slow Bullets" and the recent "all tracer" mute. Then go to the range.

Meplat-

Demosthanese said:

The resistance is something the team has little control over, as it is a product
of the level in the variable of terminal velocity. Any object going faster than
what the level assigns as terminal velocity is slown down gradually (apparently
why the 40mms don't behave properly). Gravity affects the bullets in the
same way it affects the player or a flak shell in Vanilla UT.

I doubt that it uses the distance formula. I'd imagine that every unit of time,
the game subtracts or adds to the velocity of the pawn, and the position is
altered based on the speed.

Click to expand...

Wrong and wrong. (40mm's are affected by the bBounce variable and will not display that behavior if it is set to false)

The ballistics are using a minor variation of the RAv2 ballistics, which work as follows:

Air resistance acceleration = negative constant per bullet * velocity * (another per bullet resistance constant ^ distance) * velocity

This is recalculated basically every .02 of a second. It is basically a changing air resistance based on distance and velocity, which models an approximation of the bullet flight pattern (speed, distance, ToF) that I have calculated beforehand. Acceleration decreases as the bullet slows down, and the rest of the calculation of the bullet (velocity, position) is left to the MUCH faster engine native code.

It is quite accurate and velocity is even added back to correct the small amounts of error that occur between the .02 second interval. Air resistance has a massive effect on ballistics (approximately half a 5.56's energy is lost in the first 200m) and this models it quite well.

On top of this manual gravity acceleration is added, not UT's gravity. Only disadvantage of this is that it will not be affected by lowgrav areas or mutators.

The code is executed seperately on client and server, meaning no information needed to be sent between them during the flight, only the initial characteristics. Like always, server has final say in case of a discrepancy.

Are this ballistics (like those in RA) on 2.9? I tried the robar on the 500 long shooting range and it seems that the bullet lands where the crosshair is (more or less)

That's because the robar is zeroed at 500m (or close to it believe, am at work and can't check).

Shoot at at 100m and see if it's high. Shoot it at 700m and see if it's low.

Hmm... So what's the robar's max height and at what range?
And at what other range except 500m does it hit with 0 offset? As in M4A1 zeroes to 250m hits exactly where u aim at 250m AND somewhere around 45-50m (don't remember, I think it's 48m).