Skip to end of metadata
  • Created by Unknown User (mark.allen), last modified by Unknown User (zheni.metodieva) on Sep 02, 2020
Go to start of metadata

This page provides troubleshooting assistance for general V-Ray problems.

 

Windows

In this section you can find some common issues that may arise when working with V-Ray for Modo.

 

Cannot Install V-Ray

Symptoms: 

The installation file crashes when you attempt to run it.

Cause:

The installation file is not downloaded properly.

Solution:

Please re-download the installation file from our web site.

 

The ChaosGroup License Server could not be reached

 

 

Here you can find the list of symptoms and their likely cause when V-Ray could not obtain the license. Check the resolution part at the end of this section.

Symptoms: 

When attempting to render, the Modo status line shows the message: "error: The ChaosGroup License Server could not be reached (10061)", "error: The ChaosGroup License Server could not be reached (111)", or "error: The ChaosGroup License Server could not be reached (61)"

Cause:

V-Ray could not connect to a working license server.

 

Symptoms:

When attempting to render, the Modo status line shows the message: "error: The ChaosGroup License Server could not be reached (-98)".

Cause:

V-Ray connected to a working license server, but there are no licenses

 

Symptoms:

When you start the V-Ray RT render server, there are no error messages in the V-Ray console, but when a job is sent to the V-Ray RT render server, the error in the console is: "The ChaosGroup License Server could not be reached (10061)."

Cause:

No access to the V-Ray license server.

 

Symptoms:

When you start the V-Ray RT render server, there are no error messages in the V-Ray console, but when a job is sent to the V-Ray RT render server, the error in the console is: "The ChaosGroup License Server could not be reached (-98)."

Cause:

No available license on the V-Ray license server.

 

Symptoms:

When you try to render with V-Ray Standalone, an error message appears in the console: “The ChaosGroup License Server could not be reached (10061).”

Cause:

No access to the V-Ray license server.

 

Symptoms:

When you try to render with V-Ray Standalone, an error message appears in the console: “The ChaosGroup License Server could not be reached (-98).”

Cause:

No available license on the V-Ray license server.

 

Resolution:

Please go through the check-list below:

  1. Checking the V-Ray license server:

    Restart the machine with the V-Ray license server and dongle installed. Unplug the dongle and plug it again in a different USB port, preferably USB 2.0. Make sure that Windows properly recognizes the dongle and does not show an error message. If you receive an error message, refer to V-Ray License Server Can't Start in this section.

    Start the V-Ray license server from Windows Start menu > All Programs > Chaos Group > V-Ray License Server for x64 > Launch V-Ray license server

    You may receive a message warning that the V-Ray license server is already running.

    Open the link http://localhost:30304 in a web browser on the same machine.

    This opens the V-Ray license server status web page. If it looks like the screenshot below, the license server is working.


     

  2. Checking the available licenses on the license server:
    After you ensure the V-Ray license server is working, you need to check the available licenses. On the same machine, where the V-Ray license server is running, open http://localhost:30304/getstatus
    Refer to V-Ray license server status in the Dongle Usage section for more information on the type of licenses you need to look for.

    If you do not see the V-Ray 3.0 licenses, this means that your dongle has to be reprogrammed as described in Dongle reprogramming in the Dongle Usage section. If you don't see free licenses, this means that all available licenses are in use and you can't have more concurrent users.
     

  3. Checking the connection to the license server:

    If V-Ray is on the same machine as the V-Ray license server, you can skip this step.

    To make sure that nothing is blocking the connection to the license server on the machine where you want to run V-Ray, open the link http:// <IP_address> :30304 in a web browser, where <IP_address> is the IP address of the machine with the V-Ray license server. If you get a web page like the one below, V-Ray can access the V-Ray license server from this machine. In the example screenshot below, the IP address of the machine with the license server is 10.0.0.160

    If you get an error message that the web page cannot be accessed, there is a network problem that prevents the connection to the V-Ray license server. If you have any firewall or antivirus software running on your machines, make sure they are not blocking applications' access to the network or blocking the communication on TCP/IP port 30304. Contact your system administrator for more information.
     

  4. Checking the V-Ray license settings:

    On the machine where you want to use V-Ray, run the V-Ray license client configuration utility from Windows Start > All Programs > Chaos Group > V-Ray for Modo x.x for x64 > Change license settings. In the dialog that appears, make sure that the IP address in the License server field at the Primary license server tab is entered correctly and that the connection port is 30304. If you modify any of these settings, you need to restart Modo.


     

    If the V-Ray license server is running on the same machine as V-Ray, you can use localhost or 127.0.0.1 in the License server field.

 

 

