BlackRook

Is it still true that the MacOS version is the best version? Or have those updates made their way into the other OS versions, as well?

I am getting an angry TERMINATE call at 162 knots, too. So maybe the FM was tweaked again and this needs another look? Took a moment to get the screenshot, and the HUD shows 166. Other speeds have been fine up to this point in the campaign. null

@Shadow_039 Sorry to resurrect this thread from earlier this year, but I have a few questions since you say that you spent some time there. 1. Is it realistic that aircraft parked on MIKE Ramp used the 21L (eastern) runway as a taxiway to get to the northern/active end of 21R? I agree that the revetments and block walls are blocking two very important taxiways: ECHO East and LIMA East. 2. It seems to me that the proper taxi pattern when cleared by the tower to cross either runway, would be PAPA Taxiway to JULIET and north to the active end of 21R. 3. Is the military pattern for Bagram generally north of the airfield? The ILS glideslope critical path is shown in diagrams to be at the south/west end of 03R and the resources that I have found indicate that the 03 approach is the standard. DCS has aircraft landing from a northern pattern. I will work with the wind direction to see if this changes AI decisions.

SOLVED: So it turns out that my HOTAS binding for COMM2 was invalid. All other comms for the mission worked fine (Sentinel, etc) off of COMM1, except for Bravo. Bravo required COMM2. Once I fixed my bindings so that COMM2 could be activated, F10 entry showed up as it should've.

SOLVED. See next post. Leaving this here in case anyone else has this issue. I am replaying OCN after a year, and am having an issue with M4. No matter what I try, while orbiting the coords above the village, and trying every radio freq in the range for B6, am not getting an F10 menu entry to attempt contact. Now, admittedly, I took notes the first time I flew this and know the freq (unless it has changed, of course) but no F10 menu at all? The voiceover instructions state that COMM2 should be used, with COMM1 still on the Flight ('2') freq. So I am trying that. No F10. I've tried using the 'M' channel and the funny 'aO' character-named channel (what is that, by the way?). No F10. I even watched a walkthrough (screenie above from that) and did step by step what I thought I saw being done. Help?

+1 Though, for me in the Superhornet mod (E model) he runs into me and we're both screwed. Essentially only workaround is single-plane flight.

Same on the FA-18C and E/F mod, wingman #2 given permission to taxi before me, trapping me against his plane when he runs into me.

Okay, so the first post has a YouTube tutorial that is obviously several versions behind. The UI and terms have entirely changed in many ways. Has anyone a grasp of the DCS setup of OMM to the point that they could write a tutorial or how-to? The tutorial has downloadable, pre-build mods, and that is clearly not how DCS community works (almost all mods are manual installs). So a quick-and-dirty how-to would be amaze.

Not sure why anyone would pay money for any 3D program for non-professional (read: your bread-and-butter income earnings) usage when Blender is free.

That was it, Razo+r, thank you.

It must be me, unless it is a brand new bug. New Trigger (first one, list is otherwise blank): 1. 4 MISSION START (Radio Chatter) 2. No conditions, but I've tried with and without a TIME MORE < 10 3. RADIO TRANSMISSION* with file set, playable, and with the options filled out, including Name. When I save the mission, this trigger disappears entirely. There is no 'Save' button in the Trigger subscreen that I'm missing, and no video tutorials show there being one that is suddenly missing. So what am I doing wrong?

I've noticed that damage is almost a sure thing if the Hornet is not off of the runway before it starts that downhill turn (the runway dips). The FCS will try to fly the plane up, and in getting the nose high enough to clear the level horizon, it scrapes the exhaust on the runway, as the angle is too steep. Thus, you take damage.

I've seen the same thing, and it is super-annoying in that it is not reproducible. Restarting a mission sometimes it works, but not always. Definitely sporadic. I tried many things to try and isolate "what I was doing wrong", from making sure I started D/L before IFF, varying my power-on of the D/L in the startup sequence, and so on. Never did find a trick, so I feel like it is an elusive bug.

All in all, this is a very well-written, entertaining and challenging campaign. Kudos to @ChillNGand the team. Extremely enjoyable.

No wonder I loitered and searched for 10 minutes and couldn't find it!