A really funky ballistic computer glitch...

[Hell_Hound]

Playing Dewman's Attack/Defend scenario the other night, one of my M1s started behaving oddly.

In an M1 I hadn't crewed previously (it was at full ammo) I spotted a Leopard in a treeline, stationary, about 2500m away (estimated range based on target size).

I lased, fired, round went so far overhead I couldn't even see it.

Huh. I must have selected HEAT. [Tap Insert several times, Sabot confirmation message comes up]

Fire on same lay. Round goes way overhead.

Well, I'm indexed properly; must be a lasing issue, even though the displayed range (2280, I think it was) looks plausible. Switch to daysight. No dust, no smoke, target 70% visible. Select first-return, aim at the top half of the target to make sure I'm not catching the hill crest, re-lase. Range changes insignificantly (20m?)

Fire. Round goes way overhead.

Tank notices me, engages, I duck into a ditch. Tank rushes me. Hoping that the buggy range-finding situation will resolve itself, I pop up, lase, fire. Round goes way overhead.

I don't know what made me think of this, but I duck into the ditch, manually enter half the range the LRF just found, pop up (aim a little low because the Leo has closed some distance since my lase)...

fire. Target. Cease fire.

I went to another tank for a while, came back to this one, and it kept happening. On another target at about 2.5km, and a third at 800m, I lased, a correct-looking range was indicated but the gun lay was for twice the correct range. Manually entering half the indicated range would result in correct gun lay and a hit.

