- User Since
- Apr 29 2018, 8:11 PM (55 w, 2 d)
Mon, May 20
Sun, May 19
Sat, May 18
I've had occasional crashes when using the color ramp node in Cycles and EEVEE in the past. I've been using ShaderToRGB for a while, though, and I haven't experienced any crashes except from specific nodes in specific situations (which I've reported).
@Vyacheslav (Vyacheslav) (hitrpr) Is EEVEE's crash linked to any particular node in your shader graph? For example, try replacing your color ramp with a Greater Than node and see what happens when you edit the shader. And do the same with other nodes if you can, sometimes you can isolate the problem. If there's a specific node causing the problem, editing anything upstream of that node will cause the node to re-evaluate which will probably cause it to crash (and it might seem unrelated).
Tue, May 14
Fri, May 10
Thu, Apr 25
Apr 16 2019
Apr 9 2019
I'm getting the same bug with 2019-04-08 21:54
This is related to commit: rBdec9c7d87e5b.
Also, let me know if it is helpful to mention the commit/bug if I know the root cause. I usually don't, so I can see how that could be annoying if I was wrong. Let me know! I want to provide good bug reports.
Apr 6 2019
Apr 3 2019
Mar 25 2019
Feb 21 2019
Bug occurs on today's build, too.
version: 2.80 (sub 45), branch: master, commit date: 2019-02-21 14:33, hash: 8986c92b651d, type: Release
build date: 2019-02-21, 15:38:00
Feb 6 2019
I the same issue with a model exported from Maya. It has UV's (that are an utterly awful mess), imports just fine in 2.79 (with the awful UV map) but fails in 2.8.
I have a file from Maya that has the issue in 2.79, and weird import in 2.8-- it only imports the vertices, no faces! Might be Maya's fault, but here it is:
Jan 21 2019
Here's a simpler file, with just the bug and none of the other stuff.
Sorry, somehow hit enter early