Matrix Games Forums

Download: https://drive.google.com/open?id=1EWZ25 ... Y2k_BEryAS

(This will also become available through Matrix and Steam, but players waiting urgently for any of the listed changes can use this instead)

To apply, unzip to the installation folder, overwriting as necessary.

Changes from B1115.6
---------------------------------------
* Includes a number of older DB versions, in order to support loading various community scenarios.
* FIXED: 3D shape for Arleigh Burke-class DDG missing from Tacview resources
* FIXED: Script issue in QBG template "Submarine 1v1 duel"
* FIXED: Car navigation bug on "Raid on Kismayo"
* FIXED: Startup freeze on high-DPI desktop when the automatic 4K-fix has been rejected
* FIXED: Aircraft on strike mission flight path not obeying manual (player-given) changes to waypoint altitude
* FIXED: Aircraft on strike mission may automatically enter RTB status after takeoff even though they still fly the path
* Map tweak: Show the flight paths of airborne strike flights

Thank you....back to testing.

Thanks again, great support!

Francesco

Almost everything connected to strike paths works perfectly. I did find two relatively minor things:

For some reason, when returning to the base after a strike mission, a two-plane group seems to travel at two different speeds. One plane is moving at 520 kts, and the other (his wingman) is traveling at 480 kts. This is easily recognized by the fact that the fuel bars are decidedly uneven.

Also, and this may be tied to the above issue, planes assigned as ESCORTS follow their striker home, allow the striker to land, but then the ESCORTS don't land themselves. Instead, they fly circles around next to the base.

Congrats on so quickly fixing these other issues.




The file is a test scenario that I use. It is designed to test numerous things at the same time. At this point the ASW is still searching for a sub and is not involved in this discussion. Another strike group is returning from another strike. The group to the immediate right, however, is the topic. It was an ESCORT for a striker, which had already landed. Notice the difference in the fuel bar. Earlier, while flying home, one of the two ESCORTS was traveling at 520 while the other was at 480. Now, that their striker has landed, both are together and merely circling.

EDIT 1: I just tried another strike, this time with a EA-6 as an ESCORT. Same thing. The strikers all land, but the ESCORT continues to circle to the right of his airbase. So, it appears that this is isolated to ESCORTS.

EDIT 2: I forgot to mention it, but you can MANUALLY order the ESCORTS to RTB, which they will do. Otherwise, they will continue to circle, and just before they run out of fuel they will land.

You guys rock. Best support of any developers. And has been from the start.

does it solve white screen with red cross?

The white map issue is usually an individual setup issue. Either drivers or some issue in loading map/overlays. I think you'll have to wait until the devs can address it directly with you in your post in the tech forum.

First of all thank you very much for this patch! It has solved the biggest issues regarding the unit altitudes for me.
Still there are a few bugs remaining:

- The "Terrain following" checkbox in the F2-menu is ignored by units. I have observed this on a strike mission. The units act as if the altitude values are always given in ASL. AGL does not work.
- The old altitude bug of strike missions still exist for support missions. The altitude of units on support missions can only be changed by the slider in the F2-window. The other altitude override methods in the F2-menu are ignored. The station altitudes of support mission are ignored as well. Maybe other mission types are also affected by this bug.

ORIGINAL: Tiramisu

First of all thank you very much for this patch! It has solved the biggest issues regarding the unit altitudes for me.
Still there are a few bugs remaining:

- The "Terrain following" checkbox in the F2-menu is ignored by units. I have observed this on a strike mission. The units act as if the altitude values are always given in ASL. AGL does not work.
- The old altitude bug of strike missions still exist for support missions. The altitude of units on support missions can only be changed by the slider in the F2-window. The other altitude override methods in the F2-menu are ignored. The station altitudes of support mission are ignored as well. Maybe other mission types are also affected by this bug.

Thank you!

If easy, could you please post these individually and with save files in the Tech support forum, so that we can begin tracking them? Thanks!

Any idea how long before it makes its way onto steam? I've just applied the attached patchset but steam decided to undo all that and restore the old files ;/. I guess patching steam games like that is a no-no and I've to wait for it becoming offical... Would love to give it a shot this evening...

I used the patch on Steam with no issues. Might have to turn off auto update, I think.

It should be coming on Steam any moment now.

when i try to un zip this to CMO... i get 7zip messages that access is denied.....

ORIGINAL: magi

when i try to un zip this to CMO... i get 7zip messages that access is denied.....

Strange. Which program are you using to unzip it ?

I think an unprivileged user might have issues copying directly into C:\Program Files (x86), depending on a few settings.

ORIGINAL: Dimitris

ORIGINAL: magi

when i try to un zip this to CMO... i get 7zip messages that access is denied.....

Strange. Which program are you using to unzip it ?

7zip.... which I’ve used in the past to download your updates.....
Oh and your updater on CMO works rather nicely for the B1115.6 patch..... which it never did in my CMANO...

Unzip it all to a directory in your Downloads directory, and then select all, copy to the CMO directory. That will work because you'll be asked to provide administrator permission to do that, which 7z probably just doesn't ask for.

Unzipped the contents into my CMO directory. The launcher states I'm running 1.00.11156

Is this correct?

ORIGINAL: ultradave

Unzip it all to a directory in your Downloads directory, and then select all, copy to the CMO directory. That will work because you'll be asked to provide administrator permission to do that, which 7z probably just doesn't ask for.

Thank you sir I was wondering if I should do that ......

ORIGINAL: Dragnaath

Unzipped the contents into my CMO directory. The launcher states I'm running 1.00.11156

Is this correct?

I did the same as you and noticed the same thing. However, when I ran CMO and the checked the version on the Help menu, the correct build for this update was displayed, that of 1.00.111.7