Customizing LightWave

Clearing Configs

If you are required to clear configs for any reason, the way to do it is to make sure LightWave is closed, including the Hub application (in your Windows taskbar or Macintosh dock). Then, navigate to:

Config Backup

When configs are changed now, a backup is created of existing settings before changes are enabled.

Edit Keyboard Shortcuts

(default keyboard shortcut Alt F9)

We strongly suggest that you keep the default keyboard mapping assignments and make new shortcuts only to unmapped keys. (Most of the function keys are open.) Otherwise, technical support and using the documentation may become difficult.

Like the menus, keyboard shortcuts can be configured to suit your needs. To display the Configure Keys Panel, choose Edit \> Edit Keyboard Shortcuts.

Edit Menu Layout

(default keyboard shortcut Alt F10)

We strongly suggest that you keep the default menu organization intact. Otherwise, technical support and using the documentation may become involved. A better solution is to create a new menu tab and/or groups and place your frequently used tools in them.

LightWave menus are customizable. You can add, remove, group, and reorganize commands. Choose Edit \> Edit Menu Layout to open the Configure Menus Panel.

In the (right) Menus window, several main sections have sub-items, which are indented to show the hierarchical relationships. Top Group contains the items that are always visible no matter which tab is selected. Main Menu items are the main tabs and related buttons for the main interface toolbar. Left, Middle, and Right Mouse Button Menu (when available) are the menus that appear when the Shift + Ctrl keys are held down along with the corresponding mouse button. There may be other menu sections defined.

In the Menus window, dots indicate commands while arrows indicate groups of commands/sub-groups beneath it. If the arrow points to the right, the group’s sub-menu items are collapsed and not visible. To reveal the sub-menu items for a collapsed group, just click on its right-facing arrow. To collapse an open group, click on its downward-facing arrow.

Finding Assignments and Commands

If you have a command selected in the left window and click Find, the command, if any, on the right will become selected. Selecting a command in the right window and clicking Find will choose the matching command in the left window.

Clicking Search allows you to type in a search phrase to find a command. Search is case-sensitive and will find the first instance when first run, and can be used iteratively to find additional instances by just hitting the button again, as it retains the string until you type in a new one.

Menu Branches

Menu branches can be exported and imported allowing for rapid customization of several menu entries. To export a menu branch, right-click over the group you wish to export and choose Export Branch.

The file saved can be loaded into a different installation of LightWave using the same method - right-clicking the area in which you wish to import a menu branch and choose Import Branch.

New to LightWave 2020 is an additional command Import and Replace Branch.

Edit Plugins

(default keyboard shortcut Alt F11)

Use the Edit Plugins command to review and delete plugins that have been added. In Modeler, choose Utilities\> Plugins > Edit Plugins.

Window Config Loader

This command is a quick way to launch a window configuration that was generated by the Window Configure tool.

Scene Metadata

If your pipeline dictates that you need to use a different path structure for use with other applications, it can be awkward when you need to bring scenes back into LightWave for further editing, needing to tell LightWave where a project's images are for instance because you have them under a different path. You can now save metadata to a scene file as comments if your workflow dictates that you vary from the standard LightWave content directory structure of Images, Objects, and Scenes.

When saving out a scene file, append the content directory information as comments to the very end of the scene file.

If Use Custom Paths is left unchecked, this should be a single comment like this:

// ContentDir: "X:/project/_library/assets/LW_Content"

If Use Custom Paths is checked in your LightWave options Paths tab, append all of the custom paths as comments to the end of the LWS file as well:

// ContentDir: X:/project/_library/assets/LW_Content
// ObjectsDir: X:/project/_library/assets/LW_Content/Objects
// ImagesDir: X:/project/_library/assets/LW_Content/Images

The full list of custom paths is as follows:

