Andrew Shpagin

3D-Coat 3.7 updates thread

1,787 posts in this topic

Andrew, the delay 2-3 second delay (after each brush stroke), seems to occur after about the 200th brush stroke, I did a test with the default hi res sphere and mainly used the move tool and smooth, I counted every brush stroke I made. Using the latest 3.7.01B (CUDA)GL64) on Fedora core 14 (with all the updates), my system is 16core@2.3ghz AMD Opti, 32gb ram, mirrored 2TB drives, Quadro 4000, ASUS MoBo, system is rock solid and I also run Mudbox 2012 and ZBrush4 without any problems or delays.

By the way, I also had this exact same problem with my Intel 8core Xeon system, 16gb ram, Geforce 9800GT, also had FC14 and before that I had Centos 5.4 on it.

I hope you can sort this out soon as it is a MAJOR inconvenience when you are concentrating on the job at hand and you have to break concentration to Toggle the proxy mode.

T.

Share this post


Link to post
Share on other sites

WOW, something weird just happened, when I was in the delay after each stroke, I went into the settings and changed the no of cpu cores from the default to 16, then when I went to undo some brush strokes, the object just shot out some shards at right angles to the model. and evey click on the Edit on the menu bar caused more shards to emanate from my model, the model is pretty well stuffed now and there is no way to undo this craziness.

T

Share this post


Link to post
Share on other sites

The above craxiness only occurs when the Preference dialog box is open, when I closed it then I could undo all these shards emanating from my model.

T.

Share this post


Link to post
Share on other sites

Andrew, the delay 2-3 second delay (after each brush stroke), seems to occur after about the 200th brush stroke, I did a test with the default hi res sphere and mainly used the move tool and smooth, I counted every brush stroke I made. Using the latest 3.7.01B (CUDA)GL64) on Fedora core 14 (with all the updates), my system is 16core@2.3ghz AMD Opti, 32gb ram, mirrored 2TB drives, Quadro 4000, ASUS MoBo, system is rock solid and I also run Mudbox 2012 and ZBrush4 without any problems or delays.

By the way, I also had this exact same problem with my Intel 8core Xeon system, 16gb ram, Geforce 9800GT, also had FC14 and before that I had Centos 5.4 on it.

I hope you can sort this out soon as it is a MAJOR inconvenience when you are concentrating on the job at hand and you have to break concentration to Toggle the proxy mode.

T.

Tser,I'm not sure it happens at 200 strokes(I mean in general).

In my experience it depends on different things.

First of all,how high is resolution(for example with more resolution the delay happens before)

Second,how big is the radius of the brushes(big radius brush makes the delay happens faster)

For example,as I work it happens frequently that the bug starts on the move tool,which is a tool that in general I use with a radius bigger than other brushes.

Anyway,this bug isn't a surface mode/liveclay bug, it happens even on voxel mode.

Imo it must have something to do with the data structure used to store the points(to find the closest to the mouse pointer),maybe after the stroke the structure needs to be updated/recreated for next strokes, and here 3dcoat start to have problem.

Share this post


Link to post
Share on other sites

Yep, this bug happens throughout 3DC, but I just did a test to see how long it would take to occur, I started in the Voxel room, selected the hi rez primitive sphere and proceeded to use the move tool and also used the shift to smooth, it took about 200 actions with these two tools before the bug manifested itself. This just gives Andrew something to go by to sort this out, I hope this bug can be sorted out soon as it is VERY annoying. I would even suggest adding a button in each room, or on the tool bar, which automatically toggles the proxy mode for the short tern until Andrew fixes this. Also, I first discovered this bug when painting a model in the paint room many moons ago.

T.

Share this post


Link to post
Share on other sites

Hello!

I am using 3.7.01 Windows 64 bit with CUDA.

I really like the new:

remove stretching

live clay crease

Starting to love using surface mode!

However, I am also experiencing the slow down after using 3D-Coat for a while. Restarting fixes it, but restarting often is annoying.

Also noticed that if I export OBJ from Maya, import to 3D-Coat, edit as voxels, retopo, then export new OBJ, when import back to Maya OBJ position is slightly off (even though I chose "remember position" when I imported to 3D-Coat).

A bunch of bugs, but overall 3D-Coat is great, and it is getting better all the time!

Share this post


Link to post
Share on other sites

Yes, I can confirm that slowliness , it seems to be a bug in recent updates but don't worry, we'll hunt them down!

Share this post


Link to post
Share on other sites

This last build is pretty good. I'm having slow down when using LC for a while, and some strokes can be a little wonky. But other than that it's doing fine. I'm trying to figure out what is causing the wonkiness of some strokes compared to others, haven't nailed it down yet.

Thanks Andrew & Raul for your hard work! It is much appreciated. Please, don't let the negative or rude posters get you down! You're both doing a super awesome job. :drinks:

Share this post


Link to post
Share on other sites

Andrew, the delay 2-3 second delay (after each brush stroke), seems to occur after about the 200th brush stroke, I did a test with the default hi res sphere and mainly used the move tool and smooth, I counted every brush stroke I made. Using the latest 3.7.01B (CUDA)GL64) on Fedora core 14 (with all the updates), my system is 16core@2.3ghz AMD Opti, 32gb ram, mirrored 2TB drives, Quadro 4000, ASUS MoBo, system is rock solid and I also run Mudbox 2012 and ZBrush4 without any problems or delays.

By the way, I also had this exact same problem with my Intel 8core Xeon system, 16gb ram, Geforce 9800GT, also had FC14 and before that I had Centos 5.4 on it.

I hope you can sort this out soon as it is a MAJOR inconvenience when you are concentrating on the job at hand and you have to break concentration to Toggle the proxy mode.

