[Bf-cycles] preview settings and RGB values in texture paint and cycles

[gandalf3]

Since it's now after a release (though not the same release), would it 
be possible for someone to implement this?
This would save much time spent constantly re-enabling viewport border..

On 03/03/14 07:18, Brecht Van Lommel wrote:
>
>
> I agree, it should be removed and use ctrl alt B instead, I can do it 
> after the release.
>
> On Mar 3, 2014 3:14 AM, "Daniel Salazar - patazstudio.com 
> <http://patazstudio.com>" <zanqdo at gmail.com <mailto:zanqdo at gmail.com>> 
> wrote:
> >
> > I agree, this border select functionality that disables render border
> > when you select the whole camera space was a great addition by Matt
> > Ebb years ago, however now that we got interactive preview this option
> > is more troublesome than helpful. A simple fix would be to revert the
> > automatic disabling of the border
> > Daniel Salazar
> > patazstudio.com <http://patazstudio.com>
> >
> >
> > On Sun, Mar 2, 2014 at 3:08 PM, Jim Cantley 
> <semajcantley at hotmail.com <mailto:semajcantley at hotmail.com>> wrote:
> > > Hello,
> > >
> > > I'm a big fan of cycles and wanted to give quick input to help 
> streamline
> > > its use and make it more awesome! Very easy stuff to fix (and 
> gosh, I wish I
> > > knew what you guys know!)
> > >
> > > The ctrl-b preview feature is fantastic! However, if I want to 
> preview only
> > > the camera view and nothing outside of it, I have to select beyond the
> > > camera bounds to reset the border checkbox in render settings, 
> then I have
> > > to check the border checkbox again to render exactly what's inside the
> > > camera border. There should be an option to lock render bounds to 
> the camera
> > > border. Changing the ctrl-b preview to beyond the border of the 
> passepartout
> > > resets this feature and renders stuff beyond the camera border 
> (increasing
> > > preview time), but there should be a way to lock it permanently to 
> camera
> > > bounds. I always keep passepartout alpha set to 1 because seeing stuff
> > > outside of the camera bounds seems to throw off the way to gauge
> > > composition.
> > >
> > > Something else - the RGB settings in texture paint don't match the RGB
> > > settings in the cycles nodes. I can set RGB to .5, .5, .5 in 
> texture paint
> > > and I get a HEX code of 808080 (perfect gray), but in cycles I get 
> a HEX
> > > code of BCBCBC. To get a middle gray I need to set cycles color 
> nodes to
> > > .216, .216, .216. Is there something I'm missing there?
> > >
> > > I really love what you guys are doing, thank you so much! If this 
> is helpful
> > > and you'd like me to make any more notes in the future I'd be 
> happy to do it
> > > because I want this rendering engine to be the best it can be! I 
> really
> > > appreciate everything the blender community is doing, thank you.
> > >
> > > Kind regards,
> > > Jim
> > >
> > >
> > >
> > > _______________________________________________
> > > Bf-cycles mailing list
> > > Bf-cycles at blender.org <mailto:Bf-cycles at blender.org>
> > > http://lists.blender.org/mailman/listinfo/bf-cycles
> > >
> > _______________________________________________
> > Bf-cycles mailing list
> > Bf-cycles at blender.org <mailto:Bf-cycles at blender.org>
> > http://lists.blender.org/mailman/listinfo/bf-cycles
>
>
>
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> http://lists.blender.org/mailman/listinfo/bf-cycles


-- 
-gandalf3

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-cycles/attachments/20140625/cad5cbdc/attachment.htm