CMO public beta - Build 1258.2

[Dimitris]

Download: https://drive.google.com/file/d/1p4ArX0 ... sp=sharing

To apply: Unzip on the existing installation of CMO + "Tiny" update.

NOTE: This is a public beta. Standard disclaimers apply.

Build 1258.2 Release Notes (changes from B1258.1)
========================================================================

FIXED: Silent exception in sensor check blocks LOBL IR weapons from firing
FIXED: Removing mount from an AC with Loadout selected was crashing the game
FIXED: ACs with empty weapon records were unable to fire

[eleos]

Damn, that was fast.
Good job Devs

[hrfepo1]

Nice!

[c3k]

Hah! I just -knew- that beta 1258.1 was going to be consigned to the trash heap of history!

Once again, fellas, damn fine.

I'm very eager to try out the ToT function!

Thanks.

[sparky577]

Incredible!

Thank you all again!

[gennyo]

Goodbye, one of my favorite exploitation in the game from CMANO years.

I do wish to have a CHEATER.ini to re-enable all these features.

[ParachuteProne]

Can't wait for this to hit Steam Beta

[TalonCG2]

To apply: Unzip on the existing installation of CMO + "Tiny" update.

I cannot seem to get this to work with the Steam version. I manually put the files in and overwrite like all the other beta patches I've previously gotten here, but the old version number still remains and none of the changes show with this one.
I tried circumventing Steam and tried starting directly from the command.exe file. I got an error message stating cannot start because steam is not running, which is odd, because it was... But in the background, I could see the right version number on the title start up screen behind the error message. If I use the launcher through steam (as is standard to start CMO in Steam), it doesn't work.
I tried redownloading the file and tried unzipping with windows, 7z and winrar all the same result.
Any help or suggestions getting this to work would be appreciated.

[KnightHawk75]

Goodbye, one of my favorite exploitation in the game from CMANO years.

I do wish to have a CHEATER.ini to re-enable all these features.

Which one of the 3 fixes above related to that? or are you talking about something else in 12xx line?

[gennyo]

Goodbye, one of my favorite exploitation in the game from CMANO years.

I do wish to have a CHEATER.ini to re-enable all these features.

Which one of the 3 fixes above related to that? or are you talking about something else in 12xx line?

The last one, I can't stuff my drones with 0 OODA time and shoot laser like crazy,

[KnightHawk75]

Goodbye, one of my favorite exploitation in the game from CMANO years.

I do wish to have a CHEATER.ini to re-enable all these features.

Which one of the 3 fixes above related to that? or are you talking about something else in 12xx line?

The last one, I can't stuff my drones with 0 OODA time and shoot laser like crazy,

I'm still confused, why not? The fix description seemed to indicate it related to aircraft not-firing when a unit had an weapon record that was empty/depleted but other available records still remained. Sure hope you can still do what you mention, so long as their are weapon records with unused yet laser shots still on-board. So is there more to the "fix" then was communicated?

[Easy301]

To apply: Unzip on the existing installation of CMO + "Tiny" update.

I cannot seem to get this to work with the Steam version. I manually put the files in and overwrite like all the other beta patches I've previously gotten here, but the old version number still remains and none of the changes show with this one.
I tried circumventing Steam and tried starting directly from the command.exe file. I got an error message stating cannot start because steam is not running, which is odd, because it was... But in the background, I could see the right version number on the title start up screen behind the error message. If I use the launcher through steam (as is standard to start CMO in Steam), it doesn't work.
I tried redownloading the file and tried unzipping with windows, 7z and winrar all the same result.
Any help or suggestions getting this to work would be appreciated.

This is very weird indeed and I haven't seen this report anywhere. From the symptoms you describe it's almost like the .exe didn't get replaced properly or you somehow ended up with two .exes in your main CMO folder.

Command can't be started directly via the Command.exe in the steam version regardless of if Steam is running or not. Otherwise it'll produce an error like you said. This is normal behavior. You may be able to use the launcher.exe in the same folder as the command.exe with steam running and it'll start properly or start it via Steam.

I don't know if the above applies to the beta.exes as those are modified but either way you should be starting it via Steam or the launcher.

