3DCoat 2025 Development

[Carlosan]

It is not a release, it is a BETA.

things not working as intended because we are migrating to Python (as you can read previously) to let the users create their own addons.

This is the function of the free beta release.

[Elemeno]

6 hours ago, Carlosan said:

It is not a release, it is a BETA.

things not working as intended because we are migrating to Python (as you can read previously) to let the users create their own addons.

This is the function of the free beta release.

oh ok, you means this? no worries i was just saying and nice! i didnt see the previous about python , other than allowing users to write their own addons , are there any other benefits of switching to python?

[wendallhitherd]

Hey there! Sorry if this is the wrong place, it is more of a general dev question: is it possible using the API to grab a render or screenshot, and the current view + camera data?
If it is possible I'd be happy to create a "grabdoc" like feature. I know there is grab depth along Z but I would like to grab a screen-space view of the current camera and use it as a stencil. Reasoning being: I am processing some scandata and I love how well 3DC handles the dense geometry with texture mapping baked into the voxels (yay!) but there is usually an empty side of the object. The easiest way to fill this empty side in is to switch to voxel mode, sculpt it a bit, and then stamp on a projection texture from a textured side of the model. I am also aware of the paint mode transform texture tool, which is very similar to what I'm wanting to do here, but it only works in paint mode and doesn't make a stencil. The functionality is less generically usable than a stencil because it's baked into the tool

as a sidebar, I love the effort being put into python lately because it allows me to smooth over my own art workflows from the difficulty of the UI similar to how toolkits like HOPSCutter for Blender are specific UI setups built around a specific thing you're doing. In that case, it's a scalpel for boolean hardsurface. I think exposing more python will allow the community to grow their own workflows that will take away a lot of the frustration.

For a feature like the grabdoc tool, I imagine I'd need api hooks to:

- get the viewport camera

- render out PBR maps from the viewport ( albedo, metallic, roughness ) to a textureset

- Reload those textures as a new stencil with full pbr maps

Edited April 27, 2025 by wendallhitherd

[Ctc_nick]

On 4/13/2025 at 7:38 AM, carrots said:

We haven't uploaded a version with these fixes yet.
Here is today's build, if you're interested, you can try it, but it could potentially have a lot of bugs since the interface has been completely rewritten in python
https://drive.google.com/file/d/1GyKa_GNaeN97igoWnI03ue8-MwRIPnhc/view?usp=sharing

Oh hey, I have overlooked that. That is great. I was surprised Maya uses an QT UI as well.

[Carlosan]

Please try this version

https://drive.google.com/file/d/10GmUvdth-CAJjhm2FuzWbt00Zw9KR7XV/view?usp=drivesdk

Remember to enable the Python Terminal extension in the Extensions window

[Elemeno]

BUG :

unlinking planes from retopo room into sculpt room, 

 

 

 

 

 

[carrots]

Version 2025.02
Latest build

https://drive.google.com/file/d/13OmytqD3C6xJ0mab0m1aHXtsPNVU6EUS/view?usp=sharing

- Fixed crash during automatic update
- Fixed problem of unnecessary ALT-rotation of the 3D-splines (used in pose/freeze)
- Automatically reload python modules when they change. You can enable this option in the extensions window for comfortable extension development without restarting 3DCoat
- Updated Python API
- Essential multiresolution improvement: Possibility to work with multiple objects simultaneously. All operations may apply to current object / selected / all visible objects. Also, retopo objects used as lowest multiresolution level should match the volume name to be able to manage multiple multiresolution objects in scene. It simplifies posing in big scenes very essentially.
- Faster rooms switching
- All scripts and commands converted to python
- Fixed Node Graph crash when shader debug mode is enabled
- Retopo/Modeling Room: Some tools ware polished.
- Retopo/Modeling Room: Smart Retopo - little Improvement.
- Fixed view modes for sculptured objects (smooth shade, relief only, flat shade, gloss only)
- Fixed node baking when using AO and curvature
- Once Ambient Occlusion is baked, it will automatically be assigned the Occlusion blend type.
- Fixed a bug where material previews were displayed black
- Automatic renaming of nodes with the same name.
- Fixed rendering of shader previews.

[Elemeno]

15 hours ago, carrots said:

Version 2025.02
Latest build

https://drive.google.com/file/d/13OmytqD3C6xJ0mab0m1aHXtsPNVU6EUS/view?usp=sharing

- Fixed crash during automatic update
- Fixed problem of unnecessary ALT-rotation of the 3D-splines (used in pose/freeze)
- Automatically reload python modules when they change. You can enable this option in the extensions window for comfortable extension development without restarting 3DCoat
- Updated Python API
- Essential multiresolution improvement: Possibility to work with multiple objects simultaneously. All operations may apply to current object / selected / all visible objects. Also, retopo objects used as lowest multiresolution level should match the volume name to be able to manage multiple multiresolution objects in scene. It simplifies posing in big scenes very essentially.
- Faster rooms switching
- All scripts and commands converted to python
- Fixed Node Graph crash when shader debug mode is enabled
- Retopo/Modeling Room: Some tools ware polished.
- Retopo/Modeling Room: Smart Retopo - little Improvement.
- Fixed view modes for sculptured objects (smooth shade, relief only, flat shade, gloss only)
- Fixed node baking when using AO and curvature
- Once Ambient Occlusion is baked, it will automatically be assigned the Occlusion blend type.
- Fixed a bug where material previews were displayed black
- Automatic renaming of nodes with the same name.
- Fixed rendering of shader previews.

is this how we update now or is auto updater being worked on?

[carrots]

22 minutes ago, Elemeno said:

is this how we update now or is auto updater being worked on?

It is planned that the auto updater will work.  

[Mihu83]

Version 2025.02 - something weird is going on with Retopo Room. At first, almost all tools were quite slow, with slight delay and now, when I switch to Retopo, it just freeze whole app.

[Dmitriy Nos]

15 hours ago, Mihu83 said:

something weird is going on with Retopo Room

Can you give more details about your workflow?

[Mihu83]

3 hours ago, Oleg Shapov said:

Can you give more details about your workflow?

Nothing special about my workflow, just switching to Retopo room and it either freeze immediately or when I choose Smart Retopo tool, etc... No idea what is going on.

EDIT:

Seems like one of the polygroups was messed up(don't know which one) - after deleting all groups, it started working normally.

2025-05-07 14-04-08.mkv

Edited May 7, 2025 by Mihu83

[GoG]

The new version is quite nice. Quite a few things run a lot faster than before, like switching between tools, multires, switching rooms, etc. It's nice to see python working well with 3DCoat.

I only had some problems:

- After multires operations (add levels, jumping between levels), the active object always switch back to the 1st layer in sculpt tree.

- Same viewport problem since 2024.32. If vsync is on or cpu/fps is limited some other way to make 3dcoat run at 60-80fps, the viewport feels like 30-40fps.

[Andrew Shpagin]

It will be today or tomorrow with auto - updater.

[GoG]

Does 3DCoat have launch parameters or something like a command line switch to specify data folder on startup?

It would be great for testing purpose, having multiple data folders for comparisons, or even using different data folders for each version.