V-Ray License Server Can't Start

Symptoms:  

When you start the V-Ray license server, it pops a dialog box like the one shown below:

 

 

Cause:  

This error message appears when the V-Ray license server cannot find a dongle attached to the machine.

Resolution:

Before you start, make sure the dongle is NOT plugged-in.

  1. Uninstall the WIBU-KEY driver from Windows Control Panel.

  2. Update your USB drivers to the latest version.

  3. Restart your machine.

  4. Download and install the latest WIBU-KEY drivers from http://wibu.com/download_user.php.

  5. Attach the dongle to a different USB port, preferably to USB 2.0. Make sure that Windows recognizes the dongle and does not show error messages. To verify that dongle is properly installed, go to the Windows Control Panel > System applet. Choose the Hardware tab and then press the Device manager button. Expand the Universal serial bus controllers list and check for a WIBU-BOX/RU entry there:

     

 

Dongle Disconnects Periodically

Symptoms:  

The dongle works for extended periods of time but periodically disappears for no apparent reason and is no longer detected by Windows as a USB device. This could cause the V-Ray license server to fail or V-Ray licenses to be refused.

Cause:  

There can be a number of reasons related to the hardware configuration and Windows settings like the Power options.

Resolution:  

Check your Windows Power Options, make sure that your USB devices are not powered off.

Try to plug the dongle into a different USB port on the same machine, preferably USB 2.0, and restart the V-Ray license server. If you still experience problems, try to install it on a different machine.

 

Missing V-Ray License Server Icon

Symptoms:  

The V-Ray licensing server is running but there is no icon in the Windows System Tray.

Cause:  

The icon is hidden by the Auto-hide unused icons option of the Windows System Tray or the V-Ray license server is registered as a Windows service.

Resolution: 

  1. If you have the Auto-hide unused icons option of the Windows System Tray, press the double-arrow icon to expand the full list of icons.

  2. If you still do not see the V-Ray licensing service icon, that means that the V-Ray licensing service is started as a Windows service and in that case it cannot show any graphical user interface. There is currently no resolution for this; you need to manage the V-Ray license service from the Windows Control Panel > Administrative tools > Services applet.

Updating Dongles when the .rtu Files are not Associated Properly

Symptoms:  

WIBU-KEY drivers are properly installed but double-clicking on the .rtu file does not update the dongle.

Cause:

The .rtu file is not associated properly with the WIBU-KEY drivers.

Resolution: 

First, try the steps from V-Ray License Server Can't Start in this section. If this does not help, proceed with the steps below:

  1. Make sure that the dongle is plugged-in.

  2. In the Windows Control Panel locate the WibuKey management tool and run it:

  3. Now you need to start the Advanced Mode from the system menu by right-clicking onto the title bar. Go to the WibuBox Update tab.

     

     

  4. Click Browse, specify the .rtu file, and press Apply.



V-Ray RT GPU is Crashing

Symptoms:  

When rendering with V-Ray RT on CUDA/OpenCL, it crashes without showing a specific error message.

Cause:

The scene you are trying to render is too large and the Graphics card memory is insufficient.

Resolution:

You can try to reduce the scene size by reducing the polygon count or by using lower resolution textures. V-Ray RT has an option called “Resize textures for GPU” that you can use to automatically resize textures during rendering on the GPU.

Alternately, you can upgrade your graphics device with one containing more memory.

 

V-Ray RT GPU is not Rendering

Symptoms:  

When rendering with V-Ray RT running in OpenCL mode, it takes too long for the render to begin and the vray.exe process is taking a lot memory.

Cause:

Your GPU drivers are unable to compile the OpenCL code needed to render the scene with your video card.

Resolution:

The best solution is to switch V-Ray RT to use CUDA.

Alternately, you can try and find drivers for your graphics device that are capable of compiling the OpenCL code needed to run V-Ray RT on GPU. However, the latest drivers are not always appropriate. This means that it may require some experimentation until you find the correct drivers.

 

