Aurora juutilainen

affirm, weather in MP but not the SP mission I tested, I assume it is a bug that the system does not correct for wind since it already knows wind conditions.

Not seeing anyone else mention this but I seem to be able replicate the issue consistently. AUTO GBU12 drops in single player are perfect AUTO GBU12 drops in Multiplayer - first drop and the bomb falls in the correct direction - all of the following drops miss the TGT designation point roughly 5 miles to the left of the target every time Anyone notice this issue MP as well?

Having the same issue, unable to contact ground crew more than once. After the first time the comms menu does not show up

Performance definitely could use an improvement On a totally empty mission Fps drops to around 70-80 in city areas, choppy and sluggish feeling I can imagine it being a lot worse with AI and ground units 2D I9-13900K 3090 64GB DDR5 980 PRO M.2

Still have issues with DCS and GPU usage dropping relatively frequently, none of the other graphically demanding games I play have this issue.

Wow that fixed the second issue, thank you a lot!!! I'm curious how or why but either way glad that part has a workaround. The original issue in the first post is still present and I can replicate it consistently by placing my camera exactly where it is in the screenshot for anyone that wants to have a crack at resolving that issue.

This is mildly frustrating to troubleshoot I can free camera look around sometimes and the usage will stay high and FPS 100 if I look up at the sky the usage drops and fps locks to 65 the problem is sometimes usage and fps returns to normal by looking back down but it mostly just gets stuck this way half usage and 65 fps both on Caucasus map and Persian gulf

In regards to the OP I have ruled out track IR and alt+enter

green is far away from the player airfield in the attached mission yellow is when I am looking at the airfield and move the free camera closer to it red is when I move the free camera even closer to the airfield as for the fps locking to 65 sometimes on Persian gulf I have no clue CPU is not downclocking and staying around 5GHz temps seem stable for both GPU and CPU 16 mavs.miz

I have ran a clean/full repair on DCS and played with graphics setting in both DCS and NVidia but still notice this bizarre behavior on the Caucasus map when I look straight fps and gpu usage drops down to 50-60 then jumps back up, like it will count backwards from 100+ fps down to 50 then jump back up consistently in intervals, just up down up down over and over persian gulf will sometimes just get stuck at 65 FPS with lowish usage and stay there, like when I look out at the water or up at the sky, and will even stay at 65 after I look at a city for a bit, then eventually it jump up to 80-90 when looking at said city Ive tried turning off gysnc, changed my refresh rate from 165 to 144, turned off trackir, disabled 2nd monitor So far it's just DCS, other games I have tested do not do this

SSAA on or off doesnt seem to change much FPS drops still show up tied with GPU usage So far just a DCS issue

When look at the horizon I get consistent and repeatable frame rate drops and GPU usage drops in tandem (see screenshot) When I look straight down at the ground for example FPS does not drop, and gpu usage stays around 96% I tried turning SSAA from off to 1.5 to try and put more load on the GPU but this does not change the results and got the same ups and downs as the screenshot. Any Ideas? i9-9900KS 32GB RAM 3090 2560 x 1440

Someone more experienced than myself might could confirm this but I noticed that you entered the MAGV which should not be required, especially with a hotstart as I believe it is already setup, also the passes seemed kinda low and steep when you take into account the burst altitude of the cbu's.

I am unsure if this is a bug or improper release parameters, I cannot find anything in the manual stating this is the latter. Rippling 6 to 12 MK82SE's with spacing below 50ish feet sometimes results in them exploding in mid air thus destroying the aircraft that dropped them. Attached is pair and single releases with 10Ft spacing, these results are relatively consistent, spacing them out more will lower the frequency of mid air collisions. Again this may be an improper release setup on my part, I was unable to find anything that confirmed this. Thanks, Aurora SE single level.trk SE pair level.trk

Thank you! I believe this fixed the alert.