DimSim

Just completed this mission, and enjoyed it. Did do the decode rather than just google the solution or radio wing man. There is definitely a bug in this mission, as suggested above, the 1st coordinate cypher should be K,V,G,U,S,W,H (V, not I for 2nd number). This turns the 3 into 7 which makes the coordinates accurate. The current documentation is understandable, though the 'Set number' was confusing. Another sentence describing that all letters in a 'set' such as 'G through L' use the same decoding top-of-set-row, might have helped. But once you follow the example and get the same result, it makes sense. (In fact the set is irrelevant as the code sheet has the same values for all sets, which BD noted.) @VdK The fact there are 7 numbers instead of 6 for latitude is not important because the Mirage enters numbers in decimal minutes, so it simply ignores precision beyond the first 2 decimal places. It's not Minutes and Seconds.

Good information. I noticed the lock box missing from recent builds. It does enable with either missile selected so I assumed it was intended behavior. I must try police mode what following or investigating friendly aircraft.

I experienced the same today... if I stop short, planes either bump into me or over take me. If I cross over left, instant fail. I just held back and let planes pass to avoid collision. I must have missed a trigger though, because the whole mission played out poorly for me and I struggled to keep up with Rocket. It's a pity the triggers and missions are so finicky, even though I had final mission success and RTB, no further comms occurred, that is, no approach contact etc. Beta 2.5.6.55960 EDIT: For the sake of testing, I replayed the start of that mission and aircraft correctly stopped behind me without ramming this time.

This reappeared again for me after installing F-16C, though it is the Mirage 2000 that has messed kneeboard bindings. Last time, I fixed by editing the Mirage keyboard config and deleted duplicate config entries. This time there are no duplicates and the config file is identical to a backup I made months ago. Have not found a solution yet, but I need that kneeboard to work in flight! Beta 2.5.6.55960 EDIT: Some minutes later, after about 4 restarts, since I was checking version and testing other aircraft profile, the issue has disappeared. I did nothing. I did not modify the config files. It appears this is an intermittent bug, or part of a group of related bugs.

That had no effect for me, but thanks for the suggestion.

Yes, Full Screen is enabled. This is not a Windowed vs Full Screen issue, it relates to the full screen window losing focus during startup phase. If I uncheck Full Screen, I get a floating window which looks different.

I just switched from Steam version to non Steam. Every time the application starts from desktop shortcut, the app window appears in top left corner instead of full screen. * Resolution set to 2560x1440, while monitor res is 3840x2160 * Always occurs with non steam version, never occurs with Steam version unless I click around while loading. * Does not occur if app restarts itself (eg. change settings or logout causing auto restart.) * Doesn't matter if vsync on or off. * No video driver customizations * Not VR * System: Windows 10, Geforce 2080 * Build: Open Beta 2.5.6.55960 Work arounds: * Alt-Enter - Always and instantly restore full screen, HOWEVER mouse behaves strangely. Every 4th click or so on the UI will reposition the cursor as if the resolution does not match somehow. * Alt-Tab - May require multiple presses, but once DCS is in focus, works fine. * Click on task bar icon after loading - Causes DCS to go full screen with focus. Works fine. * Click on task bar icon while loading - Also works, and prevents it showing as window first, but requires careful timing. * Click on app window - Sometimes works, depending on current state of app Why not just use workarounds? Why should I need to re-focus the app every time I start it? No other application requires this. Worse, the Alt-Enter which would work best has the jumping mouse cursor issue which persists until app restarted. I would guess this could relate to the way non steam version shows 2 popup windows for login and authorization each start, while Steam does not.

My work around was inadequate, even with the heading tape correct, the waypoints remain incorrect. This makes the mission unplayable at this present time. Track file linked (attachment too large). m2000_red_flag_mis3_bad_ins_wpt1.trk https://mega.nz/file/09EizTwJ#KejzoeLbvSQjGq0Hq1L7srBwOeHZ8caAeBYbzOWnEsg

Same issue for me. HUD Heading tape/indicator is incorrect. I have special option 'INS does not require alignment' on. This occurs only for Mission 3 of Red Flag campaign to my knowledge. I tested some Instant Action and loaded Mission 1,2 and 4 into the Editor. Those all started correctly. I loaded Mission 3 into the Editor and changed the date from 23 Jul 2012 to April 2012 and Oct 2020. Each date change caused the heading to start at different position. It seems the INS setting is not honored for this mission. Yet selecting the player craft shows 'Enforce INS Align & Drift' is Off. Work around: Performing the INS alignment procedure, (even without editing the Lat, Lon digits which are not accurate), causes the heading to align to correct value after first phase. EDIT: Work around inadequate, see next post. Running Beta build 2.5.6.55960

I'd be interested to know of ways to improve detection, other than point craft toward possible target. I've sometimes had friendly and enemy craft not detect less than 15nm away. Almost appears random and not related to low flight through mountains.

@Adam there's just a few critical things you need to know to survive Huey: 1) Keep the vertical descent below 1000 feet per second to avoid VRS. Best way is to descend at 500fps while moving forward as descent can change rapidly at low speed and requires larger power changes. Keep an eye on this gauge. 2) Keep an eye on the power gauge. If you are in the red for more than 15 seconds or so you will burn out the engine. Find the gauge, keep out of red, all good. 3) Avoid mast bumping. Don't land or start on slopes or rock the controls side to side or back to front. If you do, you you'll bump your mast and lose your rotor. Try it in practice to see how easy it is to do, then don't do it! As for cargo, it takes practice and patience to hover. Cargo is mostly hover and flight. Flying overloaded is not fun, so keep as light as possible. Slopes are terrible to hover over. Use the auto hook by landing nearby and hooking. Use the pop up guide to hover over the location. Well designed missions allow a little grace, nasty mission designs are nasty. You can easily set up a practice with the editor by placing aircraft and a cargo then use radio menu to target it.

