Capn kamikaze

LOL, that may be taking things too far.

The bit where you're selecting your role in a server.

Rakkis, I think you must not have read the thread, this idea is not about flying for hours in circles, it is about being able to jump into a role when notified that that role is going to be something other than sitting there looking out a window.

The current placeholder implementation is next to useless on MP, you see a diamond, then launch, then it turns to a bloody square, then you get kicked because you just shot down a friendly because your IFF said it was an enemy, FFS, if it's going to be a placeholder, then at least for the time being make it so it is more reliable.

I was thinking about war time deception, especially with the WW2 modules and the Normandy map, could we have fake tanks, trucks and other vehicles, that could be used to make fake armies, so in MP it would actually be possible to fool the other side into attacking dummy targets?

Kind of like a dialogue box comes up (if you enable it in your DCS options) for everyone in the lobby if someone calls a boom equipped tanker from a plane that uses the boom like say an F-15 or A-10 and then if you hit ok, you're put in the boom operators seat until you decide to go back to the spectators/role selection list.

I was thinking you'd just jump into the role if you're still in the lobby, when someone contacts the tanker if you've not selected a flying role yet.

Player controlled tanker boom operator?

I can see I am in VACQ mode by how my radar display is behaving, narrow beam horizontally, large vertical sweeps, but the two vertical bars on the HUD are not showing, and there is no text indicating what mode I am in. All other ACM modes work fine.

Orso, I find it amazing that you consider my post a "strawman" or an "attack", grow up.

No, you rock.

I feel the need.....

Excessive curves are a bad idea, you end up with a whole lot of no response, and then a whole lot of loads of response in the extremes of the axis.

Sorry but I find that very hard to believe, for one single flight hour, I think this is a case where wiki is wrong again.

Some of them are now wrong in certain parts, eg how certain weapons and or sensors are set up and used.

We're getting the HARM C.

Deactivate your modules before you proceed.

They did say they are looking at converting all older modules over to keyless.

Exactly, a lot of the vids are now simply wrong, and so of little to no use.

With all the changes to modules are the people who do instructional videos going to replace them with more up to date versions, or at least re-edit the relevant sections that are now out of date. The vids are great, but having tutorials on youtube that are in some cases more than a year out of date causes a lot of confusion.

This currently has a "condition" option, but could we also have a "stop condition" option?

Specs: Asus ROG x470f, Ryzen 2700x, 32GB DDR4 3000, 2x GTX970's, Win10pro, OS on SSD 1, DCS on SSD 2. https://www.datafilehost.com/d/95f6bb4a

The first time I press the Mav-F's MFD button for the second time in a mission to bring up the sensor camera's image, I get about a 5-6 second pause.

At the moment I find I'm having to press the button multiple times before it catches it and responds, inputs from the keyboard seem fine, but not from my flight stick (Warthog)

Would it be possible to specify a target or area that is off limits. So if I want an AI to not engage anything in a particular area or a particular target, even if it can detect it, and has weapons that can be used on it, it will not under any circumstances enter that area and engage anything in it, or a specific target. Reason being sometimes AI is just dumb as a rock and will get it into its head to go take on something which isn't its mission objective, and likely get itself killed.