Forums

Hello. I can confirm that. Any Texture lower then 512 shows up empty in the Texture editor and is unpaintable. I also dont know if that is the new minimum? But I rather dont think so. 

Creating a Mars Rover Using Booleans #3dsculptingView the full article

Creating a Mars Rover Using Booleans | Demonstration of Creating a Hard-Surface ObjectView the full article

Windows, 2026-20 3DCoat-2026-20.exe 3DCoatTextura-2026-20.exe 3DCoatPrint-2026-20.exe - Fixed a bug in the Primitives tool where using the Lasso selection on the Free Form (FFD) cage would accidentally move a point and cause the tool settings to disappear. - Fixed a crash that could occur when using the Undo command while editing primitives with the Free-Form Deformation (FFD) tool. - Fixed a crash that occurred when typing a long search query into the tool search field in the Space Menu. - Fixed a crash that occurred when trying to create a new Python or Core API script if the script templates folder is missing. - Fixed an issue where uniform Metalness and Glossiness shader parameters failed to bake properly into textures, and corrected a bug that caused the baked colors to appear too dark. - Fixed an issue where layer channel assignments were lost when loading a saved project (most commonly noticed when assigning the Color channel to Normals).

Has there been any communication regarding linux? 2026 is unusable for me and I  also don't have access to any older builds in my account ever since upgrading to 2026.

Try using the 3DCoatGL64Legacy version; this is a special version designed for compatibility with projects created in earlier versions.

Thanks ! found it: something wrong is inside \Documents\3DCoat2026\UserPrefs A new folder created by 3DC at start solved the issue. (time to find the reason)

It is working well from my side! 

fresh install paint.mp4 //edit It was fixed after deleting \\Documents\3DCoat2026\UserPrefs

Version 2026.19 - seems like Smart Materials, Presets, Alphas, etc. are fine after update, but almost all the folders with custom shaders are empty. These few custom shaders that are left are messed up, doesn't display properly.

Can you explain how to replicate this?

PPP result: anyone ?

Fixed on version 2025.19

Windows, 2026-19 3DCoat-2026-19.exe 3DCoatTextura-2026-19.exe 3DCoatPrint-2026-19.exe - Fixed an issue with GLTF scene export when visible objects mode was disabled.- Fixed "Specular Color only" and "Metalness only" view modes. - Write "[floating, used X of Y]" to persistent log file "Documents\3DCoat202x\FloatingLicense.log" with ISO UTC timestamps - Approximately 150 automated crash reports processed; a large number of crashes fixed. - Fixed severe UI lag that occurred when tweaking node properties with sliders in Per-Pixel Painting mode. - Fixed an issue where the final merged texture of paint layers would show an opaque white background in erased areas instead of being fully transparent.

I updated 2025 to 2026, and it feels unusable compared to the 2025 version. When I load a painted model the texture loads piece by piece and the viewport feels sluggish and choppy. Does anyone else have this problem and is there anything that I can do about it? I have to use the 2025 version as it works smooth as butter.

Here https://d345hrihx5j0zk.cloudfront.net/3DCoatTextura-2025-17.exe

Change the method from line to object Hope this help