[FT] SSD

Anyone have business card sized SSDs for FB1 ships?
From - Mon Jan 29 11:57:28 2001
Return-Path: <owner-gzg-l@scotch.csua.berkeley.edu>
Received: from scotch.csua.berkeley.edu (scotch.CSUA.Berkeley.EDU
[128.32.43.51])
	by lilac.propagation.net (8.8.5/8.8.5) with ESMTP id EAA21947;
	Fri, 26 Jan 2001 04:25:17 -0600
Received: from localhost (daemon@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with SMTP id
f0QAROv23527;
	Fri, 26 Jan 2001 02:27:24 -0800 (PST)
Received: by scotch.csua.berkeley.edu (bulk_mailer v1.12); Fri, 26 Jan
2001 02:27:20 -0800
Received: (from majordom@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) id f0QARJq23506
	for gzg-l-outgoing; Fri, 26 Jan 2001 02:27:19 -0800 (PST)
Received: from soda.csua.berkeley.edu
(IDENT:YkiXBKkUwhEuGLW06ofeLRQgtcP6n4GZ@soda.CSUA.Berkeley.EDU
[128.32.43.52] (may be forged))
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with ESMTP id
f0QARHn23501
	for <gzg-l@lists.CSUA.Berkeley.EDU>; Fri, 26 Jan 2001 02:27:17
-0800 (PST)
Received: from kuju.com ([212.134.167.6])
	by soda.csua.berkeley.edu (8.11.0/8.11.1) with SMTP id
f0QARFk00674
	for <gzg-l@csua.berkeley.edu>; Fri, 26 Jan 2001 02:27:16 -0800
(PST)
	(envelope-from tony.francis@kuju.com)
Received: from kuju.com ([192.111.111.94]) by kuju.com ( IA Mail Server
Version: 3.2.2. Build: 1087 ) ) ; Fri, 26 Jan 2001 10:36:31 +0000
Message-ID: <3A715177.C9B13E26@kuju.com>
Date: Fri, 26 Jan 2001 10:29:11 +0000
From: Tony Francis <tony.francis@kuju.com>
Organization: Kuju Entertainment
X-Mailer: Mozilla 4.73 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: gzg-l@csua.berkeley.edu
Subject: Re: [FT] SSD
References: <p0432040fb6952c9cccec@[63.202.83.21]>
<001f01c08765$2041be40$47fc0e3f@pavilion>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-gzg-l@lists.CSUA.Berkeley.EDU
Reply-To: gzg-l@csua.berkeley.edu
Delivered-To: gzg-l@csua.berkeley.edu
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000
X-UIDL: 39d245de00000f51
Status: RO
Content-Length: 440
Lines: 15

