atazar

Wow! You have solved the problem, I don't know how to thank you. I have noticed that this affects the projection of shadows on some objects like roofs of buildings, etc., but the improvement of the texture is so necessary that I prefer not to see shadows on the roofs than that frightening glow of the fuselage.

:thumbup: Thanks

Does anyone know what lua file I have to modify to reduce the brightness of the UH-1H fuselage? The brightness is excessive, does not fit reality. I leave two comparative captures. [ATTACH]216563[/ATTACH]

I would not like to have that guy in dog fight in real life as an enemy, but in simulation I would love to:)

Thanks, resolved, I did not know that undesignated was pressing (s)

I did it, but the camera does not move, neither up nor down, neither left nor right, it is locked. This does not happen when I first use the MAV-F It happens when I combine weapons and the TGP, but if I only use the MAV-F I have no problem.

:thumbup:

I cannot move the AGM-65F cursor after using the TGP.

Thanks NineLine Then, one last question is whether the autonomous AGM-65F objective designation system will be available with its initial resolution, because at this time the resolution does not allow the identification of the objectives as before the update and after synchronizing the MAV F with TGP, for some reason the designator is blocked. This would avoid the problem of TGP synchronization and blocking unwanted targets. Forgive me for putting so much force in this matter, but for me the AGM-65F are fundamental, since they are the perfect weapon to shoot down moving targets autonomously. Thank you.

https://drive.google.com/file/d/1rswRVpjwZTcRgfqixQQaUVepR0zyDYTf/view?usp=sharing

I would like to know if in real life the AGM-65F blocks objects such as trees, buildings, street lamps, etc. Because, although I managed to use them to knock down moving targets with the TGP, when the targets are in populated areas, the pointer always enslaves any object. I find it more effective to use the designator of the missile head than the TGP, although the image offers a much lower resolution and less distance.

Yes, I have noticed. In autonomous attacks without Litening it will cost to identify the targets by the silhouette.

Apologies and thanks also to you. :thumbup:

I have to apologize and thank you for the patience and intention to help.

I am using AGM-154C in TOO TGP mode for priority targets such as static SAMs to not get too close and AGM-65F for moving targets, which is the escort of a convoy. The problem is that if I use AGM-154C first, then nothing works with AGM-65F. Finally I have to apologize and thank you for the intention to help and patience. I have managed to shoot moving targets through the TGP with the MAV F. As soon as I finish processing the video, I will attach it. It is completely possible to block mobile targets.

:thumbup: All individual procedures are perfect, they work without problems, the problem comes with mixed loads, when we are going to make several attacks against fixed targets and mobile targets. I am glad to know that I am not the only one to whom the AIM9X sensor has disappeared from the HUD. All my support to Eagle Dynamics in its development, for my part, patience. I understand that we are in BETA.

You may be doing something wrong, but have you blocked static targets or moving targets? If so, could you show the procedure in some way, or maybe share the clue? And can you see the AIM9X sensor in the HUD, after using the TGP? Thank you.

Correct, I understand the procedure. But for some reason, after using the TGP in an attack with mixed weapons, the heads of the MAV F are blocked and it is not possible to use them in a conventional way, through its integrated camera. That is why the partner says that in a mixed-load attack, it is advisable to use the MAV F first. Excuse me if I express myself badly. Another thing that I have observed is that after using the TGP in A / G, the AIM-9X sensor is not displayed in the HUD.

It is the same conclusion that I have drawn. I agree. +10 :thumbup:

Thank you feefifofum! Finally someone understood me :)

The procedures of the MAV E cannot be applied to the MAV F because the MAV F is a weapon (IR) is not a laser weapon. Pressing the trigger would not guide a missile (IR) to a moving target.

I am referring to what the DCS Hornet can do today, not what it is capable of doing in the future. If the hornet really has this capability at this time, explain in some way how to knock down moving targets with the MAV F using the (TGP) Thank you.

Perhaps I have expressed myself poorly because of my low level of English. What I mean is that using the MAV F with the TGP, what we designate is a coordinate, not an objective. It is here that I want to know if I am wrong.

The advantage of the MAV F is that it destroys moving targets, but the TGP sets static targets. I'm wrong?

I wanted to report several problems detected in mixed ground air configurations. When we use the TGP (Flir) with the AGM-154C in TOO mode and want to switch to an attack with the AGM-65F (for moving targets), the maveric designator remains locked. Greetings.