Mav broken??

[T0x1s]

Hello

 

So when i chose maverick then i slew it to a target and lock it and then i try to do a final adjustment to get it to lock a vehicle i can't. When i turn each time i turn it after it's locked it start by going up then turn where i want. Same in Su 25. Anyone else get this?

PAC doesn't work either.

Edited September 13, 2013 by T0x1s

[Pepec9124]

Mav locking problem is confirmed. PAC is working, press 7 and then c.

[T0x1s]

Will this ever be fixed?

[VTJS17_Fire]

Hey ED Team,

 

to sell the A-10A as a separate module is fine, I bought it at release day. But without Mavericks, the DCS FC A-10A is useless! :mad:

 

When will we get this issue fixed? :cry:

 

 

kind regards,

Fire

[Pepec9124]

Hey ED Team,

 

to sell the A-10A as a separate module is fine, I bought it at release day. But without Mavericks, the DCS FC A-10A is useless! :mad:

 

When will we get this issue fixed? :cry:

 

Fire

 

Try some AAR :megalol:

[Buzpilot]

Hey ED Team,

 

to sell the A-10A as a separate module is fine, I bought it at release day. But without Mavericks, the DCS FC A-10A is useless! :mad:

 

When will we get this issue fixed? :cry:

 

 

kind regards,

Fire

 

It's not just the Maverics, if you try out CBU-97, in CCIP mode at relative low altitudes, you need to aim 3-800m behind (depending on speed/altitude), to make cluster ammo release in air right above targets.

http://forums.eagle.ru/showpost.php?p=1867848&postcount=13

Edited November 6, 2013 by Buzpilot

[rassy7]

Mav locking problem is confirmed. PAC is working, press 7 and then c.

 

Wait. Do you HAVE to press C for PAC to work? That just selects the cannon right? Shouldn't PAC be always on?

[Wags]

Both Maverick lock range and low altitude CBU release issues have been resolved internally. These will be part of a later update.

[VTJS17_Fire]

Both Maverick lock range and low altitude CBU release issues have been resolved internally. These will be part of a later update.

 

Sounds good, Wags. Hope, it will be the next update. :music_whistling: But I can't release the Maverick, no matter in which range. Hope, this will get fixed, too.

 

 

regards,

Fire

[Buzpilot]

Sounds good, Wags. Hope, it will be the next update. :music_whistling: But I can't release the Maverick, no matter in which range. Hope, this will get fixed, too.

 

 

regards,

Fire

 

Release should work, sure you do it right? Only problem with Maveric's are ,it's very hard to slew to lock on, if you only have a 4 button switch. And range is better in A-10C now, so it should improve on A too.

Edited November 6, 2013 by Buzpilot

[Pepec9124]

Wait. Do you HAVE to press C for PAC to work? That just selects the cannon right? Shouldn't PAC be always on?

 

Nah, it's not A-10C.

 

Both Maverick lock range and low altitude CBU release issues have been resolved internally. These will be part of a later update.

 

That's cool, what about A-10A shaking relatively to other objects ?

[VTJS17_Fire]

Release should work, sure you do it right?

 

I do it, like the last 6 years ... did anything changed with FC3/ DCS FC A-10A for launching the Mav?

 

 

regards,

Fire

[Magician]

I just did a random generated mission with A-10A and 4 AGM-65Ds and had no issues with locking them onto T-80s at 6nm, getting the cross to blink and launch, no misses.

 

I was curious whether the Mavericks were in fact broken on A, but they work perfectly for me. So it's something on your side.

 

My DCS install is since 1.2.3 with regular updates and with all modules enabled and it's working normally.

 

Maybe it's because I have FC3 and not the stand-alone A-10A, which shouldn't be any different though.

 

T-80's are no problem to lock on, the only problem I have is with the Strela. Something for which you really need the stand off distance.

 

As far as I can tell it won't lock to a Strela at all, at least not before eating an SA-9.

[T0x1s]

I just did a random generated mission with A-10A and 4 AGM-65Ds and had no issues with locking them onto T-80s at 6nm, getting the cross to blink and launch, no misses.

 

I was curious whether the Mavericks were in fact broken on A, but they work perfectly for me. So it's something on your side.

 

My DCS install is since 1.2.3 with regular updates and with all modules enabled and it's working normally.

 

Maybe it's because I have FC3 and not the stand-alone A-10A, which shouldn't be any different though.

 

First i had this problem with the standalone but now i have FC3 and the same issue. My friend have it to. Notice i am not using an axis or anything. Only 4 buttons. However i don't care about it so more since i play the C version now but i still hope this should be fixed as soon as possible for the other players :) Also wags said this will be fixad and is a know bug so it isn't on my side.