hi, I would like to submitt a session for burp testing. Is this possible?
I\'ve been burp member for some time. Now I have made an animation which I don\'t have the capacity to render.
Sample Images can be seen here:

www.ffa.vutbr.cz/~novak/dwnflz/mucha/

I\'ve already rendered parts of the animation, in fact, I had the files finished before Suzanne awards, but didn\'t manage to render the animation in time.

The files use the new particle features, which would now probably be a problem. (Since the patch is still not in the official cvs)

But if a test could be run, please contact me.

---

Sure!

Generally, there\'s a couple of things to notice though:

1) As long as BURP is in pre-alpha there\'s no guarantee when it will be rendered. It has to match a particular test purpose.

2) It must not use any plugins (since they probably aren\'t present in the Blender distributed with BURP)

3) All effects must be baked and all textures included in the .blend

4) Filesize matters. If the file is too large (>15MB) there\'s a high chance that it will not be rendered during pre-alpha at all. It will instead be rendered at the big End-of-pre-alpha Test.

5) The rendertime per frame should be between 10mins and 16 days. In the case of more than 1 day, it will be rendered using splitframes (so don\'t use the sequencer to add glow effect, it will look odd).

6) Framecount doesn\'t (!) matter So make a lot of frames in the same .blend, the more the better actually - it\'s starting a render that takes time, not the actual render... And the more frames there are, the better it is for testing.

7) Output should be set to PNG RGBA at whatever resolution you\'d like the result to be returned in.

8) The .blend file will be sent to the participants of BURP. Theoretically they could open the blend and look inside. The content has your copyright so noone is allowed to modify it or make derivative works - but if you don\'t like people looking inside your .blend-files, BURP isn\'t the place for you =)

9) You are not allowed to submit other people\'s material unless you have their written permission.

10) Only the internal Blender renderer is supported at this point, no Yafray or similar external engine will work right now.

In you special case you\'ll also have to wait untill the new particle code reaches the official CVS (and BURP updates the client).


Anyone who are interested in contributing a .blend-file for render testing can drop a mail to csr at boinc.dk - filesize limit on the mailaccount is 10MB. Remember that (1) applies...

I\'ve already managed to render the file in the school. Look at it at:

www.ffa.vutbr.cz/~novak/files/mucha_xvid.avi
the render has been done with passes(one of them, the ground, is blender opengl render :) )
you can look at the file with the first pass(fly without ground) here:
www.ffa.vutbr.cz/~novak/files/mouchaRENDER.blend

warning - the video is 5 mb(half pal, have rendered it in full pal), but the file is 16mb.

We still could render the session as a comparison, if wanted, i\'ll optimize the file a little, and we can try to render in a single pass.

I had to split to passes because the shadow pass is made with a simple model of the fly, without dupliverted hair and without hundreds of eyes :)

---

File not found.

Try http://plant.ffa.vutbr.cz/~novak/files/mucha_xvid.avi

That animation looks pretty cool. A little strange seeing the fly dissappear from time to time, but its would be nice to have a high quality version on BURP.

Sure!

Generally, there\'s a couple of things to notice though:

1) As long as BURP is in pre-alpha there\'s no guarantee when it will be rendered. It has to match a particular test purpose.

2) It must not use any plugins (since they probably aren\'t present in the Blender distributed with BURP)

3) All effects must be baked and all textures included in the .blend

4) Filesize matters. If the file is too large (>15MB) there\'s a high chance that it will not be rendered during pre-alpha at all. It will instead be rendered at the big End-of-pre-alpha Test.

5) The rendertime per frame should be between 10mins and 16 days. In the case of more than 1 day, it will be rendered using splitframes (so don\'t use the sequencer to add glow effect, it will look odd).

6) Framecount doesn\'t (!) matter So make a lot of frames in the same .blend, the more the better actually - it\'s starting a render that takes time, not the actual render... And the more frames there are, the better it is for testing.

7) Output should be set to PNG RGBA at whatever resolution you\'d like the result to be returned in.

8) The .blend file will be sent to the participants of BURP. Theoretically they could open the blend and look inside. The content has your copyright so noone is allowed to modify it or make derivative works - but if you don\'t like people looking inside your .blend-files, BURP isn\'t the place for you =)

9) You are not allowed to submit other people\'s material unless you have their written permission.

10) Only the internal Blender renderer is supported at this point, no Yafray or similar external engine will work right now.

In you special case you\'ll also have to wait untill the new particle code reaches the official CVS (and BURP updates the client).


Anyone who are interested in contributing a .blend-file for render testing can drop a mail to csr at boinc.dk - filesize limit on the mailaccount is 10MB. Remember that (1) applies...

Janus <- Which do notices concern submit session still today ???

---

Janus <- Which of these notices still concern sessions submitted today ???

Please correct me if I interpreted the question in a wrong way.

Pretty much all of the above points are valid still, however session submission is done through the Submit session-page.

You may also want to read the alpha restrictions and How to prepare a .blend file.

Janus <- You correct understood my question :).

In my opinion every restrictions should be on this page:
http://burp.boinc.dk/upload_animation_intro.php

Because it is not good solution \"hiding\" in forum these important restrictions ! These are very important and should be good visible for every users !

Regards

---