Explore topic-wise InterviewSolutions in .

There is a known bug in LW 4.0's HANDLING of the scene FILE parameter for the animation type. The workaround is to edit the scene file in a TEXT editor. Look for the line: 

AnimationType 4 (the number will vary depending on what you selected for type) and either remove the line or change the number to 0. 

Another workaround is never to save the scene with an animation type selected; always wait and select that at RENDER time. 

This is fixed in LightWave 3D v.5.0.

There is a known bug in LW 4.0's handling of the scene file parameter for the animation type. The workaround is to edit the scene file in a text editor. Look for the line: 

AnimationType 4 (the number will vary depending on what you selected for type) and either remove the line or change the number to 0. 

Another workaround is never to save the scene with an animation type selected; always wait and select that at render time. 

This is fixed in LightWave 3D v.5.0.

This indicates a FAILURE of the hardware key or associated drivers. If re-installing the SOFTWARE fails to CORRECT the PROBLEM, an RMA should be issued for the hardware key.

This indicates a failure of the hardware key or associated drivers. If re-installing the software fails to correct the problem, an RMA should be issued for the hardware key.

This is a bug. On the Camera PANEL, SET RENDER DISPLAY to none, and you will be ABLE to render FlyerClips.

This is a bug. On the Camera Panel, set Render Display to none, and you will be able to render FlyerClips.

Here is the RELEVANT SECTION of the [DRIVERS] section, as it should LOOK after you EDIT it: 

VIDC.IV32=ir32.dll 
;VIDC.IV31=ir32.dll 
;VIDC.RT21=ir21.dll 
;VIDC.YVU9=iyvu9.dll 
VIDC.MSVC=msvidc.drv 
VIDC.MRLE=MSRLE.drv 
VIDC.AASC=AASC.drv 
VIDC.AFLC=flccodec.drv 
VIDC.AFLI=flccodec.drv

Here is the relevant section of the [drivers] section, as it should look after you edit it: 

VIDC.IV32=ir32.dll 
;VIDC.IV31=ir32.dll 
;VIDC.RT21=ir21.dll 
;VIDC.YVU9=iyvu9.dll 
VIDC.MSVC=msvidc.drv 
VIDC.MRLE=MSRLE.drv 
VIDC.AASC=AASC.drv 
VIDC.AFLC=flccodec.drv 
VIDC.AFLI=flccodec.drv

When INSTALLING Lightwave on an HP Vectra Pentium PRO with CONFIGURABLE parallel PORTS and NT, you must set the port type to Centronics. Bi-directional and DMA will return errors.

When installing Lightwave on an HP Vectra Pentium Pro with configurable parallel ports and NT, you must set the port type to Centronics. Bi-directional and DMA will return errors.

This is caused by an OUTDATED Pointer.dll file in windows. Pointer.dll is AVAILABLE on the BBS. Simply REPLACE the old one with the new one and reboot.

This is caused by an outdated Pointer.dll file in windows. Pointer.dll is available on the BBS. Simply replace the old one with the new one and reboot.

This error message will occur after a user has installed the patch file which updates Intel LightWave 5.0 Rev B to Rev C, if the user FAILED to de-archive the plugin ".zip", which is contained INSIDE the MAIN patch ".zip" file. The solution is simply for the user to unzip that archive and make sure the updated plugins end up in the PROPER directories.

This error message will occur after a user has installed the patch file which updates Intel LightWave 5.0 Rev B to Rev C, if the user failed to de-archive the plugin ".zip", which is contained inside the main patch ".zip" file. The solution is simply for the user to unzip that archive and make sure the updated plugins end up in the proper directories.

OpenGL and the Matrox Millennium SEEM to only WORK consistently in 24bpp(24 bit mode) mode in LW 5.0. The 32bpp (TRUE color) mode does not work at all with OpenGL, and the 16bpp mode SEEMS to produce some oddities.

