Slew AGM-65F

[DarkStar79]

Yea the radar slew is fine and axis tune works for that. But the slew on the mavricks are very fast. and I cant change that even thou i have made a huge curve on the axis tune. So something is wrong here..

[Linhael]

Also same here. Using X56, mini stick on throttle set for TDC axis and Mavs can't be used at all as even without moving it uncaged visual is going crazy. If I disable it and use directional keys it is better.

[toutenglisse]

I saw this elsewhere : set deadzone to some (I use 10 with no curve) and it's ok.

[=Pedro=]

I saw this elsewhere : set deadzone to some (I use 10 with no curve) and it's ok.

 

It is not...

[ShadowVonChadwick]

Its the mini stick on the TM Hog that is the culprit here.

 

 

Hat switch is fine , even the arrow keys work

 

But as soon as I touch the mini stick the mavG wants too look a the skyward @ my 11oclock.

[backspace340]

Its the mini stick on the TM Hog that is the culprit here.

 

 

Hat switch is fine , even the arrow keys work

 

But as soon as I touch the mini stick the mavG wants too look a the skyward @ my 11oclock.

 

It's not just the Warthog, same on the TWCS mini stick and the x56 from the sounds of it. Wags has the TWCS so hopefully he's seen/experienced the problem and we'll get it fixed...

[LeCuvier]

Increase Deadzone, Reduce ASaturation Y!

 

I reviewed the slew axis parameters I use with the A-10C, and they are:

Deadzone = 30

Saturation Y = 15

The large deadzone is necessary because of the nature of the mini-stick, and to avoid "crosstalk" between X- and Y-axis. The low Saturation value reduces the sensitivity of the axis.

 

With these parameters I can control the seeker of the AGM-65D and G, although it seems still a bit over-sensitive. And they work with the A/A radar although that seems a bit under-sensitive (slow).

It may be difficult for ED to make both radar and IR seeker equally sensitive with a single shared input axis. That could be solved by introducing one or two adjustment parameter(s) under Options/Special.

Edited November 25, 2018 by LeCuvier

[=Pedro=]

Try to put the marker over a target when zooming from let say 3-4 nm while auto bombing :music_whistling:

[LeCuvier]

Try to put the marker over a target when zooming from let say 3-4 nm while auto bombing :music_whistling:

I'm not sure what your scenario is. I use it with the IR Mavericks and it's working albeit far from ideal.

[toutenglisse]

It is not...

 

Sorry - should have said ok for me with TWCS mini stick.

