looking at your video, it's worth noting the following: - Collapse bool tree seems to work differently than merge subtree. Collapse caused instant crash for me, while merge visible / merge subtree caused hang - There seems to be different behavior if you use painting tools AFTER vox hide. Though for me any painting would cause crash most times on home machine. On work machine sometimes it would succeed, but painting after vox hide on internal surface would crash every time. Hm, I repro'd the crash on another machine by following the steps, but if you save and load the file before applying the bools, it doesn't occur. I think the invalid state that causes the crash is not saved. I have a theory. It might have to do with the "pseudo surface" edits you are allowed to do while in voxel mode. EG you sculpt in surface mode but you don't actually go back to voxel mode until it is resampled. seemingly Random 3dcoat events seem to kick off a voxel resample, but using things like the fill tool or the move tool on boolean objects will cause a surface edit to a vox tool and I think this might be related to the family of crashes. 2026-03-02_pre_crash_to_dmitriy.3b Here is a file that definitely crashes every time when you use "collapse bool tree" I arrived at this one slightly differently (also collapse bool tree using steps in video would work occasionally on other machine depending on what exact  buttons I pressed)  On this one I used vox hide, then used the paint fill tool on the intersected region. 

LuxCore produces such sublimely beautiful results...not fakery, but authentic mathematically, physically correct caustics, even unto the materials of the refractive transparent materials that vary according to their scientifically measured chemical substances indices.  

source... The latest version of Quixel Mixer has been released as a free, offline app, without official support. Quixel Mixer has been abandoned for some time, leaving users speculating: some hoped Epic Games might turn it into something new, while others expected it to be shut down entirely. The end of an era is here: Quixel Mixer's final offline version has been released, with no further updates to follow.

Hi! I'm trying out some sculpting with layers (in Surface Mode), and just wanted to check if the layer masks are supposed to work with sculpt information. Because I can't seem to make it work. Cheers Andreas

I have built 3DCoat 2026.01 for Linux and included libxml2 with the package. Please download it as always from here: https://pilgway.com/~sergyi/links-Linux.html

@wendallhitherd I was able to replicate the program crashing only a few times, but then it stopped happening. Maybe I'm missing something. bandicam 2026-03-02 10-30-42-473.mp4   Please send your .3b scene file before all Boolean operations.

Reproducible crashes related to live booleans in 3DC 2026.01 crash 1: paint tools + boolean collapse causes crash 2026-03-01 20-15-34.mp4   Crash 2: paint tools + live booleans + merge subtree hangs 2026-03-01 20-17-41.mp4   Non-crash bugs with live booleans - Live booleans are missing a bunch of visibility updates, resulting in visible gaps and incorrect live booleans. Must toggle visibility on / off to refresh live boolean preview 2026-03-01 20-33-22.mp4    

Yep, I'm on board with implementing third party render engine or reworking built in one, but... only if it will go along with current shader/smart material system inside 3DCoat. I really don't want to recreate/rebuild my vast library of shaders/smart materials.

Hi Please try sync layer option, don't edit layers. Hope it help 

