Bruce_D

I’ve managed to solve this problem by editing the “mission” file (inside the “.miz” file) with notepad++ the aircrafts will appear in at least 12 different spots on the aircraft carrier.

Situation 1: I’m flying in single player on the PG map with 3 wingmen. I contact my flight and send then to the tanker. As soon as I do that all the radio and cockpit sounds disappears. You can only hear the engines. Even Jester is mute. When all 3 end their refueling the sound comes back. Situation 2: I’m flying in single player on the PG map with 3 wingmen. I contact the tanker and start my refueling. My flight stays on formation and nobody goes to the other side and starts their refueling. As soon as I send then to refueling the sound stops again. No radio or Jester calls. I’m attaching a mission so somebody can try to reproduce and confirm the same error. Tks! AAR.miz

I discovered that the tomahawk can destroy runways. It even appears on the debriefing that the runway is destroyed. I let 12 hours pass and it was still destroyed.

If you go on the base supplies, the "ADM-141A" is listeded on the air to ground missiles as "BMG-71E TOW-2A"

Great! Do you know any American bomb that take the same time to fix the runway in game? Tks!

I didn’t find this report. When you try to use the trigger “dead zone” and star the mission, the game crashes. dcs.log-20190329-131311.zip

I’ve managed to solve this problem. I’ve opened the mission file (.miz) and changed the information inside “mission” so the aircraft can start on the carrier. I put 11 planes to start on the deck and worked

I did the test. After bombing with the MK family take 1 hour to fix the runway

I bombed a runway on the Persian Gulf map. The AI Stopped to land in that base, but after a few minutes they start to land again. Is the repair runway modeled? Is that possible to keep it destroyed for at least an hour?

The aircraft only slides when the engine is on. With engine off it stops. I hate this bug.

Try a deadzone 4 with max curve 25 and minimum curve 20.

I've managed! Tks! the problem was the distance and altitude to lock

I use to have this problem, then I start to do everything slow and the problem was solved. I connect to the catapult, wait for the clear to take off message, put the throttle in mil and wait for the RPM and fuel flow reach the max, only after that I salute and take off. Try to do everything a little bit slow. Worked for me.

I will check the weather for the next mission and try to lock a ship again. Thks

What I've noticed is that point does not work when you try to lock ships. Targets close to water, depending on the angle where you put the camera, lost the point and area lock.

This problem only happens with F-14 AI and even in cold start

Cool! Tks!8

I don’t know if it’s a bug, but we can lock a Ship when using the “Target designate Fwd / PAL” mode with more than 50nm away. Edit: You can even fire AIM-7 on it!

When you press as a pilot “LCrt+c” in flight the canopy will appear open inside the cockpit and no canopy appears on the aircraft view.

I only have this problem with cold start

I divided the 16gb between my 3 ssd. I will try to raise in just one and see the result.

Crashed Again after last update dcs.log-20180803-203106.zip

Is this srill an issue?

I discovered the problem. DCS is still demanding to much memory. To solve the problem I’ve raised my virtual memory to 10GB. I have 16GB of memory RAM, 4GB on my video Card and I’m using 10GB of virtual memory from my 2 SSDs and 1 HDD.

DCS Crash on SP. Mission uses Moose Script. I don't know if it is related. Mission attached. dcs.log-20180719-032440.zip Persian Free.miz