If you’re seeing strange crashes in Windows 10 when you zoom, rotate, or interact with menus (or other random movements of your stylus or touch gestures) then the culprit is probably Press & Hold for Right Click. This is a tablet and touch input setting that can conflict with tablet drivers and software in strange ways.

• Go to your Control Panel > Pen and Touch > Change touch input settings
• Disable or enable ‚Äòpress and hold‚Äô (whichever it currently is, change it)

This feature has also caused strange zooming or ‘right clicking’ behaviour with older Wacom drivers and previous versions of Windows.

If you are using ArtRage 3 Studio/Studio Pro and are seeing crashes, this might be due to an incompatible feature that you can disable: ArtRage memory crashes on Windows 10

If you can interact with the menus and buttons, but can’t make any marks on the paper, or can draw fine but can’t use the menus properly, then the problem is usually the tablet driver settings.

If you are using ArtRage for iPad or ArtRage for Android, make sure that you haven’t set it to ignore touch input from your finger or use a different stylus.

If you are using Windows, then the issue is usually tablet drivers. Go to Edit > ArtRage Preferences > Input Devices.

If both Realtime Stylus and Wintab are ticked, this is almost always the problem (ArtRage tries to autodetect the one you need to use, but if the tablet driver or operating system sends the wrong signal, ArtRage can’t use it and appears to not be responding). If only one is ticked, you might need to change to the other one.

• If you are using a separate graphics tablet to draw on (or a mouse!), turn off Realtime Stylus and restart ArtRage.
• If you are using a touchscreen device (e.g. a Cintiq or Surface Pro), turn off Wintab and restart ArtRage.

How can I rescue a PTG painting that won’t open in ArtRage?

If you receive an error message and are unable to open a PTG file, then it probably means that your ArtRage painting was were corrupted at some point. Damaged PTG files usually result from interrupted saves (for example, if the computer shuts down or ArtRage crashes). We will do our best to help troubleshoot the source of ArtRage errors, but usually cannot fix corrupted or partial files. However, if you can see the image thumbnail then that means that the PNG preview image is intact. If you use File > Import Image File to open the damaged files, then it will import the PNG thumbnail. This PNG file is the full size of your painting and high quality. It won’t rescue your layers or other paint information, but it will give you something to work with.

Backup Save Files

If crashes happen frequently for any reason, or you are working on an important painting, we recommend turning on the Store Backup Files option. You can find it by going to Edit > ArtRage Preferences > Advanced > Store Backup Files. Adjust the slider to the number of backups you would like to keep. Important: This function does not save a duplicate file. Instead, it keeps a history of previous saved versions. Every time you save, it will delete the oldest backup file, and save the latest changes as a separate file, so if you have made important changes, save twice to update the older back up and the file you are actually working on.

Mac OS X – Crash Issue

We have seen a few instances of a crash when attempting to save a file for the first time on OS X when the save file dialog tries to open, and may occur in other situations where a file dialog is trying to open.

Cause:

In many cases this crash appears to be caused by a bad file in the system. This file is called ‘SCFinderPlugin’ and is located in the Library folder. The crash is actually happening outside ArtRage in an OS system so we don’t know exactly why that file is causing it but it has been known to cause crashes in multiple different applications.

Checking the Crash Log to confirm the problem:

Note: This is optional, you can skip straight to the solution if you like.

You can do a quick check yourself in the crash log to see if this specific crash is the problem you are experiencing. To do this:

1. When the application crashes, select the Report button. A window with a crash log appears.
2. Near the top of the crash log text, look for a line that starts with: ‘Crashed Thread:’.
3. This line tells you which system thread crashed (a number) but also indicates the function the crash occurred in. You can ignore the number.
4. If the line contains this text, the crash is probably the one described in this FAQ answer: Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue

Solution:

Removing the file should resolve the crash. You need to locate it and move it out of the library. It may be installed in more than one library location so follow the steps below to locate and remove it.

1. In the Finder, open the¬†Go¬†menu. If you see a ‘Library’ entry, click it. If you don’t see a Library entry, hold down Option on your keyboard and it should appear, then click it.
2. In the Library folder, open the ‘Contextual Menu Items’ folder.
3. If you see it, drag the SCFinderPlugin.plugin file out of that folder to your desktop.
4. Now open the Macintosh HD, the place you see your Applications folder. There should be a ‘Library’ folder in there too. Open that.
5. Repeat step 2 and 3 (you may want to put folders on the desktop to contain the duplicate files).
6. Reboot and try the operation that crashed again.