OpenGL and the Matrox Millennium seem to only work consistently in 24bpp(24 bit mode) mode in LW 5.0. The 32bpp (true color) mode does not work at all with OpenGL, and the 16bpp mode seems to produce some oddities.

This occurs when a LOT of images are used, and is due to a BUG in the HIIP LOADER plugin in the initial 4.0 release, wherein images are not FLUSHED after being used. The SOLUTION is to apply the 4.0 patches.

This occurs when a lot of images are used, and is due to a bug in the HIIP loader plugin in the initial 4.0 release, wherein images are not flushed after being used. The solution is to apply the 4.0 patches.

1. On SYSTEMS that do not have VIRTUAL memory, this indicates insufficient RAM to RENDER the scene. The user must add RAM to the SYSTEM or institute virtual memory. 
2. On systems using virtual RAM, if the virtual memory is a set amount, that setting must be increased; if virtual memory is dynamically allocated, the user may have FILLED up the hard drives, and the system will not able to allocate sufficient virtual memory unless the user clears some space on the hard drive.

Just TURNING on'Use OpenGL' under options is only half the operation. Go to the scene panel, and under the 'Show' pulldown, select "Show All Objects as Full Solids". 

In order for OpenGL updating to be DONE in real TIME, the "Bounding BOX Point/Polygon Threshold" on the Options/Layout panel must be set to a number higher than the number of POLYGONS in the scene.

Just turning on'Use OpenGL' under options is only half the operation. Go to the scene panel, and under the 'Show' pulldown, select "Show All Objects as Full Solids". 

In order for OpenGL updating to be done in real time, the "Bounding Box Point/Polygon Threshold" on the Options/Layout panel must be set to a number higher than the number of polygons in the scene.

Toggle NUM lock a few TIMES, you should get the pointer BACK. Weird but it works. We're using Stealth 64 DRAM version here on a couple of machines. If you don't have 2MB on the card, add RAM, and if you don't have the drivers that will let you do 64K colors in 1MB and 24-bit color in 2MB RAM, you can download them from the Diamond BBS, they were recently POSTED there. Check your manual for the number.

Toggle num lock a few times, you should get the pointer back. Weird but it works. We're using Stealth 64 DRAM version here on a couple of machines. If you don't have 2MB on the card, add RAM, and if you don't have the drivers that will let you do 64K colors in 1MB and 24-bit color in 2MB RAM, you can download them from the Diamond BBS, they were recently posted there. Check your manual for the number.

• LIGHTWAVE USES both Phong and Gouraud shading. 
• Phong shading is USED during REALISTIC mode. 
• Gouraud shading is used in quickshade mode.

1. Full HD, any platform. 
2. In Windows systems, if attempting to save to the root directory: If the drive you are saving to has been formatted using the FAT formatting method, there is a Windows limitation of 255 file entries in the root of a FAT partition, including folder names. This limitation does not affect NTFS partitions, and does not affect the number of files that can be placed within a folder on FAT drives. Do not save rendered files to the root of the drive, instead, create a folder and save the output frames into the folder.
3. If saving to a remote drive on a network, try saving to a local drive temporarily to SEE if network issues are really at fault. A "drive full" error is often not returned when the drive is a network share, so it can be harder to troubleshoot. In some situations, a minor POWER glitch due to power grid problems or lightning may not be severe enough to bother the computers, but the network may go dead until the systems are restarted. In these situations, "Unable to write image body DATA" will occur on the systems, even though none of the computers have crashed.
4. If using Windows for WorkGroups 3.1.1 or WINNT FAT File System, and the root filename you have chosen for the sequence exceeds 5 characters, the program's procedure of appending incremental 3 digit SUFFIXES would then exceed these OS's "8 dot 3" limitations for filenames. This is not applicable in WINNT NTFS or WIN95 as these do not have this limitation.

This can occur if full size RENDER display and SHADOW mapping are both TURNED on. Do not ATTEMPT to use both together.

