Fleet Ops 3.0.2 - My bad start

posted on February 17th, 2009, 4:20 pm

Ok, I just had the patch e-mailed to me and installed it. After trying 2 games I just quit after getting an instant problem with both.

Game 1: After selecting my avatar (Adm. Mayson), I got the Starbase but the starting units were sitting in the build list. They were quite noticebly not building and I was stuck with a Starbase and not units. Then it crashed.
Game 2: I started the game and no matter how many times I clicked (and I got the rollover & click sounds), it would not activate either of the avatars. I just clicked one after the other and neither the Mayson nor Risner avatars would select.

posted on February 17th, 2009, 4:20 pm

did you use any special game settings?

posted on February 17th, 2009, 4:22 pm

Default with double resource. Even the map was default. Me & li_deimos Vs 2 AI Medium (Borg & Dominion).

posted on February 17th, 2009, 4:24 pm

hm, is this issue reproducable? does it occour in singleplayer for you too? may have been just some serious lag

posted on February 17th, 2009, 4:29 pm

I only used it in multiplayer immediadly after installing.

In game 1, I selected my base then went to the other side of the map, couldn't select my allies base (like a backround object) and then went back to my base and they were still not building. If it was lag, I couldn't have been in the build/Autonamy lists.

In game 2, would lag allow clicking on the avatars repeatedly one after the other? I got the sounds, tooltips and everything.

posted on February 17th, 2009, 5:38 pm

1: yes, that is the default behavior with stations when no avatar has been selected. they cannot be selected
2: yes, even with lag the tooltips and sounds would be working

i guess it just was a faulty connection or something like that

posted on February 17th, 2009, 5:43 pm

Lag can stop units from building with the rest of the game working fine and make avatars unresponsive? My side wasn't going very slow, it was working at a normal speed.

Lag confuses me, it only effects one thing in the game at a time.

posted on February 17th, 2009, 5:52 pm

if you know a way reproduce the issue, just post it here

posted on February 17th, 2009, 5:54 pm

The best way I can explain it is in game 1, it didn't build the starters, like trying to build normal units with resources. In game, it was like trying to use warp-in without any credits left.

posted on February 17th, 2009, 10:07 pm

I once had a yard stop building for no reason at all.  It resumed once I cancelled a build.  So if it's not building your starters, try cancelling the scout and see if it will build your builders for you.

posted on February 18th, 2009, 12:29 am

The only bug I have come across as yet is the menus on facilities occasionally freezing up.

When this happens I cannot select any ship or scroll the screen around the battlefield. The solution is to click on the build menu (or anything else that opens up a sub-menu on the facility) and cancel out. The screen is then 'unfrozen'

Also, when there is a huge number of defensive facilities which are under attack, they are prone to not fire at enemy targets. I believe this bug may have also existed in vanilla Armada 2 v1.1 though.

Other than that: Fantastic patch. It's great to have save games re-instated and the AI crashing bug has been fixed 

posted on February 18th, 2009, 8:08 am

Only to avoid another 3.0.2-bug-thread:
I tried to use the Avalon's fighters (torpedo and pulse-phaser variant) against a Borg collector and the resource node but they actually did nothing. They were launched, headed for the target and flew through it and circeld around my fleet for the rest of the time. Neither the collector nor the resource node took damage whenever I tried to attack it with the fighters.

What about that one?