3DCoat 2024 development thread

[liok]

-I just checked and baking seems still to only work if we select the "Brush" tool (maybe otehrs too), but if a random tool is active/selected when baking, painting the cage bugs, like if the select tool is active, then painting the cage actually selects faces ect.. kinda like the bug where menus where "transparent" and clicking on a menu was actually clikcing on the mesh behind, cutting seams on it for example ect...

-Would be nice to be able to edit the cage before baking, it's theoretically possible by clicking "baking scan settings" but all the work done here (that can be done with symmetry which is important, unlike when baking as then it would bake with symmetry and break the created paint objects.) all this cage work seems to be deleted/reset once you click bake, and have the bake scan settings appear again, but without and the edit on the cage you just made.

[liok]

-yup another case of tool preset breaking when updating Coat, the alpha in this case is actually visible on the tool preset, but it's the default round alpha that is selected in Brush panel, and that is used in 3d, although the correct alphas that's visible in the tool preset is still there in Coat in a folder I made, Coat just lost the connection to it on the tool preset when updating it seems.

[liok]

-Something quite counter intuitive is that the Brush Option Panel, affects each Brush, so every time you change your alpha on a tool, it reset the whole Brush settings.
But the conventional approach would be that you set your tool, like Depth streght/modulator, jitter position/opacity ect.. and then you can select an alpha, or another one ect..
Like you do a skin Tool that jitters or paint a skin pore texture, and then you change to your 4-5 different skin pores alphas with this tool.
But currently if you click on another alpha it resets to default the whole Brush Option Panel.
Brushes should be nameds Alphas, because they are not Brushes like in photoshop (Brush= Alpha+tool settings in photoshop, here in Coat a brush is just an alpha, which is nice you can change alpha on the fly while keeping your tool)
Brush should not exist as a term in Coat, we should just have Tool (default), Tool Presets (the one you create with proper settings and alpha) and Alphas.
From my perspective anyway, it's just that I can't comfortably switch alpha as it resets the options.

 

[liok]

A very small issue, but when exporting object/textures, the file explorer for the object is all good, but the one for texture is a very slow/unpractical to navigate popup, instead of the windows file explorer where we can paste a directory address like for the object export path.

[rubeos]

On 4/4/2022 at 8:58 AM, rubeos said:

I use a stylus/tablet (bamboo tablet wacom) instead mouse.
Alt key is on keyboard.

In summary, when I activate the spline curves on the brushes, and sometimes even not, the zoom and pan/move in the space functions are blocked. I did other tests, with the Maya preset and 3DCoat everything works.

P.S. why is blender navigation objectively better, in my opinion? because center and right clicks are not used for navigation, an inconvenient thing to do on a pen (because it is not very natural to press those small keys on the pen with the thumb) and once you are used to it, navigation is much more fluid than other combinations....less click.

If it can be useful to anyone. I partially solved the problem by activating '' simultaneous '' in setup navigation for '' scale or move '' and '' move in screen space ''. But it is not the ultimate solution, however always better than before.
Strangely, sometimes the navigation returns to normal (changing brushes or tools), as if I hadn't activated '' simoultaneous ''.

[Frimasson]

The main bottleneck in 3d coat is the mesh import limitations.
I still can't import large meshes in ths sculpt room - more than 12 millions polys without having a out of memory error.
I've got 64 go of ram, and tried all the possible file formats  : Obj, Stl, Ply. I even tried to use the 3dcoat bridge in Blender to transfert my mesh, without success.

[Carlosan]

Have you tried importing using this command?

[Frimasson]

3 hours ago, Carlosan said:

Have you tried importing using this command?

It works with my 12 million poly mesh.
I still can't load a 70 millions poly mesh, but it's a good step forward

[allanmrtn]

Guys what do you all think of a checkbox option to auto-delete hidden mesh when Voxelize Hidden is performed? Should be fairly simple to introduce and would save so much time not having to keep going back to the original object and deleting the hidden geometry that now has been voxelized.

Edited April 9, 2022 by allanmrtn

[liok]

This would be nice as it happened to me quite often to break/corrupt my vox mesh because I forgot a part was hidden after doing a VoxHidden.

[rubeos]

9 hours ago, allanmrtn said:

Guys what do you all think of a checkbox option to auto-delete hidden mesh when Voxelize Hidden is performed? Should be fairly simple to introduce and would save so much time not having to keep going back to the original object and deleting the hidden geometry that now has been voxelized.

 

I agree, would be enough somewhere to be able to choose to set it as the default option.

 

I take this opportunity to add another request about voxelized hidden.
I don't know if there is a way to avoid it:

 

1-I create a cut with voxel hide.

2-I activate object-ify hidden volumes

3-the resulting voxel mesh has bevels, as seen in the second picture. I would like the edges to be sharp...and eventually add bevels after.

 

 

Before objectify

 

After objectify

 

 

I also add this thing that I don't know how to avoid: when I perform unhide, corner are always NOT ninety degrees, but they always have big bevels. How can I avoid this?

 

 

 

Last question about voxels:

1-use Voxel Hide

2- delete hidden volume

3- increase resolution of mesh

4- the mesh I had deleted reappear ...randomly, sometimes it happens and sometimes not.

 

 

 

 

 

 

 

[Koray]

rubeos;

- You need really high density meshes to make sharp hides and corners. It has always been like that.

- Delete hidden, increase mesh res and reappear has always been like that too. Best way to make sure that doesnt happen is to switch to surface and back.

 

Auto delete hidden vs checkboxes would really be great

[AbnRanger]

15 hours ago, allanmrtn said:

Guys what do you all think of a checkbox option to auto-delete hidden mesh when Voxelize Hidden is performed? Should be fairly simple to introduce and would save so much time not having to keep going back to the original object and deleting the hidden geometry that now has been voxelized.

That would be a good option to have, but in the mean time, you can assign a hotkey to that Menu option, to delete with a simple press of that hotkey

[rubeos]

6 hours ago, Koray said:

rubeos;

- You need really high density meshes to make sharp hides and corners. It has always been like that.

ah, ok, I thought it was some kind of bug or caused by my pc ... maybe it's an impassable mathematical limit (I mean objectify and unhide sharp edge). It would be nice to have the edges clean every time you use 'unhide' , even with only 2 res ++, like in the photos above.

Quote

- Delete hidden, increase mesh res and reappear has always been like that too. Best way to make sure that doesnt happen is to switch to surface and back.

I understand. I have done some more tests, and for now it works, but as soon as it doesn't work I will try to do as you said. This behavior seems random to me, now i can't reproduce the issue.

[Elemeno]

vox hide doesnt use alphas...

dont worry it is working 

Edited April 11, 2022 by Elemeno