- User Since
- Apr 7 2016, 11:41 AM (180 w, 1 h)
I confirm. You are using and old version of Blender (2019-05-17). However I tested the file on current build and indeed it crashes during render.
In the "slav" collection there's Plane.004 mesh which is hidden in viewports but not in rendering:
Hide it in rendering or delete it and everything renders fine:
It's a known bug: T68826. Change Viewport Shading Color to "Material", save file and reload file.
I was probably a little to quick to call this a bug...
I can't reproduce it. Could you please upload your system info:
and a simple .blend file.
Tue, Sep 17
Ok, I found out "default.001" etc. are added to the list of Screens every time you open new window. They don't disappear when you close it, though. That's why I have them saved in my startup file.
Can you test the newest build from https://builder.blender.org/download/ ? Perhaps whatever is causing crashing has already been fixed.
I guess changing status to invalid will do.
The default light has a rotation:
If you copy those values into the rotation of the newly created light you'll get the same ugly shadow on that particular face. Apparently rotation of point lights in Eevee matters?
Mon, Sep 16
Edit > Preferences > Editing > Duplicate Data > Material
It's the same issue as described here: T68826 Try changing your viewport shading color to "material". Save and reopen.
Since you created new report T69937 about the same issue you can close this one.
duplicate of T69919
Sun, Sep 15
Please always strictly follow these guidelines when reporting bugs:
- Always test with the latest official release from blender.org and daily build from builder.blender.org.
- Please use Help > Report a Bug in Blender to automatically fill system information and exact Blender version.
- Find steps to redo the bug consistently, and include a small and simple .blend file to demonstrate the bug.
- If there are multiple bugs, make multiple bug reports.
- Sometimes, driver or software upgrades cause problems. On Windows, try a clean install of the graphics drivers.
Otherwise developers will not be able to help you.
Fri, Sep 13
I have flickering in wire frame mode but I don't need to drag. Just click to place cursor anywhere.
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15
reported also in T69852
Same on GTX 750 Ti ; 436.15 driver. Material preview works.
Are you sure you don't have this selected?
If you found out that the bug was fixed I think you can close the report.
Thu, Sep 12
Probably the same bug? T69785
That's correct :)
Wed, Sep 11
You didn't provide enough information about your system and version of Blender. Always use "Help" > "Report a bug":
You also should provide blend files that are causing problems. You also didn't describe what the problem is exactly. "The something happen character controls" doesn't say much. Perhaps you should look for help on https://blenderartists.org/ first, before reporting a bug.
Mon, Sep 9
Hi, it's the same issue as reported here: T68826
Looks similar my report: T69167
Freestyle lines are also randomized they just don't align with the geometry. I think Freestyle is using different seed for noise texture.
Looks similar to T64785
Sat, Sep 7
You have long triangles in your geometry. Displacement works best when you got nice, even wire frame. You could for example try using "Remesh" modifier.
You're not supposed to hold down the "x" key. You should press it once.
Fri, Sep 6
Edit > Preferences > Navigation > Auto Perspective
Normals on those arms are in fact inverted:
In 2.80 shading is correct despite incorrect normals.
Duplicate of T69574
Duplicate of T69575
Just tested in 2.81 (sub 8), branch: master, commit date: 2019-09-05 22:13, hash: rB4c4a8bf588c5
Works as expected.
- Select hand
- Select armature
- "ctrl+p" > "With Automatic Weights"
Thu, Sep 5
Wed, Sep 4
Mon, Sep 2
I can confirm. Clicking on the "unselected" box immediately crashes Blender.
Sun, Sep 1
It doesn't crash on my computer.
Can confirm. If you zoom out long enough it will eventually close without a warning. In graph editor there doesn't seem to be any limit in vertical space like there is in the horizontal.
That's how it looks on my end. How does it look in your case?
You should specify version of Blender you're using and attach your .blend file. Also make sure your graphic drivers are up to date. Always use Help menu to report your bugs.
Here's a good tutorial.
"Voxel size" is a setting of the Remesh tool
Dyntopo has "Detail Size"
So does it crash when you turn on Dyntopo or when you Remesh?
Sat, Aug 31
I can confirm. Doesn't crash when both windows are in Solid mode.
Fri, Aug 30
Thu, Aug 29
I can only confirm. It does work in 2.79.
You should always attach your .blend file. Did you try changing "Clip start" and "End" values?
Just checked in a7ac8a22f8eb Shift+d does create a single user. Alt+d makes a multi user object. Copying and pasting also produces single user.
This has always worked like that. 2.79:
You should provide a blend file and exact steps to reproduce the error, otherwise developers won't be able to help you.
You did not provide enough information in your report. Please watch this tutorial https://www.youtube.com/watch?v=JTD0OJq_rF4 and complete your bug report.
Wed, Aug 28
3d brick texture would be nice to have. @Abid Maqbool (cto.abid) Notice that your example is physically impossible. You would need two textures with different parameters to cover that cube.
Tue, Aug 27
@Adam Janz (Copperplate) AO we're talking about here is a screen space effect so I don't think you can bake it.
Mon, Aug 26
Aug 14 2019
Aug 2 2019
In 2.79 if you opened image in UV/Image editor it was visible on a model in texture mode - but only in "Blender Render". You can not do that in 2.80. Texture needs to be connected to shader.
Aug 1 2019
I couldn't reproduce.
Jul 30 2019
Just tested on 2.81 (sub 0), branch: master, commit date: 2019-07-29 20:43, hash: rB1178046ed222
The problem is still there. Crash seems to happen only (or at least a lot more often) in wireframe mode.
I made a test file:
Can confirm. It doesn't happen when I use ctrl+r. Only when I use loop cut tool from the shelf.
Jul 25 2019
Jul 24 2019
Possilbly related to T67217
It's a duplicate of T66768
Jul 22 2019
I could reproduce it. It doesn't happen immediately but after couple of minutes.
Jul 19 2019
Must have something to do with transparency. If you turn transparency off in Film -> Transparent they look the same.