Daemoc

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.

Aye, I have messed with Lua before. On to the next stupid question. So the .lua pylon hack works with some weapons, but not all. It seems to only work with weapons that are noted with long serial numbers. (maybe not all, but the ones I have tried seem to work) Some of the weapons are just called out as the weapon name, eg "LAU3-MK5" which does not seem to work. Is there another internal weapons table that the F5 is calling on internally that the C101 does not have access to or something? I also looked at the A4 mod for another example, but it also just uses LUA3MK5 rather than (1F3JD8DN3JSDN3UDSS-3WMAJMSJDKJ) like some do. Am I missing something or should the "named" weapons just work as well?

Right. A persons will to have their privacy respected is because they have something to hide. I suppose you would not mind microsoft filling your home with microphones and cameras either then? I mean, you have nothing to hide right. They are only going to use that information to better serve you as advertisers will know better what to sell you. Sounds like a win for everyone. It amazes me that people will gladly pay for that privilege. Some people like to be bent over I guess. Not that there is anything wrong with that. You do you. Anyway, back on topic. I don't necessarily need Linux "support", but it would be nice if they made an attempt to keep it proton friendly going forward.

Awesome, thanks for the info! I had no idea where to even look, but this gives my a place to start at least. Thanks again.

It was worth a shot anyway. I use Track IR, but I have never tried 1080. I could see how the lack of pixel information would compound the issue.

How hard would it be to add the F-5E rocket pod options to the C-101CC? I have modding experience, but not with DCS. I have no interest in learning C++, visual or the Russian language, but I can do a bit of scripting. I don't mind doing the work, but would this be something that is easily doable, or are we talking rewriting half of the Library of Congress?

I noticed MSAA broken on my AMD card quite a few updates ago. I don't remember exactly when, but it has been a while. ReShade is another option though. You can use a version of DLAA through ReShade that has no ghosting, but it does soften the image quite a bit. You will definitely need some form of sharpening as well. I use personally use DCS TAA with no sharpening and the ReShade "AMD FidelityFX Contrast Adaptive Sharpening" with the "Contrast Adaptation" and "Sharpening intensity" both set to "1". That is the best sharpening option I have found that does not over sharpen and cause random pixels to pepper the image. As long as you have a decent framerate, the TAA ghosting is not as noticeable. It is still there obviously, but not a game breaker. I dunno, I guess I would rather deal with a little ghosting than the flashing pixels everywhere, but YMMV. As far as enemy spotting using TAA, I found it is best to use the 2x pixel dot option in DCS. Especially at 4k. The dots are impossible to see otherwise. This is no fix the MSAA bug, but I thought I would post what works for me on the off chance others might find it useful.

I just noticed this the other day. I don't know when it happened, but there is something wrong with the 30mm/50cal gun pods and the upper landing gear struts/arms. I only noticed this on the USAF skin, but it may affect more?

I pretty much stick to SP for that reason. I play to have fun and have an immersive experience. I have not played DCS multiplayer, but I used to play multiplayer games in the past and it's just not worth it. All of the bickering, accusations, little kids blowing out my speakers screaming in their headsets... ...yeah, no thanks. Anyway, back on topic. I would say the spotting dots are not ideal at the moment, but I am not sure what the fix is. I have just been sticking to 4k because I can't see the dots anyway.

To be fair, to say I can see the dots easier at lower resolutions does not necessarily mean an exploit. This is just what I have experienced during different missions. I have no idea at what distance those targets have the larger dots appear compared to the 4K native. I have not tried to replay the same missions and analyze every pixel at x miles. The sad truth is though, most of the "eye candy" options make it harder to spot everything period. TAA at high frame rates looks great overall, but the temporal aspect of it makes fine details hard to see.

I would not say "it works", but I do not see what the VR users see. 2D at 4K, I can not see anything. The dot's are so small, they might as well not even exist. There are very rare occasions that you may spot a dot in a clear sky, but it's rare. Using MSAA vs TAA helps a bit, but not much. I am using a 48" Samsung 4K TV for a monitor. If I drop the resolution to 2560x1440 and turn off TAA, I can see the larger dot squares much like the VR users describe. With a single aircraft it is not so bad though. It is REALLY noticeable in large formations at specific distance bands.

Yes, I am only having issues with the replay tracks. I watch the replays of about 90% of my flights and never had issues like this. I mean the replays do break a lot of times, (as in not represent the real flight), but they always open and play. This only seems to happen with the CH47 and it only seems to error out like this on the longer missions. That last part is just circumstantial though, I have no real way of proving it. The replay tracks do work using the CH47 sometimes. But I never had a replay track fail to load using the Huey or other modules. (I fly the Huey the most, and pretty much daily.) I am at work at the moment, but I will play around with it some more this weekend. I only check the logs when I have issues, so I will clear them and take a look after saving and replay a Huey track or two using the same mission to see if I get the same type of error in the log. BTW, are those CH47 debug controls entries normal, or is there something wrong with my control setup?