Do this:

Install Tiny via the beta steam branch.

Download this update and unzip it to a folder on your desktop

Open steam select the game in your library list right click it and then select properties or manage game (Forgot which one.)

You'll see a button card "Browse local files" click that. A widow will open showing the files of your CMO install.

Drag the files from the folder on your desktop you created earlier and place them in the folder and click YES when it asks you to overwrite.

Close this folder and launch regularly via steam and you should be good to go.

Can you follow these steps exactly and let me know what happens please?

[TalonCG2]

To apply: Unzip on the existing installation of CMO + "Tiny" update.

I cannot seem to get this to work with the Steam version. I manually put the files in and overwrite like all the other beta patches I've previously gotten here, but the old version number still remains and none of the changes show with this one.
I tried circumventing Steam and tried starting directly from the command.exe file. I got an error message stating cannot start because steam is not running, which is odd, because it was... But in the background, I could see the right version number on the title start up screen behind the error message. If I use the launcher through steam (as is standard to start CMO in Steam), it doesn't work.
I tried redownloading the file and tried unzipping with windows, 7z and winrar all the same result.
Any help or suggestions getting this to work would be appreciated.

This is very weird indeed and I haven't seen this report anywhere. From the symptoms you describe it's almost like the .exe didn't get replaced properly or you somehow ended up with two .exes in your main CMO folder.

Command can't be started directly via the Command.exe in the steam version regardless of if Steam is running or not. Otherwise it'll produce an error like you said. This is normal behavior. You may be able to use the launcher.exe in the same folder as the command.exe with steam running and it'll start properly or start it via Steam.

I don't know if the above applies to the beta.exes as those are modified but either way you should be starting it via Steam or the launcher.

Do this:

Install Tiny via the beta steam branch.

Download this update and unzip it to a folder on your desktop

Open steam select the game in your library list right click it and then select properties or manage game (Forgot which one.)

You'll see a button card "Browse local files" click that. A widow will open showing the files of your CMO install.

Drag the files from the folder on your desktop you created earlier and place them in the folder and click YES when it asks you to overwrite.

Close this folder and launch regularly via steam and you should be good to go.

Can you follow these steps exactly and let me know what happens please?

Did exactly as you described last night, several times to be sure, to no avail.
I'm considering a fresh install at this point. Or I'll just be patient and wait for it to show up in the steam beta.

[Easy301]

I cannot seem to get this to work with the Steam version. I manually put the files in and overwrite like all the other beta patches I've previously gotten here, but the old version number still remains and none of the changes show with this one.
I tried circumventing Steam and tried starting directly from the command.exe file. I got an error message stating cannot start because steam is not running, which is odd, because it was... But in the background, I could see the right version number on the title start up screen behind the error message. If I use the launcher through steam (as is standard to start CMO in Steam), it doesn't work.
I tried redownloading the file and tried unzipping with windows, 7z and winrar all the same result.
Any help or suggestions getting this to work would be appreciated.

This is very weird indeed and I haven't seen this report anywhere. From the symptoms you describe it's almost like the .exe didn't get replaced properly or you somehow ended up with two .exes in your main CMO folder.

Command can't be started directly via the Command.exe in the steam version regardless of if Steam is running or not. Otherwise it'll produce an error like you said. This is normal behavior. You may be able to use the launcher.exe in the same folder as the command.exe with steam running and it'll start properly or start it via Steam.

I don't know if the above applies to the beta.exes as those are modified but either way you should be starting it via Steam or the launcher.

Do this:

Install Tiny via the beta steam branch.

Download this update and unzip it to a folder on your desktop

Open steam select the game in your library list right click it and then select properties or manage game (Forgot which one.)

You'll see a button card "Browse local files" click that. A widow will open showing the files of your CMO install.

Drag the files from the folder on your desktop you created earlier and place them in the folder and click YES when it asks you to overwrite.

Close this folder and launch regularly via steam and you should be good to go.

Can you follow these steps exactly and let me know what happens please?

Did exactly as you described last night, several times to be sure, to no avail.
I'm considering a fresh install at this point. Or I'll just be patient and wait for it to show up in the steam beta.

