Ironhand

I don't know. When you set similar lighting and contrast conditions, it's not all that different: Given that the Caucasus climate runs from temperate to subtropical to glaciated mountains, it'd be impossible for one set of seasonal trees to cover it all, as draconus notes. So compromises needed to be made. My "complaint" would be that autumnal leaves remain on far too many trees. But I don't imagine that's going to change anytime soon.

It has everything to do with AI FM. The new General AI FM will replace their current FM with one which is realistic. Currently they can defy the laws of physics. And this is based on what? Just curious.

I think the easiest way to load the skin will be to add it to whatever folder modelviewer2.exe is already at for that aircraft’s skins. Obviously, the above mofication instructions no longer mirror what is currently in the lua file.

According to your screenshot, you have the right and left engines tied to the Warthog throttle. Remove those and see what happens.

You won’t see it for at least as long as Russia remains Putinesque and, then, several years beyond.

Excellent!

Left to right, top to bottom. Attitude Hold :: Route Following (Enroute/Return) :: Emergency Leveling Mode (Panic Mode) Barometric Altitude Hold :: Landing Mode :: Radar Altimeter Hold There’s also Combat Steering Mode, when in A2G and a target or terrain point is locked on the Shkval. The АУ-МАРШР-КВ buttons will be lit. More detail is provided in the manual somewhere around pg 20, I think. Edit: Last time I checked, Landing Mode is still bugged. Don’t use it unless you like crashing. This is true in all FC3 aircraft as well.

My mistake. They’ve added a VR section to the options.lua, since I had last checked one. I was thinking it was only there, if you were using VR. But that section is there for every track regardless. Hope a repair does the trick.

Very strange, indeed. If I take over your track right at the start, I have your issue. If I start it as a mission, there are no issues. The AP works fine. I notice that your voice warnings are in English. Is that selected in the sim? Edit: So clearly something on your end is amiss. If I start it with your settings, etc (in other words, play it as a track file), the issue persists. OTOH, if I start it as a mission, there’s no issue. I tried some edits to try and pinpoint what it might be but, so far, no joy. But it definitely something that would get saved to the track file that’s causing it. You might want to rename your DCS folder in Saved Games and let the sim create a new one. Then see if the problem still exists with the new. Edit 2: Thinking that it might be something in the track section's options.lua, I tried replacing it. No difference. So I'm at a loss, unless it has something to do with VR.

You’re using the Mercury pod and, yes, it’s a reported bug with that pod introduced in the last update.

Your death experience in the sim all depends on how you’ve lived your life until that point. It’s all part of DCS making the sim as real as possible. It’s always quiet and peaceful for me…

It’ll be interesting to see what happens in your TRK. All modes work fine on my end. Just a thought. Is there, by any chance, a failure set in the mission? It’s been awhile since I set one in the ME, but I think AP failure was one.

Please remove the mods and see if the issue persists.

Any mods? Especially but not limited to the FC3 clickable cockpit mod.

The mission plays completely different for me. The B-52x2 kill their assigned units in a single pass. The B-52x4 group dropped all their bombs in a single pass. I think there was 1 T-80 left. The B-1B group focused on the BPMs. Once they were destroyed (it took several passes), they took out the lone T-80. All ground units were destroyed. I wasn’t paying attention to altitudes. So I can’t speak to that.

When I viewed it, the B-52x2 group attacked the group off on the island, the B-52x4 attacked the tanks, and the B1-B group attacked the BMP3s repeatedly until all units were gone.

From your response, it sounds like the radar entered mem mode prior to the radar hitting its limits. In which case, no problem.

Haven’t had an opportunity to view the TRK myself but I’m not sure what memory mode has to do with anything in this instance. If the target is beyond the gimbal limits, it’s beyond the gimbal limits and no longer illuminated. Memory mode will not be a factor.

Your assumption is correct. There is only a single dial in the cockpit controlling radar elevation. IIRC, it is discrete (like the keyboard control) rather than continuous. EDIT: (from the real world manual):

That’s weird. Works every time for me without any issues. What happens if you place a static object and use F12?

Probably the easiest way is to use F7 to bring us one of the ground units. The LCtrl+F11 to set the free moving camera and position it where you want.

Why don’t you post the mission so that we can take a look at it? Otherwise it’s a guessing game.

It’s on your C drive (regardless of where DCS is installed) under your user name. In saved games you’ll see a DCS folder. In there will be a bunch of folders one of which will be “Missions”. EDIT: If memory serves, in Windows File Explorer, go to: C:\users\(your user name)\AppData\Local\Saved Games

Open the mission in the Mission Editor and check the season. If it’s a winter month, then all is well. If a summer month, there’s an issue.