DimSim

I was a bit confused by the radio comms also. At first I thought Saint would perform all comms or it would be mission scripted. After some silence I tried contacting ATC manually. The second confusion was being told to switch Marshall then Tower. The kneeboard lists both Marshall and Tower as different frequencies. Marshall responds (I think), Tower does not. The Mission 2 kneeboard simply lists Mother, which works.

Just reporting. Not sure if I accidentally pressed some key. Immediately after Mission 2, I see a message box "Can not open debriefing file" and blank debrief page. Thankfully I could still End Mission and record success. Never seen this before.

Please see attached image with circles. The flat colored cloud or fog regions were flickering. A bit like a shimmer or high frequency flicker. This is with latest beta 2.7.x. However I do recall something similar with v2.5 before recent clouds. The region in question may be fog, not clouds. Both times this occurred the flickering regions were appeared like a flat color. Pausing the game still flickered. nVidia RTX 2080-S DSC 2.7.1.7139

Thanks. That was it. Surprised I didn't notice when attempting auto with manual flight. I do notice it's a bit finicky and can turn itself off if it doesn't thing the sequence is perfect.

Thanks for replying. I'm referring to ready made missions both bundled with the F18 and user made ones I've down loaded. The waypoints already appear in sequence, the SEQI button shows lines connecting them. CPL steers toward the current one. If I don't advance with UP arrow button, the aircraft will reach waypoint then steer in circles. Just can't get AUTO to box.

New to F/A-18 here. Trying to get the active waypoint to advance automatically when I fly past or use autopilot CPL. The AUTO button on HSI will not select for me like the guide and Wag's video show. I have googled but don't see any discussion of it not working or common user mistakes. What am I doing wrong?

No, learning and flying them one at a time. But, recently learned and flew A-10 and enjoyed it a lot. Just finished excellent Enemy Within 3.0 campaign. Definitely a great plane, very mature and featured and unique CAS missions with HOTAS experience. Not to mention a very big gun.

Allow modifier button alone to act as Finger Lifts. It can be inconvenient to dedicate a button to act as Finger Lift(s) to move the throttle into after burner zone etc. It would be great to somehow allow the axis to be restricted or not entirely based on on of the existing modifiers. This should feel very natural to have restricted movement or full axis movement based on a modifier. It's quite possible this is a limitation of the DCS application.

Just finished The Enemy Within 3 played for first time with DCS v2.7 and A-10c II. That was an awesome, immersive and memorable experience. Well done Baltic Dragon and all contributors to the campaign. I don't know if there was a The Enemy Within 2 or 1, but the campaign felt quite polished both story and play through. Probably the most stable campaign I've played. Perhaps starting this late had benefits? Using the helmet sight and A10 v2 was great. Errata: Coming from Red Flag Mirage, I initially wasn't aware there were no radio messages to start the mission, just get going when ready. That made me late for the stadium fly over, but the crowds didn't mind. I never got ILS to work even once. Used TACAN and eyeballs. Mission 20 was the only one really needing it. I ended up landing on the taxiway. Made a test mission for Kobuleti and it worked fine. Not sure why not in campaign. Some further tweaks for v2.7 would be nice, as per other thread. DCS needs to improve AI. My wingman often didn't return home due to controlled flight into terrain. Otherwise he made it to the runway only to crash on landing or land and drive through fences and trees.

Same here. Came here looking for answers.

Just finished Mission 18. I enjoyed it a lot, but it was much harder than it should have been... My wingman crashed into a mountain early on, offering me no fire support. The F16s were on F10 call but didn't hit anything thought they did respond in the affirmative. The relieving A-10 flight on RTB did not attack anything (likely by design). So it was all up to me. A very target rich environment. However, There was >50% cloud cover over the AO, so I had to make many passes overhead to try and spot things and laser bomb. There were a number of time limited events which I could not keep up with. The TGP has changed over time and is much more difficult now to locate vehicles near trees and buildings due to lower contrast. The mission takes place in the dark of night. However night vision has changed over the years and is much much more difficult to use. I could not confidently fly low except briefly along lit roads or I'd crash into a mountain. I'm attaching two images, one from a YouTube of someone playing in 2019, one from me in roughly the same place, but actually from Mission 19 since I didn't take a shot during 18. Mission 19 Is actually clearer and has less cloud. Source of 2019 screen shot: 2019 screenshot. My screenshot (May 2021) With cockpit lights dimmed below what I'd normally use and NVG brightness adjusted for max contrast:

