User Tools

Site Tools


FAQ & Troubleshooting


How do I contact Knald Technologies?

You can reach us via e-mail at the following addresses:

Or join us on the following social networks/sites:

What are the system requirements for Knald?

Please see the System Requirements page for more information on the minimum and recommended system requirements for Knald.


Activation Issues

Knald periodically requires an active internet connection in order to contact our license authorization servers. This check is preformed to ensure that your machine is authorised to run Knald and once license authorization has been confirmed you can continue to run Knald off-line until you wish to update the software (when an update is released)

Which ports and/or address does Knald need access to?

To ensure that the authorization servers can be contacted please configure your network so that the following addresses and ports are assessable from any machines Knald is installed upon.

Many studios and university networks sometimes block the ports required for Knald's license/authorization process - please contact your network administrator to ensure the required ports are open and any proxy servers are not blocking HTTPS traffic for the above addresses.

What happens if I don't have access to the internet?

Following the initial activation, Knald will re-authorize with our servers whenever the application is launched. If Knald is unable to communicate with our servers during startup, it will allow up to a 30 day grace period before authorization is required for use.

Knald isn’t working correctly. What can I do to fix the issues I am having?

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 minimum requirements. Knald requires an OpenCL compatible GPU. If you are not sure if your card is compatible, you can find a partial list of conformant GPUs here. If your GPU was made after 2008, there is a good chance it is OpenCL compatible.
  • 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 here and the latest AMD/ATI drivers here.

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.

Knald Unsupported Drivers
  • 344.11
  • 344.48
  • 344.60
  • 344.65
  • 344.75
Lys Unsupported Drivers
  • 364.51
  • 364.72
  • 365.10
  • 365.19
  • 368.22

Installing new drivers

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.

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 page

If you are still having issues, please contact us! You can reach us via e-mail at:

Machine Virtualization

We are unfortunately unable to support any kind of virtual machine for use with our products. This is due to GPU driver functionality and hardware acceleration being severely limited in such virtualization scenarios.

I can run other 3d programs on my virtual machine. Why doesn't Knald work?

When using a virtual machine the sandbox does not have direct access to the GPU via direct passthrough and as such resorts to GPU emulation which gives the ability to run some 3d programs.

In addition, GPU hardware vendors often restrict direct passthrough functionality on consumer GPUs, which would be a prerequisite for any compute program running within a virtual environment, preferring to keep that functionality for workstation graphics.

Please see the minimum requirements for more information on the minimum and recommended specifications required needed to use our products.

How do I submit a bug report & what information should I provide?

When submitting a bug report to us you will need to include a minimum of the following:

  • Name & build number of the program you are reporting
  • Operating system version
  • Graphics card model & VRAM amount
  • Currently installed GPU driver
  • System information (a DXDiag report is often easiest)
  • A zipped copy of the Logs folder found at %username%/AppData/Local/Knald Technologies (This contains crash logs and information).

An example bug report might look similar to the following

  • Knald 1.1.0, Build #
  • Windows 10 Pro 64bit
  • NVIDIA GeForce GTX 980 4GB VRAM
  • 361.43

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.

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 through The Integrator1)

  • 512² = 90mb
  • 1024² = 140mb
  • 2048² = 330mb
  • 4096² = 1.2GB
  • 8192² = 3.8GB
  • 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.

There are striations/strange patterns on my Normal map. How can I remove them?

Striations such as these are often due to the bit depth of your source images being too low. As a result of this limited precision, it can be difficult to reproduce variations of angle and slope with acceptable accuracy.

We suggest the following solutions to fix these issues:

  • Use at least 16bit source images wherever possible and then export them at a lower bit depth if necessary.
  • Use the ‘Enable Noise Reduction” option which is found within the Integrator panel in the Main tab. This will not give you identical results to using higher precision images and results in a softer overall image, but is a reasonable solution if using if your images are restricted to 8bit.
  • 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?

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.

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.

Why do my exported textures not contain Alpha Channel information or Dilation after export?

Rather than using the de facto industry standard of Alpha as a mask some image editors always pre-multiply the alpha channel data and delete the masked pixels, resulting in transparency and no dilation/bleed on import. Unfortunately there is often isn't a way to change this behaviour internally within many image editors, so it can be prudent to try another image format or application that handles the data in a more expected manner.

Single channel textures exported from Knald do not currently support Alpha Channel data.

Export via Clipboard

Checking/Unchecking the Enable Copying of Alpha Channel data to Clipboard option within the preferences will enable/disable the copying of Alpha channel data to the clipboard from within Knald.

While Knald fully supports Alpha in the Windows clipboard, some applications fail to correctly interpret the data, requiring this option to be enabled or disabled depending on image editor support.

1) 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.
faq_knald_1.1.txt · Last modified: 2017/05/23 03:49 (external edit)