Andrew Shpagin

3D-Coat 3.7 updates thread

1,787 posts in this topic

Testing Linux 64 bit non-cuda 3.7.01A OGL

Surface mode

Beta tools enabled with remove stretching selected

When using the curve tool with the default splnes, holes or missing pieces are produced in the spline meshes after applying for the boolean operation.

Clean surface produces an explosion of the splines that were boolean into the mesh. The above holes I would think causes the explosion

I can cause 3DCoat to crash in surface mode by the below method.

Start with a default sphere, work on it for awhile using surface and LC brushes.

Clear the mesh using the clear command

Add a sphere primitive in surface mode

Select the draw brush, start brushing

3DCoat crashes to the desktop.

Edit reported to mantis...

post-518-0-66010900-1321805521_thumb.jpg

Share this post


Link to post
Share on other sites

@Andrew,

and other friends

Merge a primitive, drop it to surf mode, decimate once, try to export object or scene under vox layers palette. This kills my OS. It takes 30 seconds, what GPU heating are we talking about? I can work under Voxels for hours at 10-20 M and no heating at all.

Simple as this! The system still works after 3dcoat hanging but I Can't force quit it!

Share this post


Link to post
Share on other sites

Does anyone else have this problem:

After working with 3DC for a while, no matter if you are in the Paint room painting, or Voxel room sculpting or even editing some UV's in the Retopo room, out of the blue comes a 2-3 second delay after every brush stroke? this has occurred for me in just about every version of 3DC. The only way to restore 3DC to remove the delay (remove the 2-3 second delay), is to either save your work and restart 3DC and reopen your work OR go over to the Voxel room and click on the "Toggle proxy mode" twice, then all is well with the world for a while then the delay occurs again and its off back to the "Toggle proxy mode" again.

I have reported this to mantis but nothing is done about it.

Running Linux x64.

PLEASE can anyone confirm this MOST annoying problem.

T.

Share this post


Link to post
Share on other sites

You are not alone my friend. I can confirmed this lag with the new version and the last few versions. It happens in voxel mode and well as the surface mode too. The way to fix it is the same too.

I have not posted a bug report to mantis yet. Just signed up about a week ago...

Linux 64 bit non cuda 3.7.01A

Windows 32 bit non cuda 3.7.01A

The problem occurs after working on a sculpt for awhile...

Share this post


Link to post
Share on other sites

Does anyone else have this problem:

After working with 3DC for a while, no matter if you are in the Paint room painting, or Voxel room sculpting or even editing some UV's in the Retopo room, out of the blue comes a 2-3 second delay after every brush stroke? this has occurred for me in just about every version of 3DC. The only way to restore 3DC to remove the delay (remove the 2-3 second delay), is to either save your work and restart 3DC and reopen your work OR go over to the Voxel room and click on the "Toggle proxy mode" twice, then all is well with the world for a while then the delay occurs again and its off back to the "Toggle proxy mode" again.

I have reported this to mantis but nothing is done about it.

Running Linux x64.

PLEASE can anyone confirm this MOST annoying problem.

T.

It is really strange. Is it dependent on stroke length? does it lag even with very light and short strokes?

Please look ap "Pointers" below screen. Please look if growing/decreasing of this parameter related to lags.

Share this post


Link to post
Share on other sites

long stroke, short stroke, light or heavy seems to make no difference. You will be sculpting just fine and then your next storke lags big time and keeps lagging. I have not posted to mantis as I am in the middle of sculpting when it happens and use the workaround so I can keep working. I had no concrete information I could give you for a mantis bug report.

I will make a test soon and watch closely for any telltale signs of when the problem starts occurring...

Share this post


Link to post
Share on other sites

Andrew, it happens after a while of working on an object, doesn't matter what you are doing and what brush you are using, I have on numerous occasions, been working on a project which has no lag after brushing a stroke, then gone away from my computer for maybe 1 hour, then when I get back to 3DC the lag is suddenly there after just performing 1 brush stroke. The question I would like answered is "why does toggling proxy mode on then off fix the problem"? Even when I have imported an obj mesh and I am working with it in the Paint room the delay after each stroke occurs, then a quick trip to the Voxel room to toggle proxy mode twice and its back to painting without any delay. I mean, what has the "Toggle proxy mode" got to do with an imported obj file in the Paint room, there is no voxel sculpt in the Voxel room at all!

