Saruman

Nice thanks, Flappie. I'm curious. Do you know if it happens because of some graphic settings or only on certain videocards? Because a friend of mine does not have it (he's on Nvidia, I'm on AMD).

1) MT, I did not try ST. 2) No mods installed at all, I never use them 3) Yes, fresh fxo and metashaders

Hello, since latest update, flying during night, it seems light sources create some problems. This is how I see the light coming from a ship near the carrier. Same problem when flying above random urban cities, if I look towards them. Syria map, by the way. null

Cold and dark on carrier, carrier doing its own straight route, ground crew screaming "Hey what are you doing" all the time, at random, when you request rearm and refuel with airplane still off. Now, I'm happy about all announcements in "2024 and Beyond", wonderful, I love you and your efforts and will continue to support them, but could you address core's fundamental issues first of all? Let me say this one does not seem too difficult to solve, I don't know DCS' code of course but I know coding and it would require perhaps a couple minutes to tell DCS to consider F18 cold and dark stick and literally glued to carrier to avoid it. Please, do not ask me for tracks. You know problem is there, you just have to put one carrier and one F18 in a clear day with a bit of windgust and ask ground crew to rearm and refuel,. This issue exist since years, yet it's not solved. And it has consequences, because if you take off ignoring all the "Hey, what are doing" screams by ground crew, your weapons are probably unwilling to detach from pylons when needed, so....

I can confirm, I found this thread while looking if someone had this same problem. I was flying F18 and exporting AMPCD to second monitor. It only happens during night missions and, for me, only since latest update. Flickering is not terrible or continous and not very noticeable in my case, it seems like a quick monitor refresh every 40-50 seconds and only on the second monitor (the one I usually export MFD to).

Yes, I watched the videos thanks, and I'm doubtful whether I should add Awacs to donors on mission editor for every flight. It seems like it flashes on SA/HSD page of I don't do that? Inviato dal mio BLA-L29 utilizzando Tapatalk

About new datalink features: do we need to add Awacs as donor in mission editor for any group or will Awacs be added as donor in any case?

@Braunn In my case 7900XTX does not become really hot because I don't use Zero RPM and I set fan curve, so junction hottest temp in DCS is around 60 degrees, but as I said I'm CPU bound (old Intel 6700k) and I have an old 1080p 60hz monitor, so GPU workload is low anyway. I use Radeon Chill to have between 100 and 120 FPS because I can reach over 200 fps in DCS and therefore fan noise from GPU can get a bit annoying. You know, I went for the Sapphire Pulse, because the Nitro+ costed too much more (+150 euros), and fans on Pulse are a bit noisy if they spin over 1800 RPM (at maximum 3200 RPM they are a proper tiny jet). Back to the matter of the topic, I tried TAA but it's disappointing, whether you use it with FSR or not. Too blurry aliasing and tons of ghosting. If you really need extra FPS and have a compatible GPU, you could take some risk and try the new frame generation tech provided by latest preview drivers from AMD (you could enable it in all games, even the ones that do not support FSR). P.S.: I know 7900XTX is overpowered for my current build. I'm going to upgrade rest of my rig in a few months of course, I bought 7900XTX because I had a 10-years-old Nvidia 970 and decided to start upgrading by changing GPU first of all. Inviato dal mio BLA-L29 utilizzando Tapatalk

Because flight could belong to a public server with tons of F16/F18. Inviato dal mio BLA-L29 utilizzando Tapatalk

But the fact that DCS would not generate a kill event at all is not. It's relevant for scripting, whether you use DCS' own SSE or any other scripting framework.

Don't name Moose or they will never fix it, but will take shelter into the usual "We do not support external mods/scripts"...

As per object, TAA + FSR draws only half of my main screen (I have 2 monitor, the main one and a little 10'' one I use to export one MFD) Cockpit bar, in the lower part of monitor, is correctly drawn for all the monitor size though (see second image). EDIT: Just to be clear, it only happens in 3D. Main menu and mission editor are ok, before you enter pit. null

No problem here with 7900XTX, but I do not use FSR (I dislike upscaling). FPS went even higher on their own, though I set all on high/ultra and max values. But GPU load went higher too (from usual 35% up to 70%, I am CPU bound). I'm on latest stable driver and no AMD's tech enabled besides Radeon Chill (to limit FPS to 120 to make GPU stay more cool, I have a poor monitor) Inviato dal mio BLA-L29 utilizzando Tapatalk

After latest update, I self-killed twice when 120C left the rail. I might be doing something very stupid, but I am not maneuveuring in A/A in a different way I used to before latest patch. Missile leaves the rail, lofts in front of the plane then it does not gain speed and you overtake it at 1.10 Mach. It should accelerate a lot faster, otherwise you could not fire it while supersonic. Attaching last tacview file. Tacview-20230903-140102.acmi

Still an issue. If clients are bugged (usually, the first client taking a slot on dedicated server), in MP tankers are all 1-1... If you leave, and reconnect, radio comms are ok, but callsigns on F10 map are not.