buur

any news?

To push this topic here a picture. You see JTAC request IP ADDER but it is not on the MFD.

Have seen the same problem!

hm, had the same problem. Should I clean my joystick with alcohol or use the alcohol by myself?

Unfortunately this bug is not solved.

When the AI JTAC plans a attack he chose randomly initial points and very often the initial points are to far away from the target. A good solution to avoid this problem is that we can choose the initial points for the JTAC. So, please give us the possibility to advice initial points to JTACs.

It is a very big improvement that the target advised by JTAC is now marked on the kneeboard map with a red triangle. But if an other JTAC send a new target you have now two or more red triangles on the map. It would be very helpful if only the actual target is on the map or the triangles marked with a number so that we can differ them.

Hi, I have seen that ED has added the Target Point send by JTAC to the kneeboard. Great addition. Now we need also the Initial Points (IPs) which you can set in ME on the Kneeboard. This will help the pilot to understand his Mission given by JTAC.

Check your Kneeboard. The nine line is nowadays added automatically to the kneeboard.

um es mal so zu sagen: Der JTAC ist nicht gerade der stabilste Teil der Simulation. Kann gut sein das die einfach so verschwinden. Was du machen kannst um die armen JTACs nicht zu verwirren: Überlaste die Jungs nicht mit zu viel Funk. Die sind dann manchmal etwas verwirrt und haben keinen Bock mehr. Gehe die Prozeduren komplett durch. Nicht irgendwo in der Mitte aussteigen. Auch das verwirrt die. Gib jedem JTAC ne eigene Funkfrequenz. Wenn die sich gleichzeitig hören sind die auch verwirrt. Deine Einstellungen sehen richtig aus, daran sollte es eigentlich auch nicht liegen.

First, check your speed. If you got to fast in a dive you loose control. Above Mach 0.9 the plane get unstable. Second, do not pull to much gs. Above 6 Gs you can get problems.

https://discord.gg/gj68fm969S

Check Admiral189 mods, both are there.

Also have in mind that a high FPS rate gives you more sensitivity with your controls and make it much easier.

I talked about this thread:

This is a known issue, search the forum for this topic and you will find a thread about it. There wasn't a solution other than a new install of the game as I remember.

@OzCougar check your line 92. You have a capital C where a small one is needed. Always check your log for errors.

Normally this shouldn't happen. Is this new or a longer going behavior? With the last big update we get some new failures. This is not a AV-8B bug but an ED bug. Best is you post a track in the right forum section.

Yes, I saw the same problem.

Where else should you looking if you want to hit the basket? It is the easiest thing you can do.

Have a look at OnspawnGroup to hook into the new spawened object. Best place for help with Moose is the moose discord. https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Spawn.html##(SPAWN).OnSpawnGroup

As suggestion, a little bit equipment for the Farps and rode bases: http://www.boguerat.www4.50megs.com/Equipment.html It must not always shoot

Give the develop branch of Moose a trial. There is the ops.Chief class and it could do what you wish together with the other new ops classes. Best is you have a look on the Moose discord where you can find a lot of tips and help.

From LotATC discord: @everyone After the today DCS OpenBeta's update, if you have no contact on LotAtc screen on running mission, some DCS api has changes that break some loading, you will have to update to LotAtc Server 2.3.3, it contains a fix for that problem

@71st_Mastiff nose wheel steering is out since a long time, maybe a year. And the lost of control binding is unfortunately we have to aspect on every update. Best is to take it with a lot of humor