On 2008-06-24 06:20, Gejaheline wrote:

Attack craft, particularly B-27s, often don't respond to shift+N. I attacked a planet with B-27s several times and they never returned. The "fighters returning to base" message didn't show either.

On 2008-06-24 08:24, 1000 Unit Block {OLIOLIO} wrote:
This is because they get mapped to the B Button, as they are "bomber craft"

I wonder if pressing shift+b would recall them (and at the sametime blow up all your bombs)

[/quote]

Testing shows that all attack craft (for UGTO, at least) are mapped to N and respond to shift + N recalls them when they are attacking a point in space. Shift + B produces no effect.

Other notes and discoveries:

Platforms do not appear to attack "unknown" targets and do not fire in point-defence at any hostile ordnance or attack craft. Gaifen were happily zapping them, and placing a platform in enemy defence base range gets them blown up by IT missiles.

On the point of Gaifen, they appear to have asymmetrical armour, with the front arc also defending the right, and the rear also defending the left. This makes for a relatively easy kill, since breaking left after a head-on attack allows you to continue to attack the weakened area. All AI ships, incidentally, go fast enough to cause odd behaviour in weapons like fighters and missiles, since the aimpoint goes out of range even when the weapons should be able to fire. I have seen sabot rockets launch backwards at a target in front of me.

I observed K'luth platforms with more than 100% armour, which gave them red armour rings. Reducing them below 100% caused the armour rings to behave normally.

UGTO battle dread missile launchers are orientated asymmetrically. The left launcher fires at a shallower downward angle than the right.

Planets with no population but with units will have an extra comma in the status display; ", X units", presumably due to a bug in the method that prints that line on the status display.

Jumping towards a planet prompts collision alert warnings. This might be intentional, though.

WHs cause horrible desync problems. Insofar as I can tell, the server sees players using WHs as moving very fast, and extrapolates their motion as being several thousand GU/sec, and launches them off the edge of the universe. It then compensates by moving them back at a similar speed, but overcorrects. This continues, with the client of the player actually doing the jumping acting as thought nothing has happened, except they won't be able to WH or shoot, since the server thinks they're somewhere else. Logging out and logging back in puts the player at the position the server thinks they are, which may be several billion gu away from anything.

And finally, trying to write long posts in the beta lobby software browser tab causes it to be lost should the lobby decide to refresh itself.


[ This Message was edited by: Gejaheline on 2008-06-24 16:44 ]


[ This Message was edited by: Gejaheline on 2008-06-25 17:24 ]
_________________
[Darkspace Moderator] [Galactic Navy Fleet Officer]

---