db&w documentation wiki

finest software | finest docs

Site Tools


installation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
installation [2018/07/27 14:48] – [Installation] lightwolfinstallation [2020/08/24 15:48] (current) lightwolf
Line 3: Line 3:
 ===== Installation ===== ===== Installation =====
  
-Download and extract the appropriate ZIP file for your platform.+Download and extract the appropriate ZIP file for your plugin.
  
-**Please note:** The paths to install the plugins to depends on the version of LightWave 3D. These instructions assume that LightWave 2018.0.5 is installed.+<WRAP center round important 60%> The paths to install the plugins to depends on the version of LightWave 3D. These instructions assume that LightWave 2018.0.5 is installed. 
 + 
 +Make sure to install the version of the plugin file that matches your LightWave 3D installation. 2018 is designed to be used in LightWave 3D 2018 and 2019, 2020 is designed for LightWave 3D 2020. 
 +</WRAP>
  
 ==== Windows  ==== ==== Windows  ====
Line 15: Line 18:
 You can also copy it to You can also copy it to
  
-  %userprofile%.NewTek\LightWave\2018.0.5\plugins+  %userprofile%.NewTek\LightWave\####\plugins
  
-to allow LightWave to detect the plugin automatically.+(#### is the version number of your LightWave 3D installation) to allow LightWave to detect the plugin automatically.
  
 ==== MacOS ==== ==== MacOS ====
Line 25: Line 28:
 You can either copy it to: You can either copy it to:
  
-  ~/Library/Application Support/Newtek/LightWave2018.0.3/Plugins+  ~/Library/Application Support/Newtek/LightWave####/Plugins
      
 for the current user or for the current user or
  
-  /Library/Application Support/Newtek/LightWave2018.0.3/Plugins+  /Library/Application Support/Newtek/LightWave####/Plugins
      
-for all users.+for all users. (#### is the version number of your LightWave 3D installation) 
  
 In both cases LightWave 3D will automatically pick up the plugins once you launch it. In both cases LightWave 3D will automatically pick up the plugins once you launch it.
  
 You are of course free to copy the plugin file to another location and use the **Edit Plug-ins** panel (alt-F11) of the **Add Plugins** menu item to add the plugin file **<plugin>.plugin** to LightWave 3D. You are of course free to copy the plugin file to another location and use the **Edit Plug-ins** panel (alt-F11) of the **Add Plugins** menu item to add the plugin file **<plugin>.plugin** to LightWave 3D.
 +=== macOS Catalina and higher ===
 +
 +<WRAP center round important 60%>
 +Since macOS Catalina, plugins need to be signed by the developer. This affects all existing plugins. We will try to make it possible to sign plugins in the future though.
 +</WRAP>
 +
 +
 +To allow macOS to run unsigned plugins, please use the following steps:
 +
 +  - {{ :pasted:20200128-132401.png?640}} Before adding plugins manually, open macOS's **System Preferences/Security & Privacy** alongside. If you use our recommended method to let LightWave 3D scan for plugins automatically, launch **Security & Privacy** before launching LightWave 3D.
 +  - Scan the directory or launch LightWave 3D if you copied the plugin to one of the recommended directories. <WRAP clear/>
 +  - {{ :pasted:20200128-133356.png}} When an un-signed plugin is detected you will see a warning. Click **Cancel**. <WRAP clear/>
 +  - {{ :pasted:20200128-133559.png}} Immediately after clicking cancel, you will see the plugin popup in the Security & Privacy pane. Click **Allow Anyway**. \\ During the scanning directory phase you may have to jump between the **Cancel** and **Allow Anyway** process a few times depending on how many unsigned plugins you have.
 +  - Some plugins may also require you to **Open** them. Continue until everything is scanned. You shouldn’t have to go through this again!
  
 + <WRAP clear/>
 ===== Licensing ===== ===== Licensing =====
 {{ :infinimap2018:registration.png?nolink|}} {{ :infinimap2018:registration.png?nolink|}}
Line 50: Line 68:
 You can now import the keyfile and press OK to complete the licensing process. You may need to remove the plugin from the scene and re-add it to reset the user interface ((you can also exit LightWave 3D and start it again)). You can now import the keyfile and press OK to complete the licensing process. You may need to remove the plugin from the scene and re-add it to reset the user interface ((you can also exit LightWave 3D and start it again)).
  
-The registration file is stored in ''%appdata%db&w\licenses'' on Windows, ''~/Library/Application Support/db&w/license'' on MacOS. If you use multiple licenses of LightWave 3D from a single network share, the registration manager will only append/edit licenses locked to the dongle installed on the host machine. +The registration file is stored in ''%appdata%\db&w\licenses'' on Windows, ''~/Library/Application Support/db&w/licenses'' on MacOS. If you use multiple licenses of LightWave 3D from a single network share, the registration manager will only append/edit licenses locked to the dongle installed on the host machine. 
  
 It will manage multiple licenses allowing for a single registration file on your network share. It will manage multiple licenses allowing for a single registration file on your network share.
Line 58: Line 76:
 Unfortunately there is no built-in mechanism to upgrade a license. To upgrade, you will need to deleted the existing license manually and then re-register using the new license. Unfortunately there is no built-in mechanism to upgrade a license. To upgrade, you will need to deleted the existing license manually and then re-register using the new license.
  
-The licenses are stored in ''%appdata%db&w\licenses'' on Windows, ''~/Library/Application Support/db&w/license'' on MacOS and are named according to the plugin name with a file extension of ''.key''+The licenses are stored in ''%appdata%db&w\licenses'' on Windows, ''~/Library/Application Support/db&w/licenses'' on MacOS and are named according to the plugin name with a file extension of ''.key''
  
  
installation.1532695689.txt.gz · Last modified: 2018/07/27 14:48 by lightwolf