Re: [Bf-committers] Socket storage and backwards compatibility

2012-05-07 Thread Lukas Tönne
Just made a trunk merge in my local working copy, no big conflicts encountered. All 3 bugs seem to be solved :) The image and file output implementations in Tile need to be updated still, will let you know when i have a patch ready. ___ Bf-committers mai

Re: [Bf-committers] Socket storage and backwards compatibility

2012-05-07 Thread Lukas Tönne
It looks like these would be solved with a trunk merge. The file output node is still the old version, without any of the dynamic socket list stuff. The main problem seems to be that the old image node cannot properly cope with custom OpenEXR files that don't follow the render_layer.render_pass.cha

Re: [Bf-committers] Socket storage and backwards compatibility

2012-05-06 Thread Brecht Van Lommel
Old files should be backwards compatible as much as possible and certainly not crash Blender. I don't understand why it would crash though, usually that's when opening files created in a branch in trunk? If the latest trunk changes are merged it should be fine, and that needs to be done before merg

Re: [Bf-committers] Socket storage and backwards compatibility

2012-05-06 Thread Dalai Felinto
Hi, > What are the ideas about backwards compatibility of the image node/file output node? The 'File Output' seems to be pretty backward compatible. The one in trunk seems like a subset of the one in Tiles. What is wrong with creating an output node set with the scene parameters (image type, comp

[Bf-committers] Socket storage and backwards compatibility

2012-05-06 Thread Jeroen Bakker
Hi All, We have some issues with the new image node. Users are creating files with trunk and read them using tiles. And it crashes :) for example: * http://projects.blender.org/tracker/index.php?func=detail&aid=31329&group_id=9&atid=524 * http://projects.blender.org/tracker/index.php?func=