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.
50 Comments
Matro on
Now that was very informative, thanks Chris. I enjoy your entertaining way of teaching.
Perhaps you could follow this with with a tutorial on submitting a feature request. Most of the time people post a feature request in the middle of a random forum on elysiun. So what's the right way?
"panzi: As a next video please: How to make such an awesome video tutorial." +1
And what program you use to capture you screen? its so cool the mouse pointer moving. :)
I would add the "Bug tracker" option in the Home page of Blender.org, or even an option in Blender's "Help" menu.
I think the faster and easier it is to post them, more bugs would be reported, and laziness would affect less.
Could be a Blender feature to automate some of the steps Cris does here. Also a "text" search for the bug tracker could be helpful to find if the bug was already submitted.
Would it be difficult to implement a system as in Firefox where if the program crashes, it writes the system info in a file and uploads it to a server? Whenever Firefox or Thunderbird has a crash, it asks you if you want to send in a crash report. I'm not much of a coder so I don't know if that's feasible or not...
Would it be difficult to implement a system as in Firefox where if the program crashes, it writes the system info in a file and uploads it to a server? Whenever Firefox or Thunderbird has a crash, it asks you if you want to send in a crash report. I'm not much of a coder so I don't know if that's feasible or not...
Thanks Chris. Great to start the series with bug reporting. Everybody waited for the video and wanted to see, what quality you can create. I'm really curious if you can keep up with this very tense time schedule - is it still hanging in your bathroom? ;)
As already mentioned - bugs have to be reproduceable. Yo have to use a certain version and click with a certain data set the same few clicks to reproduce the error. That helps the developers at least to look at the right spot to find the bug.
Only an idea - can you add the most important phrases or sentences as a footage? Some people do not have speakers, but still love to watch your videos. Or perhaps your scretch notes (which I assume you have). It would be nice to see how a "pro" creates its scretch notes and texts for a video and it would allow people without speakers to watch the video and to get the info.
Cyrr? "Some people do not have speakers, but still love to watch your videos" - Seems a bit of a stretch, people can GET speakers if they want to watch online video.
Great video, Chris, very informative and entertaining!
As was already mentioned, I also would like to see a followup how to actually use the bug tracker, submit a bug report or feature request. Ok, it's not too hard to figure out, but it would still be nice to actually see it explained how it's done properly.
1) you need to have an account before you can file bugs.
2) If you can include a simplified blend file that has just enough stuff to show the bug by doing one step (ie press render to see the render bug; click the button and it crashes) etc.
3) while crash bugs are obviously important - bugs that cause render errors, stuff 'not working', or stuff 'behaving wierdly' can also be filed
4) bugs are 'stuff that worked that doesn't now' - not stuff I think would be cool to have - feature requests should be discussed on forums or emailed to bf-funboard not put in the bug tracker
5) try and have someone else confirm the bug for you in irc or in the forums before submitting the bug - if can be reproduced by someone on a different platform (ie you use windows they use linux) then the bug is cross platform. If it can be reproduced by someone with a different video card (ie you use nvidia they use ati) then it isn't a graphics card bug (graphics card bugs should be reported to your graphics card vendor!!!).
6) if you have some free time - find a bug in the tracker and see if you can reproduce it - if you can reproduce it add a comment to the tracker that you were able to reproduce it and info on what build you were using (ie current svn build; on windows; with NVIDIA 9600 graphics card). If you can't reproduce it - let us know if there isn't enough information in the bug report to reproduce it or if you followed the directions and the bug isn;t in current svn (sometimes bugs will 'fix themselves' due to other fixes etc.)
Great video! You should post a transcript of the video so us BlenderHeads that are slow on the uptake can step through the process at our own speed. Some of us are kind old, you know. :o)
I needed a cool way to say "Blender Nation" --- "Blenda Naaation"
Now I have it Chris, thus giving me ample reason to type in your long url and check out other videos.
On topic: Helpful and informative video about bug reporting. I'll admit I'm too lazy to LOOK for bugs, but if I get hit by one, now I know how EASY it is to report.
I am having a problem downloading Blender. It downloads, i click on Blender icon. I receive a Blender error message. The Blender dialog box did not allow me to copy the box. I type some of the error information in notepad. Help me, direct me to someone that may help me. Thanks.
50 Comments
Now that was very informative, thanks Chris. I enjoy your entertaining way of teaching.
^_^ Defenetly! When described by Chris even Bug Reports become Fun ^_~
As a next video please: How to make such an awesome video tutorial.
BNTV is now live! And it's off to a great start. Glad to have this from you, Chris.
Excellent as always, Chris. Thanks!
Good good! :)
Perhaps you could follow this with with a tutorial on submitting a feature request. Most of the time people post a feature request in the middle of a random forum on elysiun. So what's the right way?
My new motto as a coder is:
"If you can't repeat it, it didn't happen."
The guy is super cool!
Really cool Chris ;)
Like panziI said, i would like to know: How to make such an awesome video tutorial?
Thanks Chris! (Much appreciated by Ton, Brecht and myself :) ) A great time to post it too.
"get the latest binaries, to have your bug´s up-to-date" --- thats my new motoo.
Anyway, again a nice video.
Greetz...Jens
yeah, harkyman best quote of the month :)
Thx for the vid. Chris - Im glad you got a backdrop :)
Good video.
Good info. Those fast zoomed-in pans made me kinda seasick tho. Keying looks bad too. But good info for sure.
Glad there's a download option cos the embed won't work for me. Locks up IE7. Loads up but won't play in Opera (didn't try with FF).
BTW Vimeo and their embeds is the best imo.
How is it Chris that you can make the mundane so magnificent?
This video makes me itch all over....
Hmm, then none of my crashes actually happened. Great!
Yeah, that was awsome. Great style, very convincing. I'll report next time ( hopefully not soon ) if sth bad will happend.
Cheers
Hehe! GJ!
Good job with this video, it's informative & fun to watch.
It would be nice if all of Chris' vids were prefixed for easy searching
how did you get the video to follow the cursor like that.
cool production. I remember seeing some of your other work, too.
May I'm a bit stupid for this but how do i post a bugreport into the bugtracker?
(a step by step tutorial would be great ;) )
Excellent video. Entertaining presentation and really good information!
"panzi: As a next video please: How to make such an awesome video tutorial." +1
And what program you use to capture you screen? its so cool the mouse pointer moving. :)
Great Video Chris!
I would add the "Bug tracker" option in the Home page of Blender.org, or even an option in Blender's "Help" menu.
I think the faster and easier it is to post them, more bugs would be reported, and laziness would affect less.
Could be a Blender feature to automate some of the steps Cris does here. Also a "text" search for the bug tracker could be helpful to find if the bug was already submitted.
agrees with Galtey
Would it be difficult to implement a system as in Firefox where if the program crashes, it writes the system info in a file and uploads it to a server? Whenever Firefox or Thunderbird has a crash, it asks you if you want to send in a crash report. I'm not much of a coder so I don't know if that's feasible or not...
Would it be difficult to implement a system as in Firefox where if the program crashes, it writes the system info in a file and uploads it to a server? Whenever Firefox or Thunderbird has a crash, it asks you if you want to send in a crash report. I'm not much of a coder so I don't know if that's feasible or not...
What personality, style, and panache! A GREAT video! Editing was tight, narration is spirited, and overall... I simply enjoyed watching!
Thanks for using my music, too. =o)
Chris ftw! He just has this funny touch without over-doing it
that makes his videos very enjoyable.
Nice done Chris!
....but it seems you have a lot of free time to create this enjoyable reports! :)
Waiting on the next Chrisreport!
Thanks Chris. Great to start the series with bug reporting. Everybody waited for the video and wanted to see, what quality you can create. I'm really curious if you can keep up with this very tense time schedule - is it still hanging in your bathroom? ;)
As already mentioned - bugs have to be reproduceable. Yo have to use a certain version and click with a certain data set the same few clicks to reproduce the error. That helps the developers at least to look at the right spot to find the bug.
Only an idea - can you add the most important phrases or sentences as a footage? Some people do not have speakers, but still love to watch your videos. Or perhaps your scretch notes (which I assume you have). It would be nice to see how a "pro" creates its scretch notes and texts for a video and it would allow people without speakers to watch the video and to get the info.
Cyrr? "Some people do not have speakers, but still love to watch your videos" - Seems a bit of a stretch, people can GET speakers if they want to watch online video.
a nice one. Much better than those before.
What's with the goatee?
how to make a tutorial fun to watch. great work Chris!
Now that rocked, as ever a silly smile is on my face...great style and useful info!!!
Great video, Chris, very informative and entertaining!
As was already mentioned, I also would like to see a followup how to actually use the bug tracker, submit a bug report or feature request. Ok, it's not too hard to figure out, but it would still be nice to actually see it explained how it's done properly.
You know how to inform in an entertaining way and entertain in an informative way. You got the touch, boy. Nice one.
Potential bug reporters -
1) you need to have an account before you can file bugs.
2) If you can include a simplified blend file that has just enough stuff to show the bug by doing one step (ie press render to see the render bug; click the button and it crashes) etc.
3) while crash bugs are obviously important - bugs that cause render errors, stuff 'not working', or stuff 'behaving wierdly' can also be filed
4) bugs are 'stuff that worked that doesn't now' - not stuff I think would be cool to have - feature requests should be discussed on forums or emailed to bf-funboard not put in the bug tracker
5) try and have someone else confirm the bug for you in irc or in the forums before submitting the bug - if can be reproduced by someone on a different platform (ie you use windows they use linux) then the bug is cross platform. If it can be reproduced by someone with a different video card (ie you use nvidia they use ati) then it isn't a graphics card bug (graphics card bugs should be reported to your graphics card vendor!!!).
6) if you have some free time - find a bug in the tracker and see if you can reproduce it - if you can reproduce it add a comment to the tracker that you were able to reproduce it and info on what build you were using (ie current svn build; on windows; with NVIDIA 9600 graphics card). If you can't reproduce it - let us know if there isn't enough information in the bug report to reproduce it or if you followed the directions and the bug isn;t in current svn (sometimes bugs will 'fix themselves' due to other fixes etc.)
LetterRip
Cool as always. one note though - we should make the whole bug reporting flow easier.. from the looks of it, 6 steps is too long
Was he winking at me? ;)
These videos were a really good idea.
Great video! You should post a transcript of the video so us BlenderHeads that are slow on the uptake can step through the process at our own speed. Some of us are kind old, you know. :o)
Yes!
I needed a cool way to say "Blender Nation" --- "Blenda Naaation"
Now I have it Chris, thus giving me ample reason to type in your long url and check out other videos.
On topic: Helpful and informative video about bug reporting. I'll admit I'm too lazy to LOOK for bugs, but if I get hit by one, now I know how EASY it is to report.
I didn't know we could get a sytem info summary like that. That's rad!
LOL...
I am having a problem downloading Blender. It downloads, i click on Blender icon. I receive a Blender error message. The Blender dialog box did not allow me to copy the box. I type some of the error information in notepad. Help me, direct me to someone that may help me. Thanks.