ifxs

I too wonder this? CUDA support on OSX would really be great!

+1 to the question from 3DArtist. The ability to export vCols from 3DC into Blender, this would be great to have :-)!! @Haikalle, this is such a great script, thank you for your work on it :-)!

v3.7 is a VERY worthwhile milestone for 3DCoat. Thank you Pilgway, you've made a massive amount of progress in relatively little time, and it definitely shows with 3DC 3.7! 3DC is beginning to show signs of a maturing & cohesive interface, on top of the now very robust toolset. The feature-set of 3DC is very impressive, and getting better by the week; with an intelligent & cohesive interface now taking form, I'm excited to see the direction 3DC will take as it heads to v4. We went from not being able to use 3DC in our pipelines a few sub-versions back, to now using it on a very regular basis, thats a mark of true progress(from the perspective of our team :-). The stability gained in the recent 64bit OSX release is also a very welcome addition. Thank you all again :-)

@Haikalle, thank you for the update to Applink :-)!!! such a useful tool/script. I very much appreciate your hard work!

thanks for the hard work and updates Haikalle ! :-) a valuable addition to any blender/3dcoat pipeline

New 64bit OSX build!! Thank you Andrew & Sergyi

this is an issue that is quite bothersome, time after time, losing the autopo mask each time i save my file. is there a way to prevent this, or BETTER YET, save an autopo density mask?

cant wait to test out the new 3.5.23 beta release on OSX, I've been enjoying the 3.5..21 beta 64bit release for a while now, its been great overall, compared to the previous 32bit release. Thanks Andrew & Sergey & team!

a bunch of welcome additions, thanks Andrew! Lookin forward to the OSX build

the opposite happened for me. Before the 64-bit build I ALWAYS had a modifier key locked down in 3DC only, and now, with the 64-bit beta, that has been remedied. Sounds like an underlying issue in 3DC. I couldnt even use it before the fix that occurred in the 64-bit builds. OSX 10.6.8

@Michalis, for that issue, I've had to use the triangle edgeFlow tool in MeshMixer(such a useful tool). The ability to retain shape/volume, while arranging edgeloops on a tri-based mesh has allow for good bakes, for me anyway.... any also allowed for a much easier merging of tri's to quads when needed. ITs not a great solution, but it works for me often when I have the tri-based baking issues.

Thanks for the new build Andrew and Sergey! :-)

has anyone heard anything on the new 64bit osx build?

thanks for the update Andrew, and thank you, as always, for your diligent work on developing this excellent tool for us all !

Thank you for your continued support of this VERY VERY useful plugin/script

from a professional app perspective, I'd suggest forgetting about DESKTOP users that are using single button mice, on any platform. Older mac laptops are a bit trapped in this perspective(due to the reliance on control to trigger a right click on VERY old macbooks/macbookpro's), so I see the need for possibly supporting them, for at least a bit longer. Aside from that though, if you're on a desktop, and you use a single button mouse(not even an apple mightymouse), I'd suggest you strongly consider an investment in a new mouse(even a 5$ 2 button USB mouse) before buying a pro app like 3DCoat ;-) P.S. any word on the release of the next build? I know Andrew's on vacation, just very eager to see more development on the 64bit branch, and test out some liveclay! in the meantime, its sculptris & meshmixer time ;-)

lookin forward to OSX liveclay, in 64bit 3DC :-)

Is the plan to discontinue the 32-bit beta builds of 3DC for OSX? After using the 64bit version now for a while, I'd prefer not to use the 32bit build any longer(except for occasions that cause major crashes in the 64bit build, till they're fixed). As an aside, the ATI SDK for OpenCL came out some time ago. I personally prefer NVidia cards, I just happen to have an ATi card in the Mac that I do my 3DC work on. There are a number of external render engines & high-end compositing apps that support ATI cards for OpenCL acceleration, Eyeon Fusion, Octane Render, Luxrender, Indigo Render, and the list goes on. CUDA is great, just VERY proprietary IMO. has anyone in this thread seen/tested an Ati FirePro V8800, pretty darn decent competition with even a NVidia Qudro FX in SOME cases(if not many ;-).

its starting to seem that this 64bit build doesn't include some of the recent OSX fixes performed in the last few builds, I cant repeat the issues often enough, but If can later, I'll report them. I'm still constantly impressed with the speed gain ATI RADEON 5770, 16+gigs RAM, 8-core 2.8xeon now if only STRONG consideration would be given to OpenCL support, then I might not have to buy Mari (immediately ;-)) when the OSX version(of Mari) is released ;-)

so far, no major "out of the ordinary" crashes. I'm really enjoying the speed of this build. And a ton of the Ui graphical bugs I still get with the 32bit builds are gone in this 64bit build

@Sergyi if the CMD key must duplicate a function key, I'd vote for CTRL.

yeah, to chime in again, its VERY smooth, noticeably smoother than the 32bit version. This is a very mature alpha/beta, especially being the first 64bit OSX build to publicly test. And for me, since a number of 3D apps on mac use control, not command, I personally dont mind.(especially since I use windows and linux often enough as well)

!!!!!! THANK YOU :-)!!!!!!!!!!!!!!! I can finally(hopefully) open my .3b files that were too large to reOpen on 32bit 3DC OSX. EDIT: So far so good, no major bugs/crashes. I'm seeing a frame-rate gain as well, looks like I'm getting about 25% more FPS now with this build. And a few minor glitches with the 32bit OSX 19a build are gone now in this 64bit build, !!! good stuff. Thanks again Andrew(and company)

@ BeatKitano First off, I enjoy your work, have for a while. Second: IT WORKED!!! I deleted the HOME event, that was the only way your suggestion worked, but it did indeed work!!! Thank you :-) I can no longer use the home key in this manner, but I can get back to work in 3DC, thanks again. IMO, This should be noted that NO OTHER APPLICATION ON MY SYSTEM REACTS AS IF THE HOME BUTTON IS/WAS PRESSED/STUCK, I did thorough testing. ONLY 3DCOAT, that is very important IMO. Something in 3DCoat seems to be possibly cataloging which keys are pressed upon application quit, and upon application launch, 3DCoat is considering those buttons that were PRESSED upon 3DCoat closing, as NOT being pressed any longer, THUS 3DCoat would then be interpreting a button that ISNT pressed as being CONSTANTLY PRESSED(when in fact it isnt being pressed). I was able to reproduce this effect many beta's ago, then it disappeared, again ONLY in 3DCoat on OSX, but it has begun to arise again, now that there were the modifier-key-fixes made to the OSX build a few betas ago. Maybe a 64-bit build for OSX will fix this(probably not ;-), but I REALLY need a 64bit build) ;-)

whoa, replies... Thank you both!!! I'll try that now, and report back with any results. I appreciate you both taking the time to comment regarding my issue. 3DCoat is one of my favorite toolsets, hopefully I can use it again soon! :-)