Petrovich firing missiles on their own?

[Stratos]

Since the last update Petrovich fires without me giving the order, any idea how to prevent that?

[unknown]

Is your Petrovich menu green? If yes you ordered him to fire at will. Petrovich menu up once(long) to activate weapons, after weapons are active (from red -> yellow ->white menu) and you use petrovich menu up again you will give him the order to "free fire", press menu up again for "hold fire". 

Atleast Petrovich is behaving on my end like he should.

Edited November 21, 2021 by unknown

[Stratos]

And do you know the name of the command? I never used it before

[ARM505]

I had the same problem - despite the Petro HUD being in the (yellow/tan?) colour, and with him being in the default state, unchanged since mission start, he still 'free fired'. To double check it, I then switched him over to Free Fire, and the menu, and text box in the top right showed correctly, and he continued to Free Fire. I didn't change back then (ran out of missiles), but yes, I saw the same thing.

 

The command is the Petro menu up - long press (key W by default I think, don't use keys myself)

[Stratos]

As ARM505, Petro is in tan state, Weapon Hold, and he still fires all on his own.

[unknown]

Would it be possible for you to upload a track please? I spend 5 houres in the Hind SP/MP last weekend and Petrovich never ever shot one missile without me commanding him to do so.

Did you check for double key bindings? What joystick do you use? "Phantom" key presses by the joystick? I'm just guessing here.

 

[ARM505]

https://drive.google.com/file/d/16G84xAPdvqfYn_E8-LhL6L-8dF4Ynvqr/view?usp=sharing

Track is 7mb. Pardon the stupid VRS crash at the end, my wife started quizzing me on the dogs suppers, and woe betide I don't answer instantly.

The first set of missiles fired was done in the Petro Hold Fire (tan) mode, and he just fired as soon as he got the tone (no command from me - this is the part of relevance). Then I chased after the indestructable CH47 from hell for quite a while (I suck at gunnery) and then returned to fire some more missiles at the trucks - this time, Petro didn't fire at will. I then set him to fire at will, which worked normally. Then the dogs supper became a priority, derp....

 

Edit to add: The CH47 absorbed 2 missiles, and countless 23mm rounds. Somebody might want to have a look at that.

Edited November 22, 2021 by ARM505

[Radsr30]

If you go to user files, set it for documents, MI-24 and the author is Falconmasters. He created kneeboard pages for Petrovich commands.

Very useful. 

[unknown]

On 11/22/2021 at 5:09 PM, ARM505 said:

https://drive.google.com/file/d/16G84xAPdvqfYn_E8-LhL6L-8dF4Ynvqr/view?usp=sharing

Track is 7mb. Pardon the stupid VRS crash at the end, my wife started quizzing me on the dogs suppers, and woe betide I don't answer instantly.

The first set of missiles fired was done in the Petro Hold Fire (tan) mode, and he just fired as soon as he got the tone (no command from me - this is the part of relevance). Then I chased after the indestructable CH47 from hell for quite a while (I suck at gunnery) and then returned to fire some more missiles at the trucks - this time, Petro didn't fire at will. I then set him to fire at will, which worked normally. Then the dogs supper became a priority, derp....

 

Edit to add: The CH47 absorbed 2 missiles, and countless 23mm rounds. Somebody might want to have a look at that.

 

Thanks for your effort, i only had time this morning to download your track, sadly i can only see you doing your cold start, hovering over to the runway and there you crash at the takeoff, so i would say your track is not replaying correct for me

[Stratos]

Is a bit random, sometimes flying as a pilot you "lock" a target and then he fires, sometimes it waits until you give the order.

[ARM505]

As a slight update to this, there are certain other oddities happening - for example, in the F16, if I switch to guns after using the laser (having held the trigger down), the gun will just fire, and keep firing until I press and release the trigger. If I enter a cold start mission (again, in the F16) and switch to rockets, the entire pod will fire as soon as I turn the master arm on. In the Hind however, no 'fire' command is seen in the upper right corner of the screen (as if I'd pressed the fire weapon button), but Petro still fires. I'm thinking there's some kind of DCS weirdness with controls going on, and it's only started happening after the last patch. Obviously, checking controls in Windows shows that no buttons are being pressed.

[unknown]

1 hour ago, ARM505 said:

As a slight update to this, there are certain other oddities happening - for example, in the F16, if I switch to guns after using the laser (having held the trigger down), the gun will just fire, and keep firing until I press and release the trigger. If I enter a cold start mission (again, in the F16) and switch to rockets, the entire pod will fire as soon as I turn the master arm on. In the Hind however, no 'fire' command is seen in the upper right corner of the screen (as if I'd pressed the fire weapon button), but Petro still fires. I'm thinking there's some kind of DCS weirdness with controls going on, and it's only started happening after the last patch. Obviously, checking controls in Windows shows that no buttons are being pressed.

I never had anything you report ever happen on my end. What controller do you use? I know Virpil has a joystick tester where you can log the input of your device. It wouldn't be the first time that a HOTAS started showing its age/a defect by some random "ghost" signals.

[ARM505]

Virpil base with a TM Cougar grip. And yes, that's the exact software I used to test it. No inputs detected. I can't rule out that it's something on my end, but a) it's happening to more than one person, and b) it's reproducible. Running the VPC Joystick Tester alongside shows no inputs when it happens.

The 'sync HOTAS' checkbox in DCS is unchecked - I'm not sure if there's some other weirdness happening though. No big deal. If I make sure to pull all the triggers etc. before they're 'live', it doesn't happen.

[unknown]

That is a wired thing. I don't know if you can reproduce this in a short track(hot start, takeoff, problem...kind of track) because your last one is not playing correct on my end.

My thought was if it is a HW problem on your side i should see it happen in the track replay and if i take over control before the "automatic missile" fire happens and no missile is fired it would show there is something odd with your bindings or HW. If it also happens on my side after i take control it has nothing to do with your bindings or HW and would be a software thing.

There are 2(with you) people in this thread saying they have this problem, not that much so i would think its a) a HW thing or b) a very rare bug. Ok, you could say and only 1(me) who says he has no problems

But i also can't reproduce what you see in the Viper.....

 

[ARM505]

I've isolated the problem (for me at least) - long story, but I'm using a mish-mash setup: A Virpil base, TM Cougar Grip, and the old TM Cougar throttle. The throttle won't work without being connected to the old TM Cougar base. So it is still connected, albeit minus it's grip (which is of course sitting on the Virpil base, and being used successfully). What happened however, is that in DCS, all the devices of course show - so I have the VPC base (with the Cougar grip, whose buttons I must rebind to exactly what they were before on the Cougar), but the Cougar still shows - I'm still using the throttle, so buttons are mapped to it. BUT, I did not delete the OLD Cougar Stick bindings - so for some reason, even though it is sitting at the back of my desk, headless, some or all of its buttons initially register as pressed. Boom, fail.

 

Deleting the *Stick* mappings on the *Cougar* device solved it.

 

tl/dr - don't leave buttons mapped to sticks which aren't really physically connected properly anymore.

[unknown]

Great you figured it out!