Quetzalkoatl

I've just tried fast repair and it brought back Marianas for me. Thanks for the fix.

I can confirm the issue. I had Marianas installed earlier, didn't uninstall them. For some reason map disappeared from the game - can't find its files in DCS World\Mods\terrains. Fast and slow repair doesn't bring it back. It doesn't display in module manager as "available for install" - launcher on the other hand does. When trying to install it via launcher there's same kind of error as in the message above.

It looks like multiple trees disappeared between Folkestone and Dover in the most recent feature update. Texture in this area indicates that it wasn't a grass only land in previous patches, I guess (and hope) this wasn't intentional. Here's a picture from teases before the release where you can see that trees are present in this area:

I can give you a direct link to the post with my Mosquito

Quetzalkoatl

I own Syria already and I was looking to get Sinai at some point, but what happened last patch certainly makes me reconsider those plans Honestly... both of these maps should have full Israel territory, and because Syria would go farther north and Sinai farther south they would still serve different purposes.

Quetzalkoatl

New Ural 4320 model seems to have an issue with one element of its chassis - I'm fairly sure this element should be stationary. Here's a short video:

Quetzalkoatl

Quetzalkoatl

Quetzalkoatl

I'll throw some more screenshots I think it looks amazing now, although there's one more thing left to do... External liveries need to have it updated, different colour on the padding may be enough:

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.