Krita/Manual/FAQ: Difference between revisions

From KDE UserBase Wiki
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page contains common problems people have with Krita
This page contains common problems people have with Krita
==General==
==General==
===Krita start with a black canvas and nothing changes when you try to draw===
===Krita start with a black canvas and nothing changes when you try to draw/shows a black screen on my Windows system with an Intel GPU===
This is due to a graphics driver fault. Update your graphics drivers, or complain to the driver vendor and then turn off OpenGL under <menuchoice>settings->configure Krita->display</menuchoice>
 
This is a bug in the Intel OpenGL driver. Update to 10.18.14 or later. On Windows 8.0 and 8.1, you might need to manually install the driver. Follow the instructions from the [http://www.intel.com/support/graphics/sb/cs-022355.htm Intel Website]. No, we don’t know either why they made installing an updated driver so hard. :-(
 
As an alternative turn off OpenGL under <menuchoice>settings->configure Krita->display</menuchoice>
 
===OBS can't record the Krita openGL canvas===
Apparantly the workaround for this is to either...
 
# Turn off OpenGL in settings->configure Krita->display.
# Or don't use the hardware accelerated mode(game recording mode) in OBS, so capture the whole desktop instead of attempting to capture only Krita.


===Resetting Krita configuration===
===Resetting Krita configuration===
You can reset the Krita configuration in two ways:
You can reset the Krita configuration in two ways:
* Press <keycap>Shift+Alt+Ctrl</keycap> in Krita. This should show a pop-up asking if you want to reset the configuration.
* Press <keycap>Shift+Alt+Ctrl</keycap> while starting Krita. This should show a pop-up asking if you want to reset the configuration.
* Delete/rename the kritarc (not krita.rc) file in .kde/config/, .config/ or %APPDATA%\Roaming\krita\. If the config was causing a crash, don't delete but instead rename and send us the file so we can figure out what caused the crash.
* Delete/rename the kritarc (not krita.rc) file in .kde/config/, .config/ or %APPDATA%\Roaming\krita\. If the config was causing a crash, don't delete but instead rename and send us the file so we can figure out what caused the crash.


Line 48: Line 57:
# Try to reproduce your problem
# Try to reproduce your problem
# Go back to DebugView and save its output to a file. Attach this file to a bug report or paste using services like paste.kde.org :)
# Go back to DebugView and save its output to a file. Attach this file to a bug report or paste using services like paste.kde.org :)
===Surface Pro and NTrig===
Krita uses wintab, but we have noticed that N-trig's wintab support is a little broken. Which means that pressure sensitivity doesn't work on the surface pro 3 and 4.


To fix this, you can try to install the photoshop CC trial. This replaces certain windows libraries with ones that do work.
==Toolbox==
==Toolbox==
===Toolbox missing===
===Toolbox missing===
Line 71: Line 83:
You probably have too many resources installed. Deactivate some bundles under <menuchoice>settings->manage resources</menuchoice>
You probably have too many resources installed. Deactivate some bundles under <menuchoice>settings->manage resources</menuchoice>
===Slow Brushes===
===Slow Brushes===
* Check if display filter under <menuchoice>settings->configure Krita->display</menuchoice> is set to 'high quality'. Set it to trilinear.
* Check if you accidentally turned on the stabilizer in the tool options docker.
* Check if the color space of the image isn't 16-bit or higher.
*Try an other display filter like trilinear. <menuchoice>settings->configure Krita->display</menuchoice>
* Check if you didn't accidentally turn on the stabilizer in the tool options docker.
* Try a lower color space value then 16-bit.
* For NVidia cards it can help to check if a 16-bit floating point color space is faster.
* For NVidia, try a 16-bit floating point color space.
* For AMD, Krita 2.9.10 will have an option to turn off the vector optimizations that are broken on AMD CPUs. You can find this option under <menuchoice>settings->configure Krita->performance</menuchoice>
* For AMD (Krita 2.9.10 and above),  turn off the vector optimizations that are broken on AMD CPUs. <menuchoice>settings->configure Krita->performance</menuchoice>
* Don't try to run Krita on a netbook. It's a fairly ram hungry program, so 2 gig of ram is the minimum, and 4 gig is the preferable minimum.
* It's a fairly memory hungry program, so 2GB of ram is the minimum, and 4 gig is the preferable minimum.


===Slowdown after a while of working===
===Slowdown after a while of working===

Latest revision as of 21:45, 21 January 2016

This page contains common problems people have with Krita

General

Krita start with a black canvas and nothing changes when you try to draw/shows a black screen on my Windows system with an Intel GPU

This is a bug in the Intel OpenGL driver. Update to 10.18.14 or later. On Windows 8.0 and 8.1, you might need to manually install the driver. Follow the instructions from the Intel Website. No, we don’t know either why they made installing an updated driver so hard. :-(

As an alternative turn off OpenGL under settings->configure Krita->display

OBS can't record the Krita openGL canvas

Apparantly the workaround for this is to either...

  1. Turn off OpenGL in settings->configure Krita->display.
  2. Or don't use the hardware accelerated mode(game recording mode) in OBS, so capture the whole desktop instead of attempting to capture only Krita.

Resetting Krita configuration

You can reset the Krita configuration in two ways:

  • Press Shift+Alt+Ctrl while starting Krita. This should show a pop-up asking if you want to reset the configuration.
  • Delete/rename the kritarc (not krita.rc) file in .kde/config/, .config/ or %APPDATA%\Roaming\krita\. If the config was causing a crash, don't delete but instead rename and send us the file so we can figure out what caused the crash.

I can't edit text from PSD files created by photoshop

There is no text support for psd file yet. The text will appear rasterized and converted into paint layer.

Multi Monitor Setup

How to fix a tablet offset on screen on Windows

If you see that your tablet pointer has an offset when working with Krita canvas, it might be highly probable, that Krita got incorrect screen resolution from the system. That problem happens mostly when an external monitor is present and when either of monitor or a tablet was connected after the system boot.

Now there is a simple solution to fix this data manually.

  1. Lay you stylus aside
  2. Start Krita without using a stylus, that is using a mouse or a keyboard
  3. Press Shift key and hold it
  4. Touch a tablet with your stylus so Krita would recognize it

You will see a special dialog asking for real screen resolution. Choose the correct value or enter it manually and press OK.

What if your tablet is not recognized by Krita?

Linux

We would like to see the full output of the following commands:

  1. lsmod
  2. xinput
  3. xinput list-props <id-of-your-tablet> (id can be fetched from the item 2)
  4. Get the log of the tablet events (if applicable):
    1. Open a console application (e.g. Konsole on KDE)
    2. Set the amount of scrollback to 'unlimited' (for Konsole: Settings->Edit Current Profile->Scrolling->Unlimited Scrollback)
    3. Start Krita by typing 'krita' and create any document :)
    4. Press Ctrl+Shift+T, you will see a message box telling the logging is started
    5. Try to reproduce your problem
    6. The console is now filled with the log. Attach it to a bug report or paste using services like paste.kde.org :)
  5. Attach all this data to a bugreport using public paste services like paste.kde.org

