Room flythrough
"Room scene flythrough, interior only. I'm probably rendering and compositing the exterior and some other stuff locally since it renders quite fast. Here are some stills i have rendered and composited: http://mirrordream.dyndns.org/~kerneli/room/"
Session details
Session CPU Use
Session log
|
2010-12-21 14:28 UTC Registration
2010-12-21 15:18 UTC Submission
2010-12-23 17:08 UTC Accepted by admin
2010-12-23 17:08 UTC Preprocessing begin
2010-12-23 17:08 UTC Preprocessing ends
2010-12-23 17:08 UTC Render begin
2011-01-02 09:10 UTC Render ends
2011-01-02 09:10 UTC Postprocessing begin
2011-01-02 09:10 UTC Postprocessing ends
2011-01-02 09:10 UTC Encode begins
2011-01-02 09:18 UTC Encode ends
|
Comments
I actually checked the settings with the uploader and it reported everything was correct except some simulation things that i didn't even have in my scene. So that's why i had to upload through the web.
Unless something new is wrong (which I doubt), it's probably just that the .blend resolution doesn't match what was put in to the web form. I wish we had spotted that. Still the fact is that we need to fix these sorts of usability issues ASAP, so that the service is as easy to use as possible. :)
Edit: Well I checked the .blend and it seems that the resolution is in order. This could mean two things. 1) There's some new bug that's preventing BURP from stiching. 2) You would think that if the parts have been rendered with the proper resolutions, they could be stiched together quite easily. Let's see.
Having a lot of failed WUs on this session, apparently due to memory errors... Each WU is claiming 8 GB+ of virtual memory! However, I don't seem to be running out of system memory (4GB, 2 cores) before they crash out.
WCG Badges: 
With MT these memory issues should mostly be a thing of the past. We'll try to get it running within January.
Wow - that's all that I can say. Something obviously went really wrong here. We'll have to pull some stuff out by hand from the database and see what's up. Might take a while unfortunately.
Any progress finding out what went wrong? Is it still possible to stitch the images together correctly?
This session was unfortunately put in (and accepted) with the wrong resolution, which results in us not being able to stich it together appropriately. We'll try some scripting magic once it's finished, but the results may not come out right.
I think that once Blender 2.6 comes out (hopefully with Python 3.2), we'll probably remove support for uploading through the web interface altogether. It's simply causing too many grievance in terms of users getting all the settings correct.
Julius Tuomisto Project Administrator Laurea SID Networks, Espoo, Finland Tel. +358-50-4135412