Command v1.11 Service Release 7 - Release Candidate [CURRENT: B906.21]

[lamboman43]

So, since comms jamming isn't in the regular people's edition, do the communication sensor stats in the DB still mean essentially nothing? Like communication still isn't modeled in the regular version?

[Dimitris]

ORIGINAL: DWReese

** IMPORTANT NOTE #2 **: A newer version of VC++ must be installed before starting up. To do this, run vc_redist.x86.exe from the "\PreRequisites" folder. Otherwise you will receive Lua-related errors/crashes on startup.

I experiencing some difficulty with this step. This install program starts working, the green bar advances all the way to the right, the message indicates that it is processing. I wait and wait and after 10 minutes I gave up. The install appears to hangs up there and will stay there indefinitely. If I close out of it, it informs me that the set up is not complete. If I try to start CMANO it gives me the Lua error message.

Any thoughts?

Thanks

Doug

Hi Doug,

I'd try rebooting and then running the setup file with admin powers.

[Dimitris]

ORIGINAL: lamboman43
So, since comms jamming isn't in the regular people's edition, do the communication sensor stats in the DB still mean essentially nothing? Like communication still isn't modeled in the regular version?

Comm devices in the commercial version are used for platform-to-weapon communications which can be disrupted (e.g. SLAM loses link to guiding aircraft because of no LOS). They are not used for platform-to-platform communications which are currently abstracted as omnipresent.

[DWReese]

I tried rebooting. That didn't work either.

Doug

[ultradave]

I had the same problem and updating using the vc_redist.x86.exe DID solve the problem for me. I noted that there is also a file vcredist.x86.exe (without the underscore) in the prerequisite directory.

So far I've started up one small scenario (Maria .... the Argentine sub scenario from standalone). When I "Add New Mission" the small box seems to be too small. The the check box to open the editor is almost hidden, there is text to the right that I can't see and the OK button must be off the bottom right. I can't resize the window. I reset windows to defaults and that didn't change anything. Picture of the box is attached.

This is W10 using Parallels Desktop on a MacBook Pro.

This is the whole window:

[michaelm75au]

Delete the command.ini file and restart.

[DWReese]

I'm still having trouble, but I did manage to install the VC_ file. (I managed to do thatby updating my Windows files. I would recommend that to everyone.)

I am now getting a message when I try to open the game. I have deleted the Command.ini and I have rebooted several times before trying this. This error message should help.

It mentions NLUA, version=1.3.0.0

Also mentioned iss Culture=Neutral, PublicKeyToken=8df2ab51803ea95

Later it mentions Assembly's Manifest Definition does not match assembly reference
Exception from Hresult: 0x80131040

The open screen (where the ad is)is as far as I can go.

I'd sure like to get back into business is someone can tell me what to do.

Thanks in advance.

Doug

[DWReese]

I got it to work.

It appears that the game is very sensitive to having Windows Updates being completed. Mine were a couple of months old, and without being updated, the game would not work. After updating the Windows files, everything works.

Please remind everyone to update their Windows files BEFORE they do this install.

Doug

[mikmykWS]

ORIGINAL: DWReese

I got it to work.

It appears that the game is very sensitive to having Windows Updates being completed. Mine were a couple of months old, and without being updated, the game would not work. After updating the Windows files, everything works.

Please remind everyone to update their Windows files BEFORE they do this install.

Doug

Good news Doug. I think most Windows systems update by default but will surely keep this in mind.

Thanks

Mike

[jun5896]

ORIGINAL: Sunburn

Command v1.11 Service Release 7 - Release Candidate - Build 906.15

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

See OP for instructions, warnings and release notes.

Fixes
#11337 - Some AA missiles have unlimited range under RC7
#11339 - [B906.14] Problem with aircraft in scenarios with DB459 and 460
#11336 - SR7 RC - Exception message on DB viewer

Thanks. Aircraft tab works fine.

ORIGINAL: BrianinMinnie