You should be able to delete the files at this point. As noted above, the file and the crash it causes aren’t part of ArtRage so we don’t know exactly why this is happening, but you may find other applications also becoming more stable after its removal.

If you still have problems:¬†Please send an email to¬†[email protected]¬†letting us know, and include a copy of the Crash Log generated when the application crashed. To include that, click the Report button when the crash occurs, copy the crash log text from the crash log window and paste that text in to the email you send us. We will need the crash log before we can help resolve the problem.

If you’re seeing strange crashes in Windows 10 when you zoom, rotate, or interact with menus (or other random movements of your stylus or touch gestures) then the culprit is probably Press & Hold for Right Click. This is a tablet and touch input setting that can conflict with tablet drivers and software in strange ways.

• Go to your Control Panel > Pen and Touch > Change touch input settings
• Disable or enable ‚Äòpress and hold‚Äô (whichever it currently is, change it)

This feature has also caused strange zooming or ‘right clicking’ behaviour with older Wacom drivers and previous versions of Windows.

If you are using ArtRage 3 Studio/Studio Pro and are seeing crashes, this might be due to an incompatible feature that you can disable: ArtRage memory crashes on Windows 10

If you can interact with the menus and buttons, but can’t make any marks on the paper, or can draw fine but can’t use the menus properly, then the problem is usually the tablet driver settings.

If you are using ArtRage for iPad or ArtRage for Android, make sure that you haven’t set it to ignore touch input from your finger or use a different stylus.

If you are using Windows, then the issue is usually tablet drivers. Go to Edit > ArtRage Preferences > Input Devices.

If both Realtime Stylus and Wintab are ticked, this is almost always the problem (ArtRage tries to autodetect the one you need to use, but if the tablet driver or operating system sends the wrong signal, ArtRage can’t use it and appears to not be responding). If only one is ticked, you might need to change to the other one.

• If you are using a separate graphics tablet to draw on (or a mouse!), turn off Realtime Stylus and restart ArtRage.
• If you are using a touchscreen device (e.g. a Cintiq or Surface Pro), turn off Wintab and restart ArtRage.

How can I rescue a PTG painting that won’t open in ArtRage?

If you receive an error message and are unable to open a PTG file, then it probably means that your ArtRage painting was were corrupted at some point. Damaged PTG files usually result from interrupted saves (for example, if the computer shuts down or ArtRage crashes). We will do our best to help troubleshoot the source of ArtRage errors, but usually cannot fix corrupted or partial files. However, if you can see the image thumbnail then that means that the PNG preview image is intact. If you use File > Import Image File to open the damaged files, then it will import the PNG thumbnail. This PNG file is the full size of your painting and high quality. It won’t rescue your layers or other paint information, but it will give you something to work with.

Backup Save Files

If crashes happen frequently for any reason, or you are working on an important painting, we recommend turning on the Store Backup Files option. You can find it by going to Edit > ArtRage Preferences > Advanced > Store Backup Files. Adjust the slider to the number of backups you would like to keep. Important: This function does not save a duplicate file. Instead, it keeps a history of previous saved versions. Every time you save, it will delete the oldest backup file, and save the latest changes as a separate file, so if you have made important changes, save twice to update the older back up and the file you are actually working on.

Mac OS X – Crash Issue

We have seen a few instances of a crash when attempting to save a file for the first time on OS X when the save file dialog tries to open, and may occur in other situations where a file dialog is trying to open.

Cause:

In many cases this crash appears to be caused by a bad file in the system. This file is called ‘SCFinderPlugin’ and is located in the Library folder. The crash is actually happening outside ArtRage in an OS system so we don’t know exactly why that file is causing it but it has been known to cause crashes in multiple different applications.

Checking the Crash Log to confirm the problem:

Note: This is optional, you can skip straight to the solution if you like.

You can do a quick check yourself in the crash log to see if this specific crash is the problem you are experiencing. To do this:

