Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them.
But since replying to reports takes time, we have decided to limit bug reports to module team members.

Try setting the lamp size to 0 or a small number, in this .blend it is set to cover a big part of the hemisphere. We have a to do item to clarify this by changing the sun size to display as an angle.

In T55423#509890, @LazyDodo (LazyDodo) wrote:

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

Cant reproduce with the "one-window" setup, but maybe someone else can?
Going back to "Needs Triage" for the time being...

Wanted to follow up -- is this in fact still "incomplete" somehow? Meaning, should I be supplying anything else? Thanks!

Like this. Old post but still helpful! Although, I have real flashlight https://tacticalflashlightguide.com/j5-tactical-flashlight-review/ and working on a program that will automatically switch on and off.

Thanx for investigating. In that case, I'll pass this on to @Brecht Van Lommel (brecht) or @Sergey Sharybin (sergey) for judgement.

Dear @Philipp Oeser (lichtwerk) , thanks for your answer. Yes, you are right in some places I have gaps in the mesh, that's why positions were wrong. But in most cases 3D positions are almost correct, I get deviations from correct positions in ~cm or ~mm range. After careful debugging, I have noticed, this happens due to place in file "blender/intern/cycles/kernel/geom/geom_triangle_intersect.h", line 221:

Thanks -- with me the gradual slow down in rendering speed happens with both the one-window setup and the original demo project two-window setup, but in the one-window setup the green cursors move as expected in both the "good" and "bad" renders, where with the two-window setup the green cursors do not move in the bad render.

Thanks for testing, closing report then.

Dear @Brecht Van Lommel (brecht) , thanks for your advice. Yes, you are right I had anti-aliasing issue. After choosing following settings to switch off AA, positions at the edges were correct.

I can confirm with attached file.
This seems to be a "two-window" issue for me though.

Not really sure this is the solution to all issues in question (havent checked any code and your first example pic seems unrelated to the example scene?)

In T54768#496256, @Philipp Oeser (lichtwerk) wrote:

Thanx for investigating.
Could you please attach a .blend as well so someone can reproduce with your geometry?

I don't think shared meshes have anything to do with this, the output looks identical to me if I make each object use its own mesh.

Thanx for investigating.
Could you please attach a .blend as well so someone can reproduce with your geometry?

also added to TODO here: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Scripting
Will have look again if time permits

I believe this is caused by an extreme value for bump (causing the normals to point in all kinds of directions). Or I'll quote @Brecht Van Lommel (brecht) from T54498:

Good joke! What means "don't know"? This problem is since 2013 or early. For 5 years you can't to know how resolve this problem? Why other render platforms can do this, and you can't? Or don't want to resolve?

Please don't reopen issues. At this moment we don't know when it will be solved.

Guys, April 2018, when u fix problem? Blender internal and Cycles have this problem{F2686577}. And don't say about subsurf, when i need lowpoly, with smooth normals. When?

Adding @Sergey Sharybin (sergey) & @Bastien Montagne (mont29) as after a quick search seem to be the most active on the subject of VSE Proxies.

First part has been fixed.
Second part fixed by @Sergey Sharybin (sergey) in D3083 rB370a2d6917eb

And .... now that I am home, I just tried playing the rendered mp4s above on my pc and they play fine (so long as I don't use Quicktime). So it is not a Blender issue but a Quicktime playback issue on the macs at the center. I feel like an idiot for not having tried that before.

Hi - please read my last comment below first, before reading this one ...

Hi - the media/art center is closed today for Easter Monday, so I will have to go there tomorrow to generate the bug output.

I will send you debug output and new zip file on Monday

I don't have permission to install anything on the machines at the media/art center, I just teach there sometimes. So I can't install 2.79b.

@Trudy Wohlleben (trudyvfx) Yeah that was for you. Run blender with debug options on:
open Terminal and start blender with:

doesn't seem like the attached .blend is using any of the video files, (or i'm not bright enough to figure out how to reset the paths) if you could attach a .blend file where we just have to hit 'render animation' to get the problem to show that be appreciated.

Is this question for me (probably not but answering just in case)?