Quetzalkoatl

The most important thing is that we're not getting something we already have in FC3. FC3 has 9.12, we're getting 9.12A which is slightly downgraded variant when it comes to avionics. And from what I know, countries outside the USSR that acquired it never had access to the R-27ER and ET. This naturally raises the question of whether they will be included in DCS, or if it will be limited to the R-27R and T variants, even though it probably could carry extented range variants.

Also, as I see others mentioning viewAngleVertical, it really seems to be the reason why it didn't work. It was absent in settings untill recent patch. And it doesn't look like RAlt+Num0 (save cockpit angles) can influence it. But changing viewAngleVertical to appropriate value 35.983398 worked... which I calculated for my 60.000000 degrees horizontal FOV for 16:9 screen with some basic math.

This method doesn't work for thing we have problem with. It doesn't set the desired FOV value for options [13] / [14] in SnapViews.lua - which are default view for head tracker users and VR users (the one that allows us to look freely in the cockpit) Values for default view that I've manually set in SnapViews.lua (60.0 degrees) are still ignored by DCS and it remains 78.8 degrees after pressing key binded to ZoomNormal.

Yes, it got fixed in 2.9.1.48335.

I checked if it could be that simple. I changed FOV value to 41.2 deg, so if DCS always adds 18.8 it would go back to 60.0. The result was 56.3 deg - which means that this time DCS added 15.1 deg. Whatever it is, it doesn't add constant value.

Can confirm the issue. I have custom FOV set to 60 deg. for all aircraft but after today's patch DCS sets it to 78.8 deg. Have to admit that it's quite annoying

Golden hint for new players: In case you want to exit F10 map, press F1 to get back inside the cockpit.

I'm sure it's not on my side. I am using GTX 1070, no any mods that would alter in-game graphics. I made a comparison video that shows the difference between liveries with and without mipmaping, I hope it would make it more clear what I am trying to point out.

Hey, that's not how mipmaping works. You won't see the difference when viewing from close up. Mipmaping makes livery to have several "layers", each one has 2 times smaller linear dimensions than previous one - and they are being swapped by DCS when viewing same livery from various distances. When livery file is missing a mipmaping then from farther distance it appears that some parts of it (usually details like lines, digit edges, small points) start flickering during camera movement. When watching your track file I can still see it very well. It's also possible to view it in model viewer. The fix is very simple, I can do it myself with use of free paint.NET... all it needs to be done is to resave files that have the size of 16 385 KB with setting BC1 (linear, DXT1) + generate mipmaps. After that livery no longer has those issues and its size matches other files (10 923 KB) that appear to be made correct way. It most likely will look different on professional software that devs are using.

I noticed that some files in default liveries are missing mipmapping which causes small spots and thin lines to flicker during view movement. You can see in this photo that nose section has those small white dots (and those are flickering), rear section doesn't have this issue as it has mipmaping. (Probably a video would show it better - for seeing the details please open this screenshot to the full size, dots I'm talking about aren't visible without it) Here are all livery folders with files that I suspect to be missing mipmaping (marked with see-through red) - they seem to have higher size than files with mipmaping. The fix is very simple, all that needs to be done is resave files - just now with mipmaping.

You completely missed the point of what I am requesting.

I'd like to suggest these to be added under Ka-50 III "Special" options tab: Cockpit Voice language: Russian/English ABRIS language: Russian/English After that there would be a possibility to fly with e.g. Russian cockpit, Russian Rita and with ABRIS in English.

Today's update fixed the issue. Thank you ED

There's another bug which coexists with one described in this forum section. Not modelled parts of the map appear black in spring and autumn months, but they look fine during summer/winter England, western map border May 31st And the same location but 1st day of June Here are screenshots from the same mission. Possibly those two bugs have common reason, or one is linked to another.

As F-4E is planned to be released in late 2022, I was wondering if it's still possible that two remaining variants of Tomcat (F-14A-135-GR (Early) & F-14A-95-GR (IRIAF)) would come before Phantom or I should expect them after F-4E release