Metromot

Shift Tool not working on Mac Hello, I have a problem with 3DCoat, think this is a bug.. The Shift (Layer) Tool in Paint Room is not doing anything for me in 3DCoat v.4.5 and above. Neither the Smudge, Pinch nor Expand Tool Options work, but the smoothing with <Shift> works. I reproduced like this: - (optionall) delete the ~/3D-CoatV45 folder to have a fresh start - open 3D-Coat 4.5.19(GL64) - import Model for PPP, load the sphere or anything else - paint a stroke with the brush with depth, diffuse and gloss - switch to Shift tool and draw across that stroke - nothing happens in V3.x and up to 4.1 the Shift tool works for me as expected. If you can not reproduce it, I will be glad to give you any more info you need. Unfortunately V4.1 does not seem to open files that were created with V4.5, is there any way to achieve that? Specs: iMac (27-inch, Mid 2010) 3.6 GHz / Intel Core i5 12 GB / ATI Radeon HD 5750 1024 MB OS X 10.10.5 (14F1021)

Great! can't wait to finally give it a go - Thanks for the info Andrew!

I apologize if anyone feels there is too much impatience about Mac/Linux versions being expressed here. I am confident Andrew does the right thing but the last time we heard about it was back in January and we are all anxious to see it.

Thats awesome! But wait, month after month goes by and still no Mac/Linux versions? We're starting to feel a little abandoned, just a teeny-weeny tiny little bit..

OK I installed a new OS on a wiped partition and added fresh installs of 3D coat B14A and 3.7.18F - the same problem: most of my .3b files would make 3d coat hang at load or give an out of memory error. After lots of fiddling, I found a strange thing: While using the 'Open' Menu command or CMD-o does not work, if that same file is in the 'Open Recent' menu and loaded from there, it works just fine ! Now I can edit the Options.xml file and put a filename in where the recent files are and then I can access it either from the menu or the panel at startup. Works for both versions I tested B14A and V3.7.18F.

Thanks AbnRanger. I deleted that whole folder (the Mac OS equivalent of it) already as mentioned. It might be something with the demo period/licensing mechanism and thus not easy to find and discuss here.... I will now try using a new clean system and see if that brings any clues and contact support/Andrew then.

I am not sure there is an offending file unless you mean a file somewhere in my system which by its mere presence causes a crash on any 3D coat version when opening ANY non-small .3d file and which I dont know where to find. I was working on several different files before it became apparent and It might as well have been just an action I performed. I don't remember and I cannot reproduce how the problem comes into existance because for that I'd have to get rid of it again in the first place. Again, is there anything being installed by 3D coat other than what I mentioned? How do I completely uninstall 3D Coat getting rid of ANYTHING that gets installed or altered?

I cannot tell because of cause and effect. I ran 14A when the problem started, as if it 'poisoned' my system. The effect of that 'poison' is, every version I run, at least back to V3 has those memory problem which I never had before. I can not remove the poison with a delete/reinstall of 3D-Coat and the mentioned files/folders. As long as my system has that condition and I can not get rid of it, I can not see if any other versions would introduce the same problem. Please tell me which files does 3D-COAT write or change, other than the ones mentioned. If I can delete/reverse all of 3D-Coats marks and changes, logic tells me that should get rid of the problem and I can switch to older versions and see if it happens again. Otherwise, the only thing I can now try is setting up a new OS on a clean disk and hopefully, I will be able to continue my work.

Hi. I'm having a very serious memory issue with 3d-Coat after using V4-BETA14A for a while on Mac OS X 10.8.3 with 12GB Ram. I can no longer open most of my .3b files bigger than about 10MB which all worked fine before. Even when I use V3 to open projects from last year, the program hangs forever, sometimes giving an "Out Of Memory" error before that. Activity Monitor shows that 3D-Coat uses less than 300-900 MB while it hangs and there are more than 8GB free. Everything else than 3D-Coat seems works fine. What I did so far without success: - Reboot, repair disks and permissions - Delete and reinstall the 3DCoat V4 application folder, trying out different of the latest versions (remember, even the V3 installation is affected) - Delete the 3D-Coat V3 and V4 folders in the home directory - Delete ~/Library/Preferences/pilgway.-D-Coat - Installi and run 3D-Coat with a different user account - Boot the System via Firewire on a different computer to eliminate hardware issues - uninstall the license key Sometimes after entering the registration code, it would again load a somewhat smaller .3b file fine, but after it hung on loading a bigger file, that same smaller file wouldn't load again. It seems as if 3DC is putting (or maintaining) something in the system that causes any version to consume too much memory afterwards. Did I miss anything to delete to completely de-install 3D-Coat or are there any other suggestions? This is leaving me unable to use 3D-Coat and continue important work, so any help is very much appreciated.