It's a fully developed professional studio quality render engine that rivals and even surpasses Maxwell Render and Octane render in many areas. All it would take is to set it up so it's embedded in 3D Coat, part of it's fabric. Yes I know it comes in Blender. But many of us can't stand working in the Blender UI (no I'm not up for memorizing another immense set of hotkeys). Yes there's stand alone LuxCore but it's free, it's the best and   it solves the current problems of 3D Coat render room by  having all the necessary lighting tools in it. It's a studio of the best lighting tools you can find anywhere. (Save time and just vibe code it in Grok or Alembic Claude Opus 4.6?)      

For context, I am syncing my all my layers in an external editor, being Clip Studio Paint. Previously, working between the two was no issue, but now I have a problem. Folders created in Clip Studio paint do not save over correctly back into 3DCoatTextura, instead converting them into a blank painting layer with the name of the Folder. It's also ruining my layer structure, as I cannot drag folders out of other folders in 3DCoatTextura, making my layers trapped in folders inside folders. Is this a known issue?

Hi  In case if you want to help with translation to your native language there are two options:  - First, default is to translate ID and then send it to us via the web form. - Another option: you may translate the whole language file locally and then send it to us (to support@pilgway.com).   Enable this option ( pay attention to the Edit->Preferences->Translate directly into the language file), translate, ensure that your ID-s appear in UI.   Pay attention that the file InstallFolder/data/Languages/YourLanguage.xml will be modified, modification of the file in the install folder requires running the coat "as administrator".

Hello Mr. Andrew Shpagin! I am a toy designer from China, and 3dcoat is great. Many advanced features are ahead of other software and have been copied and imitated by other software. I now most expect it to perfectly integrate all modeling methods into one! China is currently experiencing a surge in industrial products, film and television, animation, and gaming, and there is a great need for 3dcoat because it can produce prototypes faster and the subsequent details can be automatically generated by AI. But after so many years, not many people in China know about this software because the Chinese version interface translation is not done well, and there are few tutorials in China. The operating interface of 3Dcoat is simpler, easier to learn, and logically clear compared to other software. It is a very easy to learn software, but many Chinese translations in the Chinese version interface are incorrect and confusing, so many Chinese people cannot understand it and have given up on 3Dcoat. I really hope the author can rewrite the translation in the Chinese version. I believe it will attract a wave of dissemination in China. It is very suitable for the current environment in China, where productivity is saturated and creative styling is more valued. What is needed most is a rapid prototyping software like 3dcoat. Blender has been popular in China since version 2.8, and 3dcoat is not far from spring. I also sincerely hope that Ukraine will end the war as soon as possible. It would be great if the development headquarters of 3dcaot could move to China, so that you will not be affected by the war. Sincerely wish everyone in the development team success in their dreams!

is there a possiblity we can lock out camera view rotation? so it perfectly moves along an axis and doesnt move off that axis?

Thank you very much for your explanation — my issue has been perfectly resolved. After switching to the OpenGL normal map preset in 3DCoat, the normal direction problems no longer appeared in KeyShot. Although the normal map itself still seems to show errors along the UV seams when viewed directly, the actual KeyShot render looks completely correct, with no visible issues at all. This preset change is honestly amazing. That said, I feel that the KeyShot export preset in 3DCoat doesn’t produce very strong results visually, at least in my case. I’m not sure whether this is due to some incorrect settings on my side in KeyShot, but the PBR material response feels rather subtle or muted, and I’m not sure if I’m describing this clearly enough. From my experience, exporting from 3DCoat using the Blender preset and then using KeyShot’s standard material type actually gives better results. Simply setting the contrast of all grayscale (black-and-white) textures to 0 in KeyShot already helps improve the final render quite a bit — at least perceptually, that has been the case for me.

The only difference between OpenGL and DirectX is that the green channel is flipped. KeyShot primarily uses OpenGL for its user interface, real-time viewport, and core functionality.  For OpenGL, you may need to invert the Green channel (Y+) depending on the target engine, although 3DCoat usually handles this in its export dialog. - 3DCoat Normal Map Format: When exporting textures, ensure the Normal Map is set to OpenGL.     version 2026 have added Keyshot, but you can create your own. Test another preset to find which one works for your current workflow

Thank you very much for your suggestion. However, I couldn’t find an Unreal Engine 4 preset on my side. I used the export settings shown in the image I sent earlier, but the manually painted normal map still shows the same seam issues. Would it be possible for you to share a screenshot of your export settings? That would really help me understand exactly how the setup should be configured.

Is anyone else having problems with their Brush disappearing when you switch (using Vertex Paint on a Sculpt Object) to the Paint room? I have had this issue on and off for over a year now...and I wanted to know if it is some kind of corrupted .xml file in my Documents/3DCoat directory, or not. I think this is DEFINITELY a BIG Bug because it's repeatable, even if I temporarily rename my Documents/3DCoat folder (so 3DCoat will generate a fresh new directory on the next opening of the application), I run into this problem over and over.  To repeat this issue, I simply pick a brush alpha and instantly lose my brush in the viewport. Brush Disappearing Bug.mp4

Hi  At export, try selecting another preset as Unreal 4 Hope this help