Current renders
Looks like you have started the first two new renders.
But they seem to be very resource-demanding.
Session 67 takes a lot more than 1,4 GB RAM, my memory is swapping around 3 GB from time to time when I try to start a WU on my X2. But unfortunately every single one errors out after one or two minutes.
As I can't look in the results yet (you need to fix that in the next time hopefully) I don't know the exact error but I guess it's from a too heavy memory load.
The WUs of Session 66 seem to have a very long rendertime. I've not yet could get one on my X2, but on my "little" AMD XP 2200, and it seems the WU will run for over 15 hours, already at 8 now. I guess even on the X2 it would run 5 hours.
Edit:
Looks like the WU is finished. As I don't have seen it finishing, I can only guess, that it was at 9 hours (on my slow machine).
Edit 2:
The forum navigation is a mess IMHO.
Can you somehow add links while reading the messages of a thread to maneuver back?
I have to apologize for the waste of resources, but we needed to "hard" cancel sessions 66 and 67. Session 66 will need to resubmitted and split into more parts. Sessions 67 was basically trying to take up 2x1,4GB of RAM, which of course resulted to just errors on (at least most of) the clients.
Hope you guys understand as we're still very much learning about BURP and it's "best practices".
@DoctorNow: About the forum navigation. Would you care to explain a bit more in detail what kind of functionality you'd like to have. I added links to the main post for quickly moving from one thread to another. Edit: Are you asking for the breadcrumb? I will try to fix one ASAP. It turns out to be a bit complicated due to the way Drupal acts with the forum (forum posts are like any other content in drupal - so-called nodes).
I have a few things on navigation:
- The home page doesn't have the header with 'server status' and other links
- The home page is the only one with a link to the forum
- I can't browse by session id's in the url, or if I can it is hidden. This is one of those 'features' that is great but a pain
- I appear twice in the 'Online users'
- There are lines in some links
Considering that a site like this only has those things on my nerves, it is pretty good! I like the color, and layout. One thing that is un-clear: is it ORE or renderfarm.fi now? The logo says renderfarm.fi but I know it (as do many others) as ORE.
~Good looking site overall! Is it hard for you to re-submit my session (66) with more parts? Is it all in your DB still? Istvan.
[EDIT] One last thing is that I can't get e-mail subscription updates from the forum.
I'm sure it's a stylistic choice, but IMHO the navigation buttons could use captions.
WCG Badges: 
@Istvan:
The session ID for navigation purposes is a very good point. I think we'll change our script to make the content available (by using path aliases, this is what they really are in Drupal. All content in reality is based on nodes), for example, from /animations/sessionID.
@DoctorNow:
That's what I call breadcrumb. We will try to figure out how to do this in Drupal. We'll hopefully have some clue next week and be able to implement this. To achieve this we probably have to use the taxonomy features and find the appropriate module in Drupal. This might prove a pain, but anyway we're working on it as of yesterday.
I also agree that we need to have quoting enabled. We'll be installing a WYSIWYG editor next week for registered users. So you won't need to use HTML if you don't want to.
@Noderaser:
I'll be adding helps to the buttons.
Thank you all.
-Julius
What's up with session 85?
It seems to got stuck at 100% with all frames rendered since days...
And though it's already a progress to have it (thx!), I'm sorry to say, that I'm not yet fully satisfied with the "breadcrumb":
It does not appear when reading a thread like this here.
Session 85 crashed due to being accepted with the wrong resolution (actual resolution was 600x750, the numbers typed into the upload interface were 800x1000).
The admin interface does not yet incorporate the facilities to correct this kind of errors once a session has started. Furthermore it is particularly complicated to fix it when a session uses splitframe rendering since the rectangle that defines each part has to be recalculated and the images need to be restitched with these new settings.
Anyhow, thanks for reporting the issue, I fixed the session resolution and it should be available again soon.
I've seen 67 frames error out too almost without exception. I've asked vildanovak if he can change his scene to use less memory. 66 has a very long rendertimes indeed. I've also asked if we can cancel the 66 session (the WU's are just too long without checkpointing functionality).
/Nathan
http://www.lumikuu.com || http://www.letworyinteractive.com || http://www.planetblender.org || http://www.blender-fi.org