Hi It's been a while since I last posted here, but I have a concern regarding the Knife tool whilst retopologising. I'm not sure if there's an option I need to adjust, but is there any way of getting the Knife tool's cuts to influence the low poly mesh so it conforms to the reference mesh? In other words, like the Split Rings tool, when you add a loop, it makes the low poly mesh conform to the reference mesh by pushing the loop out and matching the curvature and silhouette. All I get with the Knife tool are the cuts, but the low poly mesh remains flat. Thanks

It really depends on what functionality will it have. That should work from within browser?

Share the project (by PM) to take a look

Hi to all. I am doing only hard surface modeling, working mainly in Paint Room - UV Room and only for separating the model in the Modeling Room. Models themselves are created in Blender, right now in Version 5. Right now I use 3DCoat 2026.1 I have been using 3DCoat for some years now on a daily basis and to me it sounds funny what is written on the topic of this forum section by Carlosan, that more detailed information is needed to solve problems. I do have high resprect for Carlosan, he is really doing his best in support, but, in my opinion, forwarding the problems to the developers does not bring any results. I have been reporting multiple problems in Paint Room and UV Room over the past years. All of the problems have been checked and confirmed as faults by different high ranked testers and been reported to the developers. The problems are not minimal small side effects that are not working correctly, the problems are fundamental problems. None have been solved up to now! I wrote a personal message to Mr. Shpagin, the lead developer of 3DCoat. I dared to do this, just because Mr. Shpagin wrote in the forum: "...just in case you have problems and get no solution for it, contact me in person" BUT, not even an answer to my mail. So even though I´m sure I won't get a solution for the problem, I will post it here. The model is created in Blender 5. Imported to 3DCoat by per Pixel Paint with Auto mapping In UV Room I separate the corresponding UV Islands to separate UV sets. After separating a part to a new set, I do an "unwrap" command and "apply UV set", switch to Paint Room, check if the different UV sets are correct, return to UV room, and then I continue with the separation process. After some time this strange effect happens. As seen on the pictures (attached),  the UV Sets in the UV Room are all correct, but one of the UV sets in the Paint Room is completely broken. You may swith back to UV Room, do an unwrap, do an apply UV Set, return to Paint Room, confrim the change in the UV Room, but nothing changes, the UV set is broken and stays broken. There is no way to correct it. Result .... restart your work, lose more time. Pictures Bild 1 and Bild 2, show the different rooms: UV Room and Paint Room. You may check the memory consumption in the bottom line, as well as the time and date stamp, just in case you think that I want to fool someone. My system can´t be the problem, there is enough memory, enough harddrive space, all these things have been checked and confirmed within the last years of error reports. I clearly understand that solving a problem like this is nearly impossible, because there could be any number of problems with the model itself. But the model  is checked in Blender for manifold problem or any other related problem and over all, the problem has nothing to do with this model specifically, the problem appears nearly every time I do work with models with a high polygon count. So, maybe the problem was already reported by someone else, maybe there is already a workaround, but I don't think there is a solution and my experience shows me that there probably won´t be a solution, either.  Another frustrated user of 3DCoat Best regards Walter PS: I´m well aware of the terrible situation in Ukraine and my heart is heavy when I´m thinking of the daily threat to the Ukraine people. 

Try exporting trough Textures Menu   same result ?

It is for Sculpt Objects (Nodes Workspace), but not just yet for Paint Objects. They are preparing it for the 2026 release and working all the bugs out before dropping it to beta. Should be anytime now.

3D Coat team, can you guys answer why this is the case? This is quite a major issue for hand-painted texturing.

is this currently available now?

Source... Overview Join us on Saturday, April 25th as we dive into sculpting a game character in 3DCoat. Program Details Who should Attend: Adults (Ages 18+). All experience levels are welcome. What to Expect: This 5hr workshop will be taught by industry professional, Gavin Ball. Gavin will be covering the ins and outs of sculpting, retopology, baking, and texture painting a character in 3DCoat. Additionally, we will go over how to export it to a game engine. The workshop will be interactive so you will have ample opportunities for asking questions as Gavin works through these processes. We will also record the session and provide it to all participants afterwards so that you can replay and practice it at home.

What is the problem ? Bend tool does not work the same for different users OS Windows Steps to reproduce a Bug Using bend tool Expected Result Actual Result   Software version 2025 and up

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).