Member Nisachar Posted August 14, 2019 Member Report Share Posted August 14, 2019 Hello used v 4.8 and now 4.9 3dcoat is highly unstable and just seems to take forever to do some tasks 7980xe 128 GB ram windows 10 pro titan RTX hardware shouldn’t be an issue Quote Link to comment Share on other sites More sharing options...
Reputable Contributor AbnRanger Posted August 14, 2019 Reputable Contributor Report Share Posted August 14, 2019 3 hours ago, Nisachar said: Hello used v 4.8 and now 4.9 3dcoat is highly unstable and just seems to take forever to do some tasks 7980xe 128 GB ram windows 10 pro titan RTX hardware shouldn’t be an issue Can you be more specific....maybe even do a screen recording. OBS is always a good free screen recorder. Upload it to Youtube (you can choose to make the upload PRIVATE, so only people with the link can see it). That will help us see what the root of the problem is. In the mean time, try to follow these steps to make sure they aren't causing the issues 1) Close the app > go to your DOCUMENTS/3DCOAT 4.9 directory and delete the OPTIONS.XML file. Once in a while, a crash or some other issue could corrupt that file and make 3DCoat exhibit bug-like behavior. 2) Install the latest version 4.9.05 (the SL version has Sculpt Layers which is still in a Beta State) 3) Install the latest drivers for your graphic card. A bad driver can cause lags and other strange behavior 4) Install the latest Wacom tablet drivers (assuming you have one). That too can cause lag or issues if the driver is bad or has gotten corrupted somehow. 5) Make sure the 3DCoat.exe file is added to your EXCEPTION list in your Anti-Virus and Firewall software. I've had my AV make 3DCoat unable to open once. I thought it was the application, but it turns out the AV was blocking it. Quote Link to comment Share on other sites More sharing options...
Member Nisachar Posted August 15, 2019 Author Member Report Share Posted August 15, 2019 Hello Thanks for the reply. I have all the latest drivers, 3dCoat version, windows updates installed. Most other softwares work fine. Please check the following https://www.dropbox.com/s/fd1qqzasglim3wz/3dcoat_Test01.gif?dl=0 Quote Link to comment Share on other sites More sharing options...
Member Nisachar Posted August 15, 2019 Author Member Report Share Posted August 15, 2019 Another Crash... Quote Link to comment Share on other sites More sharing options...
Carlosan Posted August 15, 2019 Report Share Posted August 15, 2019 Are you using default folder installation ? Please send crash report at support@3dcoat.com Quote Link to comment Share on other sites More sharing options...
Member Nisachar Posted August 15, 2019 Author Member Report Share Posted August 15, 2019 Hello Yes. all defaults. I have been sending it via the link generated after the crash report all this while. Thanks Quote Link to comment Share on other sites More sharing options...
Reputable Contributor AbnRanger Posted August 15, 2019 Reputable Contributor Report Share Posted August 15, 2019 Can you test on a sample object from the splash screen, to see if it still occurs. If not, that means the file you are working with is corrupted, somehow. You can send that to support through the HELP menu. Once it is uploaded, contact support@3dcoat.com and let them know you just sent it and what is happening in your scene when you experience these problems. Quote Link to comment Share on other sites More sharing options...
Reputable Contributor AbnRanger Posted August 15, 2019 Reputable Contributor Report Share Posted August 15, 2019 I think that mesh has issues and is the source of the problem. It appears to be super dense for one thing. Hard to tell the poly count because the gif was so low res and grainy. I couldn't make out any numbers in the UI. Possibly some self intersections and/or holes. That is why it's always best to test on a new scene with a sample object or newly created primitive. Another thing you can do when you run into problems with an object like that, is to basically "Dynamesh" it (3DCoat had this feature years before ZBrush) by hitting ENTER. That temporarily voxelizes the object > puts it back into Surface mode, with the polys all nice and even. Quote Link to comment Share on other sites More sharing options...
Member Nisachar Posted August 16, 2019 Author Member Report Share Posted August 16, 2019 (edited) Hello Both of the crash scenes were created out of primitives in 3D coat. The second post’s Geo had no holes. I had just switched to the UV window and it crashed. And these type of random crashes were occurring in 4.8 and now 4.9 as well. Edited August 16, 2019 by Nisachar Quote Link to comment Share on other sites More sharing options...
Reputable Contributor AbnRanger Posted August 19, 2019 Reputable Contributor Report Share Posted August 19, 2019 On 8/16/2019 at 5:45 AM, Nisachar said: Hello Both of the crash scenes were created out of primitives in 3D coat. The second post’s Geo had no holes. I had just switched to the UV window and it crashed. And these type of random crashes were occurring in 4.8 and now 4.9 as well. It doesn't matter what you originally created it with. From that GIF (we cannot see the polycount because it's too grainy/low res), it looks like a lot of LiveClay brushing was done, and that there is some self-intersections going on. Test on a new scene in order to determine if the mesh is the source of the problem. If it's still acting up, email support@3DCoat and send the work file through the HELP menu, so Andrew can take a look at it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.