Path: chuka.playstation.co.uk!news From: James Russell Newsgroups: scee.yaroze.programming.3d_graphics Subject: Re: GsLinkObject4 Confusion Date: Tue, 25 Aug 1998 09:59:51 +0100 Organization: Sony Computer Entertainment Europe Lines: 24 Message-ID: <35E27D07.B1C5AFB1@scee.sony.co.uk> References: <35E1C90B.AE@funnytown.com> NNTP-Posting-Host: mailgate.scee.sony.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.5b1 [en] (Win95; I) X-Accept-Language: en Gerrit Goossen wrote: > > While attempting to write some code to read primitives from an already > linked TMD model (for the purpose of using its polys for collision > detection) I discovered that GsLinkObject4 is tinkering with the first > primitive in the object: Specifically it writes over the first > primitive's ilen and olen with "0x0400". It's not just the first primitive that changes. It adjusts the Ilen/Olen every time the primitive code changes. The number that it writes is a 16 bit value that describes the number of primitives of the current type to follow. So it looks like you've got 0x400 (= 1024) polygons of a certain type in consecutive order. Subsequent primitives of the same type are not adjusted. If there are primitives of a different type, then the first primitive in that set will also have the number of primitives of that type. Cheers, James -- == James_Russell@scee.sony.co.uk +44 (171) 447-1626 == Developer Support Engineer - Sony Computer Entertainment Europe My lucky color just faded.