Windows

  1. Install DebugView from the official Microsoft site
  2. Start DebugView
  3. Start Krita
  4. Press Ctrl+Shift+T, you will see a message box telling the logging is started
  5. Try to reproduce your problem
  6. Go back to DebugView and save its output to a file. Attach this file to a bug report or paste using services like paste.kde.org :)

Surface Pro and NTrig

Krita uses wintab, but we have noticed that N-trig's wintab support is a little broken. Which means that pressure sensitivity doesn't work on the surface pro 3 and 4.

To fix this, you can try to install the photoshop CC trial. This replaces certain windows libraries with ones that do work.

Toolbox

Toolbox missing

You either reset the workspace by pressing the right most button on the toolbar, the workspace switcher, and clicking a workspace from the list.

Or you try to select the toolbox from the docker dialogue. (2.9.7 and onward only)

Tool icons size is too big

Right click the toolbox to set the size.

Krita can't get maximized

This is due to the toolbox being too big, for example, when it's accidentally made 1-columns wide. Resize it to make it 2 columns wide.

Presets

is there a way to restore a default brush that i have mistakenly overwritten with new settings to default?

Yes, remove the newly created preset from ~/.kde4/share/apps/krita/paintoppresets/

How do I set favourite presets?

Right-click a brush in the brush docker and assign it a tag. Then when clicking the lower-right settings icon you can pick you tag.

Krita is slow

There is a myriad of reasons why this might be:

Slow start-up

You probably have too many resources installed. Deactivate some bundles under settings->manage resources

Slow Brushes

  • Check if you accidentally turned on the stabilizer in the tool options docker.
  • Try an other display filter like trilinear. settings->configure Krita->display
  • Try a lower color space value then 16-bit.
  • For NVidia, try a 16-bit floating point color space.
  • For AMD (Krita 2.9.10 and above), turn off the vector optimizations that are broken on AMD CPUs. settings->configure Krita->performance
  • It's a fairly memory hungry program, so 2GB of ram is the minimum, and 4 gig is the preferable minimum.

Slowdown after a while of working

Once you have the slowdown, click on the image-dimensions in the status bar. It will tell you how much Krita is using, and if it's hit the limit, whether it's started swapping. Swapping can slow down a program a lot, so either work on smaller images or turn up the maximum amount of ram in settings->configure Krita->performance

Tools

Why does the Transform Tool give a good result and then get blurry upon finalizing?

The transform tool makes a preview that you edit before computing the finalized version. As this preview is using the screen resolution rather than the image resolution, it may feel that the result is blurry compared to the preview. See https://forum.kde.org/viewtopic.php?f=139&t=127269 for more info.

Reference

https://answers.launchpad.net/krita-ru/+faqs