Dumb Question alert!

I see u guys referencing a "PE" version, what version do I have, I purchased this from the website way back when, Command first then N inferno later and downloaded the files and installed.
Since I did order a hard copy at the time, I also have a dvd version but I dont think Ive had to reinstall using that.
so how do I tell which I have beyond the ver. number on the splash screen, lower left on startup.

and when should I update using the above service release?

Thanks All

I know that 'PE' version made with just one purpose for enterprise services. And Dev offers one-on-one system support.
Maybe you have standard consumer version [:)]


I envy it, PE version can support full database editing.

[LordFlashheart]

Awesome work on the cockpit visibility request & dogfight improvements being included in this build so unbelievably quickly. [&o]

Quick Q though after updating - any aircraft selected in the DB (Cold War or DB3000k) will say "Cockpit visibility - not supported by this database". Does that mean although the hooks are there for this function, we need to wait until someone goes through every single aircraft one by one and a new DB is released?

EDIT

Scratch that - you need to hit "Update Scenario to latest DB version" in Editor and all the cockpit visibility stats are there!! Amazing!

[ultradave]

ORIGINAL: michaelm

Delete the command.ini file and restart.

Bingo! That did it. I should have thought of that myself. Thanks.

[Reg]

ORIGINAL: LordFlashheart

Scratch that - you need to hit "Update Scenario to latest DB version" in Editor and all the cockpit visibility stats are there!! Amazing!

I assume the scenarios will all be updated in the next official release... There are an awful lot (including community) to update... [;)]

[Eggstor]

ORIGINAL: Reg

I assume the scenarios will all be updated in the next official release... There are an awful lot (including community) to update... [;)]

The "official" scenarios (i.e. the ones included in the "Standalone Scenarios", "Tutorials", and if you have them, "Northern Inferno" and "LIVE" folders) will be updated. The other scenarios are the responsibility of the individual scenario writers, though you can update them yourself.

[Dimitris]

Command v1.11 Service Release 7 - Release Candidate - Build 906.16

Download: Superseded by Build 906.17

See OP for instructions, warnings and release notes.

Fixes
#11344 - CBU-59 not firing, version B906.15
#11342 - Ground strafing aircraft fire to early (Service release 7 B906.15)
#11341 - HARMs running out of Fuel <--- PROBABLY FIXED, PLEASE CONFIRM
#11340 - DB3k: Problem with Sky Sword IIA (ARM) guidance

[Sardaukar]

No Steam version yet, I guess?

[Eggstor]

ORIGINAL: Sardaukar
No Steam version yet, I guess?

Not yet because it's just a candidate for release. However, you can install this over your Steam install.

[Sardaukar]

ORIGINAL: Eggstor

ORIGINAL: Sardaukar
No Steam version yet, I guess?

Not yet because it's just a candidate for release. However, you can install this over your Steam install.

Ah, thanks, I wasn't sure about that. I have both Matrix and Steam versions, but former is not installed.

[Dysta]

I've tested the SR7 with my scenario Northern Phantom, and I found both PL-15 and AIM-120D descending very slowly at mid-course flight, usually way above targets and missed.

[gosnold]

Hi,

Just wanted to report on my 906.16 experience. Everything seems to be working, except a few times I couldn't launch a saved game: the "accept scenario options" button did not work (for "The Big Stick" scenario). Launching it with the scenario editor did work though.

Also I tried a few things based on the update log:
* "#11166 - SBIRS sats not working as expected": I added SBIRS to the game and it did not detect a DF-21D launch, so I am not sure they are working. Sensor range in the DB viewer is also at 2000nm so I am not sure they can see the ground.
* "#11129 - DB3k: DB-110 and Areos Pod Range updates": they have a 20nm range in the DB, so when using a Rafale to do recon, I get all of my detections from the onboard IRST (at a 30nm distance), and not from the recon pod. So there is no point using the recon pod. I think the range should be further increased, to at least the same value as modern laser designation pods.