Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
I'm getting this in the debugger.
@Germano Cavalcante (mano-wii) Thanks. Blur is probably the best case scenario for OpenCL, many other effects probably wont gain so much speedup. Maybe glow would be another one to benefit a lot. In the wiki sequencer doesn't seem to have a module owner at all, but Sergey did already notice this.
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.
I can confirm this with Windows .2.79
Thanks, let me set my report to Invalid in that case. If you can't reproduce it then it might be something else that's messed up on my end. Thanks for your time.
I can reproduce the problem with 2.79 and master 69b5165.
Nice to see activity in this field! Would be nice to have some common fundametals used by both compositor and sequencer.
Woow, 19 times faster!! That deserves attention
It has to do that there is no sensible internal connection for a texture node. What has the input vector to do with the output color of the Texture node. You can see that even when muting the node Blender does not mute to an input socket.
So it is expected that you cannot do this.
It was the ¨texture solid¨ that was active, if I disable that, it works OK. A lot of thanks!!!!
Closing, another patch was committed.
- Install the latest graphics driver from the AMD website. I guess you have an "RX 570", since there is no "570 X" as far as I know.
- Try using File > Load Factory Settings and then opening the file, to check that there are no specific user preferences causing this.
- Try using the viewport without Ambient Occlusion (in the 3D viewport Shading panel), or reducing the number Samples since they are quite high in this file.
- Try disabling Background Images, Texture Solid, and similar settings to figure out if any specific one is causing the issue
- Try tweaking settings under User Preferences > System (Window Draw Method, Multisample, Region Overlap, ...)
- Attach the file generated by Help > Save System Info.
Confirmed the artifacts, needs some investigation to figure out if this is a to do or new unknown case.
Tue, Nov 21
Thanks, @ronan ducluzeau (zeauro), I appreciate the feedback.
No the review was mainly for reviewers.
More than a week passed without a reply.
Aha, I think I found it!
I feel like the poke is meant for me, but I don't know what I'm supposed to do. I've made all the requested changes, or explained why I think they are not needed.
Is there an "I'm done revising"-button? I couldn't find one half a year ago, and I can't find one now.
Ok, I update the Blender program to the latest version 2.79, and now I create this report for resolve this problem and more:
This report can be considered as a duplicate of T47080 . To simplify, none of settings related to initial state (Emission, Initial Velocity, Initial Rotation) can be animated.
There is a warning only for some settings and first keyframe insertion is not prohibited for all of them.
So, clarification is still a TODO that should be solved during 2.8 development.
That patch works great, thanks a lot! :)
But man, the ToS footage was soo much better than the one I have to deal with right now...
The error is explained in the manual.
This issue was already fixed, see T51850.
If you find an error in Blender you need to report exactly what fails and how to redo the bug.
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.
If you encounters crashes, here is a list of checks that can help to track the problem :
Now work.. after restart PC and Blender.. I don't konw why, Blender in my laptop crash often.. and this make me crazy.
Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.