This can occur if full size render display and shadow mapping are both turned on. Do not attempt to use both together.

This happens if the object was modeled facing the wrong WAY in MODELER. Load the object in Modeler, and in the "Top" VIEW turn the end of the object you wish to be the FRONT toward the "+Z", then save the object. Replace the object in layout with the NEW version.

This happens if the object was modeled facing the wrong way in Modeler. Load the object in Modeler, and in the "Top" view turn the end of the object you wish to be the front toward the "+Z", then save the object. Replace the object in layout with the new version.

On attempt to start DEC ALPHA LightWave, Error $001 is returned. The user should refer also to the general $001 Error entry. This error can occur SPECIFICALLY on the DEC Alpha for the following reasons: 

1. The user is TRYING to startup LightWave too early after booting the system. 
2. A faulty Sentinel Driver. Re-install the Sentinel driver. If necessary, DOWNLOAD the latest driver from either the NewTek or Rainbow Technologies online sites. 
3. User is trying to open multiple copies of Lightwave. 
4. Parallel Port is not SET to Standard Parallel Port mode. 
5. BIOS may be incompatible. This should be considered if LightWave has never worked, and the user is certain he has the proper drivers for the hardware key, and all other factors have been eliminated.

On attempt to start DEC Alpha LightWave, Error $001 is returned. The user should refer also to the general $001 Error entry. This error can occur specifically on the DEC Alpha for the following reasons: 

This was a BUG in the INITIAL DEC Alpha RELEASE. APPLY the 4.0 patches for Alpha.

This was a bug in the initial DEC Alpha release. Apply the 4.0 patches for Alpha.

Make sure that the "Data OVERLAY" line in lw.cfg is set to ZERO, or CLICK data overlay button once REGARDLESS of deselection appearance. It will be deselected.

Make sure that the "Data Overlay" line in lw.cfg is set to zero, or click data overlay button once regardless of deselection appearance. It will be deselected.

This will occur when USING the Cogent DRIVERS. Use the Deskstation drivers INSTEAD.

This will occur when using the Cogent drivers. Use the Deskstation drivers instead.

DISPLACEMENT Map ENVELOPE Workaround in Lightwave 3.5

When a displacement map has been applied to an object, the POLYGON Size envelope can be used as an envelope for displacement MAPPING in 3.x LW.

Displacement Map Envelope Workaround in Lightwave 3.5

When a displacement map has been applied to an object, the Polygon Size envelope can be used as an envelope for displacement mapping in 3.x LW.

If you are only familiar with the Mac platform you will notice two problems that may cause LightWave to crash. Firstly LightWave as yet does not come with much in the way of error trapping which means that LightWave can EASILY crash your Mac if something goes WRONG. A good example of this is that normally on a Mac Application you can be two or three moves ahead with keyboard commands, the Mac will catch you up and PERFORM them, but in LightWave using the keyboard faster than the application can cause the Mac to crash. Secondly LightWave does not have any onscreen progress notification (eg : a clock or a progress bar). If LightWave appears to FREEZE just after you perform a task, it is performing the task. A freeze is INDICATED by the user not being able to move the mouse on screen.

If you are only familiar with the Mac platform you will notice two problems that may cause LightWave to crash. Firstly LightWave as yet does not come with much in the way of error trapping which means that LightWave can easily crash your Mac if something goes wrong. A good example of this is that normally on a Mac Application you can be two or three moves ahead with keyboard commands, the Mac will catch you up and perform them, but in LightWave using the keyboard faster than the application can cause the Mac to crash. Secondly LightWave does not have any onscreen progress notification (eg : a clock or a progress bar). If LightWave appears to freeze just after you perform a task, it is performing the task. A freeze is indicated by the user not being able to move the mouse on screen.

No. You can RENAME them in LAYOUT once they have a NAME. You have to name them in MODELER.

