Sylosis

I can't have these buttons to work. In the controls, these lines are shown as orange and there is an exclamation mark next to the assigned buttons. Hovering over it with the mouse doesn't tell me what's wrong. I have tried clearing the assigned button and reassign something and it still gives me the exclamation mark with no explanation. Moreover, these orange lines are all duplicated. "Kneeboard next page" is there twice. One line, I can't double-click to try to assign something, nothing happens. The other will only react in the keyboard column, but as I said, I get the exclamation mark... UPDATE: problem seems to be in the Ottoman Campaign. Tried a quick mission and although the control text is still orange, the buttons work and I have no exclamation mark. What should I do?

That explains a lot. I wrote a post about it a few days ago and was told I was possibly not "leveled" enough for it to engage.... but I'm pretty sure it doesn't want to engage. I have flown the F14 for quite some time and although I'm no pro, I never had any issue engaging the AP until very recently. Sometimes I'll push the button and the plane will even initiate some sort of movement that I'm used to see when engaging AP, but clearly it doesn't engage completely. Plus the AP Reference light stays ON. Anyways, glad to know it's not me and it's a new glitch. (although it's not entirely great news either haha) That being said, I'm not sure how much of a fix this was, cause yesterday after the patch that problem was still very much present.

At the moment, I have issues with Jester emptying our chaffs reserve for missiles that aren't aimed at me. And then, when I am finally shot at, he either doesn't do anything or well we don't have any more chaffs, so he can't do anything. How do you guys set your countermeasures? I was limiting myself to flares on the pilot, but so far it really doesn't work with Jester taking care of chaffs.

Does this mean Jester is not able to IFF interrogate by himself? I didn't know that.

Hi, 1- Was wondering if anybody also has that new issue where the autopilot reference switch seems very precious when it comes to working. I push it sometimes 20 times and nothing, and then all of a sudden it works. Some other times it works on first shot. I thought maybe I needed to be perfectly stable to make it work, but tried doing it as I was clearly not stable and it worked on the first occasion. I'm kinda confused. 2- Jester STT Lock: Suppose I have one radar contact in front and I know for certain it's an enemy. Why is it that when I ask Jester to STT lock "Enemy ahead" he's replying "uuuggghhhhh sorry can't do it" and if I then proceed to ask to lock whatever is in front (enemy or not), he then does it...? At first I thought it could be an issue of difficult lock depending on speed and bearing of the target, but if that was the case, why would he end up succeeding as long as I don't specify it's an enemy?

Well, you kinda answered my question. I could post a trk file, but I don't think it would help all that much, since what you explained is what I observe. To better explain: - Friends and I are playing online together on a server my friend set up. He uses that campaign generator available online, not sure the name, but I think it's quite popular and it does work quite well. - When going against a faction that has older aircrafts, we have to set them to Ace. But! As you point out, their CAP don't even come intercept us. They just fly their waypoints and then RTB. - If I try myself to go intercept them, it takes quite a while and by the time I reach them, they are already probably on their RTB leg, so they don't even bother my presence. - I we select a faction with better airplanes (Russia for instance), they immediately move to intercept as soon as they take off. Now, as you pointed out, it could be because of radar guidance. Modern planes see us on their radars, so they move to intercept. While old Mig21s can't see us on their radar at that distance. If that is the problem, would it be solved by providing them with an AWAC? Like their AWAC would guide their MIG21s to intercept us? Finally, it's kinda dumb that the AI on RTB will be that passive. I hope that "whenever" they fix the AI, this is going to be one of the improvements. Thanks for your help.

Probably not a bug, but I scrolled through every page of the forum to try to find the appropriate place where to ask this. I don't understand the AI, how aggressive it is. It seems to be drastically changing depending on the plane it flies. I'm trying missions where the AI is at "ACE". I fly the F-14, it has a selection of Su-23, Mig29A, Mig21, etc. It just doesn't engage. It will not try to fight me at all. It will barely try to even defend. But, if I give them Mig29S or Su-27, oh my god. It does not even make sense how it behaves. Even on "intermediate" (which is the 2nd easiest setting I believe), it'll shoot missiles when it's at 60nm or more from me. So it's either I get nuked or it's just too easy. Any suggestions to make it somewhat interesting in PvE?

Yeah... was kinda pissed that I got shot after that "possible glitch" and forgot to save the track. I need to fly it again, so this time, if it does it again, I'll save it and share here.

On a few recent occasions I have flown missions where I click the HSI button to designate my waypoint as my target and it sends the TPOD looking god knows where. Just recently, was flying a mission in the Raven One campaign, selected waypoint 8 in the HSI and used Waypoint Designate to slave FLIR to said waypoint. Waypoint was 15 nm away, to the east, but TPOD went looking north at 90nm (distance to target). I switched back to WPT 7 and back to 8 again, and then it was correct. Anybody has any idea?

Pretty sure I did, but I have had issues with TACAN lately. It doesn't always turn on when I push the button and sometimes I don't notice. I'll double check, especially since it works for others.

Is this a F18 bug, or a DCS bug, or the campaign? The TACAN beacon given for each tanker doesn't work in any of the mission.

So you mean it indeed gives Degrees, Minutes, Seconds, but that without the decimal seconds it is not precise enough. Correct?

Thx, that's pretty much what I thought!

Hi, Starting to use the F18 and JDAMs (was mostly limiting myself to GBUs and MAVs with the Harrier). I watched tutorials and read Chuck's Guide, plus read this forum. I have found some contradictory information... First, is it correct that in the F18 Pre-Planned targets you must enter Degrees Minutes Seconds and Decimal Seconds? Second, if JTAC gives me, for example, N30 30 04, am I correct in understanding that it is giving me Degrees, Minutes and Decimal Minutes? (2 digits decimal minutes)? Or is it giving me Degrees Minutes and Seconds? Either or, clearly JTAC lacks a bit of precision and I guess it's better to just use your FLIR to find roughly what he meant and then use ToO mode? (my question comes from Raven One campaign where you get only coordinates as indicated above. JTAC doesn't lase. But it seems still applicable as a general F18 question)

On the last refuel as you RTB, Exxon is not in the choices of the radio menu (or Arco if you prefer). I flew next to him (3nm) and he still wasn't in the list. Moreover, the TACAN beacons of both tankers are not working (at least in this mission, haven't tried in Mission 2 since you meet him head on).

Are you sure about that? Everywhere I looked it said the F18 JDAMs are expecting Degrees + Minutes + Seconds + Decimal Seconds (so in short, DMS). Tutorials on Youtube and/or Chuck's Guide all say it requires DMS + Decimal seconds. Yet you are the first one I see saying it requires decimal degrees. That being said, I also missed, but I assumed it was because JTAC gave me coordinates without decimal seconds (he gave me, for example, N30 30 04), or so I thought. So I entered in the UFC N30-30-04-00 and it barely missed. After some research, I'm quite confident your comment about decimal degrees is wrong, the F18 JDAMs don't work with decimal degrees

Not sure what you meant about the tanker, but I can confirm it can't be contacted after the ground attack, even when exiting the zone. I flew 3 nm from Exxon and he was still not showing up in the list. Update: I decided to write a separate bug report this radio thing.

I'm trying the mission at the moment and indeed, just saw on the kneepad that Rock is already programmed.

Ah ok, so with you said and what was also told by Padre Pio, I essentially have to manually enter it as a new waypoint using the info from the kneeboard. Gotcha. Thanks.

Oh ok thx. So in this mission I had, if I remember right, waypoints 1 to 5. And I don't remember reading in the briefing which one was Rock. Did I miss it? Was it written and my lame brain didn't know how to read?

I have a few basic questions about Mission 2 : First of all, is there a guide somewhere to help with basic things that more casual dudes like me might not understand? There is a lot of terminology I don't get on the radio chat. For example : Rock. Is ROCK the same thing as BULLSEYE? (same goes for Knock it off, I had to search a few minutes on the internet to find the answer to what that means) Moreover, looking through different tutorials on Youtube, when I'm told the bogey is "Rock 068 for 32", I understand this as "heading 68 from bullseye, distance 32nm". That being said, in order to navigate, I would need to select the bullseye as my active waypoint and make it an A/A waypoint. This way, I'd see the bullseye in my SA and be able to know where to go. All of that being said, how do I know if the missions were made with one of my waypoints on the bullseye? Thanks for the help

A lot of good information here, thank you.

No, I meant what I said, which was TDC Down. Or TDC Depress if you prefer. Or TDC Action. All synonyms.

Thanks for that, you are very helpful. One thing I noticed, watching your tracks versus what I was doing... I think that the only potential difference that I was doing, is that I left "designate" boxed in the EHSD. Could this have caused trouble? On one occurrence, I was frantically pressing TDC Depress to lock the MAV. I was at 7 NM and closing. It finally worked when I was at 3 NM, but I was just spamming TDC Depress. On future runs, I unboxed Designate in the EHSD and did not have that same issue.

This is quite depressing and frustrating to read that Razbam can't deliver, even with something like 3 years after its release...