Advertisement

You're blocking ads, which pay for BlenderNation. Read about other ways to support us.

About the Author

Avatar image for Bart Veldhuizen
Bart Veldhuizen

I have a LONG history with Blender - I wrote some of the earliest Blender tutorials, worked for Not a Number and helped run the crowdfunding campaign that open sourced Blender (the first one on the internet!). I founded BlenderNation in 2006 and have been editing it every single day since then ;-) I also run the Blender Artists forum and I'm Head of Community at Sketchfab.

26 Comments

  1. over 100 ???? a lot of work

    over 100 ???? a lot of work

    i will give it a shot ( right this moment )

    i will wait patiently for the next version, that would be more than outstanding

    but what happened with Explode modifier ? why after 2.68 ? :(

    anyway that would be brutal :)

  2. This is great I already did skip 2.6 this one though ...oh boy ... I am looking forward to see this one . It will be great . Thank you everyone who made it possible .

  3. Lawrence D’Oliveiro on

    I just noticed that Cycles-style interactive preview renders are now available for Blender Internal! I thought this was hidden in a debug menu before...

    • No offense intended but, It would be better still if you learned to fill a bug report. After all, using Blender is agreeing to fill one's role in a community, not just reaping off only the benefits. Pardon my audacity.

    • if every body would ignore the normal release and would wait for an 'a' release, that would only shift the problem. than the normal release would be as stable as the 'RC', and the normal as the 'a', and everybody would switch to wait for a 'b' release... and so on.
      every release (except of the nightly SVN builds) should be as stable as possible and should be tested well before get released - these releases should be only for "end-consumers" only. all other builds are only for devs and feature freaks of interest.
      BUT not only developer should test the software, there should be also a couple (the more the better) of artists that should test the software and report bugs...
      if nobody report bugs, it is not possible to fix them - specially at an early stage of development - the later a bug is reported, the harder it is to fix it, because in the meantime other dependencies and side effects may affected.

      • yes i agree

        i think "a" is stable even more than rc

        ´cause they already fixed the most important bugs

        now i´m waiting for 2.68 hehe i´ll love that version but with no explode modifier in blender :( then i have to wait for 2.69 haha anyway Blender Dev are brutals

        THANK YOU VERY MUCH

        • I think you got that wrong:
          1. RC (release candidate) > is an unstable pre-release that is only released to make people find bugs.
          2. The following official release is the most downloaded one and it should be pretty bug free.
          However, people still do use the official release the most so bugs do not get detected before the release. (Using RC)
          It seems there are mostly quite a few issues still in the final release which is why they have to add a third (3.) "a" release a week or two later.

          • hi randomguest

            i appreciate your point, yes, that´s right, but RC works fine ( of course ) there are many issue but it works fine, i always wait 4 "a" release

            thank you....

      • hmmm...
        my english is not so good - maybe i was misunderstood.
        what i tried to say is, if more and more people say, they don't want to use the normal release and only wait for an 'a' release is a bit egoistic. that means they only want to get a finished product, and don't want to contribute by helping finding/reporting bugs...
        that will result to that the normal release is not tested as well by end-users, so most of the bugs will be reported based on the 'a' release - because RC and normal release never been touched/viewed by many artists/end-users... so in fact the normal release and 'a' release will loose more and more on stability... than the expected stable release is not more the normal and not the 'a' release - with that mentality the people will wait for the 'b' release...

        ok, maybe i will be misunderstood again. :)
        or i am simply wrong. :P

  4. Are they going to add "Explode modifier" in next version of 2.68 ?

    I am sure many waiting for it.

    I want try explode up a tree .

Leave A Reply

To add a profile picture to your message, register your email address with Gravatar.com. To protect your email address, create an account on BlenderNation and log in when posting a message.

Advertisement

×