DimSim

I thoroughly enjoyed the campaign, thanks Baltic Dragon. I think you did very well with the balance and pacing. It's refreshing to NOT be the one hero to save the world, but part of a flight package with mixed abilities, playing a part that suits the aircraft. It is sadly easy to break the scripted sequences, which either kills immersion or handicaps the mission entirely. I also loved not being forced to refuel, disable sim assistance settings, or play far beyond my ability. I didn't realize how important it was to actually form up over Sally. In early missions, I didn't attempt to fly formation or match speed which missed some triggers. Your radio methodology was workable and somewhat enjoyable. I wouldn't mind it either being more forgiving, or somehow allowing the player to figure out what channel they should be in, if they missed a message or trigger. For example, a warning to switch back to a channel before the message, or a message saying 'you are missing a radio message on channel 7'. I realize you kind-of do that already for most major messages. As there is no chat history or logging system (for this purpose), it is still easy to miss something and there is no 'repeat last' like in real life. There appeared to be some inconsistency with ATC pattern. Some missions had departure messages, others not. Sometimes the tower or ground would not respond near or after landing. At least once we had to use the F10 menu for this, while normally it was radio + space. Just a bit confusing. I hope you and DCS developers continue to find ways to make missions more robust. Overall great effort. I'm looking forward to trying your campaigns for other aircraft. This was my first fixed wing craft.

I use two directions on a main thumb accessible hat on throttle. It kind of wastes that hat, but I zoom so much, it's critical to me. So Hat is Zoom In, Zoom Out, Zoom Normal leaving two directions for other things.

I'm stuck at the gazelles as well. Last think happened was Max reporting wingman down, not sure if he's down yet himself. Nothing happens after that. Everyone else just circling around. After 10 mins circling I tried shooting the gazelles in attempt to progress mission, they dodge everything I fire at them, they appear invulnerable. EDIT: Repeated the mission. After reading all the posts above, decided to anchor 15 miles from Wpt3 until Noble completed. This time Max did finally get hit and Noble did continue. With JTAC, I requested laser on and instructed wingman to attack objective. He said 'roger', over flew objective but did not release bombs. I then bombed 2x successfully and thankfully with F10 menu reported attack completed, which allowed mission to progress further. Opportunity to attach choppers occurred. I said 'attack together', however choppers were destroyed by A-10s or other either immediately or already. Anyway, enjoyed the mission despite glitches.

Thanks for responding. I just re-tried Mission 13 via the editor to check. Couldn't find obvious alternative radio freq in the knee pad except for 255.30 in on one page. No one responded on that frequency. However, Wingman 2 did respond to both Flight and Wingman 2 from Red radio on 1 while parked at the start. So I guess the radio must have been silent later in time when I actually played that mission and needed wingman comms. During that mission, wingman was silent, but did drop his bombs, so I think he got the message.

I'm having trouble getting wingmen to respond to Radar On and Engage Bandits. First bunch of missions, it seemed to work fine, after about mission 10, I haven't been hearing a response from them. I'm not sure if they are engaging or not. Definitely not in some cases, definitely once in one case. I normally do this: Dial 1 on red radio Press transmit on red radio Select comms menu Wingman 1 -> Radar -> On (or other) If that fails, I try combinations of: Dial 1 on red radio Dial 1 on green radio Press transmit on red radio Press transmit on green radio Use communication short cut (instead of transmit red / green) Select comms menu Wingman 1 -> Radar -> On (or other) Select comms menu Flight -> Radar -> On (or other) And still silence. Tried this directly after all airborne, and at other times during the mission. What is the optimal way to get wingmen involved in the mission?

Since the latest update (I think), the way point HUD indicator has been jumping around for me. In the attached screen shot, the indicator jumped from the center to the right. I tilted toward ground so the ground marker was visible in the correct location. This is intermittent. The marker sometimes jumps away to the side for only a few seconds, then returns to the correct location. It may do this just a few times per mission. Beta 2.5.6.57264

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

Confirm this bug still exists v2.5.6 beta channel. HSI VAD selector - turning selector left or right always increases the value Track attached m2000_hsi_vad_sel_bug1.trk

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.

Repro track attached. m2000_lighting_bug1.trk

I can confirm this issue is still present in the latest OB version. It is 100% reproducible and easy to do so.

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.