Vinifera7
29.04.2008, 18:48:51
I am severely confused as to what this flag actually does.
The entry from the Guide is rather vague and confusing.
And the explanation on the Ammo page seems to be wrong.
I have never seen more than one ammo pip reload at once, so this is clearly not true (feel free to show me otherwise).
Now for the results of my testing, which I cannot make heads or tails of.
This is on a vehicle by the way, so it uses automatic reload logic. I have never gotten manual reload to work for vehicles (again, correct me if i am wrong).
InitialAmmo seems to specify the starting ammo + 1. So if InitialAmmo=0, the vehicle will start with 1 ammo pip.
Then there seem to be two special values:
If InitialAmmo=-1, the vehicle will start with full ammo.
Furthermore, if InitialAmmo=-2, it will start with empty ammo.
EmptyReload works just as expected. It takes exactly 100 frames for the first ammo pip to reload when empty.
After that, each of the next 4 ammo pips (filling up the first pip wrap set) takes 50 frames each to reload, as expected.
The next 5 ammo pips (filling up the second pip wrap set) take 70 frames each to reload. So it would seem as if ReloadIncrement is added to Reload on the second pip wrap set.
But here's where it gets wacky. The next 5 ammo pips (filling up the third pip wrap set) take 130 frames each to reload. Where the heck did 130 come from?
On the final 5 ammo pips (the last pip wrap set) each one takes 230 frames each to reload. Again, I have no idea where 230 came from.
Hopefully someone can make sense of this.
The entry from the Guide is rather vague and confusing.
Quote:This can be used to slow down or speed up the rate of this units automatic reloading (instead of being instantaneous). This should be set to the percentage amount to add at every reload increment (which can be calculated by multiplying the units Ammo= value by its PipWrap= value).
And the explanation on the Ammo page seems to be wrong.
Quote:ReloadIncrement, which controls how much ammo should be reloaded, in percent of maximum
I have never seen more than one ammo pip reload at once, so this is clearly not true (feel free to show me otherwise).
Now for the results of my testing, which I cannot make heads or tails of.
This is on a vehicle by the way, so it uses automatic reload logic. I have never gotten manual reload to work for vehicles (again, correct me if i am wrong).
Code:
PipScale=Ammo
PipWrap=5
Ammo=20
InitialAmmo=0
Reload=50
EmptyReload=100
ReloadIncrement=20InitialAmmo seems to specify the starting ammo + 1. So if InitialAmmo=0, the vehicle will start with 1 ammo pip.
Then there seem to be two special values:
If InitialAmmo=-1, the vehicle will start with full ammo.
Furthermore, if InitialAmmo=-2, it will start with empty ammo.
EmptyReload works just as expected. It takes exactly 100 frames for the first ammo pip to reload when empty.
After that, each of the next 4 ammo pips (filling up the first pip wrap set) takes 50 frames each to reload, as expected.
The next 5 ammo pips (filling up the second pip wrap set) take 70 frames each to reload. So it would seem as if ReloadIncrement is added to Reload on the second pip wrap set.
But here's where it gets wacky. The next 5 ammo pips (filling up the third pip wrap set) take 130 frames each to reload. Where the heck did 130 come from?
On the final 5 ammo pips (the last pip wrap set) each one takes 230 frames each to reload. Again, I have no idea where 230 came from.
Hopefully someone can make sense of this.
![[Image: alexstand1.gif]](http://www.eitservices.com/andrew/img/alexstand1.gif)
gordon-creAtive
![[Image: osen2o7mpmm4jg1fs0.jpg]](http://img364.imageshack.us/img364/4989/osen2o7mpmm4jg1fs0.jpg)
DCoder