- User Since
- Mar 10 2017, 7:13 PM (136 w, 4 d)
Sep 9 2019
Jun 27 2019
Good job. As usual. ;-)
Jun 26 2019
It happens when I save the scene like with »save as« or when I render the compositing. I need to close the scene to default and reload to fix it but happens again as described. I will test this on another PC and by removing the prefs on my actual laptop. Maybe it‘s a conflict with an addon?!
Jun 24 2019
Here's a scene with embedded pictures.
Mar 26 2019
Mar 8 2019
Impressive! Good job. That's why it's a pleasure to support Blender. Literally GOLD!
Mar 6 2019
Mar 1 2019
No Terminator Effect with Redshift (latest trial):
Feb 25 2019
Feb 22 2019
I found this called "Shadow Bias":
Feb 21 2019
I spotted this issue in 2001 with Mental Ray. This was fixed later. Also Arnold is rendering as expected:
Feb 20 2019
This is a serious issue and needs to be fixed as soon as possible. I made a test with Maya/Arnold and there's no terminator effect at all.
Feb 18 2019
Looks like the workaround is to start the rendering and scale the render window content to a smaller size to prevent the CUDA crash during the rendering.
Feb 17 2019
Check this video. It has something to do with the viewport size, too. At the initial size of my scene the GPU will crash. I need to restart Blender. When scaling down the viewport it will work. Scaling up it will crash at a special level. It will crash when rendering in HD. But not crash at much smaller sizes.
Feb 16 2019
Feb 15 2019
Rendering in CPU mode only works fine.
Feb 9 2019
Good job. Thanks!
Feb 8 2019
Nov 10 2018
Thanks for your time and this info.
Thanks for the fast reply. So in my scenes there are hidden Blender material trees? Because I can't find them. Or is the scene "bugged"?
Oct 9 2018
CPU and GPU are rendering different results. Here's the comparison.
It seems to be a GPU issue. Here's the CPU result. No artifacts.
Here's again the scene I used for the above video with the settings (1024 samples). The former upload was an older scene with different settings. Just to get sure.
It also happens on my XPS with GTX 1050. I will test now CPU and GPU separately.
Maybe an issue by the AMD Threadripper and/or GTX 1080Ti?
Yes, it's not a Denoiser issue. My above rendering isn't using the Denoiser and a sampling rate of 1024. I have an older video of the same scenes without artifacts but I can't say what build I used for it.
Oct 8 2018
Sep 24 2018
Here's a workaround to bring back performance after using "Make Dupli-Face". In case I would like to animate all bricks this is not a solution but to build massive static objects and environments like a city. I would love to see an overall better handling of my attacked scenes of course ... in the future.
Sep 13 2018
Sep 12 2018
It's not resolved in aa844ad676d from today. The CUDA error still exists. Viewport works. First render after fresh load will just render CPU tiles but GPU tiles keep empty. Second try will give a CUDA error. I also had again a Blue Screen. But not everytime.
Blue Screen with 2.79.6 4594cc25ac8.
Viewport CUDA Error
Here's the scene with the issue. The original non-packed scene renders fine. In the node-tree the textures "apple_roughness.png" and "apple_normal.png" are set to "non-color". But when packed the "Color Space Setting" in the "Data-Blocks" is set to sRGB. Setting to "Non-Color" will fix the issue.
I found the issue. In Data-Blocks the Color Space Settings of the non-color textures is set to sRGB. Setting them to Non-Color will fix the issue.
Just a reminder: This bug still exist in the latest builds.
Jan 25 2018
Jan 14 2018
BTW: the new Transparent Glass option is great. So useful. Good job ... as always.
I did now a couple of tests with the latest build of today. GPU rendering with my scenes is definitely broken.
Jan 13 2018
The attached simple scene seems to work with the latest release. But keep in mind that I also could render this before but later the error appeared. Maybe its a random error caused by a specific situation?
Jan 11 2018
Nov 9 2017
Impressive. Most impressive how fast you wizards fix bugs here. Thanks!
Nov 8 2017
Fantastic work, Brecht.
Sep 4 2017
Sep 3 2017
CPU vs GPU.
Sep 2 2017
Aug 12 2017
OK. What I do now . I start the render and zoom in. When I zoom out the tiles slow down and the estimated render time is over 12 hours. When I zoom in at a maximum the tiles speed up and the estimated render time is now 5 hours. Looks like this is a fair workaround. :-)
No. That's not the point. Watch my recoreded video and you will see that the speed of the tiles in the transparent areas slow-down extremely. When moving the window they start to render in an expected and correct speed. It's not correct that the tiles will take ages in the transparent area. The same issue you'll have randomly in the areas with geometry. When moving the window the rendering speeds up to the maximum speed. When minimizing the window the geometry area seems be rendered efficiently till it comes to the transparent area. The slow-downs and sometimes freezes of tiles is not normal.
Here's a video capture showing the issue: