- User Since
- Mar 20 2014, 5:04 PM (340 w, 1 d)
(tested with blender-2.91.0 0106e17f07fe linux64)
Not a bug.
The cap object has modifiers that are disabled in the viewport but enabled for render.
Tue, Sep 15
Wed, Sep 2
I can confirm that the file above also fails.
Though this probably has a different cause than the original bug here.
I have simplified the file further and isolated the step where it fails:
Mon, Aug 31
Sat, Aug 29
Jul 30 2020
Keep in mind that calculating the volume reliably can only work on manifold meshes.
The default Suzanne mesh is not manifold.
Jul 27 2020
@Demeter Dzadik (Mets) @Roman (roman13)
Keep in mind that this will not work with Curve objects, since they have another hidden matrix that the python api does not take care of.
(E.g. doing o.matrix_world = o.matrix_world will also move an object, rather than doing nothing.)
Jul 11 2020
Jul 3 2020
I cannot reproduce.
blender-2.90.0- 5a13f682ee5f -linux64
Jul 2 2020
I wrote a patch.
Tested with commit 85980743b058e287f1d6400a64dcc60f87fad000
Date: Thu Jul 2 10:16:54 2020 -0600
I cannot reproduce this.
Jun 27 2020
Jun 26 2020
This is not a finished implementation, right?
I believe there are multiple other places, where def_nr is changed, which would destroy the sorting.
Jun 19 2020
Jun 18 2020
Probably the same bug: T75846
Back then we were unable to reproduce.
Jun 17 2020
I'm sorry, but Blender 2.79 is not being patched anymore.
May 17 2020
May 5 2020
@Jason Boycott (BlenderPlebe) If you have found a bug, please report it as a new bug.
Apr 29 2020
@Richard Antalik (ISS) Did it actually crash for you when not using a debugger?
Apr 26 2020
Apr 24 2020
Apr 20 2020
@Richard Antalik (ISS)
I was starting with the CLOUD CHARACTER TRAINING 11.blend.
I do not know of a way to reproduce it from scratch.
Apr 18 2020
I can confirm that after using the "Cut"-brush (Crease), and then Undo, some faces turn green.
No faces are deleted.
Maybe this is related to face sets somehow?
Apr 2 2020
@Jonathan Lampel (jonathanl) In what sense is it broken? If you used 32 bit float textures, it should be ok.
If you plug in the result of a diffuse bake into an Emission shader (with strength 1.0), it should show the exact same result as if you just rendered with the original shader (disregarding specular).
Always applying the view transform would destroy that.
Apr 1 2020
I think this is the intended behavior.
Mar 24 2020
I just tried with a self-built master b759857825b80af98621c2ff4b52f106ab79576c Tue Mar 24 14:02:16 2020 +0100
and with the alpha from builder.blender.org 94b8166a8b05
Feb 24 2020
I ran with --factory-startup
Feb 22 2020
Feb 10 2020
I just tried this on Windows 7 64 bit with Blender 2.68, and it hangs just the same when opening a file while selecting something in the console.
Feb 9 2020
If there's no crash, I wouldn't count this as a bug.
The console on windows always blocks if text is selected, and every software I know behaves like this.
Jan 7 2020
I disagree, this is a bug.
Nov 27 2019
Debian 9 with Intel Graphics
Thu Nov 28 06:12:17 2019 +1100
I doubt this would be due to a defective disk.
Nov 16 2019
How about adding an extra output node for eevee, to which the "corrected" node setup is connected;
and leaving the unchanged setup connected to the - now separate - cycles output node?
Nov 8 2019
Nov 6 2019
@Ahmad Bilal (SomeAB)
This certainly should not be happening.
If you can, please try to find a way to reproduce this.
@Sky (Skyfish) You seem to have added custom normals to the mesh.
Those are not displayed while in sculpt mode. I believe that is a known limitation.
Oct 12 2019
Sep 17 2019
@Mike Futcher (yogyog) I think I used an Array Modifer with count set to 1.
Sep 14 2019
Just a note:
I have been experiencing this, too, and it has been driving me crazy.
I have now found the culprit: the "Mask Tools" addon.
It automatically adds the keyboard shortcut "Double Click + Shift" for mask smoothing.
Turning that off fixes it.
Sep 11 2019
Still happens in the latest 2.81 alpha. 4ce3fbd52ae8
I'm not getting errors in the console.
Aug 27 2019
Aug 22 2019
Aug 16 2019
Jul 12 2019
Jul 6 2019
Jun 14 2019
Jun 10 2019
Just a little note:
The problem here seems to be that curves don't have tangents. You can check this via the tangent node set to UV Map mode.
However, when curves are evaluated as a mesh, they get tangents (e. g. by adding a modifier).
Jun 9 2019
Jun 7 2019
Jun 2 2019
Jun 1 2019
May 26 2019
May 23 2019
May 21 2019
This one seems to be a duplicate: T64858
Apr 14 2019
Apr 8 2019
Running Blender 2.79b in console
To run blender from the console:
- Open the folder (with Windows Explorer) where blender.exe is located (most likely "C:\Program Files\Blender")
- Hold the Shift-Key and right click in the folder.
- A context menu comes up. Click on "Open Command Window Here" or "Open Powershell here" or something similar.
- * If it is the command window (cmd), type: blender
- * Otherwise, if it is the powershell, type: ./blender
- And hit Enter.
Blender should now open, and print something to the console window.
I see. Thank you.
@Clément Foucault (fclem) Could you please take a look at this: D4662
I believe that this is an easy to fix artifact, by simply checking whether the normal is facing away from the light source (which is when these artifacts occur).
Apr 7 2019
I can't reproduce this. Volumetrics work for me.
Please make sure to attach a .blend file that demonstrates the problem.
Apr 3 2019
@Andrew Ratzlaff (Exotic) The only thing I can find wrong in this scene is that your Clip Start is very low at 0.000001m which causes some z-fighting.
No crash for me either.
Apr 2 2019
The 32 bit build also crashes sometimes on startup for me, but not consistently.
Sometimes I also get
Mar 31 2019
Mar 30 2019
This is in fact not solved.
I can still reproduce with the newest 2.80 beta build. 98f00a3eb526
Mar 28 2019
Mar 25 2019
Mar 24 2019
Jan 4 2019
I can reproduce.
Apr 11 2018
- sharp edges
- material assignments
Apr 9 2018
Apr 7 2018
Two files for testing. They both are a uv unwrapped cube, however the data is stored in different order.
With the old code, they get different hashes, with the new code, the hash is equal.
Apr 6 2018
Mar 19 2018
I'd say this is not a bug.
The same group name can apparently be reused, and refers to the same group.
Mar 11 2018
I can reproduce this.
Mar 5 2018
BKE_object_defgroup_index_map_apply now removes all weights with invalid def_nr.
If totweight is zero, it will be freed.
@Campbell Barton (campbellbarton) I'm not sure how to do that then.
If we want to keep vertex groups that are out of range, there are different possibilities:
- Map all invalid indices to -1: That could result in a vertex having multiple MDeformWeights with the same def_nr. Also, I don't know if these weights can ever be accessed again.
- Keep all invalid indices: Weights that do not have a mapping to a vertex group in the new mesh keep their def_nr. This means some vertex groups might be merged.
- Keep invalid indices only if they are out of range: Weights that do not have a mapping and are >= totweight are kept. This should not cause problems. But it has to be decided what to do with the weights with valid indices but no mapping, so they don't merge. (Move above totweight or map to -1?)
Mar 4 2018
Demonstration File to show that def_nr can be out of bounds, created with Boolean Modifier "Union" in 2.79:
Add a vertex group to the object and go into edit mode. Click "Select" to see the vertices assigned to the group. The right cube will be selected.
Mar 3 2018
MEM_reallocN instead of MEM_reallocN_id.