Shifting a number one bit to the left effectively doubles the number; was some bizarre data-storage error causing this? Or was it a connection problem? (I have trouble believing it's connection, since my connect was generally very good and the problem persisted over a 10-minute period).

:shock:

[NEpi]

i guess someone fucked up with his boresighting...

[Hell_Hound]

Yeah, just a teeny bit. :roll:

[12Alfa]

your ammo was made by the lowest bidder, and i think it was from Que, made by Newifie's, on a friday afternoon, heheheh

[Ssnake]

It certainly reads like a bug, and I alerted the One In The Know.

[OddBall]

Did you check the GAS sight to see if it was pointing to the sky or aligned with the GPS? Dunno if my head is all screwed up but I think this was reported long time ago and the response was "working as intended" or along those lines. It occurred only when you were on steep crest and gun didn't have enough "-" elevation. I could be on drugs tho, so don't shoot me if I'm wrong.

[dejawolf]

yes, check GAS as often as possible, since the main GPS usually screws up once in a while.

[Dewman]

Why am I thinking that if the gun can not lay on the target the computer will not let you pull the trigger ???
IE if GAS and Gun don't line up....

[OddBall]

Why am I thinking that if the gun can not lay on the target the computer will not let you pull the trigger ???
IE if GAS and Gun don't line up....

That's the way it should be, maybe the bug is that you can fire the gun even if it happens? :p

[JAVEHN]

i guess someone fucked up with his boresighting...

:shock:

The game is so realistic , that it's even simulates lazy / dumb gunners fucking with their borsighting on the morning ???

I knew i picked SteelBeasts for a reason ! :lol:

[NEpi]

the only problem is you can't beat the shit out of them for doing so.
you're the gunner too :shock:

[Ssnake]

It seems that the LRF found the correct range (based on your estimate) so somehow the superelevation was wrong. It would have been helpful if you would have switched to the GAS to see if the superlevation was, in fact, incorrect.

If anyone can reproduce the problem, that would be most helpful. Otherwise, I'm not sure what we can do about it :oops:


Shooting without proper alignment shouldn't be possible. However, the M1's fire control system accepts a deviation of a full mil between GPS and gun position (where it is just .25 mil in the Leo), if I remember it correctly. If that one mil was enough, this just might have been the reason.

[Hell_Hound]

I didn't think to check the GAS. :(

On the second target, I checked the range on the map (conveniently, it was almost exactly 2 grid squares due east) and the lased range agreed with that. The third target was inside 1000m (almost an inch wide in the 10x)...the sort of target I normally wouldn't bother lasing, but I was curious to see if the problem would persist. The LRF read 800m, and I still missed overhead by at least two target heights; 1-mil deviation should have caused a miss by no worse than 80cm at that range.

The first event was firing uphill, the second roughly level and the third pretty sharply downhill.

Considering this has happened once in my two and a half years of playing, it probably doesn't warrant more than a couple minutes of His attention. :) Still, I'll see if I can reproduce it.

[Bluewings]

Strangely enough , I remember I had that stuff once (didn't check the GAS) and as I switched to the coax the bullets were going waaay over the targets as well (a BMP and its troops) . I did not make any fuss as I thought it was or my mistake or a malfunction in the M1 .

Cheers . :3starSK:

[Hell_Hound]

And you had a good lase? (Not 0000, not flashing, no smoke in the daysight)?

[Lone*star49]

And you had a good lase? (Not 0000, not flashing, no smoke in the daysight)?
...

Time to jump in .. I too have had this happen and as I recall, only in online MP..

But same thing.. target 2 grids away.. 2000m lase, ammo indexed correctly, and yet shots are way over and past target.. (and no smoke..confirmed)

I am sure that this has happened both on a level BP, and on small hill as well.. and more than once.

Only way I overcame this problem was to manually put in shorter ranges.. but with loss of min 6 sabots.. before kill, or being killed.


LS :?

[Ssnake]

Hm. The ultimate help for us would be if someone found a reliable way to reproduce this kind of behavior. Still, if you notice or remember this thing, please write down all known circumstances, and post them here, please. Check the GAS. Switch to the TC position, and fire from there. Then let the computer gunner take over, and see what happens. The more we know, the better our chances to find the bug.

[Hell_Hound]

LS, was your event also in an M1?

LS, BW, do you remember anything about the scenario in which this happened?

My tank was completely undamaged (unless it took a Stab hit and recovered before I got there), I assume yours were as well.

[Poker]

Now I have an excuse for my poor gunnery ! Sweet !

[Lone*star49]

...

But same thing.. target 2 grids away.. 2000m lase, **ammo indexed correctly**, and yet shots are way over and past target.. (and no smoke..confirmed)


LS :?

...

HH, baby tanker is taking it's toll on your reading comprehension.. hehehe

**ammo indexed correctly** (human error) only happens in the loved M1.. LOL


And Confirm, that NO damage to any of my M1's when this happened..

Trying to remember sce's, but can tell you now for certain, online MP, min 3 vs 3 or bigger.



LS :wink:


PS.. was gonna list the problem under battle shock.. but revised it to "baby shock" :lol:

[Hell_Hound]

"Ammo indexed correctly" happens on the Leopard too, it's just the loader doing it instead of you. ;)

Ok, so 3/3 it's an undamaged M1.

Is it possible that your tank took a stab hit, and recovered prior to you taking control of the tank? If we can establish that one of these tanks absolutely, 100% certain, hadn't been hit, we can rule out errors in the component damage code.

[PS-SCUD]

I believe I had something funky like this happen to me at one point. I switched to emergency mode, then back to normal, and it fixed it. I'm not sure if my problem was exactly like yours, because I didn't spend time manually entering the range to test it (I didn't want to die lol).

[Lone*star49]

1.>"Ammo indexed correctly" happens on the Leopard too, it's just the loader doing it instead of you. ;)

2.> Ok, so 3/3 it's an undamaged M1.

3.> Is it possible that your tank took a stab hit, and recovered prior to you taking control of the tank?

**If we can establish that one of these tanks absolutely, 100% certain, hadn't been hit, we can rule out errors in the component damage code.
...

1. Yes, the no-error sweetness of the LEO in SB1.. :wink:

2. For sure.. undamaged M1 and On line MP 3 vs 3 or bigger game..

3. Nope: as I said, every time this happened, it took me at least 6 sabots, manual range reductions to either get kill, or be killed because of the lost eliment of suprise..

** Established from this tanker.. no doubts, everytime it happened, lase good..confirmed: by map and re-lasing with same return and correct ammo indexed (even when ammo and index matched, I entered Insert key for sabot again-no luck).. confirmed: no damage to tank, or prior and recovered from any damage, clean tanks, everytime, no smoke, confirmed: by either day optics or TC option, and confirming: incidents occured both on level BP, and small hill.., always in MP mode.. 3 vs 3 or more, and confirmed: only way to solve deliema was to either lower gun conciderably, or enter reduction of 2000m lase to around 1300m IIRC..

NOTE: would not rule out SP mode, as I "feel" this has happend also, during gunning practice in Nik's sce: Assult Curves.. in M1, always M1.



LS

[Hell_Hound]

Ok, so it isn't a damage hangover.

Unless Attack/Defend uses some unusual type of ammo (and I don't think it did) our only hope is to try and reproduce the glitch somehow, by replaying that scenario. Ah, the sacrifices... :D

[EchoLima]

your ammo was made by the lowest bidder, and i think it was from Que, made by Newifie's, on a friday afternoon, heheheh

OT: ROFLMAO. yepp that would do it... (Would there be an actual projectile or would they just stuff a pet beaver in the round? you know the attack type...)