Lace

3.0 will be reserved for the implementation of Vulkan and the DCE I'd imagine.

The Launcher updated, and then opened the new menu. I clicked 'Check for Updates', and nothing... Guess it's not quite live yet.

The most bombed piece of real estate in the (virtual) world.

It is possible to set up a trigger to launch a parachute flare if requested through the F10 menu. This works well to provide temporary illumination during landing if required. I often use it in my missions for those very dark, moonless or overcast night ops.

I'm firmly in the head-look-point camp, and have no issues interacting with cockpit controls without ever needing to touch the mouse. However, I appreciate that others may want to do things differently, so by all means offer an option, but please don't take away the coupled method.

Anyone who's been around here a while knows that 'soon' in ED parlance means sometime in the next 2-5 years. It'll be worth it when it arrives though.

Kept both copies. Ever the optimist I feel this situation will eventually be resolved, and it is too important an aircraft not to have in DCS.

Or, do they fit smaller, lighter braking systems [i]because[/i] they have a brake 'chute due to winter stopping requirements, and the SOP is to deploy it on every landing?

I think the main reason Soviet/Russian designs featured brake chutes is nothing to do with their inability to engineer an effective wheel brake system, but due to the winter conditions in which they were expected to operate. Same reason the RNoAF F-16s and F-35s have brake chutes, the Viggen has a thrust reverser, etc. You are eliminating the reliance on tyre/runway friction to stop the aircraft in ice and snow. It would be great if runway surface friction was accurately modelled, and varied due to weather conditions.

It would be great if the VR model would match the wallpaper theme. I'm sure it has been requested (several times no doubt) but it is one of those seemingly very easy to do, but also very low priority items. There is a LUA file which you can change manually but I remember it caused some issues for me a while back so I've left it alone since then.

Yes, the 'Pilot Position' needs to be bound from the WSO seat mapping, otherwise it doesn't pick up the input. Controls like this (and other views) really should come under the UI layer, but hey.

Just tried it now, works perfectly at 2x in 4k.

Is that a thing? Can't believe I missed that!

Yes I'm running MT. It was working fine full screen 1920x1080 full screen until the update though.

Did anyone find a work around with this? At the moment it is very frustrating as I can barely see to use the mission editor in 4k on a 17" laptop display. Changing to 1920x1080 just results in the same tiny text in a quarter of the screen. Perhaps a GIU scale option might be a nice solution?

Khasab is a favourite of mine. I like RAF Akrotiri, and Nellis just feels like home I've flow so many simulated NTTR missions from there.

Indeed.

Anyone going this year?

The Afghan CAA AIP might be of some use to mission and campaign builders. Afghanistan AIP.pdf

Asset packs are a whole new ball game, and I agree wholeheartedly. I wish there was a little more coherence and joined-up thinking in what ED release and develop in terms of maps and AI units.

I suggested 'Helicopter maps' a long time ago. Much smaller dimensions and a focus on low altitude details and a very granular terrain mesh designed specifically for helicopter operations. Mogadishu, Konna, Falkland Islands (without half of South America), Grenada, Panama Canal, etc. Some interesting operations which took place within a very small geographical area.

Hmm, what are those Blackhawks doing there...?

Also Afghanistan, so must be a core issue.

On a flight last night (Kola) the moon was unrealistically large, i.e. twice the size of the Sun. It should be around 30 MOA, same as the Sun. Feel free to move this where appropriate, not sure if the moon is a terrain-specific thing or not.