- User Since
- Apr 7 2016, 11:41 AM (153 w, 4 d)
Fri, Mar 15
Wed, Mar 13
I find latest builds to be much more stable. I no longer see crashes when compiling even very complex shaders.
Tue, Mar 12
Maybe it's one of the Windows vs Linux things? It happens only with that particular mesh.
It also crashes when object is in edit mode and the collection it's in is set to hidden.
Mon, Mar 11
I also noticed that if you select vertices in local view and add 'Hook to new object' (ctrl+h), the newly added empty will be outside of local view. In 2.79 it was inside of local view. Don't know if it deserves separate bug report.
Fri, Mar 8
Here's a file you can open but crashes when you enter edit mode:
Convert to -> Mesh from Curve/Meta/Surf/Text
Now modifiers are applied.
You can enter edit mode.
I can reproduce that on Win 10.
I appended the mesh to 2.79a. It crashes when I try to enter edit mode. So I did a copy of the object. Saved, restarted Blender. Now edit mode works. I Appended that 2.79 mesh back to Blender 2.80. Saved, restarted Blender. Edit mode crashes Blender.
As I mentioned, if you append this object, do a copy of it, then you can enter edit mode of that copied object. However, if you save that copied object, restart Blender and open the file, you want be able to enter edit mode again.
Thu, Mar 7
Just to let you know, here's the scene I've been working on.
Wed, Mar 6
Fri, Mar 1
Yes, I was wrong. Mixing glossy shaders is not the same as mixing roughness. Thank you for clarification.
Thu, Feb 28
Thu, Feb 21
There's the same problem with other nodes e.g. value. New value seems to be correctly inserted under the hood, but displayed value is stuck. When you copy the keyframed node, the copy will not hapy keframes, but the displayed value also stays the same.
Here's how to reproduce it:
There are two objects. Select one. Hide it (press h). Render (f12). Go back to the viewport and select second object. The first object reappears even though it's still marked as hidden.
Wed, Feb 20
Ok then, If there's nothing to be done about it.
Moire effect doesn't explain this:
This has been fixed: T61666
I don't get it. I can mix base color maps, metallic maps, roughness maps and normal maps using mix RGB nodes and screen space reflection works just fine. Why is mixing shaders any different?
Tue, Feb 19
I just noticed, that even when you mix two separate identical shaders there's still a difference in brightness. You can see that in the video in 00:25 on the lower right corner of the box, there's a slight variation in brightness.
Mon, Feb 18
Simply select a light (Point, Spot or Area) and type this:
Feb 7 2019
It's still the same in 2.80.
It seems to be fixed in 2.80.
Feb 5 2019
Jan 30 2019
Jan 28 2019
Here's an output from the command line. Debug mode was very sluggish so it took a while:
Jan 24 2019
Hi. I recently reported that thin objects cause AO flickering: T60522. I guess it's related?
Jan 22 2019
You are in lookdev mode which by default has an HDRI.
Hi. I also have had crashes in Eevee, so I took that file and recorded a video:
Jan 18 2019
The house in that scene is 700m by 450m by 280m. I imagine default settings aren't meant for such scales.
Jan 15 2019
Jan 10 2019
Jan 8 2019
Jan 3 2019
Dec 31 2018
Dec 28 2018
Dec 27 2018
It depends on zoom level. From around 1.001 / 1.002