ajz3d

And if you have a watertight object and you want to create an empty space inside it: Convert your object to voxels. Duplicate it. Right click on the duplicate in VoxTree and choose Extrude. Enter appropriate value to shrink it down. Subtract the duplicate from the original object. You can convert it to back to surface now. I'm not sure how the normals inside the object would look like though. They might need reversing. Example of an empty toroidal space inside a toroidal voxel volume:

There are at least two ways to do it: Select VoxLayer tool. Open e-panel by pressing 'E' key and pick rectangular lasso (or other selection mode you need). Make sure that Ignore Backfaces is turned off. Select an area of your object that you want to detach and thicken. In VoxLayer tool options set thickness by entering "-a" in layer offset and "a" in Thickness, where "a" is your actual thickness that you want to apply to your detached object. Hit Apply. A new object with thickness will be created as a child of the original one. Another way is to: Hide parts of your objects that you don't need. Geometry→Delete Hidden. Right click on your object and select Thicken. Positive values will give inward thickness.

Yeah, you're absolutely right. Andrew would have to intervene in this department.

Retopo mesh colour palette can be hacked with retopo.aco file put in the root of 3D Coat user config directory (%USERPROFILE%\Documents\3D-CoatV## on $hitdows). This file for example features much less saturated colours than the original ones: retopo.aco

@Imconected, I bet you chose Perform Retopology from the startup dialog window? The trick is to never use it and import your reference model directly into Sculpt Room without voxelization (well with or without, it's case-dependant). This way you not only can easily change shader of individual reference objects, but also hide different parts of it which is invaluable during retopo process.

Unfortunately I don't see much difference, if any. Brush tool (in normal or smoothing modes), Split Rings or Relax still keep snapping points to backfaces. That fix probably addressed display issues, not how snapping works.

Don, the problem is that some retopo tools, like Brush or Split Rings, when used to retopo a curved and very thin surfaces, have a tendency to snap points to backfaces no matter what snapping algorithm is currently selected. For example, in the attached scene I used Brush smoothing near the centre of the cloth. As a result most of the new points have snapped to the other side of the mesh, and it takes some time to move those points back in place. backface-point-snapping-example.7z

Good show! The following voxel commands do not work with multiselected objects: Res+, Smooth All. Sculpting on multiple objects works, but when the stroke leaves object A and picks up object B, this is treated as a separate Undo step. So as a result there are three undo steps at minimum: stroke on object A, pick up object B, stroke on object B, even though the stroke is continuous. Some other actions that would benefit from multi-selection, but don't work with it yet: convert selected objects to surface/voxels, toggle proxy mode, boolean operators, merging without booleans, flip X/Y/Z.

Michael, maybe try bringing up those issues on NVil forum. I'm sure they will be resolved very quickly.

@Michaelgdrs, have you looked in File->3D-Coat AppLink to see if 3D-Coat AppLink Enabled is enabled? Also, check paths in the AppLink Settings. Geo from NVil to 3D Coat exports fine, but the reverse operation is another matter.

@Andrew Shpagin Is the AppLink documentation up to date?

https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html

Some update: https://www.marketwatch.com/story/intel-ceo-sold-millions-in-stock-after-company-was-informed-of-vulnerability-before-disclosure-2018-01-03 https://spectreattack.com/

https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ Projected performance drop after the leak is patched is to be from 5% to 30%... What do you guys think about it?

Well yes Michael, Houdini Indie for instance. I didn't want to sound like Ebenezer Scrooge, but I couldn't stop myself from making this observation. Price aside, a couple months ago I went through Akeytsu's trial and I found the tools to be very neat and streamlined, so I fully understand why people like the program because the experience while rigging and animating in it felt kind of Zen-like. I do prefer a more technical approach though.

$179 for a rigging and animation package? Annually? I'm sorry, but I know of much more lucrative deals.

IMHO not possible right now. Please make a feature request on Mantis bug tracker: http://3dcoat.com/mantis/

I noticed that I cannot paint in the Texture UV Editor. Is this a known bug in 4.8.05? I cannot switch from Color preview to other channels either (in that very window). Wireframe preview doesn't work too.

You can store resample multiplier in a global variable which then you can use in a resample modal dialog callback. Last setting will be remembered until you close 3D Coat. You can bind a hotkey to any script that was ran at least once and exists on the recently run scripts list. Alternatively you can put it in any of 3DC menus with InstallToMenu function. See the scripting manual for more info.

GitHub is the new home of my tiny scripty-scripts. https://github.com/ajz3d/3dc-scripts Some scripts had to go, but some new were added in their place. Erm... at least one... for now... New ideas and contributions to existing scripts are welcome! //edit link to v2021 https://github.com/ajz3d/3dc-scripts/tree/3dc2021

0002331: Switching between presets using GeneralClay requires GeneralClay UI to be expanded!

Howdy! Has anyone recently switched from Windows to GNU/Linux (possibly Debian) and could describe his impressions about the difference in performance while working in 3D-Coat on those two operating systems?

It seems there's a problem with textures and noise put into alpha slots of Smart Materials. When material A is applied on paint layer and then alpha-masked material B is put over it (on the same layer) it will fully cover material A regardless of B's alpha settings. To reproduce: Create a paint layer. Fill the layer with material A (like copper) Fill the layer with alpha masked material B (like dust_1). Ignored slots: condition mask texture, edge scattering texture, mask/opacity texture. Can anyone confirm? Another one (probably related): Fill layer A with non-alpha material, like the copper. Fill layer B (above layer A) with alpha-enabled, like said dust_1. Merge Down Layer B with Layer A. Areas that were transparent in layer B will appear as pure white and opaque in the resulting layer C.