1. When the application crashes, select the Report button. A window with a crash log appears.
2. Near the top of the crash log text, look for a line that starts with: ‘Crashed Thread:’.
3. This line tells you which system thread crashed (a number) but also indicates the function the crash occurred in. You can ignore the number.
4. If the line contains this text, the crash is probably the one described in this FAQ answer: Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue

Solution:

Removing the file should resolve the crash. You need to locate it and move it out of the library. It may be installed in more than one library location so follow the steps below to locate and remove it.

1. In the Finder, open the¬†Go¬†menu. If you see a ‘Library’ entry, click it. If you don’t see a Library entry, hold down Option on your keyboard and it should appear, then click it.
2. In the Library folder, open the ‘Contextual Menu Items’ folder.
3. If you see it, drag the SCFinderPlugin.plugin file out of that folder to your desktop.
4. Now open the Macintosh HD, the place you see your Applications folder. There should be a ‘Library’ folder in there too. Open that.
5. Repeat step 2 and 3 (you may want to put folders on the desktop to contain the duplicate files).
6. Reboot and try the operation that crashed again.

You should be able to delete the files at this point. As noted above, the file and the crash it causes aren’t part of ArtRage so we don’t know exactly why this is happening, but you may find other applications also becoming more stable after its removal.

If you still have problems:¬†Please send an email to¬†[email protected]¬†letting us know, and include a copy of the Crash Log generated when the application crashed. To include that, click the Report button when the crash occurs, copy the crash log text from the crash log window and paste that text in to the email you send us. We will need the crash log before we can help resolve the problem.

If you’re seeing strange crashes in Windows 10 when you zoom, rotate, or interact with menus (or other random movements of your stylus or touch gestures) then the culprit is probably Press & Hold for Right Click. This is a tablet and touch input setting that can conflict with tablet drivers and software in strange ways.

• Go to your Control Panel > Pen and Touch > Change touch input settings
• Disable or enable ‚Äòpress and hold‚Äô (whichever it currently is, change it)

This feature has also caused strange zooming or ‘right clicking’ behaviour with older Wacom drivers and previous versions of Windows.

If you are using ArtRage 3 Studio/Studio Pro and are seeing crashes, this might be due to an incompatible feature that you can disable: ArtRage memory crashes on Windows 10

If you can interact with the menus and buttons, but can’t make any marks on the paper, or can draw fine but can’t use the menus properly, then the problem is usually the tablet driver settings.

If you are using ArtRage for iPad or ArtRage for Android, make sure that you haven’t set it to ignore touch input from your finger or use a different stylus.

If you are using Windows, then the issue is usually tablet drivers. Go to Edit > ArtRage Preferences > Input Devices.

If both Realtime Stylus and Wintab are ticked, this is almost always the problem (ArtRage tries to autodetect the one you need to use, but if the tablet driver or operating system sends the wrong signal, ArtRage can’t use it and appears to not be responding). If only one is ticked, you might need to change to the other one.

• If you are using a separate graphics tablet to draw on (or a mouse!), turn off Realtime Stylus and restart ArtRage.
• If you are using a touchscreen device (e.g. a Cintiq or Surface Pro), turn off Wintab and restart ArtRage.

How can I rescue a PTG painting that won’t open in ArtRage?

If you receive an error message and are unable to open a PTG file, then it probably means that your ArtRage painting was were corrupted at some point. Damaged PTG files usually result from interrupted saves (for example, if the computer shuts down or ArtRage crashes). We will do our best to help troubleshoot the source of ArtRage errors, but usually cannot fix corrupted or partial files. However, if you can see the image thumbnail then that means that the PNG preview image is intact. If you use File > Import Image File to open the damaged files, then it will import the PNG thumbnail. This PNG file is the full size of your painting and high quality. It won’t rescue your layers or other paint information, but it will give you something to work with.

Backup Save Files

If crashes happen frequently for any reason, or you are working on an important painting, we recommend turning on the Store Backup Files option. You can find it by going to Edit > ArtRage Preferences > Advanced > Store Backup Files. Adjust the slider to the number of backups you would like to keep. Important: This function does not save a duplicate file. Instead, it keeps a history of previous saved versions. Every time you save, it will delete the oldest backup file, and save the latest changes as a separate file, so if you have made important changes, save twice to update the older back up and the file you are actually working on.

Mac OS X – Crash Issue