++1

Please let us know if there's any movement on this. I'd love to finish this mini campaign. I have bought Red Flag to follow.

UH-1H Huey is loads of fun to fly. Ka-50 is fun to blow things up, but not fly. Mi-8 feels nice, but like a bus that wants to fall out of the sky if mistreated. Gazelle is hyperactive and feels plain weird. After tweaking control sensitivity it's not bad, but I just didn't enjoy it enough. Looking forward to Kiowa though. I own UH-1H and Ka-50. Spent hours of free play evaluating the other two but decided not to buy them.

Didn't work for me a few months ago when I tried. No menus, no troops boarding first mission.

Thanks all, I see it now. The switch tooltip is "Theta Switch (Target Bearing from Bullseye)" but as you described, yellow text "RAZ" appears near it when the yellow line is present. Clicking the switch clears both line and label.

I'm a casual player. I auto start. I check the box 'INS Aligned'. I'm proud of it! It appears I'm also not alone... "The average time a player spends in DCS in one session is 25 minutes" Simon, Global Business Development Director, Eagle Dynamics. Source: I'm also delighted some people enjoy cold & dark starts, and 2hr flights with multiple air-to-air refuelings. It's great this sim has options to support casual players and realism enthusiasts.

Where exactly is this RAZ switch? I can't find it in English or French, nor any mention in the Manual or Guide. I do see a button labelled 'declutter'.

Completed the campaign, so thought I should share some feedback. Pros: * Liked the ship base. * Liked the weather choices mostly. * Voice overs good to have. * Appreciated some of the humor. * Mostly good navigation aides (FM, ADF, flares, smoke). * Glad less 'fly in formation' than UN campaign, formation is painful and not as easy to time accel, if penalized out of formation. * Not too hard difficultly for me, casual player with limited experience and patience. * Nice to have difficult/frustrating tasks first eg. sling load so any repeat gets the frustrating part over nearer the start. * Nice to have sling loads destined for large area like FARP instead of tiny place on hill slope! * Good to see Skip Mission and Last Order in menu. More details about last order eg. repeat full description would help. I only used a couple times though. * Auto startup supported on most missions. Cons: * Broken night missions due to game engine changes. Better to switch those to NVG which is challenge enough. * Long transit time / distance to mission goal and / or home. Better to move ship 5-10 miles closer to land, locate objectives closer. I need missions to max out around 30mins to fit into life. * Locked out player options. Just let payers enable unlimited ammo / fuel, invincible etc. unless absolutely critical to mission. Just makes game more accessible to casual players. * Missions often show limited scripting, either limited by design or game engine, I don't know, but if timing or triggers are off, the immersion disappears fast. * Mixed difficultly. Overall not bad, but some missions very frustrating compared to others. * Aircraft overloaded most missions. Not fun to fly an overloaded heli as it hampers maneuverability. Also not realistic. I sometimes reduced fuel or weapons just to improve flight handling. * F10 radio help could be improved with better description of current objective, or extra radio option with specific directions like heading and distance if lost. Something for all campaign and mission designers to consider: "The average time a player spends in DCS in one session is 25 minutes" Simon, Global Business Development Director, Eagle Dynamics. Source:

Can confirm this mission start issue is fixed as of 18 Aug 2020 beta. This mission still has other issues: 1) Objective roof is hard to land on as it 'bounces' the chopper off. 2) Objective roof is hard to land on as night vision is ruined by burning vehicles nearby. 3) Landing on the ship is hard, again as night vision is ruined by flood lights. Watching old Youtube videos, this mission was much more playable with earlier lighting and night vision. At times the choice is be blinded or blind. Likely relates more to game engine than the mission, but there may be some way to tweak lighting conditions for present build.

For what it's worth, I had the same question when buying my first modules. I wanted a fighter and ground attack jet. Ended up with... AV-8B Harrier and Mirage 2000 Why? After reading many many opinions, I went for the planes that were most fun rather than most capable. I'd recommend both these aircraft whole heartedly. Harrier does lack missions and campaigns at this time. Mirage has awesome bundled campaign.

Just tested with Argo Mission 2, tune to 4300 at start. Worked fine, beeps and direction gauge. Check you've clicked the right side dial all the way to 'Home'. After not playing for a while that confused me once, I needed one more click to be at max clockwise turn to Home.

I've done that also. I presumed I had damaged the aircraft or done something wrong. Couldn't get it to retract.

Thanks, it is the 'Caution / Advisory Lights'. I didn't notice, because on minimum brightness, it's still blinding at night.

The comms menu should show regardless of radio selection and tuning. Naturally the first thing I tried was switching radios 1/2 and checking frequency in case of something on my side. I also checked for held modifiers like Ctrl, Shift. The issue occurs intermittently and always disappears (fixes) when restarting the mission. With UH1-Huey, I did find that while the 'Communications menu' failed to appear, I could bring up 'Pilot's radio trigger RADIO'. I think (not entirely sure) that in the Mirage 2000, I was able to bring up Radio1, Radio2 when the Comms menu failed. This issue has occurred for me about 4 times ever so far.