when @zdy (NGENNGT) rename fields node to correct name and commit the changed po file. I think this issue is solved.

but blender user in china almost not physicist

maybe translate field as "范围" can make sense. or use the origin mean in dictionary "领域"
we need to explain to artists know what this name exact means in their knowledge system.
if we choose field as "force field" meaning, artists will misunderstanding how the node be used, especially "string field" "float field" in node editor.
and
"This position Field will be evaluated in the Point domain." ==> 位置范围将在点域中进行估值

Chinese translation team not use d.b.o frequently. we use qq group and github pr instead for communicate with chinese people.
qq group id: 620831153

new code compile pass on linux

add rhino Tspline import support use T-spline opensource lib

you may encount the same thing what T74390

Look like This dependency cycle cause this weird behavior, did this kind of constraint is forbid or need other more rig setup to prohibt like this?

can compile on Linux . I use ubuntu19.10

mute some import knot recalculate, get more accurate model from 3dm.

add cyclic support

Thanks for the patch. Looks promising.
Blender needs a complete solution for IME on all platform, IME switch not work in MacOS for lack of developer.
@Shinsuke Irie (irie) update IME in 2018 against Blender2.8 D3058 ,the reviewed process in half way,then stop for some reason.

init support subd object type. can import subd proxy mesh to Blender.

clean update to opennurbs 7.x remove old version files.

update opennurbs lib to new version 7.x
now file import can read rhino 6 or higher file.

Hi @Jeroen Bakker (jbakker) this problem still here.
as in picture,left was problem, right are close multithread scuplt in option ,
1,creat cube
2,in edit mode,subdived several times
3,switch to sculpt mode
4,create brush texture
5,switch to texture node editor, checked use node
6,back to sculpt mode, checked dynatopo on, set pix to 2
7,draw on mesh
the problem appeared use today master git branch

diff --git a/source/blender/nodes/texture/nodes/node_texture_output.c b/source/blender/nodes/texture/nodes/node_texture_output.c
index cdacb05153d..98dd43c6196 100644
--- a/source/blender/nodes/texture/nodes/node_texture_output.c
+++ b/source/blender/nodes/texture/nodes/node_texture_output.c
@@ -60,7 +60,9 @@ static void exec(void *data,
       TexParams params;
       params_from_cdata(&params, cdata);

+      BLI_thread_lock(LOCK_NODES);
       tex_input_rgba(&target->tr, in[0], &params, cdata->thread);
+      BLI_thread_unlock(LOCK_NODES);

I compiled a new Blender on mac ,seems cycles works for me. either view shading mode or F12.

https://developer.blender.org/T65833 I've creat a bug report to solve the flaw block @zdy (NGENNGT) will handle this.

In T65410#700315, @matc (matc) wrote:

This problem is not limited to Dyntopo, any mesh with high enough density will show some defects. The problem seems to originate from node texture. I was able to somewhat isolate this particular problem.

I just picked a random lock to test things, the use of LOCK_NODES should not be relevant.

This submitted patch has been sent out directly by deleting the fuzzy translate items in many places.
The translation of an interface is not one man works.

windows 10 has a future is auto re-install GPU driver but not mentioned.
You can download a driver from nvidia's home page, then re-install GPU driver again manually.
This could solve a lot of situation when run blender on windows 10.

Thanks ,it works fine after git pull. waiting for 2.8 shipping time!

seems fine to me

I also encounter this crash.
System Information
win8.1 64bit | k2100M