T.

Share this post


Link to post
Share on other sites

I also can confirm the delay bug,I use Linux build(64 bit)more or less since a year and the bug was always there,in every version I have tried.

After you do strokes for sometimes(it depends on the number of the strokes I think)in voxel or surface mode(and even in paint room) the bug appears, toggle proxy(2 times) or restarting fixes it.

Share this post


Link to post
Share on other sites

I tested 3.7.01 Without CUDA, 32 bit on my laptop yesterday and what interesting is the Draw, Buildup and Expand which seemed very slow on another computer using CUDA worked ultra fast.

So i guess this means the CUDA version can cause problems with some tools and there is a difference between the 2 versions. I am now wondering if i should un-install it and use the Without CUDA version on my computer with a Nvidia GeForce 9600GT which has CUDA. Though i am also wondering if it's the card that is the issue because while it has CUDA, it was one of the earlier Nvidia products to have it so maybe it's not very compatible or something?

Share this post


Link to post
Share on other sites

Linux version 64 bit non-cuda 3.7.01A

Andrew, I sent a 3DCoat file via Media Fire to support(at)3DCoat.com that shows some of the artifact problems returning to voxel mode from surface mode that some users have mentioned. This is the current file I am working on. Details in the e-mail... I decided it just would be better to send the file instead of a bug report on mantis...

post-518-0-62599900-1321900440_thumb.jpg

Share this post


Link to post
Share on other sites

Andrew, it happens after a while of working on an object, doesn't matter what you are doing and what brush you are using, I have on numerous occasions, been working on a project which has no lag after brushing a stroke, then gone away from my computer for maybe 1 hour, then when I get back to 3DC the lag is suddenly there after just performing 1 brush stroke. The question I would like answered is "why does toggling proxy mode on then off fix the problem"? Even when I have imported an obj mesh and I am working with it in the Paint room the delay after each stroke occurs, then a quick trip to the Voxel room to toggle proxy mode twice and its back to painting without any delay. I mean, what has the "Toggle proxy mode" got to do with an imported obj file in the Paint room, there is no voxel sculpt in the Voxel room at all!

T.

Please check if just saving scene restes performance. If so the lag may be related to multithreaded files saving.

Share this post


Link to post
Share on other sites

Please check if just saving scene restes performance. If so the lag may be related to multithreaded files saving.

I'm not quite sure what you mean by the above statement. I do not have automatic saving enabled. I manually save all my files on a multithreaded computer. Are you saying the possible root cause of the lag is by saving a multithreaded file. I will test...

Share this post


Link to post
Share on other sites

I'm not quite sure what you mean by the above statement. I do not have automatic saving enabled. I manually save all my files on a multithreaded computer. Are you saying the possible root cause of the lag is by saving a multithreaded file. I will test...

I mean - if you experience lags what will happen if you will just save scene and continue to work? Will lags stop for sometime or nothing changes?

Share this post


Link to post
Share on other sites

I am still getting a few holes in the mesh at random times. They are small slice looking holes or the little black ones.

Version 3.7.01A Linux 64 bit non-cuda

beta tools enabled and remove stretching selected

I opened 3DCoat (not just a new scene)

Selected the default voxel sphere (appox 250,000 one)

Swtiched to surface mode, then used the move tool for a short while.

Next used the rapid2 brush and on the area shown it produce the small slice hole and black hole in the mesh.

Look in the upper right part of the mesh to see the small slice looking hole. This is similar to the ones I got on the file I sent you.

I was testing for lag but will start again on a fresh opening of 3DCoat, since I got the error stated above...

Question. When errors are random and not reproducible all the time should these be reported to Mantis?

post-518-0-27144000-1321979296_thumb.jpg

Share this post


Link to post
Share on other sites

After a save most of the time the lag is gone, but as the time pass it will become sluggish and saving will not solve the issue. Multithreaded save may be a possible cause but it's not the only one imho. With an intense use (lot of changes to model) over a few hours the reactivity slowly decrease. Also not sure if related but when save doesn't help much: cleanup memory and then after undo, sometimes bring back a bit of reactivity (not always though).

