@Dalai Felinto (dfelinto) thanks dor fix and advice, I'll use this info :)

Sadly the same. So filter turns off all addons, that only adds options to menues, like export-import addons especially.

Reproduced
System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GT 640/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35

any changes?

Main blender keymap have switch for this behavior.

@Pablo Dobarro (pablodp606) Dyntopo undo-bug still in the sculpt build ( https://blender.community/c/graphicall/dcbbbc/ ). Is there a way to fix it?
It is already fixed in the trunk https://developer.blender.org/T65437

Hello, can you refresh build?
Dynotopo undo bug it is fixed since 2.80 (sub 74), branch: master, commit date: 2019-06-05 19:33, hash: rB8fa65ed31b7f

@Jacques Lucke (JacquesLucke) idk.
Anyway I can`t figure how should it work other way than reverting as Color Ramp in another cases (nodes etc)

Shift+D - R is interrupt translation of cube for me.
Like this

Worked on:
version: 2.80 (sub 71), branch: sculpt-mode-features, commit date: 2019-05-20 22:59, hash: rB711d1f7591ad
version: 2.80 (sub 72), branch: blender2.7, commit date: 2019-05-29 18:17, hash: rBfee600f47980

Tried.
Can`t reproduce it on Win x64 version: 2.80 (sub 74), branch: master, commit date: 2019-06-05 09:46, hash: rBcd1ac4d908a8

@Marek Hollý (asil8567) it is known issue, named «terminator problem»
It can be resolved only with new tecnologies, where rays counts virtual geometry.
Like POM + PDO + shading.
Here is discussion.
https://blender.community/c/rightclickselect/t9bbbc/

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits

@Randell Acuram (Ranakade) did you try fresh build with clear installation? Another startup files?
This 4 example

Try to change input library (windows ink / wintab), try to use viziblr fixmypen to off some services. Check if windows pen handwrite input of such services are off.

I can reproduce it (win7, GT640, yesturday build)
It looks so: I move line slow, then up pen and move it aside fast. But Blender still counts pressure. The same with mouse but little less.
Feels like presure/click input lag without moving input lag, so moving is overtaking clicks.

Reproduced. Blender 2.8 (18.05.2019 build)

Now it works, but there is small difference:
This is screenshot from viewport. And lines are not aliased due multisampling.

In T64747#681200, @Michael Soluyanov (crantisz) wrote:

Have you set something here?

Yes, but it is Workbench render and its setings. It works okay.

In T61975#644188, @Clément Foucault (fclem) wrote:

This is more a feature request than a bug. Putting low priority.

Now it works similar with new slot-selector in the node-editor. So i close it as resolved. Thanks!

In T62422#666997, @Ingmar Franz (Uranus)

Thanks for explanation, but in this specific case only cage/extrusion fail, because there is no ray-limit.
As I can understand, it should work like this:

@Sebastian Parborg (zeddb), I felt that is something wrong before manual. Then I read it. And it is still not working as in manual or as expected(intuitive way).

The same problem if I want to drive property by bpy.context.scene.render.engine
It is strange that info-editor recieves almost all events (changing render engine or colors) but drivers can`t…

@Clément Foucault (fclem) I mean crashes appear in similar situations: when render is on and shader is compiling.
Not only with this particular shader.

No, my win is x64

As I found it works now back way: rays shooting from selected to active and hits inner cage.
Ray distance is not working at all.
Ofcourse cage extrusion is not working with backray: it extrudes only outside as it should.

@Antonio Vazquez (antoniov)
Thanks a lot for fixing that!
I noticed that now it works (when my addon said «object_depth_order not exist»)

Ok. It seems, that ray distance do not work for backface and inside of mesh. So cap and border baked on the bottom. And side was baked on the top:

Yup, it acts weird:

Tried. True.

@William Reynish (billreynish) yes, it`s priority can be low.
But, perhaps, it can be bonded with bug, and i am trying to reproduce it.

I agree, that it is not a bug. But loss of efficiency since 2.79.
How and where can I report it?

@zeddbb Crashes was with GPU.
Now I can`t reproduce. It seems problem was with video-drivers and with GPU frequency/voltage jumps (I decreased maximum limit a little with afterburner).
Thanks for help. And what about regression? 2.79 do not render each time I add node as you can see on the video. But 2.8 does this useless work.

@Sebastian Parborg (zeddb) With this library inside folder Blender do not start at all.
Also my system dir includes such library already.
I refreshed drivers. May be it'll help

@Sebastian Parborg (zeddb)
Can I dump crashlog somehow? I tried to find logs and found nothing.
Crashes are often, so may be I can collect info