V-Ray Environment Variables Issues

Symptoms:  

Right after an apparently successful installation, the V-Ray for Modo plug-in loads in Modo, but V-Ray does not appear in the list of available renderers. The script editor shows a number of errors: “Could not read V-Ray environment variable VRAY_FOR_MODO2024_MAIN_x64. Please re-install” or similar.

Cause: V-Ray for Modo uses several environment variables to find out where various components are installed. The above errors appear when V-Ray for Modo cannot find these variables.

Resolution: Try to log out and log in to your machine again – sometimes the environment changes are not propagated immediately throughout the system.

 

 

WIBU-KEY Drivers Issues

Symptoms:

When installing the WIBU-KEY drivers, you get the following error:

 

 

Symptoms:

When uninstalling the WIBU-KEY drivers, you get the following error:

 

 

Symptoms:

When you plug-in the dongle or when you try to run V-Ray License Server, you get one of the following errors:

 

or

 

 

Cause:

These errors are caused by the recently added Microsoft Update KB3004394 (added on December 2014 for Windows Root Certificate Program). Affected operating systems are Windows 7 and higher. This update breaks the WIBU-KEY driver.
To fix that, you can run Windows Update and update your operating system to the latest version. Alternatively, you can install the fix for that issue from here. You need to download the appropriate package for your particular OS and install it.

After you complete the steps given by WIBU follow the instructions below in order to repair your WIBU-KEY driver:

1. Unplug all WIBU-KEY dongles from the PC.

2. Go to Start > Control Panel > Programs and Features and uninstall the WIBU-KEY drivers by double-clicking on WibuKey Setup (WibuKey Remove).

 

 

 

 

 

3. Follow the instructions of the Uninstaller.

4. Open an Windows Explorer and in the address bar enter "%systemroot%\inf".

 

 

 

5. Find the file wibukeyPCMCIA.inf and delete it.

6. Search for a file named oem*.inf that contains the term "WIBU". To do that, enter "WIBU" in the search bar and when the search is complete, press the File Contents button:

 

 

 

7. The search may take a while, but in the end it should find a file named oem*.inf. Delete that file and the file with the same name but a PNF extension (eg. if you found a file named oem123.inf, delete oem123.pnf as well).

8. In the address bar of Windows Explorer enter "%systemroot%\system32\drivers".

 

 

 

9. Find and delete all WibuKey*.sys files.

10. Click Windows Start and in the Search field type "regedit".

 

 

 

11. This will open the Registry Editor. Find and delete the following keys":

in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services” if any of the folders "WIBUKEY", "WibuKey2" and "WibuKey2_64" exist, find them and delete them.

in "HKEY_LOCAL_MACHINE\SOFTWARE\" find and delete the folder "WIBU-SYSTEMS".

12. Restart the computer.

13. After reboot, download the latest driver form the official WIBU Systems site, under "WibuKey for Users" section here https://www.wibu.com/support/user/downloads-user-software.html . Ensure that you have administrative rights.

14. Make sure that the dongle is NOT plugged in. Double-click on the installation file and follow the instructions of the installer.

15. After the installation has finished, plug in the dongle.

16. The "New Hardware found" dialog will appear and install the new hardware automatically.

 

 

macOS

In this section you can find some common issues that may arise when working with V-Ray for Modo.

V-Ray Could not Obtain License

Here you can find the list of symptoms and their likely cause when V-Ray could not obtain the license. Please check the resolution part at the end of this section.

Symptoms: 

When attempting to render, the Modo status line shows the following messages: "error: The ChaosGroup License Server could not be reached (10061)", "error: The ChaosGroup License Server could not be reached (111)", or "error: The ChaosGroup License Server could not be reached (61)"

Cause:

V-Ray could not connect to a working license server.

 

Symptoms:

When attempting to render, the Modo status line shows the message "error: The ChaosGroup License Server could not be reached (-98)".

Cause:

V-Ray connected to a working license server, but there are no licenses.

 

Symptoms:

When you start the V-Ray RT render server, there are no error messages in the V-Ray console, but when a job is sent to the V-Ray RT render server, there is an error in the console "The ChaosGroup License Server could not be reached (10061)."

Cause:

No access to the V-Ray license server.

 

