Jump to content
3DCoat Forums

hOss

Member
  • Posts

    12
  • Joined

  • Last visited

Posts posted by hOss

  1. I do most of my work on a Mac. Most, but not all. Before buying a license to 3D-Coat v3.5 (both Mac and Windows), I, of course, downloaded the trial version of both 3D-Coat v2 and then 3D-Coat v3 when it was first released. Now, my experience with v2 was not so good for two reasons: 1) I am a native English speaker and the English translation for 3D-Coat was very, very difficult to follow at that time, so I found it difficult to learn the tools and proper workflow. This has since been corrected and, IMO, the English translation is VERY good and especially the pop-up help for the tools are VERY descriptive and helpful! 2) After launch, v2 on my Mac would crash almost every time I selected a tool and tried to use it. I'm not kidding, it was unusable, IMO. Now, my initial trial of v3 was better. The English translation was excellent, so, no problem there. However, I still had the problem with crashing on the Mac.

    Now, as of 3D-Coat v3.5.01 or v3.5.02, I cannot recall which build (it was the build after Andrew got advice from NVidia on OpenGL optimizations), I believe that my Mac build is not only rock solid, but it actually feels faster than my Windows version in the viewport for once. Now, there is another caveat of the Mac version that I've noticed over the Windows version-notifications. By this, I am talking about showing the user progress when 3DC is performing an operation. For example, when using AUTOPO, the Windows version shows the progress bar with an explanation of what 3DC is currently doing, as well as a % in the title bar of it's progress. In the Mac version, sometimes I get a progress bar, sometimes I don't, when I do, it's usually blank with no info, and I also have the spinning "beach ball" which makes it appear as though 3DC has crashed, even in the Dock it offers to Force Quit the app. However, I've found that if I just get up, walk away for a minute or so and come back, the operation is complete and 3DC is back to normal. Even the Windows version tends to say 3DC is "Not Responding" in the title bar and the screen will fade (On Windows 7, anyway), giving the impression of a crash, however, patience proves that if you just leave it alone for a few minutes, it will finish its calculations and return to normal. Thing is, without the progress bar appearing on the Mac version in most situations, it totally looks and acts as if the program has crashed. Thing is, it usually hasn't. Perhaps this is due to the lack of a 64-bit Mac version, yet? So there is less RAM available for intensive operations and there is more virtual memory being used? IDK, but all I do know is that the optimizations Andrew has made in the last 2 or 3 builds has made a world of difference on my Mac version.

    Keep up the great work, Andrew!!!

    -Patrick

  2. One comment from a mac user here, sorry. There are two categories of 3dc users, the mac one is not so happy, have you noticed this?

    Silo is more stable than 3DC, - from a mac user again (I trashed this app anyway). Everything is more stable in a matter of fact. :)

    Not that bitter, I have to explain. I experienced so many crashes yesterday, I spent hours in place of some five min to be able to export to blender. When I'm working in 3dc I'm not sure if I manage to see my work rendered in another app.

    I'm sure Andrew will fix these somehow. I hope so.

    Andrew is my hero for one reason. He realized the artists needs, this sounds impossible, not for him though.

    Maybe he's not so good on optimization. Who knows. But what matters is that he produces an app not only for standard VG 'methods'. Thats why I'm staying here, waiting... Am I the only one who thinks like this? No, of course not.

    Sorry, but I have to put my $.02 worth in here.

    I do most of my work on a Mac. Most, but not all. Before buying a license to 3D-Coat v3.5 (both Mac and Windows), I, of course, downloaded the trial version of both 3D-Coat v2 and then 3D-Coat v3 when it was first released. Now, my experience with v2 was not so good for two reasons: 1) I am a native English speaker and the English translation for 3D-Coat was very, very difficult to follow at that time, so I found it difficult to learn the tools and proper workflow. This has since been corrected and, IMO, the English translation is VERY good and especially the pop-up help for the tools are VERY descriptive and helpful! 2) After launch, v2 on my Mac would crash almost every time I selected a tool and tried to use it. I'm not kidding, it was unusable, IMO. Now, my initial trial of v3 was better. The English translation was excellent, so, no problem there. However, I still had the problem with crashing on the Mac.

    Now, as of 3D-Coat v3.5.01 or v3.5.02, I cannot recall which build (it was the build after Andrew got advice from NVidia on OpenGL optimizations), I believe that my Mac build is not only rock solid, but it actually feels faster than my Windows version for once. Now, there is another caveat of the Mac version that I've noticed over the Windows version-notifications. By this, I am talking about showing the user progress when 3DC is performing an operation. For example, when using AUTOPO, the Windows version shows the progress bar with an explanation of what 3DC is currently doing, as well as a % in the title bar of it's progress. In the Mac version, sometimes I get a progress bar, sometimes I don't, when I do, it's usually blank with no info, and I also have the spinning "beach ball" which makes it appear as though 3DC has crashed, even in the Dock it offers to Force Quit the app. However, I've found that if I just get up, walk away for a minute or so and come back, the operation is complete and 3DC is back to normal. Even the Windows version tends to say 3DC is "Not Responding" in the title bar and the screen will fade (On Windows 7, anyway), giving the impression of a crash, however, patience proves that if you just leave it alone for a few minutes, it will finish its calculations and return to normal. Thing is, without the progress bar appearing on the Mac version in most situations, it totally looks and acts as if the program has crashed. Thing is, it usually hasn't. Perhaps this is due to the lack of a 64-bit Mac version, yet? So there is less RAM available for intensive operations and there is more virtual memory being used? IDK, but all I do know is that the optimizations Andrew has made in the last 2 or 3 builds has made a world of difference on my Mac version.

    Keep up the great work, Andrew!!!

    -Patrick

  3. Sorry, I'm having trouble figuring out which link on your Buy Now page lets me do what I want (specifically that is, to upgrade my licenesed Winx64 3DCoat v3.5 to allow me to have a coexisting Mac license with it).

    I noticed a Mac to Win upgrade, but not the other way around. Also I noticed that new full licenses say Win&Mac?? Thanks for clarifying this :)

    The Win&Mac license is just buying both licenses in one go.

    I know it seems kind of backwards, but on the Windows buy page, there is the option of "Win to (MacOS or Linux)-$40". That should be what you are looking for to buy the Mac license at a discount from your existing Windows license. No, this won't deactivate your existing Windows license.

    -Patrick

×
×
  • Create New...