I can confirm that. Sometimes it seems random but the program will become sluggish after extended use. Closing and then reopening 3DCoat fixes the problem..

By the way, thanks for all your hard work on 3DCoat...

Share this post


Link to post
Share on other sites

Updated to 3.7.01B. Win+OSX+Linux. Changes:

- fixed crash mentioned by Michalis (export after reduce all)

- sphere tool with cubic interpolation fixed on transformed volumes

- fixed "Clear all" issue in surface mode

- multiselection in free form pose/primitives (but still without extra gizmo)

Share this post


Link to post
Share on other sites

No,saving doesn't avoid the delay,only toggle proxy and restarting(at least on my system),about this I'm sure.

About saving,on linux there is a problem(another kind of delay),that happens ONLY if you save the file on the host sub directories(windows) or on USB external drive.

In this case after the save you suddenly have a delay and slow down in performance,but if you save in your home sub directories no problem at all(apart the previous delay we are talking about)

Share this post


Link to post
Share on other sites

You are under Linux?

I'm talking about the Linux delay bug,it's a year I live with it,I think I know very well how and when it happens.

Share this post


Link to post
Share on other sites

No problem BeatKitano,I absolutely don't want to enter in a debate with you(sorry for sounding a bit harsh,it's my poor english),and I'm sure here everybody wants simply to help :)

Share this post


Link to post
Share on other sites

I do have one reproducible severe brush lag on the default voxel cube.This will be reported to mantis...

The picture here shows one cpu when lagging starts, going up to 83%. It hit 100% before being released.

The yellow cursor is left behind. The "crosshair" even though not captured in the screen cap is at the end of the stroke that is not produce yet because of the lag.

Linux version 3.7.01A 64bit non cuda

post-518-0-59483700-1321984152_thumb.jpg

Share this post


Link to post
Share on other sites
- fixed crash mentioned by Michalis (export after reduce all)

Confirmed. It has been fixed!

Thank you.

Share this post


Link to post
Share on other sites

Andrew, saving doesn't restore to "pre-lag" condition, once you get the 2-3 second lag after every brush stroke you either have to save and restart 3DC and reopen your work OR click twice on the "Toggle proxy mode" option in the Voxel room. It has nothing to do with the saving of your project, it has something to do with what "Toggle proxy mode" releases when it is toggled, its as if there is some kind of storage buffer which gets full and when its full you get the lag and toggling the "Toggle proxy mode" seems to clear this full buffer.

T.

Share this post


Link to post
Share on other sites

Linux 64 bit non cuda version 3.7.01A

Surface mode testing

So far I failed to find a solid reproducible way of causing the lag. It still happens but causing it to happen in a way that I can write down the steps to make it happen, no such luck so far.

I have found though that I can break apart the mesh by certain regular brush actions and cause what appear to be tiny overlaps in the polygon mesh, create tears in the mesh and sometimes black holes. What appears to be happening in the tiny overlaps is a vertex in the triangular mesh edge is not connecting to the edge it needs to or an extra edge has been created. The tiny possible overlaps cause artifacts in the voxel mesh when you press the enter key or go back to voxel mode. Some of the apparent overlaps are so small you would not see them unless you went hunting for them.

Check the wirefile picture (left side) to see the tiny overlap. The surface mesh picture (right side) shows what the surface artifact looks like before I hit the enter key. This is a really zoomed in view of the problem. It's late so I will make a bug report tommorrow...

post-518-0-39798700-1322033057_thumb.jpg

Share this post


Link to post
Share on other sites

The Hide tool does not seem to work correctly when masks are applied. If you brush it will remove the area as normal but you see a slight area of the mask with artifacts.

Before clicking -

post-1319-0-45020100-1322049940_thumb.pn

After clicking with the artifacts -

post-1319-0-09849400-1322049953_thumb.pn

Maybe it is due to it being the default resolution but it seems broken to me the way it has those contour which look like artifacts. It should probably also cut only certain parts but it seems to cut then draw a slight extrusion with the mask so i think this is probably a bug.

Edit - Yes this is definitely a bug, i just checked with a much higher res and when not masked it gives a regular high detail cut but it give the low quality contour style artifacts when masked .

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.