Daemoc

TAA really does look better at higher frame rates. I used to cap my frame rate in DCS at 60 because that was the monitor refresh and saw little point in going over that. I have been using TAA and found it is much better setting my cap at 120. Resolution also makes a big difference. My sweet spot is 2560x1440 at 120fps. Anything below 60fps is going to be a blurry mess using TAA. I found native 2560x1440 with TAA looks better than my native 4k@66% with FSR. The FSR upscale looks a little better when there is no motion, but no upscale with TAA looks better overall IMO. Anyway, there are many versions of TAA, FSR and DLSS. We have what we have in DCS, but the rumor is once they switch to Vulkan we will have more options. nVidia users can change the DLSS presets using .ini changes I guess, but we AMD users are stuck with the default TAA for now.

Check this thread here... https://forum.dcs.world/topic/353993-msaa-not-workinghideous-shimmering/ MSAA had been having this issue for a while and it seemed to be wide spread.

I agree, I am just trying to help narrow it down. The fact that MSAA has been completely broken for a lot of users until the last big update is the probable cause. Whatever they did to fix MSAA is probably what caused this heat haze render bug for some. But we don't know if it is a DCS bug or a driver bug. A lot of these types of issues could be the result of a buggy driver. And while the DCS devs may have the ability to work around it, that may not be the ideal fix. Anyway, the more information we have on what hardware/drivers are having issues the easier it will be for whoever has to fix it.

My AMD card is working fine, what model are you using and which driver are you running? I figured it was an issue with the "Pro" drivers, but maybe it's more of a chip generation issue.

You do, in fact, have to make those particular changes before you launch the game. Some, like frame rate limits and such work on the fly, but not the above. That said, you only need to try the Anti-aliasing category. Ideally it should be set to "let the application decide" or whatever it says. Normally, you do not want to use the "override" or "enhance". Since using TAA fixes your graphics issue though, it might be worth a shot to try them all. Speaking of which, I know you said TAA fixes the problem, but what about setting the anti-aliasing to "none" in the DCS options? If "none" works as well, maybe setting DCS to "none" and you graphics card to "override" Multi-sample may do the trick? Tessellation Mode does not matter as DCS does not use it to my knowledge. I would leave it at the default setting.

Nah, Windows does not care that it is installed on a mac using boot camp. It is more likely the "pro" GPU. They use different drivers than the non-pro models. I see weird issues like this all of the time on pro cards and gaming. One thing you could check is if there is anything "over-ridden" in the control panel/adrenaline settings. Also, clearing your shader cache as stated above is a great suggestion if you have not done so.

Wow, that was unexpected. It does, indeed, actually work now. Thanks for the heads up, I had given up on MSAA and never would have checked it again.

Beautiful bird.

Yeah, you can clearly see the AA is broken in that video, but only on contrasting lines with a shallow depth. The outline of the F-18 in relation to the background looks like it is indeed working properly. I wonder if it is something as simple as a wrong setting or broken depth buffer?

The reason I mentioned that is I had the same issue with DCS and the Godot game engine a while back. I would get those same lines in both if I had enabled MSAA via the game or AMD Adrenalin. Godot has had a few updates since then, and DCS just flatout does not work with MSAA anymore using AMD. I don't know if that is a result of a DCS update or the newer AMD drivers. I suspect it was a driver change. I am half tempted to roll back to an older driver and see if I can reproduce it again.

I did dig up some modding documentation, but I have yet to really read into it. By trial and error I figured out what the "arg_value" is. It is which pylon style the station uses. The new rocket pods still refuse to fire though. If I had to guess it requires some information to jettison the rocket pod front caps on the first fire and the C-101 does not have that?

I must have missed a bracket somewhere, it seems I have it working now. Now on to the next question. Everything seems to load, but they do not fire in game. There are some values that probably matter, but I do not know what they mean. "arg_value = 0.1" is on the C-101 weapons and "arg_value = 0.0" is on the F-5. There is also a "rocket connector" on the A4 weapons that is not there for either the C-101 and the F-5. Also, thanks again for the help so far. If these questions are answered somewhere else, I don't mind looking it up. I don't expect you to hold my hand while I fumble my way through this. I do appreciate the help though.

Are you using an AMD GPU and do you have MSAA enabled by chance?

I would not go as far as to say I "love" the new flight model, but I have been using it since they made the change. It took some getting used to, but I am not sure I would like to be forced to roll back to the old flight model either. It has been a long while since I have flown the original, but I remember having issues with even getting airborn while carrying weapons. There is something definitely something off about the new model though. As stated, the anti-torque pedal/tail rotor is far to anemic IMO, and it does indeed seem to hit very high speed rather quickly. I am not a Huey pilot though. I have no idea which FM is closer to the real thing, but I suspect it is somewhere in the middle.