Daemoc

The C-101 can carry a ludicrous amount of fuel internally. One of it's major design considerations was range. I think this is the most overlooked aspect of this aircraft. For a quick strike mission, 50% fuel is still way too much. IIRC, one of the first missions I did in the C-101 was over two hours and was done on 50% fuel. This was all low level. This cannot be stressed enough. Fuel has to be a major consideration on that aircraft every mission. Don't look at the percentages, calculate the fuel weight.

C-101 +It is super stable, even at very slow speeds. Best out of the three for strafing runs. +Fuel for days. -Very under powered, especially if you load it down with fuel. ---It has the absolute worst sound in game. It is borderline unplayable IMO unless you mod the engine growl sound file. L-39 +Does not make your ears bleed. -Has a long standing cockpit model graphics bug. MB-339 +Does not make your ears bleed. -Way too unstable. The smallest stick inputs and the nose bounces all over the place. It's like driving a car with bad struts. Not great for gunnery.

That seems to have done the trick. Microswitch logic set to auto off and bound a toggle switch on my throttle quadrant for the microswitch on/off. Using the physical toggle switch lets me know the on/off position. It is much better now, thank you all.

This thread was a life saver, thanks for the tips. I just bought this module during the sale and I have been fighting the damn pedal trimmer for days. One second I am in a stable hover and with no input from me the helicopter yaws off into the next time zone. I thought I had turned off all of the trimmer functions like I did for the Mi-8, but I guess it works a bit different. Anyway, if i read this correctly, I want to set up the microswitch logic to auto off and bind a micro switch toggle button on my HOTAS somewhere? Is there an indication anywhere in the cockpit on the status of the microswitch?

I have both and use the C-101 a lot. It is one of my favorite modules. I spent a lot of time learning the mission editor and make my own content though. When making your own missions, the possibilities are endless. https://www.youtube.com/watch?v=-2ez7Bltb9M But yeah, if you are looking for official/unofficial missions, there is not a lot of content out there.

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?