oah1981

Quick update on my earlier blend layer post - it turns out the problem is only when I am painting on an object directly on top of a shader - like a skin shader or default clay. If I create a new layer, fill it with colour, the layers above it blend fine. This is on both Mac and Windows.

Hi In 2021.22 the blend options do not work - I do have a video, but I am at the maximum upload limit for posts. Modulate and multiply cause the layer to vanish (to be clear the layer does not vanish - the mode makes the contents of the layer vanish as if fully transparent), the other blend modes just act as standard blend. Thanks

Hi @Andrew Shpagin, I can confirm that 2021.21 has solved the voxel mode issues for me, many thanks!

Hi @Andrew Shpagin I tested 2021.20 this morning and voxel brush mode is much smoother for the voxel brushes - the performance issues have gone i.e. 4mn triangles is no longer an issue - but the base brush tool still has the performance issues and the mesh still disappears after you finish a stroke and try to a make a new one (as per the videos I sent previously). Although performance has improved for the voxel brushes, strange things still happen more often than not when stroking - as per the video below. Cuda was off below, but same issue if cuda is on. Also, the fall-off setting for brushes no longer has any impact. Thanks, Oli 3Dcoat 2021.20 2021-08-04 06-59-00-1.m4v

Hi. Since a sculpt layer seems to be destroyed if you bake onto it, or even fill it with the paint bucket tool, could it be possible to add a warning before changing the sculpt layer with a non sculpt action? Or automatically colour code a layer with a sculpt data to make it clearer? Thanks

Hi @Andrew Shpaginbase brush is still causing issues in the latest build and the same problem with some other voxel brushes like 2d paint. The object disappears in viewport, terrible performance and then can be brought back into the scene via increasing the resolution of the object. Voxels are unusable on my machine at the moment. Thanks

Yes, it is slower for me as well, decimation too. On the decimation point, with auto retopo it would save so much time if the decimation result of the process is stored and can be reused if there is no change to the sculpt. If I tweak an auto retopo to get a better result, it is so slow to repeat the decimation again and again. It is slower than 4.9.72.

In general, sculpt mode performance - regardless of cuda or not - is so much better than voxel. Cuda does make it worse however. On my system, 25mn triangles is no problem is sculpt mode, extremely smooth, but 4mn in voxels is really sluggish and not smooth at all. FPS is over 250 on voxel mode, it just is very jerky.

@Andrew Shpagin I have discovered that if you click to increase the resolution of the sculpt layer, the missing object comes back - with more voxels - but then disappears again when you sculpt again. You can keep doing this again and again, with performance decreasing each time (even with quite low triangle counts). I am at my attachment limit, but I have a video to show you the behaviour. Thanks for all the hard work.

Hi I have now tried with cuda off, but the issue is still there I am afraid - I have two recordings attached. One showing the error that the object disappears, the other showing that once a voxel object disappears you can no longer add one from the primative tool. Thanks, Oli 3DCoat 2021.12[floating, used 3 of 10] 2021-07-26 18-45-03.mp4 3DCoat 2021.12[floating, used 3 of 10] 2021-07-26 18-43-57.mp4

I have now tried version 2021.12 - the system no longer crashes, but the object just vanishes. Deletes when I use base clay. No warning, it just deletes. The triangle count goes to zero

Hi Here is my windows build version - 10.0.19042 Build 19042, I believe it is upto date. The only change to my system (that I am aware of) has been the installation of the latest game ready drivers from Nvidia. BUT.. I've gone back over older versions and it is now crashing with earlier builds. 2021.6 manages to generate a crash report however, I have copied the text and added it to an attachement in this post. Thanks crash.txt

Hi, the latest version (11) crashes almost immediately now in voxel mode - I have uploaded movie to show the issue. Add a primitive use a brush, the screen freezes and does not recover or simply crashes, as per video. This hasnt happened in earlier releases including the beta. Surface mode works fine BUT If I then change to voxel mode, it works for a second or two and then crashes. No crash report appears, it just coses. Thanks 20210725_184600000_iOS.MOV

@Andrew Shpagin i've just tried build 02 and the problem is no longer there, I can now add models to the retopo and modelling rooms. Many thanks, oli

@Andrew Shpagin hi Andrew, tried fresh install of 3d coat, restarted machine, I still cannot add a primative to the modelling or retopo rooms, only in the sculpt room. But my occlusion baking issue is solved by @Yousung - if I hide the sculpt room objects in the sculpt room, then calculate occlusion, it bakes fine and there is no longer any crashing - but to confirm, hide voxels in paint room has no impact on the issue. The object must be hidden in the sculpt room to stop the error and crashing. Same when baking lights. thanks

@Andrew Shpagin hi, yes, I press apply but nothing is added, zero polygon count, just greyed out primative

@Andrew Shpagin sorry, I should have been clearer, I installed the license and restarted, but the same issue.

@Andrew Shpagin thank you for your reply, but using the licence on the first page still does not work and I have never seen any warnings in the program around limited mesh capabilities in learning mode.

Just following up on my last post, if I click add new primative, nothing is added and the object is greyed out. fine in sculpt room

Two strange issues with the latest release, I can no logner add primatives to the retopo or modelling rooms - only in the sculpt room. I did not have this issue with the betas. And now also strange paint objects created more often then not when I bake from retopo room - two screen shots below, one showing the retopo object and one in the paint room after baking. Also if export retopo objects to blender, I have the same issue, large part of the mesh are missing. I have tried going into the modelling room and welding the verticies, but same issue. Thanks Oli

@Carlosan thanks for your reply, but I have tried with and without voxels in the paint room, same issue either way. Calculate occulsion crashes the machine most times too. Oddly, in the 2021 none RC release I can no longer add primatives to the retopo room or modelling room (only in sculpt room), so I tried a simple model from blender and that worked fine. It seems to be an issue with meshes created in 3dCoat. All maps bake fine except for bake lighting which does not work and crashes as well.

Congratulations on the release, but occlusion still does not calculate properly for me - it is unusable. I did not have this issue with 4.9. I have a screenshot showing the issue, similar to other posts - no matter what model I am using I have the problem. I have included the .3b file incase I am doing something obviously wrong... test.3b

Hi In the release candidate, I still have the ambient occlusion problems raised by @Yousung but normal maps and curvature bake fine (as per other beta versions). The ambient occlusion bakes as a black mess. In RC1, there is a new bug when baking the mesh - inner preview no longer works, the mesh does not change shape unless at an extreme figure - over a depth of 70 for me. Outer mesh preview works fine. Thanks Oli

I have this same problem too now in the beta. I used to get a similar problem in the earlier builds of 4.x, but I haven't had an in issue for quite a few releases. I didn't see this before the latest beta build.

Hi very odd anomolies when using the grow vox brush holes in B47!