We have seen a few instances of a crash when attempting to save a file for the first time on OS X when the save file dialog tries to open, and may occur in other situations where a file dialog is trying to open.

Cause:

In many cases this crash appears to be caused by a bad file in the system. This file is called ‘SCFinderPlugin’ and is located in the Library folder. The crash is actually happening outside ArtRage in an OS system so we don’t know exactly why that file is causing it but it has been known to cause crashes in multiple different applications.

Checking the Crash Log to confirm the problem:

Note: This is optional, you can skip straight to the solution if you like.

You can do a quick check yourself in the crash log to see if this specific crash is the problem you are experiencing. To do this:

1. When the application crashes, select the Report button. A window with a crash log appears.
2. Near the top of the crash log text, look for a line that starts with: ‘Crashed Thread:’.
3. This line tells you which system thread crashed (a number) but also indicates the function the crash occurred in. You can ignore the number.
4. If the line contains this text, the crash is probably the one described in this FAQ answer: Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue

Solution:

Removing the file should resolve the crash. You need to locate it and move it out of the library. It may be installed in more than one library location so follow the steps below to locate and remove it.

1. In the Finder, open the¬†Go¬†menu. If you see a ‘Library’ entry, click it. If you don’t see a Library entry, hold down Option on your keyboard and it should appear, then click it.
2. In the Library folder, open the ‘Contextual Menu Items’ folder.
3. If you see it, drag the SCFinderPlugin.plugin file out of that folder to your desktop.
4. Now open the Macintosh HD, the place you see your Applications folder. There should be a ‘Library’ folder in there too. Open that.
5. Repeat step 2 and 3 (you may want to put folders on the desktop to contain the duplicate files).
6. Reboot and try the operation that crashed again.

You should be able to delete the files at this point. As noted above, the file and the crash it causes aren’t part of ArtRage so we don’t know exactly why this is happening, but you may find other applications also becoming more stable after its removal.

If you still have problems:¬†Please send an email to¬†[email protected]¬†letting us know, and include a copy of the Crash Log generated when the application crashed. To include that, click the Report button when the crash occurs, copy the crash log text from the crash log window and paste that text in to the email you send us. We will need the crash log before we can help resolve the problem.

If you’re seeing strange crashes in Windows 10 when you zoom, rotate, or interact with menus (or other random movements of your stylus or touch gestures) then the culprit is probably Press & Hold for Right Click. This is a tablet and touch input setting that can conflict with tablet drivers and software in strange ways.

• Go to your Control Panel > Pen and Touch > Change touch input settings
• Disable or enable ‚Äòpress and hold‚Äô (whichever it currently is, change it)

This feature has also caused strange zooming or ‘right clicking’ behaviour with older Wacom drivers and previous versions of Windows.

If you are using ArtRage 3 Studio/Studio Pro and are seeing crashes, this might be due to an incompatible feature that you can disable: ArtRage memory crashes on Windows 10

If you can interact with the menus and buttons, but can’t make any marks on the paper, or can draw fine but can’t use the menus properly, then the problem is usually the tablet driver settings.

If you are using ArtRage for iPad or ArtRage for Android, make sure that you haven’t set it to ignore touch input from your finger or use a different stylus.

If you are using Windows, then the issue is usually tablet drivers. Go to Edit > ArtRage Preferences > Input Devices.

If both Realtime Stylus and Wintab are ticked, this is almost always the problem (ArtRage tries to autodetect the one you need to use, but if the tablet driver or operating system sends the wrong signal, ArtRage can’t use it and appears to not be responding). If only one is ticked, you might need to change to the other one.

• If you are using a separate graphics tablet to draw on (or a mouse!), turn off Realtime Stylus and restart ArtRage.
• If you are using a touchscreen device (e.g. a Cintiq or Surface Pro), turn off Wintab and restart ArtRage.

How can I rescue a PTG painting that won’t open in ArtRage?

If you receive an error message and are unable to open a PTG file, then it probably means that your ArtRage painting was were corrupted at some point. Damaged PTG files usually result from interrupted saves (for example, if the computer shuts down or ArtRage crashes). We will do our best to help troubleshoot the source of ArtRage errors, but usually cannot fix corrupted or partial files. However, if you can see the image thumbnail then that means that the PNG preview image is intact. If you use File > Import Image File to open the damaged files, then it will import the PNG thumbnail. This PNG file is the full size of your painting and high quality. It won’t rescue your layers or other paint information, but it will give you something to work with.

