Forums

Hey, something is not right with update manager inside 3DC - I'm trying to "downgrade" to slightly older version, but whenever I'm clicking on update manager, either on start screen or top bar, 3DC is just closing and nothing happens.

I think the carving mode color grouping function is necessary. People need to relax by grouping different colors, so that they can easily obtain a hard surface and a smooth surface, but I haven't found the relevant function yet.

Rewritten UI in python sounds great, if it doesn't sacrifice performance (I personally don't think it will). When is the new UI rewrite rolling out? I have been sticking to 2024.27 because ever since 2024.32 the viewport gets laggy when I turn on VSync or limit 3dcoat's fps in any way (maybe something to do with the new shaders cuz I noticed some changes in unknownshaders.txt between versions)

Elemeno, you are working on Voxel mode... Mihu, try creating the low model on Modeling room, send it to Sculpt surface as multiresolution base mesh, bake and export   Or create Voxel mesh using Live Booleans

The dev team is afraid of this issue Thanks for point it up

Hello, I was using a very old version of 3DCoat on my laptop and noticed that in the viewport of the old version there is no added highlight on top of the shader/meshes. I attached the comparison between the latest 2025.01 version and the old v4 version, I wanted to ask if it's possible to emulate that old look because I think the shaders looks more clear without that blown out highlight I tried modifying the intensity of the environment light and contrast but I can't find a way to disable/modify the highlight. I exported the same clay material from the old version to the new one and the settings of the shader are the same, the difference is the highlight which I don't know how to control   I'm talking about the working sculpting viewport, I don't mean the render room. Is there a way to disable the highlight?   Thank you!

Nice...

Desktop 2025-04-25 23-56-02.mp4     some sort of strange resolution bug??  

Desktop 2025-04-25 23-56-02.mp4     well... lol i never use 3dcoat for sculpting anymore and this just reminded me why

I've tried brush alphas in different modes, stencils, even smart materials in depth only mode.

what are you using for noise? the noise tool or an alpha stamp?

That's not a voxel mode... I know the voxel/surface mode workflow, I'm using 3DC for quite some time... Yeah, then tell me how to add fine details, because no matter what, I'm getting this type of s****y result. With lower poly count, triangulation, weird artifacts or holes are even more visible or the details are blury, so... I rarely ask for advice,  usually I will figure out things on my own, but in this case, there's something weird going on.

Depends of model polygon resolution.

Are you using voxel mode ?  Try switching to surface mode Voxel is for rough sketching, surface is for fine details. And you don't need so high polycount to add fine surface details.

Quick question about fbx export - is high ram usage during fbx export normal or is this something 3DC specific? I mean, I've almost run out of memory while exporting my sculpt - I have 64GB and consumption during export was constantly over 50GB, 59 at peak... That's not a thing with obj, but then again, fbx is making some file compression if I remember corectly.

Here is an example - keep in mind that's only one part of the whole model, which is already over 100 million polys... This wheel, especially inner part(with cuts) is around 13 million polys. In this particular part, I wan't some metal surface noise, imperfections, pitting, etc. Now, there are also wood parts in this model and man, I've tried adding some wooden surface with 4096 x 4096 alphas and it's not very pretty. I really think, that I might end up somewhere in 200 million polys if I want to add decent detail to the whole model

Show the base model and any references that you like to achieve.

Hi, I've been looking for a way to add detail to my models for some time now and I have to admit that I'm having a lot of trouble figuring out the right way. I'm testing the alpha brush approach and the results are average... no matter how I set up Auto-Subdivide option, the number of polygons would grow to astronomical proportions, e.g. from 2 million to 13-16 million with a few brush strokes. The results varry but often the quality isn't good, with strange geometry, artifacts. Also, some brushes seems to add polygons even with the Auto-Subdivide option turned off. Stencils also end up with poor quality...mostly. I tested the approach with painting using Smart materials, with the option of depth only, no color, etc. The results are also rather average... you know, without really high amount of polygons you won't see miracles, but even meshes over 10 million look no so good, with jagged edges, etc. I'll just point out that I'm testing all of this on one element of a larger sculpture, so the final model would probably have hundreds of millions of polygons, which would be crazy... I only work with high poly models, I don't do retopo and UV's, so I'm looking for a way to reduce the number of polygons while maintaining detail, and at the moment I'm out of ideas. Do you guys have any tips on how to approach detail sculpting that I could try? What would be the correct approach?

I'll ask the developer if this is a bug.

Kaolin is an alternative word for bone china https://en.wikipedia.org/wiki/KaoliniteCustom sculpt for a sexy robot competition I recently took part in a competition to design a sexy robot. This was my entry made 85 percent in 3DCoat.  No i did not win anything, an off the shelf daz product won and the many hours I spent making this were not recognized.   So here she is to show off my hard work. Kaolin the bone china robot   The background scene is Bladerunner quadrant 4 by my friend 808state  

Thanks. I have since tried to run 3D Coat in Zorrin but have found there is a pile of files missing in zorrin that would have enabled 3D Coat to run and adding them would have cause problems. So in the end I flashed Pop os to a spare drive I had. Loaded everything fine from there.