Differences

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

--- faq_knald [2014/11/28 09:57]
adavies [Troubleshooting]
+++ faq_knald [2017/05/23 03:49] (current)
@@ Line 17: / Line 17: @@
-==== What are the system requirements for Lys? ====
+==== What are the system requirements for Knald? ====
-Below you will find the minimum and recommended system requirements for Lys.
+Please see the [[system_requirements_knald|System Requirements]] page for more information on the minimum and recommended system requirements for Knald.
-**Minimum Supported System Requirements((Lys may run on lesser hardware configurations, but is not guaranteed to do so.))**
+===== Troubleshooting =====
-  * Windows 7 64bit/ Windows 8 64bit
-  * Intel or AMD dual core 2.0 GHz CPU
-  * 2GB of RAM
-  * OpenGL 4.3 compatible GPU with 1GB of VRAM
-  * (Applicable AMD and nVidia GPUs with latest drivers currently supported)
-  * (Available VRAM may limit working texture sizes – see documentation for details)
-  * 200MB of Free Hard Drive Space
-**Recommended Supported System Requirements**
-  * Windows 7 64bit/ Windows 8 64bit
-  * Intel or AMD quad core 3.0 GHz CPU
-  * 8GB of System RAM
-  * OpenGL 4.3 compatible GPU with 2GB of VRAM or more
-  * (Applicable AMD and nVidia GPUs with latest drivers currently supported)
-  * (Available VRAM may limit working texture sizes – see documentation for details)
-  * 1GB of Free Hard Drive Space
-===== Troubleshooting =====
+----
 ==== Knald isn’t working correctly. What can I do to fix the issues I am having? ====
@@ Line 47: / Line 31: @@
   * 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.]]
-If you are still having issues, please contact us! You can reach us via e-mail at: support@knaldtech.com
+=== Driver Issues ===
+Some NVIDIA drivers have been reported to cause problems with OpenCL/OpenGL. Please do not use the following drivers with our software as they are unsupported by us.
+=== Driver Issues ===
+Some NVIDIA drivers have been reported to cause problems with OpenCL/OpenGL. Please do not use the following drivers with our software as they are unsupported by us.
-==== Best Practices ====
+== Knald Unsupported Drivers ==
-To get the best results from Knald we suggest that you follow a small number of recommendations to ensure that the quality of the processed maps is as high as possible.
+  * 344.11
+  * 344.48
+  * 344.60
+  * 344.65
+  * 344.75
+== Lys Unsupported Drivers ==
-=== Use High(er) Precision Images ===
-The bit depth of the images that you use in Knald have a large impact on the quality of the processed maps. Unfortunately, 8bit images have extremely low precision due to the relatively small number of values that can be represented per channel.
+  * 364.51
+  * 364.72
+  * 365.10
+  * 365.19
+  * 368.22
-As a result of this limited precision, it can be difficult to reproduce variations of angle and slope with acceptable accuracy. This limitation of 8bit height maps may become apparent in the form of banding. These artifacts may not be immediately noticeable on Normal maps, however they are still present and may reduce the accuracy and fidelity of Knald’s output.
+=== Installing new drivers ===
-The maximum amount of unique values per channel for each bit depth is listed below:
+On some occasions errors within Knald are due to cached shaders that the driver hasn't compiled correctly or are corrupted in some way. Whenever you install a new driver we always recommend that you perform a clean installation and delete any cached shaders if they are present on your system.
-  * 8bit Integer: 256 Values
-  * 16bit Integer: 65536 Values
-  * 32bit Integer: 4294967295 Values
-  * 16bit Float: 65504 Values
-  * 32bit Float: 4261412864 Values
-We recommend that you use the highest bit depth possible in whatever source images are to processed by Knald. If your current pipeline is restricted to 8bit, you can export the final map as 8bit from within Knald once the processing has been completed. You will always get more accurate results by authoring source images in higher bit depths and only converting to your target format (eg: 8bit) during Knald’s export.
+Performing a clean installation of your drivers and deleting shader cache is simple and you can learn how to do it on the [[clean_driver_installation|Clean Driver Installation]] page
-For production-quality results we recommend using at least 16bit source images whenever possible.
+If you are still having issues, please contact us! You can reach us via e-mail at: support@knaldtech.com
-=== Use A Fast GPU! ===
+==== Knald is running slowly/Normal Map is not processing/the 3D Preview Window is blank ====
+In the case of any of these issues, please check the following:
-While Knald can be used on any OpenCL compliant graphics card, you will get faster (though identical) results if you use a more powerful card.
+  * The amount of VRAM that your GPU has. The size of the image which Knald 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 512MB of VRAM and therefore should be able to process a 2048² texture with ease. If you have more than 1GB of VRAM, you should be able to process a 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.))
-=== Use Alpha Channels In Your Texture ===
+  * 512² = 90mb
+  * 1024² = 140mb
+  * 2048² = 330mb
+  * 4096² = 1.2GB
+  * 8192² = 3.8GB
-Using an Alpha channel on imported Normal/Derivative may substantially increase the quality of your results in cases where the image UVs are anything other than simple planar unwrap to a quad.
-All areas within the black area of an Alpha channel will be pinned and interpreted as flat. (128, 128, 255) Knald will assume these areas have no variance in normal information and will be processed as a flat plane. Typically, using the Alpha channel that is generated automatically when baking will be sufficient. However, useful and interesting results may be achieved using gradients and other variants aside from hard opacity.
-=== Always Use The Correct Background Color For Normal/Derivative Maps ===
-Using an incorrect background color on imported Normal/Derivative maps will always significantly decrease the quality of your results in cases where the source image’s Alpha channel is either unused or not present.
-Never use White or Black as your background color for these maps!
-The correct colurs that should be used are as follows:
-  * Normal map: 128, 128, 255 / #8080ff
-  * Derivative map: 128, 128, 0 / #808000
-==== Knald is running slowly/Normal Map 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 Knald 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 512MB of VRAM and therefore should be able to process a 2048² texture with ease. If you have more than 1GB of VRAM, you should be able to process a 4096² texture.
   * Running multiple instances of Knald. Due to the amount of GPU VRAM required to process images within Knald, 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.
@@ Line 124: / Line 91: @@
   * Toggle the ‘Tileable’ check box in the General group under the Main tab. If a map is set to tilable incorrectly, it may result in errors around the borders of the image.
-==== Why are there are shading artifacts/smoothing errors/seams on my imported mesh in the 3d preview? ====
+==== Why are there are shading artifacts/smoothing errors/seams on my imported mesh in the 3D Preview? ====
 This is a side-effect of Knald applying the integrated height map to your mesh. Sadly, it is not currently possible for Knald to generate perfectly correct values around the UV islands (which are typical if the normal map was baked) resulting in the possibility of minor visual aberrations when applying the exported height maps to UV containing meshes.

Knald Technologies Documentation

User Tools

Site Tools

Differences

Page Tools