Re: Framebuffer - Unexpected Failure
| Date : Wed, 3 Jan 2007 02:18:03 +0100 |
| To : <XSI(at)Softimage.COM> |
| From : "Tim Leydecker" <BauerOink(at)gmx.de> |
| Subject : Re: Framebuffer - Unexpected Failure |
Hi Halfdan,
thanks alot for the comprehensive response, I´ll pack the scene and see that I describe the failure as best as I can, I´m a bit too tired now.
It seems there´s multiple entries for 'Main' under the Passes>Framebuffer section of the explorer that aren´t deletable. Even thought there´s other buffers.
A workaround is to delete the pass and redo it from scratch, making a copy seems to just copy the problem along.
Thanks for the info on how the 32bit preview is handled, that´s quite some useful info to work from.
Cheers
tim
P.S: I´m glad I took the Friday evening flight to Madrid...
----- Original Message ----- From: "Halfdan Ingvarsson" <hingvars(at)Softimage.COM>
To: <XSI(at)Softimage.COM>
Sent: Wednesday, January 03, 2007 1:47 AM
Subject: RE: Framebuffer - Unexpected Failure
If there are two framebuffers using the same filename, the second one is ignored. It shouldn't fail like that unless all the other framebuffers are disabled. Do all the framebuffers have checkmarks in front of them? Please make sure you attach the scene to the bug report, if this is already the case.
The HDR format has always been 8-bit RGBE. 8-bit Red, green, blue + 8-bit exponent. It's just what it is.
The global gamma control has been removed since it is confusing and doesn't work the way people expect (it applies inverse gamma on input textures but *only* if they're non-float). We're working on a more comprehensive gamma/tonemapping system for a future release. In the interim I wanted to wean people off of that broken gamma control.
As for the preview, for float output, it simply maps the 0-1 RGB channel values of the framebuffer to 0-255 8-bit values and clips above and below. There is no additional mapping done.
- ½
________________________________
From: owner-xsi(at)Softimage.COM on behalf of Tim Leydecker Sent: Tue 02-Jan-07 19:28 To: XSI(at)Softimage.COM Subject: Framebuffer - Unexpected Failure
Hi guys, using XSI 6.0 I get the following errormessage after adding several "Main" framebuffers in various outputformats and bitdepths (*.exr, *.hdr, *.ct,..) for a test, anyone else run into this allready?
' ERROR : Frame buffers 'Main' and 'Main' both use the same file name 'disk\Render_Pictures\beauty.030.pic' ' ERROR : Cannot render frame buffer 'Main' ' ERROR : No valid framebuffers found to render. Render aborted. ' ERROR : 21000-REND-RenderPass - Unspecified failure
Can´t get the pass to render afterwards, even thought I deleted all double "Main" framebuffers.
Oh, btw, why is the *.hdr format 8 bit RGBE only?
This stuff "feels" a bit buggy, I´ll submit the file to support tomorrow...
Cheers
tim
P.S: And where´s the global gamma slider gone to? P.P.S: And how am I supposed to find the values for a 32bit tonemapping that would match the 8bit Renderwindow preview?
--- Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body: unsubscribe xsi
--- Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body: unsubscribe xsi
- References:
- Framebuffer - Unexpected Failure
- From: "Tim Leydecker" <BauerOink(at)gmx.de>
- RE: Framebuffer - Unexpected Failure
- From: "Halfdan Ingvarsson" <hingvars(at)Softimage.COM>
- Framebuffer - Unexpected Failure
| DATE: | << | >> | THREAD: | << | >> | INDEX: | Main | Thread |
|---|
- Previous by Date: shading geometry instanced to particles
- Next by Date: shading geometry instanced to particles
- Previous by Thread: shading geometry instanced to particles
- Next by Thread: shading geometry instanced to particles
- Index(es):
| Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available. |