v1.03 Release Candidate thread

[Casinn]

Are you "extracting all" over the command directory and letting it replace everything or trying to run it straight out of the zip?

[dandin384]

ORIGINAL: Casinn

Are you "extracting all" over the command directory and letting it replace everything or trying to run it straight out of the zip?

Extract to C:\Matrix Games\Command Modern Air Naval Operations (That's the default file path, if you installed command somewhere else extract it to that location) and overwrite all existing files.

[magi]

ORIGINAL: dandin384

ORIGINAL: Casinn

Are you "extracting all" over the command directory and letting it replace everything or trying to run it straight out of the zip?

Extract to C:\Matrix Games\Command Modern Air Naval Operations (That's the default file path, if you installed command somewhere else extract it to that location) and overwrite all existing files.

Ok..... Thank you.......

[Dimitris]

Build 499 - v1.03 Release Candidate 3
--------------------------------------------------------

Download here: https://drive.google.com/file/d/0B205vp ... sp=sharing

This can be applied to any existing Command installation.

Release Notes (changes since B498)

Fixed/Added:
---------------
- 0006925: [Build 498] SAMS go blind and Command crashes about 50 percent of time
- 0000600: Afterburner in IR calcs
- 0006911: [498] Game crash during Indian Ocean Brawl
- 0006921: Sensors from pods are added twice
- 0006787: [491]Minehunting got weird

* Autosave now allows going farther "back in time": When an autosave is performed, the existing autosave file is renamed to autoscen_20, the existing (if any) autoscen_20 file is renamed to autoscen_40 etc. all the way to autoscen_100. This way, whenever there is a reported problem the dev team can go back up to 100 (RL) seconds to troubleshoot reported issues. This solves the "autosave after the fact" problem.

* Engine throttle (cruise, full, flank etc.) is now taken into account when calculating the IR signature of aircraft, and thus its detection range by a sensor.

* As requested, the no-pulse mode can now be toggled on/off via two additional ways (other than Game -> Options etc.):
a) Drop-down selector "Map Update Mode", placed to the right of the "Time Compression" drop-down selector.
b) Keyboard shortcut: Ctrl+Q .

* Includes all the latest AD imports by Rudd.

[Pukeko]

Did other people settings all change after applying build 499? Sound turned on, sonobuoy visibility changed, map cursor databox, etc. Have not had this happen before when applying any other builds.

[dandin384]

ORIGINAL: Pukeko

Did other people settings all change after applying build 499? Sound turned on, sonobuoy visibility changed, map cursor databox, etc. Have not had this happen before when applying any other builds.

Yes, my settings reset as well, those large reference points bring back some memories [:D]

[Dimitris]

Are the settings reset only once after applying the update, or every time you start the game?

[lowchi]

ORIGINAL: Sunburn


* Engine throttle (cruise, full, flank etc.) is now taken into account when calculating the IR signature of aircraft, and thus its detection range by a sensor.

nice! Thanks!!

[Pukeko]

Are the settings reset only once after applying the update, or every time you start the game?

Just once. Not really a big deal, but I thought I would make a note of it as I'm not sure this was deliberate on your part or not.

[dandin384]

ORIGINAL: Sunburn

Are the settings reset only once after applying the update, or every time you start the game?

Only once for me as well.

[Sardaukar]

Probably it overwrites .ini file.

[Primarchx]

A few questions here...

o Is this a 360 degree enhancement or just from the rear arc?

o Does this enhancement kick in at the moment of an IRM attack or when the weapon is launched? IE, if I see a missile launched, can I chop the throttle to Loiter as a countermeasure?

o Does this enhancement effect ships as well as aircraft?

ORIGINAL: Sunburn


* Engine throttle (cruise, full, flank etc.) is now taken into account when calculating the IR signature of aircraft, and thus its detection range by a sensor.

[Dimitris]

1. Side and rear.

2. It works for any IR sensor check. IR missiles typically have to detect the target prior to launch and they also have to keep detecting it continuously post-launch, otherwise they'll fall behind. So in theory you can indeed pull the stunt you are describing. The catch is that by the time you are within the weapon's DLZ, a decent IR seeker will likely detect you at both idle and AB.

3. Aircraft only.

[Primarchx]

Understood. So it's not a to-hit modifier, but rather a detection modifier. This may widen the envelope (DLZ) of some earlier IRMs with creaky seekers, at least against a target with a high power setting. IRSTs seem to benefit in the rear/side quarters, too.

[Dimitris]

Build 500 - v1.03 Release Candidate 4
----------------------------------------------------------------

Download here: https://drive.google.com/file/d/0B205vp ... sp=sharing

This can be applied to any existing Command installation.

Release Notes (changes since B499)

Fixed:
-------
- 0006946: Crash and 'SAM hanging in air' with simple scenario with S-400 vs A/C
- 0006948: Crash when running SARH scenario at high time acceleration
- 0006944: During Sea Eagle Raid Soviet SAM's go blind and hang in place
- 0006945: Crash: SA-20a firing against AARGM
- 0006924: [Build 498] Salvo SARH Launches and strange lock breaking behavior
- 0006935: [499] If targets move out of radar arc SARH missiles do not go blind
- 0006926: [498] ABM intercept Crash

[lowchi]

Thank you!

[Dide]

Always better! Thanks!!!

[rjm51973]

Very nice! Thanks!

[ipe]

Hey great job with updates but i cant download Build 500 from google drive. It says something like too many downloads/usage on your drive account. I was able to download Build 499.

[renders]

yeah mee too..