Wasn't there supposed to be Collada (.dae) export beta since 3.7.18? I can't see in the menus/file types shown in 3.7.18F and 4.00 B5 Mac Version. Beta tools is enabled in prefs. Is it somewhere hidden or is it not in the Mac build yet? @Candy-floss Kid: System requirements for 3.7 (stable) is stated on the download page as being OSX 10.4.5 minimum. But I would doubt that testing with all OSs up to 6 years old is a priority in beta development.

Not using a USB Drive here but an SATA SSD for everything... Looks like a memory leak to me - when and if it crashes probably depends on how much real and virtual memory is available.

I saw the same memory issue shortly after using 3.5.25 for the first time. But it was in Paint Mode here. It told me to save but when I clicked ok on the dialog-> boom. There were no problems before using the same .3b file in V. 3.5.24 -- OSX 10.6.8, 3.6 Ghz Core i5, 12GB

I tested again in 3.5.06 and it seems to be fixed - Thanks a lot Andrew

Still there in 3.5.05

BUILD: 3.5.04B OS: Mac OS X 10.6.4 Hardware: iMac 2010 3.6Ghz i5, 12GB, ATI Radeon HD 5750 1GB BUG DESCRIPTION: Some operations become increasingly/very slow when moving/rotating/scaling merged objects. STEPS TO REPRODUCE: - Start 3DC with per pixel painting, choose the tiled subdivided plane to start - File/Merge Object, choose TiledSubdividedPlane.obj to merge another into the scene - Switch to Sculpt Mode, click 'Select/Move', 'Select Objects' and click on the plane(s) to select one - Click 'Move' in the Tool Options and move the plane back and forth continuously At first, the plane moves fluidly, it 'sticks' to the cursor. Then within a few seconds it gets more and more disconnected, updating the position less than once a second which makes precise positioning quite impossible. Same thing with Rotate or Scale. Switching Modes (Paint, Sculpt,..) also becomes very slow. Now, if you save, quit and start 3DC again and re-open the same scene, the performance is fine again, but decreases just as fast when doing move/rotate/scale on the objects.

In Sculpt Mode and wherever it applies, it would be useful to have the option for moving/scaling and most of all rotating Objects by using numeric input and/or snapping to a grid. For instance to precisely rotate by 90 or 180 degrees. Or at least have a number display while doing it with the mouse. Perhaps there is a way to do that already?

I agree, the latest version is running well and I don't regret buying it. But please consider fixing the trial download version fast, this memory leak is nasty and will put off Mac customers.

Thats a great Idea, I second that. But please restrict people from posting there who can only contribute by saying 'Steve Job is evil, get a PC'

Wow you get your software updates instantly, I wish I could have that, lmfao...Ok this has become plainly ridiculous. I will stop it right here and say I loose and you win the platform war and hope you be happy. But stop accusing me of things I did not do and read what I said! I never insulted Andrew no matter how often you suggest that, I was supporting the notion that the Mac version needs more attention and now he's hired a dedicated mac guy which tells me I was right and Andrew agrees even if you may not like that and think this 'tiny fraction' gets more than they deserve. Then, if you personally feel being stepped on your toes by someone challenging your views, I stand guilty for that. But don't claim I stepped on Andrews or anyone else's toes here, unless you really need to expose how you're trying to separate and need others to back you up... But most of all I was NEVER throwing a fit here - But I am right now, thanks to you AGAIN falsely accusing me. Write it down if it helps: I reported the bug, just the facts, in the forum first of all, then emailed support - just the way you like it - then it got fixed and I said thanks to Andrew. Now please have a nice weekend.

same problem here V 3.5.04, IMac 2010 i5 3.6 GHz

Yes, I assume it was a windows majority being asked, including people like you who seem to have great fear that development for their systems might suffer when companies open up to other platforms. A quite shortsighted view IMO. Really no surprise. - Your reasoning sounds quite manipulative, like since there must be enough pollsters who have macs they must also have voted no for the most part - which makes no sense unless they hate using their Macs. Please don't project your views onto others. There ARE people different than you who make different choices and are happy with it. Well, I can imagine that lots of potential Mac users of 3DC are and have been discouraged from purchasing when they see how buggy the trial version is while it eats up all memory and finally crashes. Going so far that Andrew needs to offer refunds. Thats not a good recipe for a return of investment, talk about a chicken and egg problem. Now as soon as he learnt about it, he fixed the memory leak in no time and I'm sure the other issues won't take long to be resolved either with a little attention and less blaming of Steve Jobs. Sorry pal, you can rant all day if you want. Im not gonna spoil my mac with windows ever. I've always found a way to avoid that .. This defeats the whole point of having a Mac (or Linux) and ultimately leads to less software being cross-platform, which I'm sure you don't see a problem with. I know windows well enough and had to laugh out loud when I tried windows 7 lately and saw how pathetic microsoft again tries to mimic innovations we've had for ages in Mac OS. The PC owner was so proud showing me all the new stuff which he thought I'd never seen before. So funny (sad?), they always need to make it a little different, less obvious where they get their ideas from when it still is. But their solutions are and have always been delayed and second best, THATS your 'lagging behind' right there. No, I'm sure he didn't

