Jump to content
3DCoat Forums

Pimpmymonkey

Advanced Member
  • Posts

    108
  • Joined

  • Last visited

Posts posted by Pimpmymonkey

  1. Well, I'll be a monkeys uncle.

    I did a couple more tests and it appears that max/LW export works fine..... Sort of.

    On most of the work we've done there are many materials on individual objects. In this case I noticed all but one material

    use normal maps with the color orientations as I described above. The one that doesn't, uses the max standard by the looks of things.

    I'd say that at some point someones decided to bring blender normals into line with Max and Lightwave but there's some legacy issues/bugs.

    This would explain why some people have been having problems while others haven't.

    As a disclaimer, I only tested this on blender 2.49 and 2.54 so am not sure as to the consistency of the issue.

    Also, I tried splitting an object up so that it's individual faces were different UV shells, but didn't notice any problems occurring with

    more than 15 UV shells.

    BTW our workflow here has people working on different object parts and then joining them together in blender.

    Hope this helps in some way with dev.

    cheers

    My monkey is an uncle too. :D

    Thanks for testing.

  2. There's apparently missing functionality in the last few beta releases, so I'd need to revert back a few to get a stable, full-featured release (I'm at "current" right now). However, as I'm not busy with 3DC at the moment, I'll instead probably wait for a build to be released that resolves the current issues, and then 'move forward' to that.

    If you're instead asking whether any recent Mac builds have been "stable", I'm not the right person to ask, as I've been pre-occupied with other work. Hopefully this coming weekend I'll get some time to run whatever is then "current" through some stability testing while I'm sculpting.

    The issue is mostly about labeling, and availability of prior releases. I've got no issue with the way betas are being released, so long as a "most-recent stable build" is also available for reversion when needed.

    Thank you for responding. I see from the previous page that you are happy with the suggestions made by Andrew.

    I don't use a Mac and after reading michalis response I became concerned that Mac users are being forced into

    situation where they are perpetually seeking a stable release.

    P. Monk

  3. The one piece that's missing is that Andew (or someone at Pilgway) needs to designate releases as "stable" once they've shown themselves to be free of showstopper bugs, etc. The problem with the system at the moment is that there's no clear indication of what's the most-recent "production-ready" release, and there's no assurance that going back to 3.5 (or whatever is the "version release base") will yield a more stable experience. In fact, often the most stable releases available are a few after that big version release and/or a few behind the current beta release (but of course they're not easily available anymore either).

    We just need a "Stable production revision: foo" "Current beta: bar" like other companies that allow open access to current development releases as they occur (see SideFx's handling for a great example of how to manage the stable revision vs current-most beta revision issue).

    I have been using 3DC for over 3 years now and in that time, as far as I was told,

    the most recent stable download is to be found at http://www.3d-coat.com/, if something has changed, I missed the memo.

    I guess we need clarification from Andrew.

    The thing that I don't understand and I'll ask you jwiede,

    do you have a stable version on your machine?

    You are using a Mac correct?

    P. Monk

  4. @Pimpmymonkey

    So I made a mistake, I know. Now, please indicate to me what is the non beta 3dc version.

    The first one I downloaded 1 1/2 year ago wasn't working lol

    After a lot of complains and bug reports Andrew will suggest me the latest beta, I can't ignore his suggestion, is more valid than yours. Sorry for this. For everybody is interested 3.5.9 is a rather stable one and I prefer to work with this.

    Another problem with latest builds is that they have so many bugs that there isn't any reason to report them to mantis. To report what? that it doesn't work at all? To test it where? On a project of course. Impossible.

    This reminds me the blender case. I reported so many times that normal maps in 2.5.---6 dont work correctly and nothing happened. In 2.49 work fine though.

    On complains like ' Andrew can you fix this move tool problem?' 'this pinch behavior?' 'can you do it like zbrush?' the answer 'describe it to me so to understand' ... ??? ... I'm so sorry. Really sorry. How can I describe the beauty? How can I explain what precise means ?

    Now, too many experiments around but I like to work as an artist and a human being. Life is short. What else can I say? So I'm following and developing a workflow that suits me. And sooner or later there wont be 3dcoat on this. There is this possibility. Here is your point Pimpmymonkey.

    If 3DC 3.5 doesn't work on your machine,

    then I would say yes you have a legitimate complaint.

    If Andrew is advising you to use a Beta version for production then we all have a problem.

    If however you have had a bug free version working on your machine and you are still using the newest Beta,

    then I say welcome to Beta testing.

    As for Blender, 2.49b is the last stable release.

    If you are using 2.5 or higher then you are Beta testing.

    If so, I'm guessing it is to avail yourself to the latest features.

    P. Monk

  5. No matter how many people you bring on for internal testing they will not be able to expose the software to nearly as many issues as the full user base can, so everyone would suffer for having to wait. I think Andrew's current approach has worked well for him and us and I trust his updates to more often than not be stable and useful.

    QFA

    Plus you then expose testers to complaints, "How could you &$&*#so's not have caught this. It &*$(@& to my hard drive",

    and what not.

    • Like 1
  6. but as a blender user, should i buy it? someone tell me =@

    I have been waiting patiently for BA to come back online to ask the same question.

    Hopefully they will be up and running shortly. I haven't tried pmG"s forum, there may

    be help there. Albeit slightly prejudiced, I'm guessing. In the end I decided to buy

    because an applink already exists and the renders in the gallery look pretty good.

    Oh, and I had $40.00 in my pocket that was desperately trying to escape. :rolleyes:

    P. Monk

  7. What do you use blender for? commercial or hobby?

    40US is not much really for an app such as this. Its a ps3 game. Or how many cups of coffee at starbucks you could skip drinking.

    While I agree most wholeheartedly on the price, it's really more about the time invested in one software as opposed to the time necessary to learning a new one, don't you think?

    If kay-Eva has little time invested in animation in Blender, as I don't, it may be a good investment.

    If she has spent many hours learning to animate in Blender then may be not so much. Don't you think?

    P. Monk

  8. I think what Michalis is saying, is that there needs to be a new protocol regarding public releases. They should first be "filtered" through an internal beta testing process (chosen team of experienced users willing to help spot bugs/issues before the release goes public). Right now 3DC is in more or less a perpetual Beta stage, where the line is blurred between a stable public release and new Beta builds. This is what I was communicating to Stas and Daniel.

    The only thing they should see is a rock solid build, that has undergone rigorous INTERNAL testing first. That effectively means the current rapid pace of development will have to slow down to allow time for thorough testing to occur before it "hits the shelves," so to speak.

    To provide an analogy...I served in the Army for 6yrs and I understand that often times a commander can get so ambitious that his combat units outpaces his support unit's ability to keep up and thus cause a major problems for the whole operation. Right now, there is no "support unit" (internal Beta team)....and I think that is where much of the source of frustration comes from. The public, right now, IS the Beta team. And many don't realize it, as there is very little distinction between public releases and Beta.

    Slowing things down a bit would also allow you (Andrew) to take a breath once in a while (you can take some time off while the Beta team scours the new build(s). No need to be sad about that. :D

    I'm sorry that I find myself in disagreement with you.

    To your first point:

    "I think what Michalis is saying, is that there needs to be a new protocol regarding releases. They should first be "filtered" through an beta testing process (chosen team of experienced users willing to help spot bugs/issues before the release goes public). Right now 3DC is in more or less a perpetual Beta stage, where the line is blurred between a stable public release and new Beta builds. This is what I was communicating to Stas and Daniel."

    As far as what Michalis is saying is that Michalis doesn't understand what Beta testing is. I'm sorry if Michalis finds this statement offensive as that is not my intent.

    He appears to be using the Betas as updates, which they are not. If he is using them in production he is being foolish. You are correct 3DC is in a perpetual Beta stage but only if you choose to partake in it. The Betas aren't official releases.

    Choosing to participate is purely voluntary. I will grant to you the fact that many here participating don't seem to understand the concept of volunteering a little time to help improve the product in exchange for availing oneself to the cutting edge in features. In order to alleviate the "line blurring" all that is required is to place a disclaimer on the download page explaining what it is that you are downloading and that you are doing so at your own risk.

    As far as Alpha testers go, I would argue against those as well as it merely slow down the process. For example, say you have 2 Alpha testers for each operating system, Andrew would have to take the time to notify them, I guess through e-mail, then wait. What if they are away or doing something more important? He waits some more. Where as the way it works now he receives almost instant feedback.

    To your second point:

    Slowing things down a bit would also allow you (Andrew) to take a breath once in a while (you can take some time off while the Beta team scours the new build(s). No need to be sad about that. :D

    While I find it commendable that you are looking for the welfare of our intrepid leader, I think that he is highly capable of that on his own. He is a grown man after all.

    Thirdly your analogy:

    To provide an analogy...I served in the Army for 6yrs and I understand that often times a commander can get so ambitious that his combat units outpaces his support unit's ability to keep up and thus cause a major problems for the whole operation. Right now, there is no "support unit" (internal Beta team)....and I think that is where much of the source of frustration comes from. The public, right now, IS the Beta team. And many don't realize it, as there is very little distinction between public releases and Beta.
    I served in the Army for 6yrs
    So sorry for you. Okay a joke.(I served as a jar-head.) :drinks:

    As to the rest, I think your analogy is incorrect. I believe a better analogy would be....Beta testing is a mine field,

    if you choose to disarm these mines, go forth with the full knowledge the your commander is steadfastly behind you. If you should encounter any mines, report back and he'll send send help as it becomes available.

    Lastly:

    Slowing things down a bit would also allow you (Andrew) to take a breath once in a while (you can take some time off while the Beta team scours the new build(s). No need to be sad about that. :D

    If Andrew at any time feels the need for rest, I doubt anyone who has used 3DC for even so little time as a week,

    would begrudge him time off.

    Best intentions,

    P. Monk

  9. A more skeptical person might suggest that they're intentionally milking that last %5 or so, but not even I could be so skeptical. ;)

    Keep spreading the word folks. Pitter. Patter. Twitter. Twatter. Whatever gets us to 100%.

    BTW: I ordered my license this morning. Not sure what difference one license makes to the update, but I didn't see it move either. Could be manually updated.

    Ditto that. No movement when I ordered either. :(

    Just kidding. I'm not sad. I'm excited. :yahoo: It's like gambling on E-bay. :o

    This marketing may not be brilliant but I'll say semi-brilliant. This appears to be a takeoff of the

    viral marketing system developed by Groupon. I have been waiting for someone

    to improvise the Groupon viral marketing idea for their own use. It appears to me that pmG has done it.

  10. You are an amazing person Kalle-Samuli Riihikoski. Thank you. :drinks:

    I have a question though regarding applinks in general. I, being a modo user as well as a Blender user,

    after using your Applink have a dream that those two apps might share this same type of synergy.

    In your opinion do you think that this is something possible or just a pipe dream?

    I ask this question in a theoretical sense, not in a definitive or suggestive sense.

    Thanks again for your time and effort in this project,

    P. Monk

  11. Hi,

    Thanks for the cool script,

    Just an announcement here that of course we will put your script in Blender Trunk.

    Thanks for the hard work,

    I'll chat to you in the projects page or you can mail me at meta.androcto1 (at that place) gmail.com

    Thanks again!

    Brendon.

    Great to hear Brendon. You and haikalle are the MEN! Thank you both for all you're hard work. :drinks:

    P. Monk

  12. -Not Falloff value

    -Not interpolate(soft stroke) on/off

    -Not interpolate(soft stroke) value

    -Not Smoothing value

    :)

    (Zb/MB store those per brushes)

    But what users really wants is way to SAVE that preset and load it in the interface as an Icon and a custom name.(its much easier for sharing too)

    It is very old MB 1.0, Zb 2.0 features. It very important for sculptors.

    All sculptors make themselves specific brushes

    (ex: Spiraloid could save to file his Cloth and Wrinkle brushes and load them like if they were a complete tool and assign them to the interface).

    In fact 70% of Zb brushes are presets based on a dozen Basic brushes.

    But they all have different names for specific purposes like Stone brush,or Wood brush ect...

    +1.....I couldn't agree more! An easy way to create and recall brush presets is very much needed. :good:

×
×
  • Create New...