- User Since
- Oct 12 2014, 1:52 PM (424 w, 4 d)
Oct 3 2022
I am the one who recommended the user to open the report just in case because I understand that developers try to make the results with different devices as similar as possible.
But I hadn't realized much about the image comparison method the user was using. He set layer blending mode to "Divide". I'm no expert on this, but it seems the blending mode used for this is "Difference" (In Krita under Blending modes, Negative and Difference).
Sep 16 2022
Sep 14 2022
Sep 7 2022
Apr 25 2022
Yes please. Move Texture Limit to Simplify Menu just like Cycles for better consistency (and Viewport separate from Render).
Apr 20 2022
Apr 6 2022
Mar 30 2022
@Pratik Borhade (PratikPB2123) I still have the .blend file shared by the user and I can confirm that this report is a duplicate of T96344. I have applied the proposed patch D14485 to fix this and with it the .blend file does not crash
Mar 29 2022
Here is the file and the steps to reproduce the problem:
Mar 16 2022
Feb 15 2022
Feb 11 2022
Jan 20 2022
I have built Blender Master with the patch and unfortunately it does not work on my Kubuntu Linux OS (KDE). "Alt Gr" Key does not work like "Alt" key if Spanish keyboard distribution is selected in my OS. Is there any information that I could share with you and that could be useful? Is there any way for debug key entries and know how are they detected in Blender?
Jan 19 2022
I'm not sure if this old report was lost in the sight of the bug tracker maintainers for some reason. Because this is a "crash" problem, I thought I was going to have some kind of feedback with maintainers to request more information about the problem.
Jan 15 2022
Jan 14 2022
@Harley Acheson (harley) , I'm not sure I understood :) Anyway thanks for the clarification. At least on my Linux OS "Alt Gr" and "Right Alt + Ctrl" are not doing the same things.
Just to say that this problem is also reproducible in Linux OS.
Dec 13 2021
I don't think this is a bug, but surely a bad design that we have on Linux.
Dec 5 2021
I have seen that Blender 3.0 has been released, and Blender still crash. Has anyone been able to reproduce the problem with the .blend file shared above (race_spaceship.zip)?
Nov 25 2021
So, with .blend file shared above (race_spaceship.zip) I get:
Nov 19 2021
Nov 13 2021
Ok, this is even weirder. I have downloaded some of the Eevee sample scenes again and it works correctly. The problem is with the same Eevee demo scenes but downloaded in 2017/08/28 (according to the information in my file browser, Eevee still beta ???). I have checked hashes of my old downloaded sample scenes with new downloaded ones, and hash differs. Have files been modified at some point? Anyway, I can open old scenes in Blender 2.93.5. Here I try to upload one of the scenes downloaded in 2017 that gives me problems:
Nov 10 2021
Hi. In my case renaming 3.1 config folder doesn't help. Perhaps this is a very new problem a little different from what others were having.
Oct 26 2021
Oct 16 2021
Oct 12 2021
@William Leeson (leesonw) , With that node setup I find that it renders differently with CPU or GPU also with Checker texture:
I have found that the problem is also reproducible with Wave Texture, do I need to create a different report?
Oct 10 2021
@Philipp Oeser (lichtwerk) Sorry for the late response.
Oct 7 2021
Oct 6 2021
With that iGPU you probably have better luck using a Linux distro.
Sep 23 2021
Sep 21 2021
Sep 20 2021
Sep 7 2021
Aug 20 2021
Aug 19 2021
Aug 5 2021
Jul 28 2021
Jul 24 2021
I wonder if now that this is inside Master we can now report graphical/GUI problems here in the bug tracker.
Jul 22 2021
Jul 21 2021
Jul 6 2021
Jun 29 2021
May 31 2021
May 28 2021
May 20 2021
May 6 2021
May 2 2021
May 1 2021
Apr 20 2021
@HEYPictures (HEYPictures) , Did you try the version of the nvidia driver @jw (jw) are using or an even newer version?
You write here the versions of the driver that you are testing and with which you still reproduce the problem.
Apr 19 2021
@Metin Seven (MetinSeven) : OK, thank you.
Regarding "When we have the list nailed down, we will do a community call for assets, so that we can go ahead and collect high quality assets."
Apr 17 2021
@Christophe Leyder (shotalot) , Does that mean that you can reproduce the problem with the .blend file on the first post of the report? What is your graphics card?
There is a problem that could be similar to this with RTX cards in Windows, but it is a report related to Volumetrics, so I am not sure:
Apparently you made the report from an unsupported build of Blender.
From what I had understood with the comment you made in another report the problem you have could also be reproduced with latest 2.93.0 beta buildbot build.
@Dustin Bowser (bowserlm), Please, you open a new report. You do it from Blender so it collects information from your system and hardware. From Blender "Help" menu, "Report a bug". Share that .blend file and video with developers.
Apr 16 2021
@Dustin Bowser (bowserlm), Can you reproduce the problem with the shared .blend file on the first post of the report? If not, what is the .blend file where the problem can be reproduced?
Apr 5 2021
Mar 31 2021
Mar 23 2021
@Clément Foucault (fclem) , Thanks for the fix, it solves most of the problem. Just to mention just in case, that even with the fix in certain circumstances (it may depend on the amount of geometry of the mesh and the angle of the view) small fireflies/artifacts may still appear at the edges. For example here (it is more noticeable in the final render image)
Mar 2 2021
Mar 1 2021
Feb 23 2021
Feb 22 2021
Feb 21 2021
Feb 16 2021
I have tried with a completely different Linux installation and the problem is also reproducible (Kubuntu 20.04 and Kubuntu 18.04). Blender 2.93 (c53022768b13)
I'm going to give it a try, but I'm not sure if this commit is related to the problem.
Feb 15 2021
Hi. I still have the problem. Maybe you manually set RMB selection from Blender Preferences > Keymap? By setting it manually, RMB works correctly again.
Feb 13 2021
I have done a couple of tests renaming the 2.93 folder in /home/USER/.config/blender. The first time I launch Blender 2.93 with empty configuration, if I configure RMB selection in splash screen then RMB works correctly. In another test with empty configuration again, if I select to copy previous 2.92 configuration (which was configured with RMB to select), then RMB does not work and Blender acts as LMB to select. This problem only in recent Blender 2.93 builds.
Feb 12 2021
Feb 7 2021
I think my report is a duplicate of this other report: