[delta_v] Re: delta_v digest, Vol 1 #243 - 7 msgs
Daniel Hill
delta_v@AmbrosiaSW.com
Sat, 05 Oct 2002 08:57:42 +0100
Istop sending me these emails
> From: delta_v-request@AmbrosiaSW.com
> Reply-To: delta_v@AmbrosiaSW.com
> Date: Fri, 04 Oct 2002 12:00:02 -0400
> To: delta_v@AmbrosiaSW.com
> Subject: delta_v digest, Vol 1 #243 - 7 msgs
>
> Send delta_v mailing list submissions to
> delta_v@AmbrosiaSW.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.AmbrosiaSW.com/mailman/listinfo/delta_v
> or, via email, send a message with subject or body 'help' to
> delta_v-request@AmbrosiaSW.com
>
> You can reach the person managing the list at
> delta_v-admin@AmbrosiaSW.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of delta_v digest..."
>
>
> Today's Topics:
>
> 1. Re: (no subject) (Michael Kelly)
> 2. Re: Here's a tougher one. (JPPAB@aol.com)
> 3. Re: Here's a tougher one. (Bryce)
> 4. Re: Here's a tougher one. (Bryce)
> 5. Re: Here's a tougher one. (Zhouj100@aol.com)
> 6. Re: Here's a tougher one. (Orrin L. Converse)
> 7. Re: Here's a tougher one. (Bryce)
>
> --__--__--
>
> Message: 1
> Date: Thu, 3 Oct 2002 09:38:35 -0700
> From: Michael Kelly <jedimike@san.rr.com>
> To: delta_v@AmbrosiaSW.com
> Subject: Re: [delta_v] (no subject)
> Reply-To: delta_v@AmbrosiaSW.com
>
> On Thu, Oct 03, 2002 at 04:04:14PM +0100, Les robinson wrote:
>> Because it sends through piles of garbage and is annoying
>
> Piles? Garbage? You don't appear to be very familiar with mailing lists...
> delta_v gets nearly NO messages and the people are suprisingly intelligent. I
> would not call that piles of garbage.
>
> --
> Michael
>
> --__--__--
>
> Message: 2
> From: JPPAB@aol.com
> Date: Thu, 3 Oct 2002 15:55:35 EDT
> Subject: Re: [delta_v] Here's a tougher one.
> To: delta_v@ambrosiasw.com
> Reply-To: delta_v@AmbrosiaSW.com
>
>> Yes. I assume this isn't a retorical question, though :)
>
>> The Shän resource is attached to the Shïp with the same resource ID, e.g.
>
>> If the Shuttlecraft has resource ID 128 then it will use shän 128.
>
>>
>
>> This was confusing to me as well at first.
>
>>
>
>> - Bryce
>
> I'm afraid it is not that simple. Say I have a ship usind shïp no. 411, if I
> put shän 411 as the animation then it just puts a picture of a stationary
> cargo shuttle up there. The picture will not visibly turn, although it can be
> manuvered. And the weapon always fires strait up. Wierd. And varients of the
> same ship are being stupid too, as I have know idea of how to do them without
> duping shän resources, not too stylish. I seriously have tried everything I
> can think of. If it works on your end then I'm happy for you. Should I
> reinstall nova's data files, for all the good that will do?
>
> -wyvern
>
> --__--__--
>
> Message: 3
> Date: Wed, 2 Oct 2002 13:16:17 -0700
> From: Bryce <evnova@hotpop.com>
> Subject: Re: [delta_v] Here's a tougher one.
> To: delta_v@AmbrosiaSW.com
> Reply-To: delta_v@AmbrosiaSW.com
>
>>
>>> Yes. I assume this isn't a retorical question, though :)
>>
>>> The Shän resource is attached to the Shïp with the same resource ID, e.g.
>>
>>> If the Shuttlecraft has resource ID 128 then it will use shän 128.
>>
>>>
>>
>>> This was confusing to me as well at first.
>>
>>>
>>
>>> - Bryce
>>
>> I'm afraid it is not that simple. Say I have a ship usind shïp no. 411,
> if I
>> put shän 411 as the animation then it just puts a picture of a
> stationary
>> cargo shuttle up there. The picture will not visibly turn, although it
> can
>> be
>> manuvered. And the weapon always fires strait up. Wierd. And varients of
> the
>> same ship are being stupid too, as I have know idea of how to do them
>> without
>> duping shän resources, not too stylish. I seriously have tried
> everything I
>> can think of. If it works on your end then I'm happy for you. Should I
>> reinstall nova's data files, for all the good that will do?
>>
>> -wyvern
>
> 411 is too high. You can only have 256 ships (Not exactly a
> crippling limitation, but not in compliance with the none-one-infinity
> rule of design), which means the highest ID you can have is 256+128 (128
> is the number at which almost all resources begin), and this wowrks out to
> 384.
>
> Lower your res IDs (Lots of work if you have many ships, sorry), or join
> the movement to whine to Matt about having any limitations on the number
> of anything. (Not at all a hard change to implement, I would think, as it
> seems to me it would be little more than a matter of having the engine
> count the number of a perticular type of resource and then dimension an
> array accordingly. Since many scenarios do not use all 256 ships, 10,000
> odd missionbits, etc, this might actualy reduce the ammount of memory EVN
> needed in most cases.)
>
>
>
> --__--__--
>
> Message: 4
> Date: Wed, 2 Oct 2002 13:20:48 -0700
> From: Bryce <evnova@hotpop.com>
> Subject: Re: [delta_v] Here's a tougher one.
> To: delta_v@AmbrosiaSW.com
> Reply-To: delta_v@AmbrosiaSW.com
>
>>
>>> And varients of the
>> same ship are being stupid too, as I have know idea of how to do them
>> without
>> duping shän resources, not too stylish.
>
>
> That is the way it's done. Nova has its unsusal properties, this is one of
> them.
>
>
>
> --__--__--
>
> Message: 5
> From: Zhouj100@aol.com
> Date: Thu, 3 Oct 2002 19:58:41 EDT
> Subject: Re: [delta_v] Here's a tougher one.
> To: delta_v@ambrosiasw.com
> Reply-To: delta_v@AmbrosiaSW.com
>
>
> --part1_d8.1e89cb97.2ace33b1_boundary
> Content-Type: text/plain; charset="ISO-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Last I heard, Nova's limit on ships was 768, not 256. Perhaps the new=20
> versions changed it...
>
>
> In a message dated 10/3/02 1:18:47 PM, evnova@hotpop.com writes:
>
>
>>> =20
>>>> Yes. I assume this isn't a retorical question, though :)
>>> =20
>>>> The Sh=E4n resource is attached to the Sh=EFp with the same resource ID,=
> e.g.
>>> =20
>>>> If the Shuttlecraft has resource ID 128 then it will use sh=E4n 128.
>>> =20
>>>>
>>> =20
>>>> This was confusing to me as well at first.
>>> =20
>>>>
>>> =20
>>>> - Bryce
>>> =20
>>> I'm afraid it is not that simple. Say I have a ship usind sh=EFp no. 411=
> ,=20
>> if I=20
>>> put sh=E4n 411 as the animation then it just puts a picture of a=20
>> stationary=20
>>> cargo shuttle up there. The picture will not visibly turn, although it=20
>> can
>>> be=20
>>> manuvered. And the weapon always fires strait up. Wierd. And varients of=
> =20
>> the=20
>>> same ship are being stupid too, as I have know idea of how to do them
>>> without=20
>>> duping sh=E4n resources, not too stylish. I seriously have tried=20
>> everything I=20
>>> can think of. If it works on your end then I'm happy for you. Should I=20
>>> reinstall nova's data files, for all the good that will do?
>>> =20
>>> =A0 =A0 =A0 =A0 -wyvern
>> =20
>> 411 is too high. You can only have 256 ships (Not exactly a=20
>> crippling limitation, but not in compliance with the none-one-infinity=20
>> rule of design), which means the highest ID you can have is 256+128 (128=20
>> is the number at which almost all resources begin), and this wowrks out to=
> =20
>> 384.
>> =20
>> Lower your res IDs (Lots of work if you have many ships, sorry), or join=20
>> the movement to whine to Matt about having any limitations on the number=20
>> of anything. (Not at all a hard change to implement, I would think, as it=20
>> seems to me it would be little more than a matter of having the engine=20
>> count the number of a perticular type of resource and then dimension an=20
>> array accordingly. Since many scenarios do not use all 256 ships, 10,000=20
>> odd missionbits, etc, this might actualy reduce the ammount of memory EVN=20
>> needed in most cases.)
>> =20
>> =20
>> _______________________________________________
>> delta_v mailing list
>> delta_v@AmbrosiaSW.com
>> http://mail.AmbrosiaSW.com/mailman/listinfo/delta_v
>> =20
>> =20
>
>
> --part1_d8.1e89cb97.2ace33b1_boundary
> Content-Type: text/html; charset="ISO-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <HTML><FONT FACE=3Darial,helvetica><FONT COLOR=3D"#000000" FACE=3D"Geneva" F=
> AMILY=3D"SANSSERIF" SIZE=3D"2" STYLE=3D"BACKGROUND-COLOR: #FFFFFF"> &nb=
> sp; Last I heard, Nova's limit on ships was 768, not 256. Perhap=
> s the new versions changed it...<BR>
> <BR>
> <BR>
> In a message dated 10/3/02 1:18:47 PM, evnova@hotpop.com writes:<BR>
> <BR>
> <BR>
> <BLOCKQUOTE CITE STYLE=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT:
> 5px;=20=
> MARGIN-RIGHT: 0px; PADDING-LEFT: 5px" TYPE=3D"CITE"></FONT><FONT COLOR=3D"#0=
> 00000" FACE=3D"Geneva" FAMILY=3D"SANSSERIF" SIZE=3D"2" STYLE=3D"BACKGROUND-C=
> OLOR: #FFFFFF">> <BR>
> >>Yes. I assume this isn't a retorical question, though :)<BR>
> > <BR>
> >>The Sh=E4n resource is attached to the Sh=EFp with the same resource=
> ID, e.g.<BR>
> > <BR>
> >>If the Shuttlecraft has resource ID 128 then it will use sh=E4n 128.=
> <BR>
> > <BR>
> >><BR>
> > <BR>
> >>This was confusing to me as well at first.<BR>
> > <BR>
> >><BR>
> > <BR>
> >>- Bryce<BR>
> > <BR>
> > I'm afraid it is not that simple. Say I have a ship usind sh=EFp no. 41=
> 1, <BR>
> if I <BR>
> > put sh=E4n 411 as the animation then it just puts a picture of a <BR>
> stationary <BR>
> > cargo shuttle up there. The picture will not visibly turn, although
> it=20=
> <BR>
> can<BR>
> > be <BR>
> > manuvered. And the weapon always fires strait up. Wierd. And varients o=
> f <BR>
> the <BR>
> > same ship are being stupid too, as I have know idea of how to do them<B=
> R>
> > without <BR>
> > duping sh=E4n resources, not too stylish. I seriously have tried <BR>
> everything I <BR>
> > can think of. If it works on your end then I'm happy for you. Should
> I=20=
> <BR>
> > reinstall nova's data files, for all the good that will do?<BR>
> > <BR>
> >=A0 =A0 =A0 =A0 -wyvern<BR>
> <BR>
> 411 is too high. You can only have 256 ships (Not exactly a <BR>
> crippling limitation, but not in compliance with the none-one-infinity <BR>
> rule of design), which means the highest ID you can have is 256+128 (128 <BR=
>>
> is the number at which almost all resources begin), and this wowrks out to <=
> BR>
> 384.<BR>
> <BR>
> Lower your res IDs (Lots of work if you have many ships, sorry), or join <BR=
>>
> the movement to whine to Matt about having any limitations on the number <BR=
>>
> of anything. (Not at all a hard change to implement, I would think, as it <B=
> R>
> seems to me it would be little more than a matter of having the engine <BR>
> count the number of a perticular type of resource and then dimension an <BR>
> array accordingly. Since many scenarios do not use all 256 ships, 10,000 <BR=
>>
> odd missionbits, etc, this might actualy reduce the ammount of memory EVN <B=
> R>
> needed in most cases.)<BR>
> <BR>
> <BR>
> _______________________________________________<BR>
> delta_v mailing list<BR>
> delta_v@AmbrosiaSW.com<BR>
> http://mail.AmbrosiaSW.com/mailman/listinfo/delta_v<BR>
> <BR>
> </BLOCKQUOTE></FONT><FONT COLOR=3D"#000000" FACE=3D"Geneva" FAMILY=3D"SANSSE=
> RIF" SIZE=3D"2" STYLE=3D"BACKGROUND-COLOR: #FFFFFF"><BR>
> <BR>
> </FONT><FONT COLOR=3D"#000000" FACE=3D"Geneva" FAMILY=3D"SANSSERIF" SIZE=3D"=
> 2" STYLE=3D"BACKGROUND-COLOR: #FFFFFF"></FONT></HTML>
> --part1_d8.1e89cb97.2ace33b1_boundary--
>
> --__--__--
>
> Message: 6
> From: "Orrin L. Converse" <converse@techline.com>
> To: delta_v@AmbrosiaSW.com
> Date: Thu, 03 Oct 2002 17:48:03 -0700
> Subject: Re: [delta_v] Here's a tougher one.
> Reply-To: delta_v@AmbrosiaSW.com
>
> 10/02/2002 1:16:17 PM, Bryce <evnova@hotpop.com> wrote:
>
>> Lower your res IDs (Lots of work if you have many ships, sorry), or join
>> the movement to whine to Matt about having any limitations on the number
>> of anything.
>
> Wait - I'm having a vision! I see Matt...His mouth is moving...I'm
> hearing a voice... "...it works fine the way it is. There will be no new
> features implemented..."
>
> Whoa. That was weird. ;-)
>
>
>
>
>
>
> --__--__--
>
> Message: 7
> Date: Thu, 3 Oct 2002 08:30:17 -0700
> From: Bryce <evnova@hotpop.com>
> Subject: Re: [delta_v] Here's a tougher one.
> To: delta_v@AmbrosiaSW.com
> Reply-To: delta_v@AmbrosiaSW.com
>
>>
>> 10/02/2002 1:16:17 PM, Bryce <evnova@hotpop.com> wrote:
>>
>>> Lower your res IDs (Lots of work if you have many ships, sorry), or
> join
>>> the movement to whine to Matt about having any limitations on the
> number
>>> of anything.
>>
>> Wait - I'm having a vision! I see Matt...His mouth is moving...I'm
>> hearing a voice... "...it works fine the way it is. There will be
> no new
>> features implemented..."
>>
>> Whoa. That was weird. ;-)
>>
> Well, whatever totaly arbitrary number the maximums are set to, it
> will always be to small for someone who wants to make the biggest
> thing yet. Making it unlimited will result most likely in more
> reasonibly sized TCs, and as a result more *completed* TCs, which are
> good for us and ambrosia.
>
>
>
>
> --__--__--
>
> _______________________________________________
> delta_v mailing list
> delta_v@AmbrosiaSW.com
> http://mail.AmbrosiaSW.com/mailman/listinfo/delta_v
>
>
> End of delta_v Digest