- User Since
- Nov 28 2009, 10:22 PM (416 w, 4 d)
This issue should be fixed in latest builds already. So test blender from builder.blender.org and see if the issue happens there.
@Brecht Van Lommel (brecht). didn't manage to find combination of flags which will solve the artifacts without introducing speed regression. More and more tempting to declare "just avoid numerical issues in shaders". But maybe you want to have a try here? (maybe disable fast divisions and use approx intrinsic when it's needed?)
Root of the issue is coming from precision issue on GPU. The thing here is that gradient texture always gives black color is such configuration, which effectively causes division by zero. Now, even though we use safe division (as in, we check whether denominator is zero or not), this does not help on GPU. Root of this issue goes to --fast-math we use for CUDA. Disabling fast math solves this issue, but gives about 15% of slowdown.
Nice to see activity in this field! Would be nice to have some common fundametals used by both compositor and sequencer.
Run Cycles tests, they are passing for me. From quick looking over the patch did not see anything obviously wrong. We can tweak code later anyway.
Tue, Nov 21
This issue was already fixed, see T51850.
This is currently expected behavior to consider all over-exposured areas as a non-screen because well, screen shouldn't be over-exposured. This was a big issue back to Trears of Steel with footage like tech. head with lamp.
Mon, Nov 20
Fri, Nov 17
@Lukas Stockner (lukasstockner97) , those changes were good since last time i've cheched them. If nothing have changed, just commit them.
Thu, Nov 16
Wed, Nov 15
Tue, Nov 14
@Sybren A. Stüvel (sybren), guess this is something known?
Limitation: the functionality is not implemented at all, code is working as it's expected within a given limitations.
Bug: functionality is there, but does not work as it is designed to.
@Brecht Van Lommel (brecht), dependency graph should indeed replace the non-interface part, but as far as i can tell here the scope is about manipulators which are exactly part of the interface. Interface MIGHT use some tagging information from the dependency graph, but then you run really quickly into chicken-egg issues because tags flush happens after notifiers are handled.
Mon, Nov 13
Setting priority to incomplete since we are awaiting more feedback now.
Managed to redo system becoming frozen at some point during synchronization after BIOS update.
Thanks for the report, but animation nodes are not in the official blender repository (not atm at least), so we can not fix anything in there. You need to contact author of the addon instead.