V4.1 BETA (experimental 4.1.17D)

[Tser]

I'm running Linux 12.04 Ubuntu, using 3DCoat 4.0.03 non-cuda GL64 bit. So far I have not encountered the same problems as Tser's problem.

I have left the computer for several hours 3DC being left open and returned with no problems...

I always do manual saves not ever having used the auto-save feature.

This does not mean Tser does not have problems just reporting so far, I have not encountered them...

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.

[Creator]

Tser have you tried to chmod 777 3DCoat directory and your saved file? Just try, maybe it can help.

When I use ZBrush I am never confronted with these types of issues

But when you use zbrush under Linux, Wine is managing all file and system I/O, so it's not Zbrush advantage but Wines Try to run 3DCoat 32bit under Wine, it would be running OK in my opinion :P

[Tser]

Tser have you tried to chmod 777 3DCoat directory and your saved file? Just try, maybe it can help.

But when you use zbrush under Linux, Wine is managing all file and system I/O, so it's not Zbrush advantage but Wines Try to run 3DCoat 32bit under Wine, it would be running OK in my opinion :P

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.

[Creator]

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.

Yeah i know, i was just joking.

Have you tried this solution? http://blog.thecodingmachine.com/content/solving-too-many-open-files-exception-red5-or-any-other-application

Edited June 2, 2013 by Creator

[Tser]

Yeah i know, i was just joking.

Have you tried this solution? http://blog.thecodingmachine.com/content/solving-too-many-open-files-exception-red5-or-any-other-application

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.

[Tser]

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?

[Tser]

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.

[Tser]

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.

[pixo]

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.

I reported this problems, by e-mail.

If you let your 3DCoat open all night long the day after you won't be able to save your file.

Because you would reach the maximum number of opened file by the system ( you can change this number ).

Edited June 3, 2013 by pixo

[AbnRanger]

The V4 Manual is slow as frozen molasses, whenever I try to use it...the one from the HELP menu. Anyone else notice this? I mean it takes 20-30sec just to go from one page to the next. If I use the manual from the mainpage, it's ok. It's just the one that is accessed from the app, itself.

[philnolan3d]

Just came across a bug in 4.0.03, the red and blue light colors in the render room are reversed. Pick red, blue appears.

http://screencast.com/t/68lIzshP9l

I had no problem with the manual, Don. It's just a PDF document. Have you tried updating Acrobat?

[TimmyZDesign]

Version 4 is released. This thread should be closed now, and a Version 5 Beta thread should be started. All new Beta versions should be labeled Version 5 Beta.

[Taros]

As long as there is no Version 5 BETA announced this thread should be kept. Else you can and should ( ! ) post v4 bugs into the official bugtracking system, please.

A big wish for the upcoming version:

I suggest to differ between v4 and a new beta 5. We will get extreme problems to differ between the two versions when posting bugs. I know a lot of professionals among my collegues that never downloaded a v4 beta and waited for the offcial release. This was already a problem with v3.x. They saw the new functions but didn't wanted to update to a "unready version".

I think official updates for v4 bugs should to be annouced and published in individual v4 updates and not while any v5 betas only. This two versions should be seperated in my opinion. Better to have less but real v4 updates, than v5 open betas that gets side effects. I know that sometimes complete systems are overworked in upcoming versions and to support two different apps is not easy. Maybe Andrew has an idea to solve this problem.

Best wishes

Chris

[Carlosan]

Why we need to download a full version in every upgrade ?

Can be only a patch and nothing more ?

Or only to patch 3DC is a license security break issue ?

[PolyHertz]

Why assume it'll be going right into v5 beta? Wouldn't the next thread be for a v4.1 ?