[3D-Coat 3.5 updates thread]

Downloaded 3.5.04. when opening the app, it says "3D-Coat cannot be opened because of a problem"

Process: 3D-Coat [1790]

Path: /Applications/3D-Coat-V3/3D-Coat.app/Contents/MacOS/3D-Coat

Identifier: com.yourcompany.3D-Coat

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: launchd [101]

Date/Time: 2010-11-03 18:30:15.638 +0100

OS Version: Mac OS X 10.6.4 (10F2090)

Report Version: 6

Interval Since Last Report: 943375 sec

Crashes Since Last Report: 20

Per-App Crashes Since Last Report: 1

Anonymous UUID: ...

Exception Type: EXC_BREAKPOINT (SIGTRAP)

Exception Codes: 0x0000000000000002, 0x0000000000000000

Crashed Thread: 0

Dyld Error Message:

Library not loaded: @executable_path/libtbb.dylib

Referenced from: /Applications/3D-Coat-V3/3D-Coat.app/Contents/MacOS/3D-Coat

Reason: image not found

Model: iMac11,3, BootROM IM112.0057.B00, 2 processors, Intel Core i5, 3.6 GHz, 12 GB, SMC 1.59f2

Graphics: ATI Radeon HD 5750, ATI Radeon HD 5750, PCIe, 1024 MB

[3d Coat Mac OSx Bugs]

Good points, xeen. Like you I also saw numerous small to medium issues in the Mac version, along with the showstopper memory leak I reported. But I don't think it's my job to list and document them all here, I payed to use it, not to beta test. Now as it seems, this is not only seen on my specific system, thus should have been found with proper testing and fixed before release. Unfortunatley I had a situation during the trial period that kept me from really using it and I jumped on the special price bait that was just about to expire. My first impression here was the developers would be listening and responding quickly unlike what you see with big companies and I liked the idea of supporting that. Right now I am not so sure if I made a good investment. It's been almost a week since I reported that major bug with no reply from any 'official' whatsoever. This is the right forum for reporting critical bugs, or isn't it?

[Mac OS X fatal memory leak when using clipboard]

Like I described, for me it doesn't matter if I load something in 3DC at all, i just need to start it, put an image into the clipboard, then switch between 3DC and other applications. It will crash eventually but before that, you can see in Activity Monitor that 3DC eats up more and more virtual memory at each switch and even when moving the mouse over other windows and back. When I copy some text instead of an image into the clipboard it stops, but the memory already taken won't get freed again.

[Mac OS X fatal memory leak when using clipboard]

I wonder where it goes from here. Will there be an 'official' acknowledgement of this bug? is there a bug tracker? I sure would like to know If I can expect to be able to use 3DC again soon or if i need to look for an alternative at this point.

[Mac OS X fatal memory leak when using clipboard]

Yes, 10.6.4. I corrected that, thanks for pointing that out.

I can positively confirm that it is NOT related to Preview at all. It clearly is the System Clipboard no matter what other program I use. Like I said, using Photoshop (CS5 Extended) gives the same effect as does copying a picture in Safari. I saw no point in testing any more applications and having to always reboot afterwards - it is ALWAYS 3DC gobbling up the memory while there's an image in the clipboard.

Needless to say that 3DC is certainly of no use for me with this showstopper bug, I just purchased it and was already recommending it to others but I cannot honestly do that anymore when I all I do with it is figuring out what's wrong instead of being productive. I've seen lots of minor and medium bugs already and now this huge roadblock. IMO with good will this could be labeled Beta-stage software - if this bug gets quickly fixed - which of course is what I rather would like to see than getting my money back because I love the ideas and still think there is huge potential in 3DC. I just wonder if the state I see is a problem predominantly with the Mac Version? I should have investigated more if there's even is a considerable amount of Mac users with 3DC here, as I've learned all too often that when small companies claim to provide Mac support, its only half-assed - I hope that's not the case with 3DC.

Regarding Preview: michalis, I never had or heard of any of the problems you describe with Preview and I can edit code fine with Text Edit - although there certainly are tools better suited for that.

[Mac OS X fatal memory leak when using clipboard]

BUILD: 3.5, also 3.5.03

OS: Mac OS X 10.6.4

Hardware: iMac 2010 3.6Ghz i5, 12GB, ATI Radeon HD 5750 1GB

BUG DESCRIPTION:

3DC eats up virtual memory fast when an image is in the clipboard, leading to unresponsiveness/crash

STEPS TO REPRODUCE:

1. Start 3DC, no need to open anything.

2. Open a big image (tested here with 1024x1024) in Preview or Photoshop, select all (CMD-A) and copy it into the clipboard (CMD-C).

3. Switch to 3DC.

4. Move the mouse over another application's window or the dock, then back to 3DC again and see 3DC's virtual memory rapidly increasing in Activity Monitor. Continue moving the mouse between 3DC and other application windows while it becomes more and more sluggish until it crashes or gives an out of memory error. Other applications are fine until too much of the memory is consumed and the whole system becomes unresponsive and needs restarting.

[Can the lights be independent from the camera?]

Thanks a lot Greg! Pity, but at least now I don't have to search for it anymore.

[Can the lights be independent from the camera?]

Hi all!

Just starting out and learning, so here's my probably basic Q: Is it possible to have the light(s) detached from the camera, i.e. fixed in the workspace relative to my model instead of moving with the camera? I need to bake the light/shadows into a texture and need to check it from different angles while tweaking the light without it ever changing on the model.