- User Since
- Jun 22 2016, 7:56 PM (169 w, 5 d)
May 28 2019
I had little hope in this one being acknowledged as a bug... Thank you so much @Clément Foucault (fclem) ! You're the man :)
May 23 2019
May 22 2019
May 13 2019
Thank you, @Brecht Van Lommel (brecht) !
Hi, Marco! To be honest, I was doubting whether this is a bug or not given my limited knowledge of rendering engines. I was thinking maybe a semitransparent material shouldn't be able to emit light too in the physical world, but then I remembered EEVEE wasn't a physically based ray tracer... although I'm neither sure about this!
May 3 2019
Sorry if this one is not for discussion, but the other referred ones are archived. So I'm not sure...
Apr 15 2019
Maybe I did something really stupid, but I couldn't apply the patch to the recent master, and neither could I figure out what was the last commit this patch would work on, so I manually (and a bit painfully) introduced the changes and managed to make it build after fixing a few implicit conversions which appear to be disallowed by the compiler options (taking warnings as errors, I think).
Excuse my noobishness, did I get right that this diff didn't get committed as of yet? When can we expect it if so?
Mar 24 2019
Feb 17 2019
Feb 8 2019
It might be relevant: Appending a mesh and curve from a 2.80 .blend into 2.79 renders the curve occluded in both object and edit modes.
I have also found this to be the case with meshes, when one of them is set to "in front" and both are selected and going into edit mode, no matter which one is the active object. But I do not know if this is to be expected anyways in this not-so-common case.
Feb 7 2019
Sorry, and thanks for clearing this up.
Feb 6 2019
Jun 24 2016
Jun 22 2016
Hello, this is still broken in 2.77a