Symptoms:

When you start the V-Ray RT render server, there are no error messages in the V-Ray console, but when a job is sent to the V-Ray RT render server, the error in the console is "The ChaosGroup License Server could not be reached (-98)."

Cause:

No available license on the V-Ray license server.

 

Symptoms:

When you try to render with V-Ray Standalone, an error message appears in the console: “The ChaosGroup License Server could not be reached (10061).”

Cause:

No access to the V-Ray license server.

 

Symptoms:

When you try to render with V-Ray Standalone, an error message appears in the console: “The ChaosGroup License Server could not be reached (-98).”

Cause:

No available license on the V-Ray license server.

 

Resolution:  

Please go through the check-list below:

  1. Checking the V-Ray license server:

    Restart the machine with the V-Ray license server and dongle installed. Unplug the dongle and plug it again in a different USB port, preferably USB 2.0. Make sure that the operating system properly recognizes the dongle. Make sure that the V-Ray license service is running. If you have issues, refer to V-Ray License Server Can't Start in this section.  

    Start the V-Ray license server.

    Open the link http://127.0.0.1:30304 in a web browser on the same machine.

    This opens the V-Ray license server status web page. If it looks like the screenshot below, the license server is working.

     

  2. Checking the available licenses on the license server:
    After you ensuring the V-Ray license server is working, you need to check the available licenses. On the same machine, where the V-Ray license server is running, open http://127.0.0.1:30304/getstatus.

    Refer to V-Ray license server status in the Dongle Usage section for more information on the type of licenses you need to look for. If you do not see the V-Ray 3.0 licenses, this means that your dongle has to be reprogrammed as described in Dongle reprogramming in the Dongle Usage section. If you do not see free licenses, this means that all available licenses are in use and you can't have more concurrent users.

  3. Checking the connection to the license server:
    If V-Ray is on the same machine as the V-Ray license server, you can skip this step. To make sure that nothing is blocking the connection to the license server on the machine where you want to run V-Ray, open http:// <IP_address> :30304 in a web browser, where <IP_address> is the IP address of the machine with the V-Ray license server. If you get a web page like the one below, V-Ray can access the V-Ray license server from this machine. In the example screenshot below, the IP address of the machine with the license server is 10.0.0.160

    If you get an error message that the web page cannot be accessed, there is a network problem that prevents the connection to the V-Ray license server. If you have any firewall or antivirus software running on your machine, make sure they are not blocking applications' access to the network or blocking the communication on TCP/IP port 30304. Contact your system administrator for more information. 


     

  4. Checking that the license server settings are correct. In the Terminal run /Applications/Luxology/modo/x.x /vray/bin/setvrlservice -dump, where  x.x is the particular version of Modo you are using (10.0v1 etc). This shows you the IP address or the name of the computer that V-Ray is trying to connect to. If it is incorrect, refer to V-Ray license settings change in Dongle Usage section.



V-Ray License Server Can't Start

Symptoms:  

When you start the V-Ray license server it pops up and closes.

Cause:  

This error message appears when the V-Ray license server cannot find a dongle attached to the machine.

Resolution:

Before you start, make sure that the dongle is plugged in directly in the machine and try again. If it still does not work, do the following:

  1. Make sure the dongle is NOT plugged-in.

  2. Uninstall the WIBU-KEY driver.

  3. Restart your machine.

  4. Download and install the WIBU-KEY drivers corresponding to your OS from http://wibu.com/download_user.php.

  5. Attach the dongle to a USB port DIRECTLY on your machine, preferably a USB 2.0. Make sure that the operating system recognizes the dongle and doesn't show error messages. To verify that dongle is properly installed, go to /Applications/WIBUKEY/WkConfig.app




V-Ray Warning: Loading Shaders Failed

Symptoms:

Right after an apparently successful installation, the V-Ray for Modo plug-in loads in Modo, but V-Ray does not appear in the list of available renderers. The script editor shows a number of errors “V-Ray warning: Loading shaders failed: no <*.txt> files in ” or similar.

Cause:  

V-Ray for Modo uses several environment variables to find out where various components are installed. The above errors appear when V-Ray for Modo cannot find these variables.

Resolution:

Try to log out and log in to your machine again – sometimes the environment changes are not propagated immediately throughout the system.