Backup Save Files

If crashes happen frequently for any reason, or you are working on an important painting, we recommend turning on the Store Backup Files option. You can find it by going to Edit > ArtRage Preferences > Advanced > Store Backup Files. Adjust the slider to the number of backups you would like to keep. Important: This function does not save a duplicate file. Instead, it keeps a history of previous saved versions. Every time you save, it will delete the oldest backup file, and save the latest changes as a separate file, so if you have made important changes, save twice to update the older back up and the file you are actually working on.

Mac OS X – Crash Issue

We have seen a few instances of a crash when attempting to save a file for the first time on OS X when the save file dialog tries to open, and may occur in other situations where a file dialog is trying to open.

Cause:

In many cases this crash appears to be caused by a bad file in the system. This file is called ‘SCFinderPlugin’ and is located in the Library folder. The crash is actually happening outside ArtRage in an OS system so we don’t know exactly why that file is causing it but it has been known to cause crashes in multiple different applications.

Checking the Crash Log to confirm the problem:

Note: This is optional, you can skip straight to the solution if you like.

You can do a quick check yourself in the crash log to see if this specific crash is the problem you are experiencing. To do this:

1. When the application crashes, select the Report button. A window with a crash log appears.
2. Near the top of the crash log text, look for a line that starts with: ‘Crashed Thread:’.
3. This line tells you which system thread crashed (a number) but also indicates the function the crash occurred in. You can ignore the number.
4. If the line contains this text, the crash is probably the one described in this FAQ answer: Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue

Solution:

Removing the file should resolve the crash. You need to locate it and move it out of the library. It may be installed in more than one library location so follow the steps below to locate and remove it.

1. In the Finder, open the¬†Go¬†menu. If you see a ‘Library’ entry, click it. If you don’t see a Library entry, hold down Option on your keyboard and it should appear, then click it.
2. In the Library folder, open the ‘Contextual Menu Items’ folder.
3. If you see it, drag the SCFinderPlugin.plugin file out of that folder to your desktop.
4. Now open the Macintosh HD, the place you see your Applications folder. There should be a ‘Library’ folder in there too. Open that.
5. Repeat step 2 and 3 (you may want to put folders on the desktop to contain the duplicate files).
6. Reboot and try the operation that crashed again.

You should be able to delete the files at this point. As noted above, the file and the crash it causes aren’t part of ArtRage so we don’t know exactly why this is happening, but you may find other applications also becoming more stable after its removal.

If you still have problems:¬†Please send an email to¬†[email protected]¬†letting us know, and include a copy of the Crash Log generated when the application crashed. To include that, click the Report button when the crash occurs, copy the crash log text from the crash log window and paste that text in to the email you send us. We will need the crash log before we can help resolve the problem.

If you’re seeing strange crashes in Windows 10 when you zoom, rotate, or interact with menus (or other random movements of your stylus or touch gestures) then the culprit is probably Press & Hold for Right Click. This is a tablet and touch input setting that can conflict with tablet drivers and software in strange ways.

• Go to your Control Panel > Pen and Touch > Change touch input settings
• Disable or enable ‚Äòpress and hold‚Äô (whichever it currently is, change it)

This feature has also caused strange zooming or ‘right clicking’ behaviour with older Wacom drivers and previous versions of Windows.

If you are using ArtRage 3 Studio/Studio Pro and are seeing crashes, this might be due to an incompatible feature that you can disable: ArtRage memory crashes on Windows 10

If you can interact with the menus and buttons, but can’t make any marks on the paper, or can draw fine but can’t use the menus properly, then the problem is usually the tablet driver settings.

If you are using ArtRage for iPad or ArtRage for Android, make sure that you haven’t set it to ignore touch input from your finger or use a different stylus.

If you are using Windows, then the issue is usually tablet drivers. Go to Edit > ArtRage Preferences > Input Devices.

If both Realtime Stylus and Wintab are ticked, this is almost always the problem (ArtRage tries to autodetect the one you need to use, but if the tablet driver or operating system sends the wrong signal, ArtRage can’t use it and appears to not be responding). If only one is ticked, you might need to change to the other one.

