Hello Everyone, Hopefully this is okay to post here. I'm a long time 3D Coat user and I just wanted to share here that I'll be doing a live workshop (in-person and online) on April 25th, 2026 from 11am-4pm EST. The in person workshop will be in at 103 Dundas st. West, Whitby, Ontario, Canada. We will also have an online option if you're not local. https://www.eventbrite.com/e/1985739453159?aff=oddtdtcreator  

thank you so much, that is amazing!

https://3dcoat.com/forum/index.php?/topic/23378-linux-updates-news/page/19/#findComment-204432

https://3dcoat.com/forum/index.php?/topic/23378-linux-updates-news/page/19/#findComment-204432

Hello, dear Linux users! The ABI incompatibility that we have encountered was the last straw that forced me to switch to Flatpak. Here is the link to the Flatpak build with a detailed manual on installation: https://pilgway.com/~sergyi/links-Linux.html With help from Copilot, I have found and fixed a long-standing problem: the inability to run 3DCoat from the launcher using a Desktop file. After installing 3DCoat as Flatpak, you will see the 3DCoat icon in your Linux launcher. This build can be unstable. I see reports from Windows users complaining about the instability of 2026.01 in general. Please consider this build as a packaging test. Regarding GTK2. A year ago, I ported the code to GTK3. Everything worked except one thing: 3DCoat's internal modal dialogs, which it draws itself (not system modal dialogs), crashed the app. For more than a month, I investigated the problem without working on anything else. But because of the enormous size of the 3DCoat source code, I wasn't able to determine the cause. I reverted to the GTK2 code only because of those internal modal dialogs, and I notified the company that we should implement them differently. I have worked around the file dialog problem by building 3DCoat on Pop!_OS instead of Ubuntu. The file dialog problem is another ABI incompatibility issue that Flatpak should now solve. Some questions I have for you. As you know, I have developed the low-level foundation on which 3DCoat runs. That foundation isolates 3DCoat tools from the platform. To do that, I have rewritten each low-level function three times using different API on each platform: WinAPI on Windows, Cocoa on macOS, and GTK on Linux. That process is tedious because you do the same work three times. Moreover, you have to build the project source code three times with different compilers, which introduces optimization errors. In the case of Linux, you have to encounter ABI incompatibility between distributions. Given the complexity of this process, I was looking for an alternative. Accidentally, in 2021, I learned about WebAssembly and fell in love with it. WebAssembly allows application developers to use a single API and to make a single build that runs everywhere. WebAssembly effectively solves the problem with updates, because users always run the latest uploaded build. I have ported the low-level foundation (let's call it "engine") to WebAssembly with deep modifications. You can see it here in action in my game: https://underseagame.com I developed this game in 2011 with an artist for iOS, but I have now ported it to my new WebAssembly engine. What do you think about the idea of reimplementing some 3DCoat functionality on this new WebAssembly engine? Please consider the real-world limitations of WebAssembly: single-threaded and 32-bit, whereas multithreading and 64-bit support are uneven and experimental. Obviously, the full 3DCoat source code is not portable to WebAssembly because it was not designed for it. But some tools, some functions, could be. How do you see the 3DCoat web tool? What essential functions should it have? Before raising this question in the company, I would like to hear your expert opinions.

Yes, it will be like having Designer integrated in Painter. You can use it with Layer Masks, and from what I understand, there should be no need for Adjustment Layers since a user should be able to add an Adjustment node. It's a lot like the current Node system for the Sculpt Workspace, but this will be for the Paint Workspace/Objects (PPP). 

Source... Goals This is a start to a series of material studies and I decided to kick it off with a rock. Often, I feel we as artists forget that less is more, and we do not focus enough on art fundamentals, so I wanted to get back to basics. Software Blender 3D Coat Photoshop Marmoset Toolbag I encourage all artists that are learning to hand-paint to try this out.  

I'm sorry, this link doesn't work. I have the same problem. 3DCoatTexture 2025.17, Windows 11. During work, the MMB bound to the stylus stops working properly. I can't move the model. Also, I see the language change window as if the Windows+Space hotkey was pressed (it really was not). I can minimize/maximize or change the active window to fix the problem.

curious , where it says development for 2026 , the node system? we talking something like designer ? 

Super excited about this "Paint Room/Object nodes and GPU engine" I've been testing texturing an 8K Terrain in 3D Coat 2024.31 - it's okay but a little sluggish so look forward to testing new build once above is implemented. On the following system specs. Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz   3.60 GHz Installed RAM: 64.0 GB Graphics Card: NVIDIA GeForce RTX 2080 Ti (11 GB)  

I think it is most often an .xml file that gets corrupted, somehow. Another thing that has probably made things more buggy than normal is the addition of QT and Python. I hope it gets sorted out soon.

there is a list of groups that have no one corresponding volume only serves to determine if a name is missing.  This function will help find Retopo Objects that have corresponding Sculpt Objects. If there are any corresponding objects with similar names, the Retopo Object will bake only the details from the Sculpt Object with the same name. Unlike SP, in 3DC the volume name on Sculpt layers and Polygroup layers must have the same name. Name correspondence it’s actually sequential texture baking. Other tools allow you to explode the mesh meaning it will move all the individual parts out in space so that you can bake everything in one pass and 3DCoat is handled somewhat differently but the objective is the same.  Another thing to keep in mind is if you have secondary elements that you want to be baked with another mesh as if they are all one then what you would do is in the Sculpt tree layer panel in the sculpt workspace you would make those child layers.

Hello,   I've been working with a lot of character models, and the one thing that really makes me wonder why it's not obvious is Paint Fill per UV Island is not available for the 3d viewport. I have clothing, complex architectures, and monsters with lots of UV islands and seams (like upwards of 50 UV Islands per material) and trying to Paint fill a certain part of a mesh, like a shirt collar or a Claw is a very slow and painful process. Trying to dig it out from the Texture Editor when its scattered everywhere is also slow and requires guessing, especially if I don't know which island belongs to what before painting it. Is there a way to paint or Fill bucket UV Islands without the Texture Editor so I can just click on certain parts of the mesh and it'll fill with that Color or smart Material only. I've read the past suggestions to use Freeze and invert, but that also requires the Texture Editor open and you finding the exact island you need to fill. Is there a better way than that to do something so simple without the Texture Editor?

I don't know if you saw my reply but it is not doing anything

I'm still getting it ):

Hi ! Try turning this option off