Warsaw

Thanks Flappie!

Placing features/ targets (planes, ground vehicles, structures, etc) in Irag map in ME, all I get are red rectangles and no shape/image of the features/targets being placed. Even after zooming in, there is no shape or aerial image, making placement and adequate spacing away from other features/targets impossible. (ie placing a vehicle next to a C17). (Latest DCS update loaded 1-20-25)

Same issue here after 4-18-24 when I downloaded the last update. Before downloading the update, Nevada, Syria, Persian Gulf and Caucasus were all smooth. After update, Nevada, Syria and Persian Gulf went jerky, but Caucasus remained smooth and unchanged. (I am detecting a pattern with updates.... seems I take 4 steps backward each time I update the "improved" version. I am concluding I should just avoid them altogether.)

New to F-16. With hotstart mission I have created, the magnetic hdg tape (MHT) on the HUD is positioned at the horizon line. In Chuck's manual the MHT is shown in a lower position on the HUD. How do I move the MHT (down) to make the horizon line less cluttered when using JDAMS?

You might want to compare your settings to the settings Spudknocker posted on YouTube for 2.9. Your upscaling selection may be the issue.

@voidwrThanks for the screen shots. I had a few differences, but adjusted to what you are using for nvdia settings and still have stuttering going on in F-18 with radar on… pretty weird. Thanks for your response!

@voidwr, since you also have a 2070 super, and our systems are very similar, would you mind sharing a screen shot of your nvidia settings?

Take it from a fellow flyer with 3.6/4.2ghz/ i7-9700k/ RTX 2070 super with windows on a ssd and dcs on a separate ssd, but with 32gb. Even with 32gb ram, since the last 2.8 update flying the F-18 has been $hit (both stable and open beta) in nevada, carrier and caucus. For my system, F-18 radar is the issue. Turn your radar off and I’ll bet you will eliminate your issues with the game settings you have, but with a low terrain texture setting and a low visib range setting. (I have resorted to fly the F-18 with radar off… kinda like flying a really fast A-10.) I fly the A-10CII also and have seen no issues. You might consider buying another a/c (like the A-10CIi) just to compare performance, since your wallet is now in the drain cycle. Keep us posted.

Results…. I purchased a Crucial X-8 1tb portable SSD and copied my eagle dynamics folder from my 1tb HDD to the new SSD and changed my shortcut path to the new drive. Jumped in the A-10 to confirm everything looked good and saw an increase in loading speed. I then jumped into the F-18 and left the radar switch on. Stutters were totally eliminated. I then went back and cranked each DCS setting and flew both a/c to see if i saw any degradation. I am happy to report I am now flying both a/c at the highest settings and they both work great with better performance and no stuttering. My conclusion is whatever changed in 2.8, broke the limits on what my HDD could handle. Seems DCS on a SSD should now be a published Eagle Dynamics minimum equipment requirement. Flappie…. thanks for the help and resulting solution!

Yes i have confirmed it is f-18 radar causing my issues. Turning radar off results in elimination of stutters. Turn f-18 radar on results in stutters. Flappie suggested moving DCS from HDD to SSD and that will be tried once my new SSD arrives this week.

Match.... My issue occurs with F-18 single player saved missions that I have created over the past year. (I don't use instant actions missions, so I don't have any experience with issues there.) Had a user on Facebook suggest deleting FXO and metashader2 folders "to force dcs to recreate the caches". Did the delete and saw no change and waiting for any other suggestions.

After installing update 2.8.7.42718 (2Jun2023), my F/A-18C single player saved missions now have significant screen stuttering (in all of the 3 regions I own), while my A-10CII single player saved missions (in all 3 regions) continue to operate normally with no stuttering. Anyone have clue as to what I should look at or change to resolve this? (The previous version I used with no stuttering was 2.8.4.39731)

Issue has not repeated itself since the my August 4 post so I am chalking it off as a fluke.

In the 2.8.4.39731 release (5May2023), there was a fix listed "AI aircraft. Attacking AI's with GBU's stay on the attack course forever after bomb run - fixed." This release fixed the problem I was having in single player A-10C II with AI wingman assigned a bomb run using GBU-12s. After installing update 2.8.7.42718 (2Jun2023), attacking AI's with GBU's are once again staying on the attack course after bomb run. It appears the bug has found its way back into stable 2.8.7.42718 and needs to be corrected once again, like fixed in 2.8.4.39731.

In reference to my rogue AI wingman post of January 6, i discovered my A-10CII AI wingman goes rouge when they are attacking a target with GBU-12 bombs. After target destruction using GBU-12s, they fly off in the direction of their last target run heading, eventually declaring bingo fuel and then declaring ejecting. I have tested the AI wingman using AGM-65D and MK-82 weapons and they perform as commanded (Rejoin, Anchor Here, RTB), so I have concluded it is a GBU-12 bug that has showed up in v2.8 stable that was not in v2.7. I will update my ticket 134823 with this new information.

It appears directly in the 3D cockpit view for TPG on the MFD (I only use one monitor). Still doing it after my download of v2.8 stable on 12-30-22.

After my update to v2.8 stable on 12-30-22, all of my A-10C II missions in Nevada and Caucus that i created in v2.7 have wingmen issues (outside of ME). After they have destroyed a target they go flying off into the sunset until they declare bingo fuel and then eject. I have created a mission in v2.8 and same issue. They acknowledge a RTB or Rejoin command I send them, but fly off in a random direction at a constant altitude. I am also now experiencing support aircraft that sit running on the airport and never take-off in v2.8 stable (oustide ME).

AI worked great in my missions in v2.7, just seems some goblins showed up in v2.8.

I downloaded v2.8 stable on 12-30-22 and now on single player A-10C II missions I previously created using v2.7, my A-a10C II wingman goes flying off into the sunset after destruction of an assigned target. The wingman verbally responds to my Rejoin or RTB commands, but flies away in a straight (and random) direction and constant altitude, eventually broadcasting bingo fuel and later ejecting. The same rogue action is occurring in missions with a flight of 3 or 4 A-10CII's. The issue occurs in both Nevada and Caucus missions. I created a new mission using v2.8 and same issues. Attached is a track file showing the phenomenon. I have written a DCS ticket (134823) but have not yet received any response, so not sure what is happening at DCS end and I decided to post here to see if anyone had any input. Wingman goes stupid again.trk

Same issue here after 2.8 stable download. Any fix known?

Most of the missions I have created prior to version 2.8 for A-10CII include a wingman or a flight group. After downloading v2.8 stable, wingmen go rogue in all the mssions I have checked after target completion and go flying off into the sunset until they exhaust fuel and eject. They verbally repond to commands to RTB but keep flying off into the sunset. (They do not verbally repond to Rejoin commands.) Naive me... I thought beta versions were to eliminate basic bugs like this. I have attached a track file of a mission where my wingman goes stupid with v2.8 if anyone has any suggetsions for a fix. I tried to write a DCS ticket, but was not accepted since the form only gives you 2.7 stable o 2.8 beta options. Wingman goes stupid again.trk

After last DCS update I now have a flickering MCD screen when TGP is displayed on all missions on A-10CII.

Just loaded 2.7 and attempted to edit some missions i created in 2.5. The 2.7 “Mission Editor” selection brings up a screen with all actions greyed out except for EXIT. How do i edit existing missions in 2.7?

Is there a setting to have spawned aircraft in a mission leave their navigation lights illuminated? Currently I have aircraft that are spawned (at night) and after takeoff, their navigation lights appear to automatically turn off, making them impossible to spot.

How can I dim the NMSP indicators for night flying in A-10C?