T.

One question:

Let's say you are doing something in voxels and lags start. Try to add a new volume with something simple like sphere and cache it. Continue to work over main scene. Will lags stop temporary? If no, try uncache. Are they gone after uncaching? Are they gone after caching/uncaching an empty volume?

Share this post


Link to post
Share on other sites

In any case, beta tools are ... beta, disable them and have a stable 3dc. Am I right? No delays then?

Testing the last mac build, I was working ~2 hours in LC mode, remove stretching etc, no delays though.

I also merged ~1M objs without voxelizing, surf-LC mode. Works fine and fast. Up to millions faces.

Will be possible in the future to directly paint in surf-sculpting mode? MVertex or zbrush similar? Without using UV maps?

Share this post


Link to post
Share on other sites

Hi there, I've had a try at V3.7.01A DX64 with CUDA

and I still have an issue in voxel room.

It is impossible for me to create any primitive voxel shape.

When I open an old file done with 3.5, I can see the voxel sculpt

but trying to add a primitive sphere on it will just open

a big hole in the middle of it.

"stuck in the middle with you"....

What shall I do? Please I wanna start a new sculpt now!!! :)

Share this post


Link to post
Share on other sites

Hi BeatKitano!

Just realized that the Marmoset toolbag 1.05 install I dowloaded today was roten too.

It is probably a virus scan problem. I'm gonna try to download V3.7.01A once more.

If the problem remain I'll try the surface mode way.

If it works all right I'll post once more today.

It is weird, because I had the 140M dowloaded, and managed to launch 3dCoat.

Thank you for your help.

Share this post


Link to post
Share on other sites

BeatKitano,

You are my hero!

It was, just like you told me, a graphic driver problem.

Sorry to frighten everyone with a new weird bug.

Wasn't a bug, probably.

Really happy to get the problem solved. :yahoo:

Time to go to bed. work awaits in 5 hours.

Share this post


Link to post
Share on other sites

To PC users, from a mac user, (also former pc user and maybe in the future again).

Did you, just saying, did you change the plugs of all possible USB devices, meanwhile? Especially the wacom plug?

What this has to do with GPU drivers? All these are basically serial connections. I have some bad feeling about these. Under any OS.

Share this post


Link to post
Share on other sites

Version 3.7.01B 32 bit non-cuda. The problem also effects the Linux 64 bit non cuda version.

The copy tool is not respecting symmetry completely. Reported to Manits.

It appears that "Translate brush along curve" is broken again in newest beta. It does not apply the spline you selected. It just produces a small line hump.

The problem was reported fixed a few versions back. Could someone test and confirm this. Thanks...

post-518-0-77530900-1322238126_thumb.jpg

Share this post


Link to post
Share on other sites

Will be possible in the future to directly paint in surf-sculpting mode? MVertex or zbrush similar? Without using UV maps?

To answer this question, Andrew said this was a feature slated for 4.0, so most likely we will be beta testing it before 4 launches.

Share this post


Link to post
Share on other sites

Andrew, I'm not sure what you mean by cache, but I performed just over 200 brush moves and the 2 and a bit second delay occurred, I then created another volume in the root, added a primitive sphere, then went back to the original volume to work on my object and the delay period had doubled, from its 2 second before adding the new volume and sphere to 4 seconds delay now.

T.

Share this post


Link to post
Share on other sites

Tser: Caching your voxel mesh is hitting the hard drive icon on VoxTree layer, it's also used for multires.

Share this post


Link to post
Share on other sites
I'm not sure we're understanding each other properly Michalis: were you asking the relation between usb/gpu driver ?

I said that because my driver got corrupt at some point without doing a hot-unplug on a removable disk (which could lead to driver corruption on windows in certain special cases).

Windows reassign drivers for every plug, so have a look at device manager. No matter if we understood each other. It's about OSs and how these understand us. LOL

I didn't mean a hot unplug case.

Share this post


Link to post
Share on other sites

Andrew, I did what you said and yes the lag disappeared after caching the sphere.

T.

Share this post


Link to post
Share on other sites

If I cache a voxel object and restore it, it comes back voxel. If I cache it and edit it and restore it, it comes back surface mode.. Is this expected behaviour?

Share this post


Link to post
Share on other sites

I also can confirm,caching a sphere and after working again over the volume that previously had lag makes this lag ends,but....after more or less the same amount of time(better to say the same amount of strokes)it happens again.

Uncaching the sphere on the other layer makes the lag ends again.

Share this post


Link to post
Share on other sites

Andrew, I did what you said and yes the lag disappeared after caching the sphere.

T.

Thanks! Now I am trying to do changes to prevent the problem. But it is done in a bit "blind" mode.

Try to disable "Preferences->UseMulticoreForSaving". Will it help to prevent lags?

Share this post


Link to post
Share on other sites

Andrew, I disabled "Preferences->UseMulticoreForSaving" and it did not prevent the lag or remove the lag once it occurred.

T.

Share this post


Link to post
Share on other sites

Thanks! Now I am trying to do changes to prevent the problem. But it is done in a bit "blind" mode.

Try to disable "Preferences->UseMulticoreForSaving". Will it help to prevent lags?

On my old Window's XP 32 bit computer which is a single core, The lag is present.

No multicoreforsaving was ever involved and the lag still happen though.

I have noticed that sometimes (random) when you run clean surface you will start lagging at the end of the brush stroke.

Lag was still present even before the clean surface tool was added...

This is one tough bug to find>>> :blink:

Andrew and Raul, Thanks for all the improvements in 3DCoat in the last year. There is so much more I can do... Good luck on hunting those evil bugs... :angry:

Share this post


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