Hi Chuck,

This is incredibly peculiar. Logically there's no reason why this should be happening. Especially the fact that it displays the wrong version number but will display the correct one under the error box when launching the Command.exe on its own.

Before reinstalling do a repair/file verify on Steam and then reapply the update and let me know if that works.

That'll bring any modified files back to their original state and grab any missing or incomplete ones. It'll essentially solve most of what a reinstall would without having to go through the entire install process again.

Let me know if the above works please as I'm incredibly curious now too. The symptoms you're seeing are really odd and I can't think of why they are happening.

It's almost like Steam is launching the game via a separate .exe than the one in the command folder and not the one that shows the correct version number under the error box as usually the .exe is what determines which version number is shown.

Let me know if a repair and then applying the update again fixes this issue.

Also one more thing to try before the reinstall and or the repair: Install the beta as normal but use the launcher.exe in your CMO folder with Steam running and see if that launches the game with the correct version. It may or may not let you run the game that way, let me know if that works.

Feel free to PM me if you want with the results or make a post in the Tech Support Forums and if a reinstall/repair and or the launcher.exe trick doesn't work I'll do my best to troubleshoot more with you and get it solved.

[TalonCG2]

Before reinstalling do a repair/file verify on Steam and then reapply the update and let me know if that works.

That'll bring any modified files back to their original state and grab any missing or incomplete ones. It'll essentially solve most of what a reinstall would without having to go through the entire install process again.

Let me know if the above works please as I'm incredibly curious now too. The symptoms you're seeing are really odd and I can't think of why they are happening.

It's almost like Steam is launching the game via a separate .exe than the one in the command folder and not the one that shows the correct version number under the error box as usually the .exe is what determines which version number is shown.

Let me know if a repair and then applying the update again fixes this issue.

Good idea on the repair/verify, I'll let you know how it works.

Also one more thing to try before the reinstall and or the repair: Install the beta as normal but use the launcher.exe in your CMO folder with Steam running and see if that launches the game with the correct version. It may or may not let you run the game that way, let me know if that works.

Did that last night, and it loaded the game as normal, but still the wrong version.

Feel free to PM me if you want with the results or make a post in the Tech Support Forums and if a reinstall/repair and or the launcher.exe trick doesn't work I'll do my best to troubleshoot more with you and get it solved.

Fingers crossed, but will do.

[TalonCG2]

No joy, but it's 03:30 now. I'll fiddle with it more tomorrow, and post in the tech support forum if my efforts are still unsuccessful.

[fulcrum28]

may I please ask which version of Tacview is playable with the current Build 1258.2? I am trying with 1.8.8 and 1.9.0 Beta, but it does not work. Perhaps should I reinstall to earlier Tacview versions? Thank you.

[TalonCG2]

This is very weird indeed
Can you follow these steps exactly and let me know what happens please?

Success!

Not sure why it wasn't working, but I deleted every file in the root folder and left the folders in the main directory alone. Then did the verify/repair thing a third time in Steam with beta enable and patched to 1258.2 and it finally worked. No idea what file was missing or corrupted. Sorry for hijacking the thread for a bit, but thank you for your suggestion, it lead me in the right direction to get it to work!

Now to go play/test the new features.

[Easy301]

This is very weird indeed
Can you follow these steps exactly and let me know what happens please?

Success!

Not sure why it wasn't working, but I deleted every file in the root folder and left the folders in the main directory alone. Then did the verify/repair thing a third time in Steam with beta enable and patched to 1258.2 and it finally worked. No idea what file was missing or corrupted. Sorry for hijacking the thread for a bit, but thank you for your suggestion, it lead me in the right direction to get it to work!

Now to go play/test the new features.

You're welcome. I'm just glad you were able to get it sorted and working correctly! Have fun with the new features.

[MaxDemian]

In the changelog it was reported that TVM SAMs now register on RWR.

But is this entirely realistic? I've read claims that TVM systems like the Patriot can guide missiles in TVM mode while still using tracking beams on the target, thereby masking their true intent.

Can you shed light on how this is modelled now? At what point does RWR trigger?