Probably should be posted in tech support with a save showing the issue.

"an intelligence center in Tel Aviv was hit and an intelligence gathering site was hit in the Golan Heights" I'd like to see the sources on that. With reporters all over Tel Aviv and not a single report, pic, or video of it, I'm highly skeptical. Unless maybe that fire in Chile that Iran c...

I suspect Iran spent a lot too. Israel and others can afford it more than Iran. Especially if BMs are running 40% failure. The other interesting aspect is that several TV reporters stated that shortly before the BM attacks, their phone GPSs shifted their location from Tel Aviv to Beirut. One of the ...

Iran announced missiles and drones were launched. They showed some launching. There's video of a lot of explosions over Israel. There is enough stuff to at least show that Iran did something and it was defended by Israel and others. I guess we can say that we shouldn't believe anything Iran says, bu...

I would also make sure you have the right versions aligned with the issue. Some of those might have been fixed in .15/.16/.17/.18.

<r>Below is the progression of fixes and then bugs in mission behavior that kept me applying beta patches.<br/> <br/> 14 had flight size issues in missions and sonar detection problems as well as a few other things.<br/> .15/.16 was Air intercept units flying off in all kinds of directions and targe...

Thanks.

I was reading the release notes for 1328.18 release and saw something that jarred my memory. I saw the comment that 1328.14 release + 1328.18 beta = 1328.18 release as above. But in 1328.16 beta I saw this from the notes: "Air-only search radars may detect any target from 5 knots up to Mach 5&q...

I'm a little concerned that a couple important issues still aren't resolved before an official Steam patch is released. I was using .14 on Steam assuming those would be addressed before an official patch went out that included those. I was using Steam .14 until the next patched fixed some of those i...

I avoid using double flame. There seem to be several critical issues around missions and strikes when using it.

There are tutorials and videos around that walk through cargo handling. Suggest search here and on Youtube.

https://www.youtube.com/results?search_ ... +cargo+2.0+

I tried it a couple ways. 1) Took them off the mission. As soon as in range and given a fire order, they fired. 2) Manually moved the sub on mission to close to within range but out of firing arc. As soon as the ship came into range, the sub fired. The short of it if you leave them on mission, they'...

First off, I assume you mean CMO, not CMNAO. CMNAO's latest version is 1.15.

MS made a change a while ago that you have to use Windows display graphics settings and change CMO to High Performance.

As I said, they were VERY unlikely the culprit. The jpgs have no ability on their own to impact execution of CMO. Plus thousands have downloaded them without any issue.

I have a very hard time believing that loading a bunch of jpgs and txt files would cause the game to not run. I would focus on something else. If its the Matrix launcher, its known to have issues at times. As was mentioned, use the exe directly.

A quick look and I can't see anything that triggers the posture change, but there's quite a bit of event activity and dependencies. Suspect there might be something inadvertent going on with the triggers. I'd suggest building a test scenario and test posture-changing events and load/save to try and ...

I've seen this as well and happens in the post from the other thread. They will eventually run out of gas and crash.

btw, anyone have insight into the "called off" message on missions? Who called it off? And why? This is the first time I noticed that message.

For a time a few years ago, rapid betas and patches were the thing. You found a major issue that impacted many units broadly across wide timespans and it got fixed and released within days. But there were a few players that couldn't handle the pace and complained about it. But stuff got fixed fast. ...

I tried it both ways. I was using .18.