Tser

BUG: I have found that 3DCoat continuously opens files (ports) but doesn't close them as stated a few posts ago, it seems that 3DCoats limit before you get the "Too many files open" dialog when you try to save is just over 1000 (1028), I reached this limit by just leaving 3DCoat open over night. Please, Andrew or Sergyi, can you fix this, without this being fixed there is NO way I can use your program. T.

Edit: (I have 500 open now). Apparently 3DCoat is continuosly, opening a port (socket), then trying to read from it which it doesn't have permission to do, then instead of closing the port, it opens another port and tries to read from that, and so the cycle continues until 3DCoat has so many files (Ports, sockets) open that it reaches its limit so you cannot save or even read from a file. T.

OK, 3DCoat had 83 files open, I went away from my system for exactly 1 hr and now 3DCoat has 208 files open, so what is going on? T.

One thing I have noticed already is that the number of files opened by 3DCoat is steadily increasing, even though I am not using it, it is just siting there in the background, surely this cannot be normal?

Well, the max number of file descriptors for my system is 4912960, so I don't think this is the problem, since the default number for Ubuntu is 294180,. At the moment I am running 3DCoat and in a terminal, running the command "lsof -p 6396 |wc -l" (6396 is the 3DCoat PID) every so often to see how many opened files 3DCoat reaches before it throws the "Too many files open" error. T.

There is nothing wrong with the permissions of my directories and running 3DCoat under wine would defeat the purpose of using 3DCoat, the only reason I use 3DCoat is because it is a native Linux application, if I was using Windows or OSX I wouldn't bother with 3DCoat due to its issues, I would stick with ZBrush. T.

I'm running Fedora core 18 with all the latest updates and drivers, My system is dual Xeon, 48GB ram, Quadro 4000 (2GB ram), the first time I encountered this problem with not being able to save I didn't have the auto save on, the second time I had auto save enabled, I also do manual saves and incremental saves, just out of the blue comes this problem with not being able to save, too many open files issue, I cannot believe that its just happening to me or its some unique hardware setup I have, my system is a top end graphics machine specifically designed for this sort of work, Fedora is the standard to which all Linux distributions are modelled. I just get the feeling that either the 3DCoat Linux user base is extremely small or the use of the Linux version of 3DCoat by people is extremely limited. There has never been a time which I have used 3DCoat on a job which I didn't have some kind of annoyingly frustrating problem which should have been picked up long before I ever touched the program. When I use ZBrush I am never confronted with these types of issues, I get in, do my work which may last a week and then get out. T.

Hi there Sergyi, I don't have this OGL problem with any other application which uses OGL, I don't have any problem with the Linux X display and I am not using the Cuda version of 3DCoat, I run my system 24/7 and never restart it unless an update asks for a restart. My new issue with the latest STABLE V4.0.03 of 3DCoat is that after using the program for a while, then taking a break for an hour or so, when returning to the program to do further work, I find that the program cannot save to the hard drive and on trying, gives a pop up dialog "Could not read the contents of xxxxx Too many open files" of course the xxxxx is the name of the folder that I am saving to, whats this all about, its as if 3DCoat cannot access my file system. All you can do after this happens is to restart 3DCoat and load a previously saved scene. I find it very frustrating working like this and will use ZBrush 4R5 (under wine in Linux) until you resolve this issue. T.

Is there a newer 4.0.03 ?

The thing that really tees me off is that when this happens it prevents you from saving your work, 3DCoat throws up a dialog stating that it could not read the contents of the folder - too many open files, so you have to restart and try to recover from a previous save. T.

Great, thanks Andrew. T.

There is definitely something wrong with the undo, after working on a model for a while the undo doesn't work any more, and the smooth brush doesn't smooth!!! And when this happens I get a pop up "File write error!" Unable to write file; This is from the auto save.... Sergyi, I could do with your help on this one...

Problem: 3DCoat V4.0.03 Linux (GL64) After Retopoing in the retopo room for a few hours, I clicked on the Commands>Clear by accident, but when I tried to undo (Ctrl+z or Edit>Undo) nothing happened, it would not undo, I then went to the preferences dialog and enabled auto save, as it was turned off, then saved the preferences, then all hell broke out with the UI with square blocks of colour randomly on the interface and total inability to do anything, I had to restart 3DCoat.

Refinement of existing features, not new features, meaning polishing and stabilizing existing features...

I REALLY hope you are kidding, I just want stability and refinement of the features which are already there...

Which one is newer, the RC01 or the version from the download page (4.0.03)? T.

Has the access to the license server changed? in RC01 T.

Thanks for pointing that out Abn, I wasn't aware of this. T.

3DCoat really needs a drag rectangle brush with orientation, so you can easily project an alpha on the surface, rotate it, scale it, then let it go to create either displacements or painted details or both at once, the alpha mask currently in 3DCoat is very clumsy and difficult to get consistent results.

The way I have been working in 3DCoat is to create a high detailed model, retopo it, create UV's for it, merge to scene then paint it, then export the retopo mesh with the displacement and Colour maps, where as in ZBrush I work the other way around, I start with a low rez UVed model created in Softimage, import it into ZBrush where I step up the subdivision levels, refine the details and sculpt until I'm satisfied, then paint, when finished, I use Multimapper to generate the displacement, colour and cavity maps and sub displacement level obj I need which also exports the lot and at any time I can easily go back to any of the displacement levels of the poly mesh and make any changes needed in a few mins, then export again at any time, this is not so easy with 3DCoat. T.

I do lots of Polypainting in ZBrush and I use the Layers to create multiple layers of polypaint which I can easily blend together at any transparency amount for each level, then when I am satisfied, I bake them all down, the only thing I can't do is use different blending types like multiply, subtract etc, but I never really need those anyway. T.

I used to love Deep Paint 3D T.

I don't know if this is related, but I did notice that ONLY 3dcoat (in Linux), caused instability with the OGL drivers and also caused my video card fan to step up in rpm. It also, at one point, caused one of my cpu cores to go up to 100%, even though I wasn't doing anything in 3dcoat. So I would say that 3dcoat definitely stresses your system and if you have any weak points, then they may fail. An audio sound emanating from your motherboard indicates that a component has failed, but it may be failing due to excessive heat, try adding extra cooling fans in your case, near your gpu and memory, to see if that works. T.

My preference is stability through reducing bugs first priority, UI doesn't matter, Renderer doesn't matter, more shaders/Materials don't matter. The Tools/Methods should work as described each and every time they are used, no exception. If a new tool or method is introduced it MUST be called a beta and labelled as such and don't remove the old method/tool until the new method/tool is completely bug free. 3DCoat development should be frozen and be thoroughly tested by as many users as possible for stability and bugs, as soon as all the bugs have been squashed the further development can continue, as long as new tools/methods are labelled BETA. In this way you can market 3DCoat as stable with the user knowing that a particular tool/method is a new developmental beta, but the other (non beta) tools are rock solid. Using this development method, users can use 3DCoat in a production setting, even though its the latest version, knowing that the beta parts of the application are well named and described. T.