ContentDir "X:/project/"
ScenesDir "X:/project/Scenes"
ObjectsDir "X:/project/Objects"
SurfacesDir "X:/project/Surfaces"
ShadersDir "X:/project/Shaders"
ImagesDir "X:/project/Images"
PreviewsDir "X:/project/Previews"
MotionsDir "X:/project/Motions"
EnvelopesDir "X:/project/Envelopes"
AnimationsDir "X:/project/Animations"
NodesDir "X:/project/Nodes"
SoundsDir "X:/project/Sounds"
DynamicsDir "X:/project/Dynamics"
RigsDir "X:/project/Rigs"
LightsDir "X:/project/Lights"
RadiosityDir "X:/project/Radiosity"
ColorTablesDir "X:/project/ColorTables"
ImageCacheDir "X:/project/ImageCache"
VertCacheDir "X:/project/VertCache"
BackupDir "X:/project/Backup"

Interface Color Customization

Customizing the Interface colors for Modeler and Layout is accessed through the Options panels in both applications - the Display tab in Layout and the Display Options Interface tab in Modeler. You will need to restart LightWave to see the changes you have made.

Configuration Files

For Macintosh OS X, the LightWave configuration files are stored in your ~/Library/Application Support/NewTek/2020.0 folder like so:

• Extension Cache

• Extensions 2020

• Hub 2020

• Layout 2020

• Modeler 2020

For Windows 7 and onwards, the configuration files are kept in <USERNAME>\\.NewTek\\LightWave\\2020.0. They are named:

• Extension Cache-64

• LW2020-64.CFG

• LWEXT2020-64.CFG

• LWHUB2020-64.CFG

• LWM2020-64.CFG

Generally, you will not need to edit these files directly; however, you might need to remove these files if they get corrupted.

Startup Options

The following options are described for use in Windows. At the end of the list of Startup options, there is an Info box for Macintosh OS X.

In Windows, shortcuts need to be edited for both the Modeler and Layout applications where appropriate for flags to take effect.

-c for Configs

If you wish to redirect where LightWave stores the configs it creates away from the regular C:\Users\<username>\.NewTek\LightWave\<version> folder, you can add -c to the end of your shortcut's targetline with the path chosen for the configs.

-d for Content

Layout has a -d option for designating a content directory to be used at startup. In Windows, it can be added as a startup option by editing the icon properties of the shortcut created for launching Layout and adding -d and the directory you wish to use, like so:

-p for Plugins

The -p option is for creating a different location for plugin files - useful for instance when running multiple copies of LightWave over a network with a central store of plugins.

-0 for Command IPC

Using the -0 commandline flag will not run the Hub but use an Interprocess communications system. Layout and Modeler all notify each other when a mesh file has been saved to disc, and the applications that have that file open and have not applied modifications during the session will update from the new version on disc. For example, if both Layout and Modeler have “bob.lwo” open, Modeler has some edits applied to it, and Layout saves it transformed, Modeler will not automatically update from the disc.

If subsequently the object is saved out from Modeler, that will overwrite the changes made by Layout, and Layout will update from the save if no further changes were applied in Layout during the interim.

-i for Isolate

The ‘isolate’ flag (‘ -i’) will completely disable all IPC mechanisms (Hub and CommandIPC), leaving the application isolated from all other product actions.

--frame-end-beep

Use this flag to play an existing sound file when a frame finishes rendering. The syntax is as follows:

--frame-end-beep={sound_file}

--anim-end-beep

Use this flag to play an existing sound file when a frame sequence finishes rendering. The syntax is as follows:

--anim-end-beep={sound_file}

--preview-end-beep

Use this flag to play an existing sound file when a preview finishes rendering. The syntax is as follows:

--preview-end-beep={sound_file}

-f for Font

Use this flag to call a system font as the typeface to use for Layout or Modeler. The syntax is as follows:

-f(font_name@font_size)

--command-port

The --command-port option enables an operating system-based communication mechanism that allows external processes to feed LightWave Command Sequence commands directly into the LightWave application. This allows real-time and continuous execution of CS commands within running LightWave programs.

The distributed LightWave product includes a Python package that works with both Python v2 and v3 that allows Python programs to utilize this mechanism.

When enabled, the command port number selected is displayed in the LightWave application's titlebar.(e.g., " --command-port=45454").

This mechanism does not function with Screamernet.

(the command-port mechanism is somewhat reminiscent of the Amiga AREXX system LightWave used to support.)

--dpiaware

Described below.

macOS Specifics