No. You can rename them in Layout once they have a name. You have to name them in Modeler.

Yes. Right click on the HUB icon, select properties>select inverval to be saved at. You can even set an AUTOMATIC SHUTDOWN if you wanted.

Yes. Right click on the HUB icon, select properties>select inverval to be saved at. You can even set an automatic shutdown if you wanted.

FILMBOX can EXPORT as a LIGHTWAVE SCENE file…but SIMI is not compatable with Lightwave.

Filmbox can export as a Lightwave scene file…but Simi is not compatable with Lightwave.

Yes, so long as the card is actually designed to do so. Some cards with an SVGA connector and a DVI connector are designed only to send the same display out both ports. Other boards use a DIGITAL-only DVI port (DVI-D) that cannot be adapted to an ANALOG monitor. The card must have a DVI-I connector that provides both analog and digital signals, and must be a true dual head card. Some such cards, the Asus V7100 2V1D for EXAMPLE, INCLUDE a DVI-to-SVGA adapter. You can also purchase such adapters. Below is a list of sources. We'll be adding sources of such adapters to the list as we locate them. 

Yes, so long as the card is actually designed to do so. Some cards with an SVGA connector and a DVI connector are designed only to send the same display out both ports. Other boards use a digital-only DVI port (DVI-D) that cannot be adapted to an analog monitor. The card must have a DVI-I connector that provides both analog and digital signals, and must be a true dual head card. Some such cards, the Asus V7100 2V1D for example, include a DVI-to-SVGA adapter. You can also purchase such adapters. Below is a list of sources. We'll be adding sources of such adapters to the list as we locate them. 

YES. As long as the PROGRAM supports .OBJ , .dxf , or .3ds you should be able to export it to those PROGRAMS.

Yes. As long as the program supports .obj , .dxf , or .3ds you should be able to export it to those programs.

SHADING SAMPLES > RENDER GLOBALS > Render.

Shading Samples > Render Globals > Render.

ADDS and REMOVES GEOMETRY SEGMENTS.

Adds and removes geometry segments.

SELECT the SURFACE in the surface EDITOR.

Select the surface in the surface editor.

1. SEPARATION
2. ALIGNMENT
3. and COHESION

%USERPROFILE%.NewTekLightWave11.0configs

%USERPROFILE%.NewTekLightWave11.0configs

It DETERMINES the CAMERA RAYS PER PIXEL.

It determines the camera rays per pixel.

The ServerTagInfo and ServerRecord STRUCTURES.

The ServerTagInfo and ServerRecord structures.

CREATING an EXPLODED MORPH MAP of the PARTS.

Creating an exploded morph map of the parts.

3D COMPUTER models of COORDINATED ANIMAL MOTION.

3D computer models of coordinated animal motion.

SETTING up scripts to handle the commands that CONFIGURE your DEVICE.

Setting up scripts to handle the commands that configure your device.

Your SURFACE's LUMINOSITY CHANNEL.

Your surface's Luminosity channel.

ASSIGNS your connected DEVICE to be USED with the VIRTUAL STUDIO.

Assigns your connected device to be used with the Virtual Studio.

BULLET GROUP, DYNAMIC BODY, COLLISION Body.

Bullet Group, Dynamic Body, Collision Body.

It creates a user-defined PADDING so that there are no SEAMS when the size of the MAP is reduced.

It creates a user-defined padding so that there are no seams when the size of the map is reduced.

It REVERSES diffuse and ambient, MAKING it NECESSARY to BACK up your PROJECT before using it.

It reverses diffuse and ambient, making it necessary to back up your project before using it.

CALCULATES the 'heaviness' of an ITEM.

Calculates the 'heaviness' of an item.

CHOOSE NODE EDITOR as the PROCEDURAL TEXTURE.

Choose Node Editor as the procedural texture.

It BREAKS an ITEM down into PARTS for USE with DYNAMICS.

It breaks an item down into parts for use with dynamics.