Argh, must remember to re-apply bug fix after every DCS update. Just finished a 1.5hr mission after a repeat, no end mission. Checked and recent patch 2.7.0.5659 had replaced with original version. It would be great for a dev to acknowledge this issue or better accept the fix since it's just moving a null reference check, which at worst can't hurt.

@BalionGreat, thanks! That's why I couldn't find it with Search, it's being moved out from every aircraft to a new sim-wide location to affect all aircraft. Not a bug, this topic can be closed.

Just updated to DCS version 2.7.0.5659. Time Acceleration / Decelerate appear to be missing from control Actions after latest patch. Appears to be DCS A-10c II and original (Also AV8B, M2000C and perhaps a few others, but not all others.) Can anyone else verify reproduction of this issue? On further investigation, I see DCS World\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick\default.lua no longer contains bindings to iCommandAccelerate etc. like the other aircraft. If I manually copy those lines from another aircraft I can work around the issue and restore time accel.

@baltic_dragonThanks for commenting. I've now completed to mission 10, and so far there have been no serious issues relating to the clouds. The clouds have fairly well matched the mission description and expectations. At worst some minor tweaks to cloud density or elevation could help some target areas. As for dialog, twice the dam / reservoir was mentioned as scenic view, but with 100% or near cloud cover at that flight leg altitude, was completely occluded. Wingman has called out spotting targets covered by cloud, but he may just have super binoculars!

Thanks for responses. I just finished a new mission, ended well, however I did try Buzzline's fix since the code change looked completely safe and reasonable.

I haven't re-played my endless mission. Instead I edited my log file to skip it. I also haven't flown another mission since. Does this bug affect ALL subsequent missions, or just some, so playing the same mission is likely to fail the same way?

I'm playing the campaign for the first time, and with v2.7 clouds. I wonder how it compares to the earlier versions and clouds. Wingman: "Look at the dam down there" Me: "Nope, just clouds" Mission: Keep above 16k feet to avoid MANPADs Me: Circle at 9k feet to be below clouds to see the ground and target anything. Up to mission 7 now, and enjoying it, but I sometimes wonder how compatible the clouds are and will be with the mission designs.

@wowbaggerYou're right, there is new behavior, cycling instead of toggling. I think this is kind of an improvement but I wish: 1) There was separately bindable Cycle vs Toggle actions. 2) For this, and any similar setting, I wish there was a text log or visual indication of what changed. Depending on what units are on screen and at what distance, it's difficult to tell what mode is currently selected.

I'm not sure if this is the same issue being discussed, but I want to set Presets from the cockpit at start of mission, NOT from mission editor. Following the guide, I do this (with VHF radio) 1) Select MAN 2) Set frequency 3) Set Preset slot 4) Click 'Load' button (To save! Tooltip shows 'Load' but no click or visual affect occurs.) (Later) 5) Select PRE 6) Select Preset slot 7) Attempt to transmit But the preset does not appear to be saved, so I must manually enter frequencies throughout flight as campaign missions don't have any presets configured.

Same issue for me finishing A-10 Enemy Within 3.0, Mission 6 I may have seen this once before a year ago. On the debrief screen I did click a couple of filters to see if my aircraft had taken a hit. The display did hang at one point, but otherwise the debrief screen and buttons appeared interactive except clicking End Mission had no effect. DCS 2.7.0.4625 logbook.lua debrief_bug_no_end_mission.log

It appears SSAO is now in the options as of v2.7 It would be nice to know if it only affects scenery or also cockpit, and at what performance cost. EDIT: Tried it myself. I couldn't visually tell the difference between on and off. Would need to take screen shots to compare. It did appear that FPS dropped from 105 to 95 with it enabled over a city area I repeated.

Probably of no help, but... Have a look in C:\Users\NAME\Saved Games\DCS\Config\Input to see if you have input configuration files containing anything recognizable. Have you switched from Normal to OpenBeta using the non Steam version? That will use a different config folder. Have you updated the firmware of your joystick so the device name has changed? (This can't affect keyboard or trackir, which you say are affected.) Did you wisely have an automatic backup system to locate an earlier version if your config files did get corrupted or deleted?

I relate to the OP. I've flown the Harrier for quite some time but only just started learning the A-10. I'm finding the A-10 easier to understand and more reliable to operate sensors and weapons. I say reliable because I still find the AV-8B sensors sometimes behave as if frozen until I reset them.

I think this was the thread and post that helped with the HUD marker or SPI: