Deezle

Surround sucks, but it's not needed with DCS.

This is simply a problem with DCS. It fails to recognize a switch in the on-state when the simulation starts, so it doesn't recognize when the switch is turned off, it's not until it sees a switch turned on that it will remember the state, and "synchronize HOTAS" is spotty at best and creates more problems for me than it solves. It will also forget the state of the switches in the middle of a flight if you pause the game and go to the control page.

Warthog grip is a must for me, If I could put mine on your gimbal, I'm in.

I can assure you it is. Going from a QX9650 to a 4790K with that same GTX760 was a massive increase in performance for me.

I've never found there to be a problem lasing for as long as I want in DCS. You can watch the bomb fall, it absolutely will not track the laser sooner than 15 seconds from impact, every time, no matter what. Dropping from too low is certainly a problem.

MANPADS are currently bugged, they emit almost no smoke and don't set off MWS. There's a thread about it here https://forums.eagle.ru/showthread.php?t=176731

Turn the radio knob to intercom, simply opening the doors is no longer sufficient with the engine running.

Turn off HDR in the meantime.

Make sure the problem isn't with the binding in DCS, as default the pedals tend to be bound to the stick and throttle.

Perhaps it's more of an announcement fortnight? :ermm:

It will for sure if you open the default.lua file and create them ;)

MANPADS are currently bugged. They emit no smoke and don't trigger the MWS in the A-10C either. Try it with a Strela.

Perhaps, easier said than done on a 2d screen. The lights tell me where I need to be, therefore I'll use them.

The lights are pretty hard to see in DCS, irrelevant for the Hog but pretty important for the F-15. I zoom in a little bit and focus all of my energy on watching the lights and keeping in position. I don't play BMS that much but I tried refueling the Viper for the first time a couple weeks ago, getting in position is a bit more difficult with the jet wash but once on the boom, the lights were easy to see and I stayed on the boom the entire time until I was topped off.

This the only module that freezes for you?

Any modified files will be replaced with the default files any time you update/repair. This is why we use JSGME to easily enable and disable mods.

This is a current DCS problem. MANPADS have almost no smoke and do not trigger the MWS in the A-10C either.

Changelog today mentions something about MANPADS, sounds like it might be fixed.

Not really. This sim is very demanding. I've found I need something with more balls than my 970, I'm maxing out it's VRAM, not to mention I'm maxing out my 16gb of DDR3. If you wanna play with 3 monitors/4k monitor you're going to need more horsepower. If you're using the default 3 screen option I'd recommend against that, it's harder on frames than a single large viewport and it just looks weird.

Using the comms menu is much more enjoyable with Voice Attack.

Okay, so I'm not going crazy. Flying the A-10C earlier in 1.5.5, I rolled in and dropped a GBU-38 on an APC surrounded by infantry, I pickled and turned away. Kept my head out of the cockpit and on the enemy location the entire time looking for a MANPADS shot, about 10 seconds later I got hit and it took out both engines. No MWS (which does happen from time to time, but I'm pretty sure my wing sensor was facing the launch location), but I never saw any smoke trail either. Checked the log and sure enough it was an Igla that got me. Just watched the above video and it appears his MWS wasn't triggered either, so maybe it's affecting that too. ETA: Definitely affects MWS too, flew the same circle around an Igla and a Strela, Strela launches were easy to see like normal and all 4 launches triggered the MWS, same pattern flown against an Igla I could barely see them launch and didn't receive a warning on any of the 3 launches.

Not what I proposed at all. Allow the editor to place aircraft anywhere, if you place an aircraft somewhere it will get stuck, that's on you. Since we know the prop planes, which would fit the Mina airstrip's use, don't get stuck, no big deal. If you put a Flanker in the dirt and you can't move it, oh well, your problem. And being able to place Viggens on the road would be neat/realistic.

They are much, much worse shots than they used to be, thankfully. If you are heading straight towards them, you're still a fairly easy target.

Rather than adding a non-existent apron, planes should be able to be placed anywhere, like the choppers. Two birds with one stone.

There's still a few airports/strips that appear to be missing in the main area of the map, Desert Rock in Mercury, small airstrip just SE of Reveille Peak, Calvada Meadows in Parhump, Alamo Landing Field right in the middle of the map, and the airport at Yucca Lake, which has been there since first release as a flat piece of concrete, but not as an actual airport. There's some on the edges, which aren't as important but I figured I'd mention them, Saint George is the obvious one, considering they added the city, might as well add the two airports there, especially the one on the Mesa, which is really cool. The one in Searchlight right between Laughlin and Jean, not super important. And the least important, but would be really neat is the airport in Hawthorne at the Army Depot, the town was added, might as well put the airport in. Anyways, not to detract from the update as it was very, very much welcome and really helps make this map seem much fuller, I do hope we at least get the airfields that are still missing from the main map area.