3DCoat 2026 Development

[wendallhitherd]

yoooooooo you guys fixed live boolean intersections crash when no geo is produced and the CutOff tool in 2026.05!!
I keep slicing my geo and can't seem to break it. Feels amazing -- edit: I was able to break it eventually, i guess im sticking to live booleans because they support sharp edges without resulting in non manifolds / holes with successive cuts 

 

I will mention, even in 2026.05 it seems like some update events are missing for live boolean. 
I have to move my object after using a tool for the live boolean to be recalculated

here's a video, basically, the boolean doesn't update until i jiggle the model. 

As well:
- surface mode brushes or any brushing mode vox brush do not udpate the live boolean parent object
- any surface mode brush results in consistent live boolean gap until a voxel brush is reactivated 
 

here's an example of trying to use brush mode with live booleans

Edited July 2 by wendallhitherd

[Carlosan]

Could you please try this simple test:
Geometry > Incremental Render = ON

[wendallhitherd]

9 hours ago, Carlosan said:

Could you please try this simple test:
Geometry > Incremental Render = ON

Hello! incremental render on / off does not seem to make difference

[wendallhitherd]

As well more things seem to be broken or bugs:
- Stroke mode doesn't any longer seem to be being saved into brush presets when set to lasso for freeze brush. resets back to hard paint. I think the storage hash in the brush xml is invalid for lasso. Sus is "EModeHash" 
Before (previous versions of 3dcoat this woulsd store lasso)
 

    <EModeHash>000087EA</EModeHash>

After. I assume this is supposed to encode lasso brush but it resets back to hard-paint

    <EModeHash>000086EB</EModeHash>

 

 

- when decimating a surface, the shift / ctrl shift mode changes to decimate.

it seems likely that the ui command for the geometry -> decimate and the brush mode -> decimate are identical and so mapping a shortcut to the geometry decimate will also invoke the shift-menu decimate

 

 

- when using detail brush modifier while in voxel mode, and then switching to surface mode, the mesh will be broken. 

 

 

[wendallhitherd]

- Cancelling or undoing a freeform move operation will cause 3dcoat to hang and crash when moving a boolean mesh with a fairly complex shape. This hang / crash does not occur on simpler models like the low-rez sphere, and it does not happen if the move is confirmed rather than cancelled.

Undoing also causes the same hang

## EDIT ##
Actually it seems to have nothing to do with live boolean. it will hang-crash if you press escape to undo any move op in a lot of cases.

Edited July 6 by wendallhitherd

[wendallhitherd]

 

Close holes is now broken for roughly half of the time in 2026.05

- make teh default sphere

- mask a section of it

- hide masked

- split hidden

- close holes on both sides. One side will splay out and  become a sombrero. you now have a gigantic not-closed hole!

 

[wendallhitherd]

rapid fire bugs lol, this time with pose mode FFD

- pose FFD with surface mode will randomly voxelize you surfaces

- it is in general "incredibly janky"

- watch the video to see all the things going wrong

 

 

 

[carrots]

On 6/30/2026 at 12:51 AM, animk said:

2026.05, there is color bleeding on the UV seams in curvature baking layer that would affect the cavity painting.  This is not in 2026.01.  Is it a temporary bug and will be fixed later? 

Fixed in 3DCoat version 2026.06

 

[Dmitriy Nos]

On 7/3/2026 at 2:18 AM, wendallhitherd said:

it will hang-crash if you press escape to undo any move op in a lot of cases.

This should be fixed in 2026.07. Please check.

[Dmitriy Nos]

On 7/3/2026 at 1:54 AM, wendallhitherd said:

- when using detail brush modifier while in voxel mode, and then switching to surface mode, the mesh will be broken. 

What details am I missing?

 

 

[wendallhitherd]

19 hours ago, Dmitriy Nos said:

What details am I missing?

 

 

hi there, might be hard to catch in my video but I use "extra detail" w/ ctrl shift when in voxel mode, then switch to surface, then smooth


your brush settings look like you are not using a brush mode that tesselates the geometry

[wendallhitherd]

On 7/18/2026 at 1:24 AM, Dmitriy Nos said:

This should be fixed in 2026.07. Please check.

yep this seems fixed for me as well

[Sal_GC]

Hi there everyone. Congrats to the devs on the 2026.12 release.   Perhaps someone can share something about this: I have been having this issue while trying to use the new materials, masks and general node features, the .avif textures seem to install in a different directory that just does not get created. Also, the new masks and stencils just appear to be black. I thought it was related to the extensions panel and activating the .avif and qt options there, but apparently nothing changed. This is what I get with the 2026.12 installation:

 

 

[Mihu83]

Something is messed up with Render Room in 2026.12 - when Realtime render is enabled, whole object manipulation(zoom, rotate, etc.) is stuttering and very slow + VRAM usage goes up quite fast and isn't released after switching to other rooms. Tested on the mesh under 1 million poly count - VRAM usage went to 6GB in really short time.

Also, I'm just starting to play around with this whole node/Material system, so a basic question - how do you stack different Materials on the same object/layer without replacing previous one?

Edited July 23 by Mihu83

[hyburn]

Attention: Dev team
 

First I'd like to say "well done", this software is amazing.

Bug, I get a 403 error when trying to access the "Read the Auto-Retopology Guide"

 

Access to www.christoph-werner.de was denied

You don't have the user rights to view this page.