[Solved] 3D Coat Pro weird artifacts when sculpting / surface modes

[EvilMP]

Hi,

   I am having an issue with 3D coat Pro version 2025.1. I thought the install was corrupted so I did a fresh install and observed the same behavior. All the previous versions of the program ran on my 49 inch curved monitor. So I am not sure if that is even the issue because it only happens in sculpting and surface modes. It does a slight flicker in the paint room. I have a video of it below so you can see it first hand. I am at my wits end. 

 

 

[Carlosan]

Hi

Try turning off this new option "Highlight"

Hope it help

[EvilMP]

Turned off Highlight and the same behavior. I even updated my video card drivers.

[Carlosan]

Press RMB over the tool and press Restore default

And vary the Fall off

To get smoother strokes (more noticeable on edge borders)

 

[EvilMP]

Tried that I am still getting that bleed effect on both sides like the video I attached in the initial post. The autopick is also off. 

[Carlosan]

You can try the latest version 2025.3

Take as Beta, it is not a stable release

The latest stable release is 2024.31

[EvilMP]

I don't know I have tried both Beta and the 2024.31 and it's still having that issue with the artifacts. I even reset the entire software to default. I even removed the license and installed 3D Coat 2024.31 entered the license again and the same exact thing happens. I am going to try and update Windows 11 pro and see if that corrects this. 

[Carlosan]

What if you run 3DC windowed, not at full maximized size ?
Display drivers are uptodate ?

[EvilMP]

I found the problem this is so badword, and Nvidia needs to fix this ****** which has been a known issue for years. So when you install any new Nvidia driver you have to do the "Custom Installation" and clean out  the previous settings,(fresh install). It hit me when I remember an IT client had a similar issue with accounting software. So when I updated the driver I did that and the 3D Coat issue is gone. Carlosan not sure if you want to put this into a Knowledge base or not, just in case someone else runs into this issue.