• If you are using a separate graphics tablet to draw on (or a mouse!), turn off Realtime Stylus and restart ArtRage.
• If you are using a touchscreen device (e.g. a Cintiq or Surface Pro), turn off Wintab and restart ArtRage.

How can I rescue a PTG painting that won’t open in ArtRage?

If you receive an error message and are unable to open a PTG file, then it probably means that your ArtRage painting was were corrupted at some point. Damaged PTG files usually result from interrupted saves (for example, if the computer shuts down or ArtRage crashes). We will do our best to help troubleshoot the source of ArtRage errors, but usually cannot fix corrupted or partial files. However, if you can see the image thumbnail then that means that the PNG preview image is intact. If you use File > Import Image File to open the damaged files, then it will import the PNG thumbnail. This PNG file is the full size of your painting and high quality. It won’t rescue your layers or other paint information, but it will give you something to work with.

Backup Save Files

If crashes happen frequently for any reason, or you are working on an important painting, we recommend turning on the Store Backup Files option. You can find it by going to Edit > ArtRage Preferences > Advanced > Store Backup Files. Adjust the slider to the number of backups you would like to keep. Important: This function does not save a duplicate file. Instead, it keeps a history of previous saved versions. Every time you save, it will delete the oldest backup file, and save the latest changes as a separate file, so if you have made important changes, save twice to update the older back up and the file you are actually working on.

Mac OS X – Crash Issue

We have seen a few instances of a crash when attempting to save a file for the first time on OS X when the save file dialog tries to open, and may occur in other situations where a file dialog is trying to open.

Cause:

In many cases this crash appears to be caused by a bad file in the system. This file is called ‘SCFinderPlugin’ and is located in the Library folder. The crash is actually happening outside ArtRage in an OS system so we don’t know exactly why that file is causing it but it has been known to cause crashes in multiple different applications.

Checking the Crash Log to confirm the problem:

Note: This is optional, you can skip straight to the solution if you like.

You can do a quick check yourself in the crash log to see if this specific crash is the problem you are experiencing. To do this:

1. When the application crashes, select the Report button. A window with a crash log appears.
2. Near the top of the crash log text, look for a line that starts with: ‘Crashed Thread:’.
3. This line tells you which system thread crashed (a number) but also indicates the function the crash occurred in. You can ignore the number.
4. If the line contains this text, the crash is probably the one described in this FAQ answer: Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue

Solution:

Removing the file should resolve the crash. You need to locate it and move it out of the library. It may be installed in more than one library location so follow the steps below to locate and remove it.

1. In the Finder, open the¬†Go¬†menu. If you see a ‘Library’ entry, click it. If you don’t see a Library entry, hold down Option on your keyboard and it should appear, then click it.
2. In the Library folder, open the ‘Contextual Menu Items’ folder.
3. If you see it, drag the SCFinderPlugin.plugin file out of that folder to your desktop.
4. Now open the Macintosh HD, the place you see your Applications folder. There should be a ‘Library’ folder in there too. Open that.
5. Repeat step 2 and 3 (you may want to put folders on the desktop to contain the duplicate files).
6. Reboot and try the operation that crashed again.

You should be able to delete the files at this point. As noted above, the file and the crash it causes aren’t part of ArtRage so we don’t know exactly why this is happening, but you may find other applications also becoming more stable after its removal.

If you still have problems:¬†Please send an email to¬†[email protected]¬†letting us know, and include a copy of the Crash Log generated when the application crashed. To include that, click the Report button when the crash occurs, copy the crash log text from the crash log window and paste that text in to the email you send us. We will need the crash log before we can help resolve the problem.

If you’re seeing strange crashes in Windows 10 when you zoom, rotate, or interact with menus (or other random movements of your stylus or touch gestures) then the culprit is probably Press & Hold for Right Click. This is a tablet and touch input setting that can conflict with tablet drivers and software in strange ways.

• Go to your Control Panel > Pen and Touch > Change touch input settings
• Disable or enable ‚Äòpress and hold‚Äô (whichever it currently is, change it)

This feature has also caused strange zooming or ‘right clicking’ behaviour with older Wacom drivers and previous versions of Windows.

If you are using ArtRage 3 Studio/Studio Pro and are seeing crashes, this might be due to an incompatible feature that you can disable: ArtRage memory crashes on Windows 10

