Hi,
It should now be fixed in latest git.
On Mon, Dec 29, 2014 at 10:15 AM, Jefferson Rausseo
jeffersonraus...@gmail.com wrote:
Everything perfect with the commit 788fb83
In the following commit (03f2855) there was a problem compiling. The
problem was resolved with commit 010f3ee, but from
Hey,
Here's the list of revisions so far. Only few nastier fixes to be
backported, rest of them are rather nice to have.
That's why mailing the list, to get feedback from the nice to have commit
authors about inclusion into 2.73.
= To be ported for sure =
jens:
Hello, we have a bug report that claims our importers do not do any
sort of color space correction
for external assets, see https://developer.blender.org/T43025
The issue should be that most exporters presume srgb color space while
our material definition is in linear space.
I am not sure if the
I reported this problem in the tracker (T42990), is fixed, can close.
2014-12-29 3:57 GMT-04:30 Sergey Sharybin sergey@gmail.com:
Hi,
It should now be fixed in latest git.
On Mon, Dec 29, 2014 at 10:15 AM, Jefferson Rausseo
jeffersonraus...@gmail.com wrote:
Everything perfect with
Awesome.
Thanks for the fix
On Saturday, December 27, 2014, gandalf3 zzyx...@gmail.com wrote:
Wow, that's great, thanks! :D
The devs are so fast they add features *before* they are requested ;)
On 12/27/14 11:59, Jason van Gumster wrote:
IIRC this feature was committed in master not too
As far as I can see the only good solution here is for import/export
to handle the conversion themselves,
We can have some convenience functions in `mathutils.Color` so py devs
can switch between spaces.
On Tue, Dec 30, 2014 at 1:40 AM, Antony Riakiotakis kal...@gmail.com wrote:
Hello, we have a
Hey there,
My 3 fixes are all really minor ones, so I don't think they should be included.
If at all rB6339ba1ee2b06174fa6 could make it in, but I personally don't really
care.
Greetings,
- Julian -
Hey,
Here's the list of revisions so far. Only few nastier fixes to be
backported, rest of
Hi,
First of all, I want to be really sure it is a blender issue, not an issue
of some particular weird working pipeline.
Hence my question here is: how often do you mix software with different
color pipelines (in regards of 3d model interchange, NOT gading/comping sw)?
It sounds a bit weird to
Would be good to hear more on the use case from the bug reporter.
But I think this issue is you may import models ad-hoc into an
existing scene, without that being a key-part of your pipeline.
In that case its not great if you want to load in some model and the
colors look different.
However
From the comments on that report (thanks Brecht) it seems that not all
software exports to srgb after all.
The way I would solve this for such formats is to just have an
option so the user can select the color space their color data is in,
same as we do for images.
Yes to both of my questionable commits, also these.
445e50fd1e7d41306ea475bd79bb89bc2d7fc3b1
8d7b2d69cf5b8de0dab487b84b5f52ba308ddf4b
870941c87a484b41294d5255c1807e0e87138458
51a66a5a6e3e409f9e6d08f8b771d8e25e6a498e
On Tue, Dec 30, 2014 at 7:54 AM, Julian Eisel julian_ei...@web.de wrote:
Hey
11 matches
Mail list logo
