Mantis Bug Tracker
Main | My View | View Issues | Change Log | Roadmap
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000575LuxRenderCorepublic2009-09-27 03:082013-02-25 05:14
ReporterSATtva 
Assigned ToLord Crc 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version1.1 
Summary0000575: Border rendering should optionally behave in the similar way as with Blender Internal
DescriptionWhen using border rendering (Shift+B in Blender) BI produces an image of original dimensions, but all parts which didn't get into the border are left transparent/black. This simplifies the task of post-processing, composing and such.

However Lux, when border is activated, just crops the image to the dimensions of the border. Not only this makes it impossible to know in advance what part of the image is included in the border (short of manually verifying this in .lxs) as nor Blender, nor LuxBlend supplies this sort of information, but also makes it harder to post-process the image: say, render the whole image for 1 hour, then set the border on one part of the image with hard to compute caustics and render it for another hour, and compose this now much cleaner part with the rest of the image; or replace some object in one part of the image and rerender exclusively this part with the border instead of the whole image (yes, there could be some inconsistencies in lighting, but unnoticeable in many cases).

So the proposal is: make Lux behavior with border rendering similar to BI's, i.e. when saving the image (i'm not sure if this is of much use with HDR, so maybe this applies to PNG and TGA only) place the cropped down rendered image over the transparent/black background to retain the original size. The best solution would be to have this behavior optional: if the option is turned on, retain the original image dimensions; if it is turned off, save only cropped down image -- this will be helpful in rendering ultra high resolution images in several passes (or slices) which can fit to RAM.
TagsNo tags attached.
Mercurial Changeset #
Requires Documentation UpdateNo
Requires Exporter Update
Attached Files

- Relationships

-  Notes
(0001549)
SATtva (developer)
2009-09-27 04:32

 > "Not only this makes it impossible to know in advance what part of the image is included in the border"

I meant with pixel precision.
(0001554)
jeanphi (administrator)
2009-09-27 13:59

 This makes perfect sense for all image types.

Jeanphi
(0001559)
SATtva (developer)
2009-09-27 23:17

 Great, thanks for 0.7 assignment!
(0001945)
psor (reporter)
2010-01-25 12:17

 Yeah it will help a lot but please make it just an option! ;o)
(0002077)
jeanphi (administrator)
2010-04-19 15:35

 Isn't the issue resolved by now?
(0002078)
SATtva (developer)
2010-04-20 00:03

 No. There is still only the border area in the output. Jeanphi, you can review the PM I sent to you in January: "Re: Bug 575 resolved status".
(0002079)
jeanphi (administrator)
2010-04-20 01:34

 It shouldn't be hard to implement but better wait for the complete overhaul using FreeImage
(0003502)
J the Ninja (developer)
2012-08-03 21:37

 It should be noted that when using LuxBlend internal mode (the most BI-like mode), border rendering in Blender does in fact work exactly like with BI, the "border" and "crop" functions work as usual as they are handled by Blender itself.
(0003688)
jeanphi (administrator)
2012-10-08 00:35

 I think this was fixed prior to v1.0, reopen if it is not. At least the core is capable of doing it.

- Issue History
Date Modified Username Field Change
2009-09-27 03:08 SATtva New Issue
2009-09-27 04:32 SATtva Note Added: 0001549
2009-09-27 13:59 jeanphi Note Added: 0001554
2009-09-27 13:59 jeanphi Target Version => 0.7
2009-09-27 23:17 SATtva Note Added: 0001559
2010-01-24 12:34 jeanphi Status new => assigned
2010-01-24 12:34 jeanphi Assigned To => SATtva
2010-01-24 12:34 jeanphi Requires Documentation Update => No
2010-01-24 12:34 jeanphi Requires LuxBlend Implementation => No
2010-01-24 12:34 jeanphi Requires LuxMaya Implementation => No
2010-01-24 12:34 jeanphi Requires LuXSI Implementation => No
2010-01-24 12:34 jeanphi Status assigned => resolved
2010-01-24 12:34 jeanphi Fixed in Version => 0.7
2010-01-24 12:34 jeanphi Resolution open => fixed
2010-01-25 05:18 jeanphi Assigned To SATtva =>
2010-01-25 05:19 jeanphi Status resolved => feedback
2010-01-25 05:19 jeanphi Resolution fixed => reopened
2010-01-25 12:17 psor Note Added: 0001945
2010-03-30 12:06 jeanphi Target Version 0.7RC1 => 0.7RC2
2010-04-19 15:35 jeanphi Note Added: 0002077
2010-04-20 00:03 SATtva Note Added: 0002078
2010-04-20 01:34 jeanphi Note Added: 0002079
2010-05-03 12:17 jeanphi Target Version 0.7RC2 => 0.7RC3
2010-06-06 14:03 jeanphi Target Version 0.7RC3 => 0.8RC1
2011-02-13 00:38 jeanphi Target Version 0.8RC1 => 0.8RC2
2011-03-19 05:59 jeanphi Target Version 0.8RC2 => 0.8RC3
2011-04-05 18:03 Lord Crc Assigned To => Lord Crc
2011-04-05 18:03 Lord Crc Status feedback => assigned
2012-02-21 07:59 SATtva Target Version 0.8RC3 => 1.0
2012-02-21 08:00 SATtva Fixed in Version 0.7RC1 =>
2012-08-03 21:37 J the Ninja Note Added: 0003502
2012-08-21 06:39 jeanphi Target Version 1.0 => 1.1
2012-08-21 10:16 jeanphi Target Version 1.1 =>
2012-10-08 00:35 jeanphi Note Added: 0003688
2012-10-08 00:35 jeanphi Status assigned => resolved
2012-10-08 00:35 jeanphi Fixed in Version => 1.1
2012-10-08 00:35 jeanphi Resolution reopened => fixed
2013-02-25 05:14 jeanphi Status resolved => closed

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker