Nooch

Thanks for the poor spoiler alert... I haven't finished the book yet, you ruined the surprise, thanks.

In the real aircraft you can feel a bump when you move the throttle into afterburner zone.

This behavior seems normal, from a logical standpoint at least. You might want to have a TGT designated (in order to have the carret displayed over it on the HUD) and want to go for a CCIP pass at the same time.

I'd like to see a F-14D as well.

#Classification

A F-111 would be a must buy for me.

I'm not sure about this one...

It would require a little extra tweaking but I'm sure they would sell more campaigns as well.

Please report.

Cool! Looking forward to that.

Yes, logically, from our point of view, it should have been designed like you just described. However, as stated in the NATOPS and as you can see by yourself if you go set up time in the IFEI, it is the other way around in the Hornet. Why? I guess we'll need to ask a Boeing engineer or some navy expert in order to know.

I already know what Zulu time is, thank you. The thing is, the Hornet doesn't care if you think Zulu is the reference or not. Hornet's reference (from the computer point of view) is local time not Zulu. I haven't invented it, this is what's written in the Natops. Also you can tell it was engineered that way in the jet because you can set up local time but not zulu. Zulu can only be selected as an offset from local time.

Please stop complaining when there is clearly progress being made and new good stuff added. Also it is still work in progress so maybe the comms menu will be overhauled in the not too distant future.

Yes but was it marked as [NO BUG] because of your initial response or because they got the word from their SME? You could be wrong, I could be wrong... I guess only somebody who actually sat in a Hornet cockpit could be able to tell for sure and that's what I'd like to know.

I'm on the same boat as you guys. Let's wait, we'll see.

Same deal here.

Yeah it's been like this forever but still hasn't been fixed. I have no idea why...

The real answer is they don't know. Nobody actually knows exactly. Developping software is like solving a math problem. The initial time estimate is usually wrong and you can end up spending way longer than expected.

According to what the Natops says, the offset is actually from local, not Zulu! Actually on the Hornet it's the local time that serves as reference, not the other way around. Hence why, logically at least, it should be -4 hours in this case.

I can confirm that, there are indeed regular issues with TACAN in DCS, and with all modules, not one in particular. It's been like this for over a year. It's about time they fix it...