Czar

A supportive argument: It doesn't have air to ground (not widely used) so it can make up for it with these variants.

It has been stated on few pages back on the beginning-ish of the thread. The team that would be working on a FF Su-27/30/35 is busy with the MiG-29. Likely in the future.

I'm more inclined towards cold war stuff, so I have no interest on the 35 (I'm never saying 'never on this, though). I but I have to say that it is really an exciting moment seeing DCS World from its inception to a F-35 being announced. Feels surreal. I wish ED the best of luck on that endeavor. This comes from countless hours of fun throughout the years DCS has provided me since A-10C early access. I just had to post it.

Yes. This is the info I was after. Thanks for clarifying! Many don't do it.

Wait... ...so the shaders does rebuild themselves up or this is unrelated to the ones inside FXO and Metashaders2 folders? You didn't mentioned that you delete these two folders at every patch on your comment. I'm familiar with the difference in load times after a major patch. I was referring to the load times after those two folders are deleted. Which for me is very close to the same results as having them compared to a previous boot on the same version build. We might be talking about different scenarios, so I just want to clarify stuff. No intention to make prolonged arguing. For me, the way things are with the shaders is a non-issue.

I haven't noticed it at all on a NVME and I don't remember it on a sata SSD. Non issue, maybe? I'd chose a compulsory shader rebuild at every DCS update, than having to face stuff like this from time to time.

Enable "G-Forces in cockpit" on DCS options. It can help a little in a few occasions, if you haven't.

yeahh.................To be fair, ED changed a whole lot on shaders when adding the fog and I only think a couple of times of this fix being actually useful before, beyond placebo effects in 12 years. I'm glad this fixed it for you. I agree on shaders being rebuilt on DCS updates. It has no major effect on performance the first time it is built anyways.

@VampireNZ I had this. I fixed it with deleting the FXO and METASHADERS2 folders inside 'Saved games/DCS'. <OS drive>:\Users\<your username in your machine>\Saved Games\DCS The issue never returned.

Well, if anything helps, excluding the saved games folder (Shaders and scripts) from the equation can be a good thing if you perhaps haven't done it so already. Maybe it's something else is delaying the DLL loading and it is in that folder. Rename DCS folder in the 'saved games' folder to something like DCS.OLD so you can keep your stuff instead of deleting it. Copy and paste your inputs folder into the new one DCS will generate after a single boot (or you can manually make a 'DCS' folder before launching the sim) so you can actually fly. Should look like DCS/Config/Input. If you never see the issue again, might be something in that folder indeed.

Looks like many of you would not survive DCS A-10C and Ka-50 early days.

I'm not going against OP, but you know you made a good product when the complaints are for something so......... small. A change in material for the HUD's emitter lens similar to what the F-16 module from ED would be nice, but that in no way affects my experience. I didn't realized it was a texture from a photo until now.

A few tours for the curious. A couple of videos from the latest update with the winter textures in 2.9.11 and another one from the previous update in 2.9.8.

Thank you silverdevil, I'll do that.

As Phantom711 pointed above. ATFLIR is for carrier ops, Litenings are usually used by USMC and foreign forces to the US in airfield based ops. If you want to follow historical realistic payload, use ATFLIR on carriers and Litening for everything else. Litening pods internals are not rated for carrier ops, literature on this is on the internet and perhaps in the manual, but you're free to chose. Back to the HUD and HMD symbology, I guess that is correct about the LITENING on the Hornet as its operation differs from the ATFLIR in DCS. IDK about IRL, but the focus is to get going working in the sim and to clear confusion.

Time stamps added. Yeah, the ATFLIR is a tad different but you just want to follow the caret/diamond to check if it is ground stabilized or not. Once you get going with it, it's hard to forget, no worries. IDK. That's something to check out. Just to get something added to the actual plane the thread is related. On the Viper, there is a constant designation/nav shift whenever you move a sensor, hence the need of the CZ. Which is completely different from the Hornet where your plane creates a new point, hence why it is a bit misleading when using the same workflow on both.

Oh no! I disagree the thread can be closed. The issue still is present. The noise still there and the sharpening filter is needed for the temporal and upscalling techniques! There is a new noise introduced since the fog update that degraded image quality by quite a margin. The sharpening filter just makes it more apparent. Right now at video editing. The noise making an apparent unwanted pattern shown on the water area at the bottom left. This effect shows on several other occasions and not only on water.

If you're reffering to the TGT diamond, half correct. Once you press TDC, the diamond is updated live and as you slew the TPOD on both. the HUD and HMD. If you press 'undesignate', it goes away. Here it is how it behaves on the HUD and after pressing 'undesignate' removing ground stabilization. Time Stamps: ATFLIR on right DDI. SCS to the right to select the right DDI. 0:00 ATFLIR is ground stabilized with TDC press. 0:12 'undesignate' button is pressed. ATFLIR is not ground stabilized anymore locked into an azimuth/elevation in relation to the plane. Cross symbology is shown. 0:22 TDC is pressed. ATFLIR regained ground stabilization and a new TGT is set. 0:25 'undesignate' button is pressed once again and TGT is lost. 0:28 looking to the right with the HMD. 'SCS' Forward to bring up the aiming reticle. 0:29 TDC is pressed and a new TGT is set where the HMD reticle was and the ATFLIR is pointing right at it. 0:30... further slewing of the ATFLIR.

My F-4 is activated at this moment. No issues. 1-Make an exception on the whole DCS root folder on your anti virus(es), including windows defender. Authorization files are being wrongly flagged as threats for a good while. (issue not exclusive to DCS). 2-verify/repair DCS (fast method).

If you disable DLSS and only run with DLAA, does this pattern you got becomes thinner and less obvious just like what it shows on my screenshots?

Hey, Lord_Pyro. Are you using DLSS or any upscalling tech by any chance? If you use DLAA, does the issue exist?