Mission 08, various issues

[Redglyph]

Hello,

 

I noticed a few issues in mission 08, though some of that seems to come from DCS (version 2.0.3.56503.102).

 

 

1) The names of the pilots, but it's been reported in another thread - I first thought it was a problem in 2.0 then saw the "DictKey_UnitName_*" in the mission file. I'm just mentioning this here in case someone else has the same question.

 

 

2) ATC is not answering. I have tried a lot of times, checked the frequency (124 MHz EDIT: I meant 125 MHz) on the map, tried different radios, nothing. Not even on the way back, when it's not as hectic.

 

It's usually hard to get ATC response, but here it was just not possible.

 

 

3) JTAC is only answering with a huge delay, and not always. When it replies, it just says there's nothing more and I can RTB. After checking in about 10 times, I finally had a task to bomb the targets, and I had to ask several times for details.

 

As for the ATC, it's usually hard to get a reply from JTAC, but it was far worse in this mission for some reason. I started querying after waypoint 6 (since the minimum is a 15' check-in).

 

I was already hovering above waypoint 7 for a while, and by the time I finally got the details, and bombed the assigned BMP's, the 2 rescue helicopters were standing right next to them! Killed one, fratricide and all unpleasantries ensued ;)

 

I thought those helicopters were supposed to wait for the LZ to be cleared.

 

 

4) No more available JTAC on the radio menu after that (?) I got a message saying it was fine, all targets destroyed, but couldn't contact the JTAC again and so couldn't get further tasks for the secondary targets.

Edited October 12, 2016 by Redglyph

[AMEDooley]

I had the same issue with pilot names and with JTAC being a bit slow. I noticed that documents had a push time of 1038, but the in game brief had a push time of 1048. Now that could be due to the fact that those docs are when I first downloaded the campaign and could have been fixed.

 

But your problem with ATC is you are on the wrong freq. ATC for Nellis is 125.00 AM not 124.00 AM.

[Redglyph]

But your problem with ATC is you are on the wrong freq. ATC for Nellis is 125.00 AM not 124.00 AM.

 

Sorry, it's actually a mistake in my first post, I must have mixed the common frequency and Nellis' ;)

 

I know I verified with the frequency shown on the map, on two iterations of this mission.

[AMEDooley]

Sorry, it's actually a mistake in my first post, I must have mixed the common frequency and Nellis' ;)

 

I know I verified with the frequency shown on the map, on two iterations of this mission.

 

Sweet! And no worries. I know I mistype a lot.

[Redglyph]

Just to avoid confusion: I mean, I used the correct frequency and it didn't respond.

[AMEDooley]

Not sure why it didn't respond. I haven't had any issues. It did take a minute but it did respond. JTAC on the other hand is super slow.

[AMEDooley]

Are you using the right radio for the tower. Not the frequency, but the AM radio. There are three and you have to use the AM radio. If you're using MHz that is the middle radio (UHF), and JTAC is usually the aft radio (FM). Although a couple times in the campaign it's been on the AM radio.

[Redglyph]

The same as usual, I know the difference between the modulations. It's just very long to answer in other missions, but this one was non-responsive.

 

Perhaps it's just even slower, no idea. This ATC problem needs fixing I guess, in other missions I get a lot of "unable to ...", either for start-up or for taking off, even though nothing prevents it (especially the start-up). Then one second later the ATC gives the authorization :noexpression:

 

 

The JTAC is more of a problem though, since we can't do without.

[AMEDooley]

I find I get a call of unable for start up if something is taking off. Not sure why that is. And the unable to clear for take off is a know issue. You can ignore both unable calls if you want to. But it does need to get fixed.