doodenkoff

On the keyboard, your trim controls are: RCtrl + , (comma) left roll RCtrl + ; (semi-colon) nose down RCtrl + . ( period) nose up RCtrl + / (forward slash) right roll Use the nose up combo to move the dial to roughly 3 deg.

Remove the other targets?

I don't think you need the full MOOSE capabilities to do that. A strategy would be to move the Ural to a very small zone and destroy the unit there. That would be the trigger to activate the EWR AI at that location.

Drop your cockpit res to 512. I had the same issue and that cleared it up with no obvious loss of quality.

Thanks Mirknir. Open Conflict was a tremendous success.

I don't have an exact reason WHY it does that; I just know it's annoying as hell. My guess is the UniversRadio plugin is polling the Teamspeak app constantly, causing the spam prevention to go apeshit. It's been awhile.

It's the UniversRadio. You must disable the plugin in Teamspeak.

I've used a large zone and activated/de-activated the AI depending on whether or not an aircraft of the right type was present. I was building scenarios where medevac helos were landing very close to hot LZs. I gave up on actual foot soldier type infantry; they simply run at each other until they're thoroughly mixed up. I kept light armor engagements sorta dynamic with a mixture of balanced opponents, range, and respawn when dead at a certain percentage. They would turn on and off repeatedly and maintain a fun level of 'splosions, tracers, and fire.

Yeah, at /r/hoggit, bignewy says the fix will be in the regular update schedule.

According to bignewy, the fix is in for the weapons.dll associated crash.

I think a PVE server with a few random AI CAP planes would be fun.

Looks like I need to give the Gaz a spin. I sure wasn't pleased with it before.

Check F10 (if possible) for any friendlies that look like they are on approach before entering the runway. When landing, throw a line in chat with your intent to land at which airport.

Yeah, I don't think his comments reflect on Mirknir's character at all.

Use F7 to get a look from the units viewpoint. They need line-of-sight to initiate combat. And your infantry will immediately start running towards each other.

So then it follows that a "sub mission" lua doesn't exist in the mission file. What you get in the .miz file is the entirety of the mission.

Follow the links in Ciribob's signature and navigate to the Github for the script. There is a very useful and easy to follow "how to" to get you started. You'll also need the MIST script.

Download the mission, rename the .miz file to a .zip file and extract all of the goodness.

Type "cmd" at the Powershell prompt and it will allow for standard console commands without complaining about "non-recognized" input.

The "Some name" part of that script is problematic. The first problem I see is knowing what the name will be for a spawned beacon unit. I suppose somewhere there's a way to predict what ID the units will get.

I was searching the .lua for "invisible". I needed to change that to "visible".

Uh...sure. That's kinda confusing though. When I place a beacon with that script, I get a mortar unit too, at the beacon location. Too close and enemy units commence shooting at it. But the mortar unit isn't in my own units list. I don't know where I would set the invisible and immortal status. I don't see anything in CTLD.lua that offers the possibility. This is in 2.1.

When I use ctld.createRadioBeaconAtZone, can I make the resulting unit invisible?

Everyone can see both public and private servers. The private servers are distinguished by a lock icon in the left column.

Yeah, port 10308 needs to be set as forwarded to your server's IP. That's for any DCS server, public or private, with access via the Internet. If you can run a private server with your friends connecting from a different physical location, then you're doing it right and can run a public server.