Commander asset switch doesn't (always) update systems?

[TSCavalier]

Has anyone else encountered this (VERY minor) glitch? I am able to consistently reproduce it, but it has a simple work around. I didn't see it as an issue in the VCF.

OPERATING SYSTEM: winXP

OS ENVIRONMENT: 1024x768x32

GAME ENVIRONMENT: 1024x768x32

GAME VERSION: 2.00.12

GAME TYPE: roam

CAREER/RACE/CASTE: cmdr/terran/mil

ASSET/LAUNCH BASE: megaron/galcomHQ

PROBLEM/TO REPRODUCE

I am running a fresh install of UC, w/2.00.12 but using a ROAM save game from 2.00.11.

1. Descend to the surface of a planet in your CC (I used a Megaron) and park it.

2. Launch a shuttle and have it deploy an OC vehicle.

3. Jump out of the ever-near airlock of the CC (Alt-E) and walk/run to the parked OC.

4. Have the shuttle extract the vehicle you are manning; when this happens you will push the marine pilot out of the way and take control of the shuttle.

5. Fly the shuttle back to your CC and dock with it (Alt-D). You can watch yourself walk back to the bridge with Perscan.

However, any attempt to access Tactical or Logistix will give you the buttons/options of the shuttle (even after you have arrived on the bridge). The computer systems do not seem to know that you are on-board the CC, but think you are still on the shuttle.

RESOLUTION

Simply command another asset or hop out of the CC and back in and the systems now "reset" and recognize that you are commanding the CC.

(I feel a bit bad that my first post after being re-commissioned is a possible bug report . I just happend to run accross this tonight, and thought I'd be helpful and report it.)

[ 08-16-2004, 03:02 PM: Message edited by: Supreme Cmdr ]

[Supreme Cmdr]

If you can reproduce it with a new game, I'll investigate it.

[TSCavalier]

OK, same setup as above. Each time I started a new ROAM scenario. I also chose different races and assets each time, to isolate whether or not it was tied to Terran/Military/Megaron. Both times I set a CC waypoint on the starting default planet (Zilon and C-...something ) and land.

The first time was as Zelon/Mercenary/Warmonger. I enter the planet, deploy SC1 with marine #1, order it to deploy its vehicle (OC1 an APC), hop out of the CC, man the OC1, and order SC1 to pick me up (it had already docked back into the CC). Once on the CC, Tactical and Logistix thought I was still in the SC1.

The second time was as Gammulan/Police/Starwarrior. Identical setup, the only difference being that I hopped out of the CC before I told SC1 to launch (I hadn't yet sent marine #1 to it). Other than that everything was the same, and when I finally made it back to the CC in SC1, Tactical and Logistix thought I was stil in the SC1 (even though Perscan said I was on the bridge).

It looks like the automatic switch(s) that occurs from OC to SC to CC confuses things, and it doesn't fix itself unless you manually switch assets (such as hopping back out and back into the CC).

Like I said, it's not a big deal, it was just perplexing the first time I encountered this. Once I figured out what it was doing, it's easy to reset Tactical and Logistix by hopping out of and back into the CC.

Unrelated, but in the second test, I instantly entered the planet's atmosphere after setting the CC's entry waypoint on the planet and hitting Shift-9. I hadn't altered the CC's heading at all (which was away from the planet). Kinda shocked me. No hyperdrive transit at all, just -bam- right to the atmosphere-entry animation, which is why I didn't have time to send the marine to the shuttle (which is what I did during hyper-transit in the first test).

[Supreme Cmdr]

OK, am all over it. It may be that this crept up because of the code change to allow the AE in the Commander career to switch to any asset other than his own. This is the only change related to this, that I made in the 2.00.12 patch.

[Supreme Cmdr]

I was unable to reproduce the steps above to reproduce the problem, but I did find and fix something that may be related. Wait for the next patch and see if it still happens.

[ 08-26-2004, 08:28 AM: Message edited by: Supreme Cmdr ]

[Supreme Cmdr]

This should now be fixed in 2.00.13