If you can interact with the menus and buttons, but can’t make any marks on the paper, or can draw fine but can’t use the menus properly, then the problem is usually the tablet driver settings.

If you are using ArtRage for iPad or ArtRage for Android, make sure that you haven’t set it to ignore touch input from your finger or use a different stylus.

If you are using Windows, then the issue is usually tablet drivers. Go to Edit > ArtRage Preferences > Input Devices.

If both Realtime Stylus and Wintab are ticked, this is almost always the problem (ArtRage tries to autodetect the one you need to use, but if the tablet driver or operating system sends the wrong signal, ArtRage can’t use it and appears to not be responding). If only one is ticked, you might need to change to the other one.

• If you are using a separate graphics tablet to draw on (or a mouse!), turn off Realtime Stylus and restart ArtRage.
• If you are using a touchscreen device (e.g. a Cintiq or Surface Pro), turn off Wintab and restart ArtRage.

How can I rescue a PTG painting that won’t open in ArtRage?

If you receive an error message and are unable to open a PTG file, then it probably means that your ArtRage painting was were corrupted at some point. Damaged PTG files usually result from interrupted saves (for example, if the computer shuts down or ArtRage crashes). We will do our best to help troubleshoot the source of ArtRage errors, but usually cannot fix corrupted or partial files. However, if you can see the image thumbnail then that means that the PNG preview image is intact. If you use File > Import Image File to open the damaged files, then it will import the PNG thumbnail. This PNG file is the full size of your painting and high quality. It won’t rescue your layers or other paint information, but it will give you something to work with.

Backup Save Files

If crashes happen frequently for any reason, or you are working on an important painting, we recommend turning on the Store Backup Files option. You can find it by going to Edit > ArtRage Preferences > Advanced > Store Backup Files. Adjust the slider to the number of backups you would like to keep. Important: This function does not save a duplicate file. Instead, it keeps a history of previous saved versions. Every time you save, it will delete the oldest backup file, and save the latest changes as a separate file, so if you have made important changes, save twice to update the older back up and the file you are actually working on.

Mac OS X – Crash Issue

We have seen a few instances of a crash when attempting to save a file for the first time on OS X when the save file dialog tries to open, and may occur in other situations where a file dialog is trying to open.

Cause:

In many cases this crash appears to be caused by a bad file in the system. This file is called ‘SCFinderPlugin’ and is located in the Library folder. The crash is actually happening outside ArtRage in an OS system so we don’t know exactly why that file is causing it but it has been known to cause crashes in multiple different applications.

Checking the Crash Log to confirm the problem:

Note: This is optional, you can skip straight to the solution if you like.

You can do a quick check yourself in the crash log to see if this specific crash is the problem you are experiencing. To do this:

1. When the application crashes, select the Report button. A window with a crash log appears.
2. Near the top of the crash log text, look for a line that starts with: ‘Crashed Thread:’.
3. This line tells you which system thread crashed (a number) but also indicates the function the crash occurred in. You can ignore the number.
4. If the line contains this text, the crash is probably the one described in this FAQ answer: Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue

Solution:

Removing the file should resolve the crash. You need to locate it and move it out of the library. It may be installed in more than one library location so follow the steps below to locate and remove it.

1. In the Finder, open the¬†Go¬†menu. If you see a ‘Library’ entry, click it. If you don’t see a Library entry, hold down Option on your keyboard and it should appear, then click it.
2. In the Library folder, open the ‘Contextual Menu Items’ folder.
3. If you see it, drag the SCFinderPlugin.plugin file out of that folder to your desktop.
4. Now open the Macintosh HD, the place you see your Applications folder. There should be a ‘Library’ folder in there too. Open that.
5. Repeat step 2 and 3 (you may want to put folders on the desktop to contain the duplicate files).
6. Reboot and try the operation that crashed again.

You should be able to delete the files at this point. As noted above, the file and the crash it causes aren’t part of ArtRage so we don’t know exactly why this is happening, but you may find other applications also becoming more stable after its removal.

If you still have problems:¬†Please send an email to¬†[email protected]¬†letting us know, and include a copy of the Crash Log generated when the application crashed. To include that, click the Report button when the crash occurs, copy the crash log text from the crash log window and paste that text in to the email you send us. We will need the crash log before we can help resolve the problem.