AbnRanger

Send an email to Andrew (support@3dcoat.com) so he may ask follow up questions and such. I didn't notice any such lag on my system.

It remeshes so it might. Try POWERFUL SMOOTHING from either the SHIFT or SHIFT + CTRL list menu at the top of the UI. It pretty much remeshes beneath your brush while smoothing. It's really good for trouble spots.

Love all of those. Great work.

Because Voxels have no normals. They are volumetric cubes. Only Polygonal Surfaces (Surface Mode) have normals.

I think what happened is some people got in Andrew's ear and convinced him to create all these different offshoots of 3DCoat, without realizing each one would require it's own resources in training and support. So, it's safe to say that one needs to use the 3DCoat manual that applies to the Sculpt tools.

I think it's the Anti-Virus blocking access to certain 3DCoat files, because this happened to me a while back and seemed to cause the same behavior.

It's not crashing on my end, so it's something to do with your PC or Network, that is the source of the problem. Hopefully, Andrew will get back to you and see if the crash report gives some clues. If Windows uses it's own Anti-Virus (I think Windows 10 does have an Anti-Virus component), then that could be withholding access to certain necessary files. Storing your Documents directory on a separate drive from the Install (.exe) folder, could also be causing problems, because it doesn't know where to look for those files. I believe Andrew added an option, recently, that would make it easier to move the MyDocs/3DCoat 4.9 folder to another drive. It's in the EDIT Menu > RELOCATE 3DCOAT'S DATA

Instead of importing as a REFERENCE MESH (that's an old legacy option), import a high poly mesh into the Sculpt Workspace. You can do this from the Splash Screen. Choose Surface or Voxel Sculpting > click the Folder icon to import/open a file.

...also, update the drivers of any graphic card or wacom tablet you may be using. Drivers can sometimes cause this type of behavior in 3DCoat.

Add 3DCoat to your Anti-Virus exceptions list, too. That gave me problems at one point, and I thought surely it was a bug in 3DCoat. Turns out the Anti-Virus app was flagging it, without me realizing it at the time.

Exactly. Use Gravity in place of a Wind force vector...that or run such a simulation in your host 3D app, as most have some type of cloth simulation and different force vectors, like wind, that you could use.

...oh, and try the DX version, instead of the GL. I find it to be more stable than GL.

Is it crashing with one particular file, and not others? Sometimes there can be a problem with the mesh or UV's you don't see. The best way to eliminate that as a possibility is to test a scene from the Splash Screen. If it's still behaving the same way with one of those, then it's likely some kind of bug. However, sometimes it's a driver, either your graphics card or wacom tablet. Try closing the app > delete the OPTIONS.XML file from the "MyDocs/3DCoat 4.9" directory (as it can get corrupted once in a while and exhibit bug like behavior) > re-install the build > update your graphic card and wacom drivers, if they aren't already > Open the app and test a scene/model from the splash screen.

That will be cool whenever they get the GPU acceleration going. It doesn't appear all that impressive as a CPU-based render, but it's good to know they are working on a GPU engine for it.

Too late. He's had one of his developers working on it for a while. As has been mentioned in the post before yours, one of 3DCoat's biggest markets is Concept Art. Andrew can lock this market down with a great built in render. I agree about the prospects for other engines like ProRender, but from what I understand, that has been explored. A major limiting factor was using large models with millions of poly's + PBR shaders + Smart Materials, etc. 3DCoat can handle that much better internally, than exporting to a standalone render engine, like it has to with Renderman. That is why the Renderman integration, as nice as it is currently, is still very limited. I'm not sure, but I think the new render engine might be able to render in the viewports, which would be HUGE.