For macOS, the procedure for adding command line arguments is more involved. Here is how to make a launch shortcut icon using AppleScript:

1. Open the /Applications/Utility/Script Editor.app application

2. Choose to create a New Document.

   
   

   Enter the following text:

   
   

   do shell script "/Applications/NewTek/LightWave_2020/Layout.app/Contents/macOS/Layout"

   
   

   (command line arguments should be added here, before the quote marks, for instance do shell script "/Applications/NewTek/LightWave3D_2020.1.2/Layout.app/Contents/MacOS/Layout -i" will set the Isolate flag.

3. In the Script Editor, use the dropdown to save the document as an Application to your Desktop.

4. Double-click the resulting application icon.

: To re-edit the resulting application, drag it to the dock "Script Editor" icon.

-r

Lastly, a joke entry for bamboozling co-workers. Enter this as an option, and watch your colleague's face as they start LightWave...

HiDPI

LightWave 2020 presents a new way of working with LightWave on screens at a resolution greater than 1920 x 1080 here.

Layout Startup Command

If the LW2020-64.CFG configuration file contains a line beginning with “StartupCommand,” Layout will try to execute the rest of the line as a command after the main interface is first opened. The command can have arguments and it can refer to a generic plug-in or script.

Default Scene at Start

If you'd like Layout to start with the same scene setup every time it's easy to achieve but you need to use a single content directory to do so (if you see the "Would you like to change content directory?" message when you load scenes, this will probably not work for you out of the box). To create a default scene, simply set up something obviously different - change the light color to red.

Now use the Save menu option Save Scene as Default. In Layout Options (O) check Clear Scene To Default and finally restart LightWave. Now, when you start Layout, you will see that the default light color is red.

To check this is working correctly, try loading a different scene. If you get a window like this:

You will need to do more work. Your LightWave content is probably arranged like so:

• Content:

  • Project 1

    • Objects

    • Images

    • Scenes

  • Project 2

    • Objects

    • Images

    • Scenes

etc.

For the default scene to work reliably, you have two choices. The first is for your content to structure to look like this:

Content:

• Objects

• Project 1

• Project 2

• Images

• Project 1

• Project 2

• Scenes

• Project 1

• Project 2

This is the same kind of organization (global) as the stock LightWave content if you have a look. Both this and the project-based way of managing content present their own problems - the first creates lots of file duplication, the second is difficult to separate out for sending to the farm, etc.

The second choice, if you want to keep the benefit of a default scene but are committed to the project-based content route, is to simply create a template content directory structure that you can always use, including a scene with your preferred settings. Copy this into place at the start of a project.

Customizing Layout Viewport Navigation

The mouse directions used for viewport navigation can be customized by editing the WorldNavigation entry in the LW2020-64.CFG configuration file. It has four boolean values that correspond to panning via icon and Alt key, and rotation via icon and Alt key. Zero values mean that the viewpoint moves in the same direction as the mouse, and ones mean that the world appears to move with the mouse. For example, the default in LightWave 9 is 0 1 0 1. The old 5.6 setting would be 1 1 0 0. See also Navigation Options.

Customizing Camera Presets

The camera resolution presets are stored in the LW2020-64.CFG configuration file using the keyword “ResolutionPreset.” Each preset includes a width and height, pixel aspect ratio, mask settings (left, top, width, and height), and a name that will appear in the pop-up menu. They can be modified, deleted, or added to. If no presets are found in the file, the original list is restored. See the configuration file for examples.

Customizing Image Savers for Output

The standard LightWave Image Saver list in the Output tab is long but can be reduced if certain file types are sure not to be needed. The plugins for this list can be found in the following locations, depending on operating system:

• Windows: LightWave_2020.0\support\plugins\input-output

• OSX: /Applications/NewTek/LightWave3D_2020.0/support/plugins/input-output

There are caveats with doing this:

1. A backup of the plugins should be kept. Perhaps the easiest solution is to add the unwanted filetypes to the legacy.zip in the plugins directory;

2. While this reduces the Output list it also cancels the ability for LightWave to handle removed filetypes for loading;

3. Doing this might cause problems with some distributed rendering plugins.