Aces High Bulletin Board

Help and Support Forums => Aces High Bug Reports => Topic started by: RSLQK186 on March 25, 2010, 08:04:44 PM

Title: . target sticky
Post by: RSLQK186 on March 25, 2010, 08:04:44 PM

No biggie but: Had target up offline. Towered and quit to offline/ online sellection screen withot putting it to zero. Went to MA and target was up and would not respond to commands. Had to go out of game compleatly to get rid of it.

Title: Re: . target sticky
Post by: shiv on March 25, 2010, 08:06:28 PM

.target 0 makes it go away.

Title: Re: . target sticky
Post by: RSLQK186 on March 26, 2010, 08:14:12 PM

I know that. What I mean is I failed to do so when I left off line mode. Then it was still up in the MA. At that point it did not respond to any dot commands.

Title: Re: . target sticky
Post by: shiv on March 28, 2010, 02:47:16 PM

Ah, read it wrong, sorry.  Never saw that.

Title: Re: . target sticky
Post by: AWwrgwy on March 29, 2010, 02:19:05 PM

Just fly south.  Of course then you're flying around with a big target on your tookas.


 :huh


wrongway

Title: Re: . target sticky
Post by: fuzeman on March 29, 2010, 04:27:27 PM

I wonder if it would have disappeared if you used .target 200, for example, and then tried a .target 0 to remove it?

EDIT- I could not duplicate this. Went offline and did .target 200 and exited and immediately went into TA. The target was there but a .target 0 removed it.

Title: Re: . target sticky
Post by: FLS on April 07, 2010, 08:24:56 AM

Fuzeman you'd have to go to the MA to try to duplicate it.

Title: Re: . target sticky
Post by: fuzeman on April 07, 2010, 09:17:14 AM

Don't really see why but...
I went offline and brought up target with a .target200 and exited. Went online into Titanic Tuesday and target was there, the target disappeared with a .target 0 command.

Now of course I don't know what plane he was in, what map he was on, if had his shoes and socks on or off or if his hair was parted on the left or right.
Either way I'm assuming it was a brief glitch, possibly, but definitely not a repeatable bug.