First Strike Forums — Aircraft targeting brackets: client or server error?

Re: Aircraft targeting brackets: client or server error?

null@example.com (FSDev| General Un-Co) — Sun, 08 Jun 2008 02:00:31 +0000

Any change in size of the mods .zip folders are detected by the server.

Re: Aircraft targeting brackets: client or server error?

null@example.com (RSF Angel) — Sun, 08 Jun 2008 01:48:51 +0000

Any chance of making a hotfix that isn't detected by the server? As in, give me the brackets back so i can shoot down more people?

Re: Aircraft targeting brackets: client or server error?

null@example.com (FSDev| General Un-Co) — Sun, 08 Jun 2008 00:17:25 +0000

We were intending on releasing a hot fix but after seeing the player numbers drop after 1.25 then again after 2142 1.5 we didn't want to see it happen again.

Re: Aircraft targeting brackets: client or server error?

null@example.com (Luke SkyRaper) — Sat, 07 Jun 2008 18:01:30 +0000

it makes it more like a real dogfight without IFF... makes you a better combat pilot ....

Re: Aircraft targeting brackets: client or server error?

null@example.com (Stardestroyersarecool) — Sat, 07 Jun 2008 16:53:08 +0000

Though its never bothered me I often see people spamming the chat with that bug.

Re: Aircraft targeting brackets: client or server error?

null@example.com (herbanator3) — Sat, 07 Jun 2008 15:11:25 +0000

I'm not really too sure, but i think its a client side bug and i doubt that there will be another hotfix before 1.3
but i don't really know

Re: Aircraft targeting brackets: client or server error?

null@example.com ([F2F]Timmyyy) — Sat, 07 Jun 2008 15:07:36 +0000

Yes this bug is driving me nuts. It's too hard to see your enemy in space at distance.
Actually, it is the only real issue that I have with FS.
Keep up the good work otherwise

Aircraft targeting brackets: client or server error?

null@example.com (-=CT=- JaFaR) — Mon, 26 May 2008 23:49:30 +0000

So, the bug where the enemy/friendly position indicator brackets don't show up. This bug popped in with 1.25. Is it a server-side bug, or client side? And are you guys going to look into hotfixing it before 1.3?