SNAFU

Thanks for the heads up.

Another example for the EGIW and 3PTSIW LSO grading I would like to understand, this time by Wags himself:

Funny, I get it less in the Tomcat.

Are there any new on this front? In the Hornet I tried to reproduce the EG bug, but I just cannot find something. Just to show, that I get an EG, even though I do not touch throttles after IC and go gate IW I made two examples for the EG issue. Maybe it helps. Currently the LSO grade logic is hard to trust, besides the issue, that the meat ball for the SC seems to be off (that is another topic). Minute 2:30 for the above PS: I know the video does not show the SC, but it is the same for the SC. I tried it here on the CVN59 to check, if it depends on the CV. It doesn´t.

Wenn du damit IFA meinst, nein, nicht zwingend.

Still broken?

Für die jenigen die es noch nicht kennen bzgl. der IHADSS:

Ok, strange behavior. I thoughts it's because the scripting engine documentation for triggerzones so far knows only centerpoint coordinates and radius. Thanks for testing.

The scripting engine only knows the centre of the zone and the radius. So basically it handles the box as a circle. That's what I meant.

As far as I have found out, the scripting engine only knows trigger circle zones, so box shaped trigger zones are simply cosmetic and cannot be used as zones for triggers or other scripting.

I made three BVR fights in an F14 Vs F16 AI Ace. At 20kft and Show the first AIM54 at 35nm and the second at 20nm and did a short skate. 2 of the 3 engagements the Vipers AIM120C the AI shot at around 30nm intercepted my first AIM54 and went straight on for me. I was also able to lock the Vipers AIM120C at 20nm and shoot it down with a AIM54. I cannot imagine this is intended, so I looked for a bug report here. This was all I found, so I report it here.

Baltic Sea

Hi, ED changed the lua designation of All weapons, so all this scripts in this regard will need a rework. If you check the Moose framwork, you might find something for 2.7 weich essentially does the same.

Moin LoHan, Hat es dich nun auch zu DCS und ins ED Forum verschlagen? Unkraut vergeht nicht, was? Und ja Zeit, ist auch nicht mehr das was es mal war. S!

Moin zusammen, Ein kleines Update von unserer Seite. Mittlerweile ist ja schon ein halbes Jahr vergangen und wir haben uns bei einer Anzahl von 6 F-14 Fans konsolidiert und befinden uns schon fleißig im Aufbau der F-14 Abteilung. Mittlerweile suchen wir also nicht nur mehr RIOs sondern auch Spieler dich sich für beide Jobs interessieren und die nicht nur die F-14 lieben, sondern auch das Multiplayer Erlebnis also die Crew Koordination der F-14 fasziniert. Bei Interesse oder Fragen einfach melden.

I still have this bug. Is there a workaround available? Is Group.getCategory() returning if plane/helicopter/ground_unit/ship/strucuture?

Are there any news on this? Does this event still has only limited information and not even an initiator? https://wiki.hoggitworld.com/view/DCS_event_player_comment

Thanks for clarifivation guys. TWS seems to have been improved significantly now, so my PSTT only approach seems obsolet anyhow.

Ok, that explains my misunderstanding. I thought it would act the same in PSTT as in PDSTT, just without the lofting. Thats a pitty, would love to have SARH mode in PSTT.

As you see in the TacView, I shot the missile at a beaming target. It was basically notched, when it left the rail. I read this, but couldn´t believe this is also valid for targets shat at with PSTT at 40nm. I understood point 4 ACM Mode related shots. In But if this is intended, PSTT is pointles at any moving target over 10nm it seems. If this was the design of the AWG9 fine. Makes it quite hard to hit anyting, which is not totally clueless. PS: Actually I never had this situation before that I tried to shoot a beaming target which is just flying straight. So far the targets always went hot at some point and just notched to defeat the shot, so it was not that obvious I guess.

I could not find any report so I post this here: Is this intended behavior? Is t

I tested from the RIO seat in SP. MLC out and loss of track untill pitbull. I checke every tacview, in tws and pdstt they loft but guide only after becoming Active.

I did some test fligts (rouhly 80+) on different altitudes 1v1 vs ACE AI F-16C and noted down, at which range a AIM54C or AIM54AMk60 hit the Viper in which radar mode. Procedure was always go for max speed, shoot, crank, recommit, shoot until the Viper was hit or I was out of missiles. At the same time I evaded the incoming AIM120C or AIM9X. The results be summarized shown in this table. Red meands Viper was hot most of the time, green flanking or blue cold: https://drive.google.com/file/d/163D...ew?usp=sharing If you want TacVIEW Files or MIZ files of tests, contact me. My Interpretation: > 35.000ft: 2 AIM54C are required for a certain kill shot in PSTT between 40-30nm, while 1 AIM54A is likely to be enough ~ 20.000ft: 2 AIM54C and A are required for a certain kill shot in PSTT between 35-35nm, while 2 AIM54A has a slight range advantage ~5.000ft: Don´t be there. Range of the AIM54C sinks drastically and 3 C-Missiles are required between 5-10nm for a PK>1, while 2 A-Missiles are needed between 15-5nm in PSTT. TLDR: -AIM54A is better than AIM54C, TWS launches have a PK~0 and only PSTT can hit a fighter like an F-16C. Don´t engage BVR 1v1 below 20.000ft against ACE AI, if you don´t want a fair fight.

Das vJaBoG32 hat sich nun auch für Interessenten geöffnet die sich für die F14B in der Piloten und RIO Rolle interessieren. Du solltest gerne beide Positionen ausfüllen wollen und zu uns passen. Mehr auf unserer HP oder in unserem Forum/TS.