At least the same than how mavericks are controllable with the A10c. (I prefer 100 times to use TGP than slave maverick's sensor).

My biggest difficulty with AGM-65-G (infrared !?) is to lock a moving hot T-90 tank instead of all the lighting pool along the road…

[Sparky1b09]

Are you guys still fighting this? Mine still is practically unusable with the problems stated above.

[Eldur]

Also, is me the only one having issues with the warthog mini stick for the mavs?, once the camera starts moving diagonally it wont respond to any other direction no matter how hard I push the mini stick ...also, the diagonal response seems MUCH more prone that pure axis response...odd.

 

Common DCS problem since LOMAC and probably even longer, also applies to TDC control on radar screens. Really needs to be fixed.

 

Try to put the marker over a target when zooming from let say 3-4 nm while auto bombing

 

I hear you... the marker will be about half a mile off target by just looking at the TDC axis control alone

 

When I first tried auto bombing, I had the axis mapped with no deadzone and though it was some kind of INS drift when the marker wasn't at the same spot anymore after pass and turn around

Edited November 29, 2018 by Eldur

[=Pedro=]

[Deano87]

I'm going toh replace that ministick in my Warthog for a custom one, but a soft solution is really needed from Devs anyway. Without tgp pointing the marker is a real pain in the arse when tried to bomb a military building and instead of that bombing a primary school in the nearby city ������

 

I have a very good custom ministick on my Warthog, and it’s no better with the Hornet mav seeker unfortunatly. Still unusable!

Edited November 30, 2018 by Deano87

[Dirty Mittens]

10+ post later and I still have to ask. How do we bring this to the attention of ED? Has any of the devs acknowledged the issue?

I think we can all agree using the TDC for functions is damn near impossible except for when slewing the radar. Maybe the issue is actually when using the TDC to slew the radar it moves to slow and we have tuned our TDCs to the wrong thing?

 

Seems like more and more features are coming online with the hornet. It would really suck for this day 1 issue to continue as we are getting into the meat and potatoes with the hornet.

[=Pedro=]

10+ post later and I still have to ask. How do we bring this to the attention of ED? Has any of the devs acknowledged the issue?

I think we can all agree using the TDC for functions is damn near impossible except for when slewing the radar. Maybe the issue is actually when using the TDC to slew the radar it moves to slow and we have tuned our TDCs to the wrong thing?

 

Seems like more and more features are coming online with the hornet. It would really suck for this day 1 issue to continue as we are getting into the meat and potatoes with the hornet.

 

:thumbup:

[ShadowVonChadwick]

10, 100, 80 & 50 Here

 

 

Be aware that using the mini stick for Mavs is problematic.

[Deano87]

Be aware that using the mini stick for Mavs is problematic.

 

Understatement of the century! Mine has a mind of its own!

[Sparky1b09]

I reviewed the slew axis parameters I use with the A-10C, and they are:

Deadzone = 30

Saturation Y = 15

The large deadzone is necessary because of the nature of the mini-stick, and to avoid "crosstalk" between X- and Y-axis. The low Saturation value reduces the sensitivity of the axis.

 

With these parameters I can control the seeker of the AGM-65D and G, although it seems still a bit over-sensitive. And they work with the A/A radar although that seems a bit under-sensitive (slow).

It may be difficult for ED to make both radar and IR seeker equally sensitive with a single shared input axis. That could be solved by introducing one or two adjustment parameter(s) under Options/Special.

 

 

After reading this I tried it and it's the best solution I have found yet. It's not perfect by any means because it slows down the radar TDC but I can now reliably use my mavericks. I may tweak it a bit to see if I can find a happy medium for the mavs and radar but this is a good starting point anyway. Thanks LeCuvier.

Edited December 2, 2018 by Sparky1b09

[=Pedro=]

Looks like They hear us. At least They respond to my question

Edited December 2, 2018 by =Pedro=

[Baaz]

I reviewed the slew axis parameters I use with the A-10C, and they are:

Deadzone = 30

Saturation Y = 15

The large deadzone is necessary because of the nature of the mini-stick, and to avoid "crosstalk" between X- and Y-axis. The low Saturation value reduces the sensitivity of the axis.

 

With these parameters I can control the seeker of the AGM-65D and G, although it seems still a bit over-sensitive. And they work with the A/A radar although that seems a bit under-sensitive (slow).

It may be difficult for ED to make both radar and IR seeker equally sensitive with a single shared input axis. That could be solved by introducing one or two adjustment parameter(s) under Options/Special.

 

I've actually gone a step further and a bit more extreme. The following is the axis settings I use, and will explain below why I use them.

 

Deadzone = 25

Saturation Y = 50

Curvature = 20

 

The above settings seem to be a happy medium for me. Yes, on the radar the slew rate is rather slow, but those settings also greatly improve MAV stability when I may not have a lot of time to slew the seeker around.

 

Going in depth a bit further, RARELY do I ever have my radar set below 40 miles, so I do have time to slew the TDC around when a target is picked up. If I do decide to engage, I'm locking the target at or about 25 miles, with first launch at 20. By the time the missile goes pitbull, we've closed to anywhere between 12-15 miles, and I'm therefore going into ACM anyway.

 

Now when using the MAV, it's usually because I'm taking out radars and missile systems (in our CVBG, I'm a part of a dedicated SEAD/DEAD squad). Their exact location is not always known, so one of our members is going to wildweasle the site, while the second member dives for it once its location is determined. The MAV remains caged until the my nose and seeker is looking in the right direction, and only uncaged once I have visual of the target in the seeker head. At that point I only have a few seconds to lock the target and fire.

 

So, getting back to my axis settings, I've put more importance on MAV seeker stability than slewing the TDC around on the radar. Thus a high saturation rate and curvature allows for smaller adjustments if necessary, yet rapid movement at the outer limits of axis scale.

 

I Hope I've explained myself clearly, and hope the settings I use are useful to some.

[Dirty Mittens]

Looks like They hear us. At least They respond to my question

 

All I was looking for, thank you!!

In the meantime I will play with the axis settings some more as a temporary fix.

[Baaz]

I posted this in a different thread, but will repeat here:

The following is the axis settings I use, and will explain below why I use them.

 

Deadzone = 25

Saturation Y = 50

Curvature = 20

 

The above settings seem to be a happy medium for me. Yes, on the radar the slew rate is rather slow, but those settings also greatly improve MAV stability when I may not have a lot of time to slew the seeker around.

 

Going in depth a bit further, RARELY do I ever have my radar set below 40 miles, so I do have time to slew the TDC around when a target is picked up. If I do decide to engage, I'm locking the target at or about 25 miles, with first launch at 20. By the time the missile goes pitbull, we've closed to anywhere between 12-15 miles, and I'm therefore going into ACM anyway.

 

Now when using the MAV, it's usually because I'm taking out radars and missile systems (in our CVBG, I'm a part of a dedicated SEAD/DEAD squad). Their exact location is not always known, so one of our members is going to wildweasle the site, while the second member dives for it once its location is determined. The MAV remains caged until the my nose and seeker is looking in the right direction, and only uncaged once I have visual of the target in the seeker head. At that point I only have a few seconds to lock the target and fire.

 

So, getting back to my axis settings, I've put more importance on MAV seeker stability than slewing the TDC around on the radar. Thus a high saturation rate and curvature allows for smaller adjustments if necessary, yet rapid movement at the outer limits of axis scale.

 

I Hope I've explained myself clearly, and hope the settings I use are useful to some.

[Davee]

Slewing Maverick - unable

 

:doh: SOLVED THANKS GUYS!

 

 

 

Latest update:

 

 

Can't get MAV to slew.

 

 

Could someone explain the sequence please. Which button to hold while slewing?

 

 

Thanks

Edited December 5, 2018 by Catseye

[Knock-Knock]

Latest update:

 

 

Can't get MAV to slew.

 

 

Could someone explain the sequence please. Which button to hold while slewing?

 

 

Thanks

 

https://forums.eagle.ru/showpost.php?p=3710345&postcount=98