Apology accepted. Seriously, what other outcome can there be from a poll among users of a program that only exists on Windows? If software development/evolution was being decided by such polls and nobody would ever challenge a Microsoft monoculture, you'd probably still run DOS

AbnRanger, you may have misquoted me, I did not blow up here. I was supporting the original poster in his view that the version of 3DC that he bought was not ready for use on his non-exotic hardware. He was overreacting? maybe, but while I fully believe that on your Windows machine or on other Mac configurations it's running awesome and Andrew fixes bugs fast when they get reported, what he (and I) payed for should not have been a release version in the first place. I still believe the Mac version needs work to be done, which should come first before adding new features. I also believe that thorough testing before release should be performed on ANY platform. - I see V. 3.5 has been out since 7 weeks now with the fatal clipboard memory leak which tells that relying on the forum members to report bugs is not sufficient . I did report it in the urgent bugs forum here almost 2 weeks ago, got it confirmed by other users but did not see any official acknowledgement for more than a week, then I sent an email to support and it was fixed today - fair enough. The fact that now there is a dedicated Mac guy is great news, TY Andrew. But still, new users will download the official 3.5 and not know what is happening when 3DC eats all the memory. Oh, and I do realize that the majority in this forum are Windows users, which may also be the reason why the Mac bugs are able to stay undetected for so long when the quality of the software depends so much on forum members finding problems. But 3DC is officially supported on Macs and sold for the same price. I did not read anywhere that the Mac or Linux versions should be expected to lag behind. There is all kinds of great and very complex Software for Macs that works as well or better than their Windows counterparts, so there is no reason to blame Steve Jobs (which I am NOT a fan of, neither Steve Ballmer, Bill Gates or [insert your favorite CEO here]), Macs in general or the 'Tiny Market Share' (which is above 10% in the US and steadily growing btw) for not testing enough. I take your opinion that Macs are 'ALWAYS lagging behind' as a typical preconception by someone that would never buy a Mac. P.S. I really don't want to see a childish platform war being started. Yours and geothefaust's remarks are not helping in letting Mac users feel welcome here who believe 3DC should get our support by buying it and pointing out where the problems lie. If you don't think that 3DC should be treated the same or cannot run equally well on all platforms because you didn't own a Mac since the 90's or they are lagging behind or for whatever reason, maybe ask Andrew to drop Mac and Linux support sooner rather than later. Otherwise, I don't think this is the place for side-blowing Mac users with those remarks.

I don't share your view. If you care more about adding features than about having a software that does not crash, there is something seriously wrong. I'm not sure which platform you use, but you probably need to try using 3DC on a Mac to make a statement about the original poster's point.

Andrew, I am sure you work a lot and I have respect for what you do. I can imagine the Windows and Linux versions are running fine and lots of users are very happy with it. But I have to say that I also was disappointed with the Mac version after starting some serious work. There are numerous small problems which can be forgiven like the progress bar not showing the progress or not appearing at all. But there are bigger bugs and very serious ones like crashes and memory leaks which is not acceptable for commercial software. I can't wait for todays release to see if I can actually start it now and use it without that memory leak bringing my whole system down, but it still looks like there is a lack of quality control at least for the Mac version and I would recommend you do more thorough testing and bug fixing before starting to implement new features again. It's a nice gesture to offer the money back but this almost looks like you are about to give up on the Mac version, I hope that's not the case... speaking for myself I would rather be able to use it and see a fix of the problems which I am sure is quite possible to do. After that we can talk about things like perhaps using the mac menu bar and GUI elements instead of having that tiny text that is hard to read on a high-rez monitor. Another thing would be using the proper folders like Preferences, Application Support and Documents instead of storing everything that changes during use inside the 3DC Application folder and losing it when you update (Why must the file selection always start in the 3DC Application folder instead of the last folder I used like any other Program does? - I never would want to save my work there!). In other words, have someone who is not just compiling 3DC on a Mac to make it somehow run, but someone who actually uses a Mac and cares about its conventions and standards.