Missle Lock - Won't hold?

[satexas69 0]

I have come across an interesting "feature" or "bug"...

I've got a map with like 50+ shilkas on it, and when you fly a heli (AH1Z, Apache, etc) and get a hellfire missle lock, the lock flashes red/white/red/white... on a live shilka.

Confused? Well, normally a live shilka will show up as "RED" and when you lock on it, it's a steady "red"... it doesn't flash because the game knows it's live.. and it stays "red" until your missle is fired, hit - then it goes "white".

My shilka's however, flash red/white/red/white over and over... so when toggling targets, you gotta sit on it and take fire from it a few extra seconds before you fire - to make sure it's really a live shilka....

I've tested this in the editor - and it does it, as well as multi-player on a dedi server. Futhermore, I started giving the tanks "names" to maybe help stop some type of ArmA confusion, and that didn't help either. Ideas?

[-SPA-LynxEye 0]

- Remove all tanks. Add now one.

- Test it again. If the tank is enemy, put AI inside.

[satexas69 0]

I think you may misunderstood my post.

I have a mass of ENEMY tanks, fully manned, trying to shoot me down.

That's GOOD.

When I get in a AH1 or Apache, and lock on them with Hellfire in the radar, it blinks red-white-red-white.... like the game's unsure of the status of the unit.

This doesn't seem to happen with only a FEW shilka's on the map... but I have 100+

[-SPA-LynxEye 0]

Yep, probably i misunderstood your post.

Then, it seems like this:

- When ArmA is 'checking' all targetable vehicles (when you targeting 'something' ), if you putting more than X enemy vehicles inside a map, ArmA is spending a lot of time to check the status of "ALL" vehicles... then... i understand why you seeing flashing RED/WHITE.

More or less... i want to say the same in this way:

If you 'removing' more than 20 tanks/shilkas/etc etc from your map, probably, that FLASHING will remains the same, but in less speed, less rate of flashing.

If this last is true... then you have 3 options:

1. Remove enemy vehicles till you seeing no flashing.

2. Keep alive this research in this forum, and/or test your own.

3. Try to test it with a soldier with Stinger. If the flashing is the same... is not fault of AH1Z or vehicles.

If nobody answering your requests, try to make a video (please), so it will be easy for all of us to analyze that flashing issue.

And sry if i misundertsood something, still i can't 'think' in English, only translate from Eng-Spa and again Spa-Eng in a crap way.

[nuxil 2]

i have had simelar issue with the lockon.. my problem was that the Ai was turning on/off the engine all the time,, when they moved just a few meters.. try to force the engine on all the vehicles. and see if that helps.

[-SPA-LynxEye 0]

Nice 'eye'.

[satexas69 0]

i have had simelar issue with the lockon.. my problem was that the Ai was turning on/off the engine all the time,, when they moved just a few meters.. try to force the engine on all the vehicles. and see if that helps.

This could be interesting - I have the fuel completely removed on ALL of them because I don't want them "moving around"....

Could it be that even on an empty tank they're triggering the engine on and off trying to move in the eye of the ArmA engine?

[-SPA-LynxEye 0]

Not only AI behaviour.

Just make yourself the test:

Try to engine on a chopper with 0 fuel

Try to engine on a car/truck/tank/animalvehiclething with 0 fuel.

It seems like when ArmA is saying 'Fuel', it means ''Batteries'

So, if a human Player can't... AI will have it more difficult than us.

[satexas69 0]

This has been SOLVED - I figured it out.

IF you put in a bunch of shilka's and you remove ALL of their fuel - when you "missile lock" them with hellfire's, etc... they will BLINK RED/WHITE/RED/WHITE/RED/WHITE over and over.

As stated earlier in this thread - it's about fuel. The game's trying to see if it's alive or not, and the AI's turning the key to the engine trying to start it... so it cycles endlessly in an "unsure" type mode.

Arrgh.

[-SPA-LynxEye 0]

Well... we see now just another TRUTH of ArmA, declaring 'some certain behaviour' when AI is inside vehciles... and players trying to get a 'fixed' target.

Nice work all.

[Big Dawg KS 6]

Targets & radar contacts will usually be white when their engine is off regardless of if they're manned or not, and the color changes to whatever it is (red for enemy, green for friendly, etc...) when the engine's running. The drivers of tracked vehicles (all vehicles really, but only tracked vehicles can turn in place) will tend to rotate the hull of the vehicle to face where the gunner is aiming, so when the gunner targets something the drivers rotate to face it (don't ask why), and normally when they turn the vehicle they must turn the engine on. If there is no fuel however, AI will continue to try to turn the engine on if they have to move. This usually results in the engine being turned on for an split second then immediatly shut off. If you trace it back to this it seems to be the problem.

[bob1787 0]

i remember this in OFP, i used to try and "hide" shilkas in trees and stuff so that they could just rip apart any air that flew over when there wasn't a chance that they'd fire back.i can't remember it ever working. i think its a great addition

[-)rStrangelove 0]

What happens if the shilka has no fuel and you force the driver to get out & lock the slot so he can't get back in?

I think the shilka should appear as WHITE since it has no fuel, but still fires on you.