User Tools

Site Tools


faq_lys_beta

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faq_lys_beta [2016/05/17 15:05]
adavies
faq_lys_beta [2016/11/22 23:15]
adavies removed
Line 40: Line 40:
  
 Here are some things you can try that might help you out: Here are some things you can try that might help you out:
-  * Ensure you have a compatible graphics card and that your system meets the [[system_requirements_lys|minimum requirements]]. Lys requires an [[http://​www.khronos.org/​opengl/​|OpenGL 4.3]] compatible GPU. If your GPU was made after 2012, there is a good chance it is OpenCL ​compatible. GeForce 400 Series and newer & AMD/ATI Radeon HD 5000 Series all support OpenGL 4.3.+  * Ensure you have a compatible graphics card and that your system meets the [[system_requirements_lys|minimum requirements]]. Lys requires an [[http://​www.khronos.org/​opengl/​|OpenGL 4.3]] compatible GPU. If your GPU was made after 2012, there is a good chance it is OpenGL 4.3 compatible. GeForce 400 Series and newer & AMD/ATI Radeon HD 5000 Series all support OpenGL 4.3.
   * Check that you have the latest drivers for your GPU. Many issues can be resolved by simply installing the latest drivers for your graphics card. You can get the latest Nvidia drivers [[http://​www.geforce.com/​Drivers|here]] and the latest AMD/ATI drivers [[http://​support.amd.com/​us/​gpudownload/​Pages/​index.aspx|here.]]   * Check that you have the latest drivers for your GPU. Many issues can be resolved by simply installing the latest drivers for your graphics card. You can get the latest Nvidia drivers [[http://​www.geforce.com/​Drivers|here]] and the latest AMD/ATI drivers [[http://​support.amd.com/​us/​gpudownload/​Pages/​index.aspx|here.]]
  
Line 61: Line 61:
   * 365.10   * 365.10
   * 365.19   * 365.19
 +  * 368.22
 +
 === Installing new drivers === === Installing new drivers ===
  
Line 98: Line 100:
   * NVIDIA GeForce GTX 980 4GB VRAM   * NVIDIA GeForce GTX 980 4GB VRAM
   * 361.43   * 361.43
 +==== Lys is running slowly/​Image is not processing/​the 3D Preview Window is blank ====
 +
 +In the case of any of these issues, please check the following:
 +
 +  * The amount of VRAM that your GPU has. The size of the image which Lys can process successfully is limited to the amount of VRAM that it takes to process, so using a very large image (4096² and above) may result in issues. Most modern graphics cards have at least 1GB of VRAM and therefore should be able to process a 4096*2048 texture with ease. If you have more than 2GB of VRAM, you should be able to process a 8192*4096² texture.
 +
 +Below you will find a rough guide of how much contiguous VRAM is required on a single GPU in order to process the various texture sizes listed((As SLI/​Crossfire and Dual GPUs on a single card do not have contiguous VRAM blocks you will only be able to access half of the advertised amount on such systems.))
 +
 +|            ^ 8bit   ^ 16bit Int.  ^ 32bit Float  ^
 +^ 256*128 ​   | 110MB  | 145MB       | 145MB        |
 +^ 512*256 ​   | 115MB  | 150MB       | 150MB        |
 +^ 1024*512 ​  | 120MB  | 170MB       | 170MB        |
 +^ 2048*1024 ​ | 155MB  | 240MB       | 240MB        |
 +^ 4096*2048 ​ | 290MB  | 500MB       | 500MB        |
 +^ 8192*4096 ​ | 810MB  | 1.5GB       | 1.5GB        |
 +
 +
 +  * Running multiple instances of Lys. Due to the amount of GPU VRAM required to process images within Lys., it is currently not recommended to run more than one instance of the program as VRAM may become exhausted. Rebooting your PC may free up stuck resources and can release VRAM which was being used by other applications and/or contended erroneously due to driver and/or application bugs.
 +
 +==== Why are my exported textures failing to load after using Post Export Actions? ====
 +
 +This error can occur (and is often coupled with a 'This app can't run on your PC' error) if the application your are trying to open the exported textures with is closed but still running in RAM from the previous time it was used. To check if this is the case please open Task Manager and ensure that any previous instances of the offending application are not already running & closing them where necessary.
 +