Yes ... but not to hand right now, and my home PC is currently down as
I'm redecorating the room it's in :-(

I've done most NAC and ESU designs on (approx) 90x50mm cards which I
then laminate. The files are in CorelDraw .cdr
files, but I can export to bitmap if required.

Laserlight wrote:
> 
> Anyone have business card sized SSDs for FB1 ships?

-- 
-----------------------------
Tony Francis
Senior Software Engineer
Kuju Entertainment
From - Mon Jan 29 11:57:35 2001
Return-Path: <owner-gzg-l@scotch.csua.berkeley.edu>
Received: from scotch.csua.berkeley.edu (scotch.CSUA.Berkeley.EDU
[128.32.43.51])
	by lilac.propagation.net (8.8.5/8.8.5) with ESMTP id MAA06085;
	Fri, 26 Jan 2001 12:26:19 -0600
Received: from localhost (daemon@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with SMTP id
f0QIOWk31894;
	Fri, 26 Jan 2001 10:24:33 -0800 (PST)
Received: by scotch.csua.berkeley.edu (bulk_mailer v1.12); Fri, 26 Jan
2001 10:24:32 -0800
Received: (from majordom@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) id f0QIOVw31873
	for gzg-l-outgoing; Fri, 26 Jan 2001 10:24:31 -0800 (PST)
Received: from soda.csua.berkeley.edu
(IDENT:CZkg3UuZVc3RdGzLopcCBYSjbAAb12II@soda.CSUA.Berkeley.EDU
[128.32.43.52] (may be forged))
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with ESMTP id
f0QIOTn31868
	for <gzg-l@lists.CSUA.Berkeley.EDU>; Fri, 26 Jan 2001 10:24:29
-0800 (PST)
Received: from mail1.svr.pol.co.uk (mail1.svr.pol.co.uk [195.92.193.18])
	by soda.csua.berkeley.edu (8.11.0/8.11.1) with ESMTP id
f0QIOSk32908
	for <gzg-l@csua.berkeley.edu>; Fri, 26 Jan 2001 10:24:28 -0800
(PST)
	(envelope-from bif@bifsmith.fsnet.co.uk)
Received: from modem-264.eared-grebe.dialup.pol.co.uk ([62.137.185.8]
helo=auser)
	by mail1.svr.pol.co.uk with smtp (Exim 3.13 #0)
	id 14MDXk-0006v0-00
	for gzg-l@csua.berkeley.edu; Fri, 26 Jan 2001 18:24:17 +0000
Message-ID: <000001c087c5$6aa6d780$08b9893e@auser>
From: "bif smith" <bif@bifsmith.fsnet.co.uk>
To: "full thrust" <gzg-l@csua.berkeley.edu>
Subject: RE:FT-Command & Control
Date: Fri, 26 Jan 2001 10:52:24 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-gzg-l@lists.CSUA.Berkeley.EDU
Reply-To: gzg-l@csua.berkeley.edu
Delivered-To: gzg-l@csua.berkeley.edu
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000
X-UIDL: 39d245de00000f65
Status: RO
Content-Length: 2287
Lines: 39

Another idea for flag bridge is that it allows a ship to fire on a enemy
ship, using the targeting range from a closer frendly ship (die rolls),
as
long as it`s within range of the target with it`s own guns in the first
place (I know that someone suggested this before, but it seams a good
reason
to have flag bridges). We set limits for a flag bridge along the lines
of it
can only control/pass data between 18 ships (3 squadrens), and to pass
more
data/link more ships requires the use of more flag bridge equipted ships
to
tie the different flag bridge groups together (like the C3 computers
from
battletech). Also, for each squadren (6 ships) tied together, a ship
needs a
communication bank (2 mass, 4 cost) to handle the data, and this is not
a
core system, so rendering a data group more vulnerable to damage to the
flag
ship (which would carry a big NUKE ME sign anyway, due to the volume of
com
traffic, the enemy would know which ship it is). A flag bridge ship that
is
tieing together the different data groups, would require 2 com banks for
each flag bridge data group it`s co-ordinating. Of course, you could
have a
different number of ships tied together in a data group by a flag bridge
(say one squadren, 6 ships), and there does not only need to be 1 com
bank
per ship (say 3 banks, 1 in use & 2 back ups), but this proposal does
make a
flag bridge data group more dangerous while this system is still
operating.
It also makes a flag bridge ship a primarry target for enemy ships, and
as
such, more inportant for the player to protect in the first place.

Another idea is that a flag bridge allows a squdren tied together in a
data
group to fire in adfcon mode, if within 6 mu, without a adfcon on board
the
ships (the flag bridge ties the data nets together just like adfcon). To
prevent a flag bridge ship lying at the back of the game board, and
allowing
the ships it co-ordinates going and attacking without it, we can say
that
the flag bridge ship is required to remain within 18 mu of it`s data
group
(except the ship linking the different gruops together, which could link
them at upto 36 mu, more valuble, so keeping the range open is more
inportent).

Another rough idea, awaiting comments?

BIF
"yorkshire born,yorkshire bred,
strong in arms, thick in head"