aozer@next.com (Ali Ozer) (06/20/91)
Hey folks, Is the LightWave 3D object file format published anywhere? It seems to be an IFF file, but not one I've seen described anywhere... Ali, Ali_Ozer@NeXT.com
ACPS1072@RYERSON <ACPS1072@Ryerson.CA> (06/21/91)
I've heard somewhere that Lightwave accepts the standard Videoscape objects. However, these VideoScape objects do not support texture mapping, bump mapping, road mapping :-> of any kind. This doesn't help does it. Derek Lang<<<<< | ACPS1072@Ryerson | "Get this clown trained. I want him in the games Toronto, ON | until he dies playing. Acknowledge." Canada | - Master Control Program
James_Hastings-Trew@tptbbs.UUCP (James Hastings-Trew) (06/24/91)
In a message dated Sun 23 Jun 91 04:52, Acps1072@ryerson.ca (acps1072@ryers wrote: A> I've heard somewhere that Lightwave accepts the standard Videoscape A> objects. However, these VideoScape objects do not support texture A> mapping, bump mapping, road mapping :-> of any kind. What happens is thaat each polygon gets mapped individually instead of each being treated as part of a surface. This does not show up very badly except in the volumetric textures - wood, marble, ripples, fractal noise, etc. The marble, fractal noise and fractal bump maps show the least problem, and the wood and ripples show the moost. I have tried importing these kinds of objects into the lightwave modeller, and using the merge points function, but this does not help.
mark@calvin..westford.ccur.com (Mark Thompson) (06/25/91)
In article <James_Hastings-Trew.3384@tptbbs.UUCP> James_Hastings-Trew@tptbbs.UUCP (James Hastings-Trew) writes: >In a message dated Sun 23 Jun 91 04:52, Acps1072@ryerson.ca (acps1072@ryers >wrote: > A> I've heard somewhere that Lightwave accepts the standard Videoscape > A> objects. However, these VideoScape objects do not support texture > A> mapping, bump mapping, road mapping :-> of any kind. The VideScape format does not support texture definitions but this does not prevent you from defining new surface attributes for the object once it is loaded into LightWave. >What happens is thaat each polygon gets mapped individually instead of each >being treated as part of a surface. This does not show up very badly except >in the volumetric textures - wood, marble, ripples, fractal noise, etc. The >marble, fractal noise and fractal bump maps show the least problem, and the >wood and ripples show the moost. This is not true. I'm am not sure what you might be doing wrong but I have no problem assigning 3D procedural textures to the surfaces of VideoScape and Sculpt objects. These surfaces work just like any other Lightwave surface except for the fact that when they are imported in, they automatically load 2 polygons for each one specified (for front and back sides) so that back face culling won't inadvertantly delete a front facing surface. As for the LightWave file format, as a beta-tester, I have a hard copy of the 3D format specification , but I don't think it has been publicly released other than to a few developers. You would have to contact NewTek. %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~% % ` ' Mark Thompson CONCURRENT COMPUTER % % --==* RADIANT *==-- mark@westford.ccur.com Principal Graphics % % ' Image ` ...!uunet!masscomp!mark Hardware Architect % % Productions (508)392-2480 (603)424-1829 & General Nuisance % % % ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~