Will try to make that a bit quicker…

When added, by default, all control points of a new curve are selected, you just need to deselect the others…

Looks like we are not the only ones to 'suffer' from this…

Indeed, Please always attach a small and simple .blend file to help reproducing the issue, always saves us a tremendous of time.

thanks for the report, but we won't be able to do much with just that info, unless you can provide us with a consistent, reproducible way to reproduce the file corruption…

Am not that familiar with new 'visibility' system of 2.80, that has changed a lot even recently iirc… @Dalai Felinto (dfelinto) or @Brecht Van Lommel (brecht) should know better?

I don’t have access to the underlying DB to do so, @Sergey Sharybin (sergey) should be able to help here.

@liveasx Stop removing people following the patch, that is another kind of useless rudeness. That is also your final warning, next time I’ll have to disable your account. We do not have time to deal further with that kind of behavior.

@liveasx I do not read Chinese (as a side note to everyone, communicating in English is required on this site, so that everybody can follow), but for what I can see here, you are not behaving properly. @zdy (NGENNGT) and his team have been working on this translation for several years already, and they are responsible for it currently as far as I am concerned.

Once imported, python keeps a module in cache. I think you'll have to use importlib.invalidate_caches() for this to work properly. And/or importlib.reload() too, maybe…

Grmlll… Core of the issue here is again very weird set-up of rigidbody simulation in that file. Why remove RigidBodyWorld collection created when you first add rigidbody sim to an object? Why use a view-layer-instanced collection as rigidbody world collection? … This is really calling for issues, at one point or the other.

Hi, thanks, patch looks complete then, will check on it and commit after 2.80. :)

Hi @liveasx, and thanks for the patch. @zdy (NGENNGT) is already maintaining the zh_CN translation, so I think best is to let him check on your patch…

@Sebastian Parborg (zeddb) that is a versioning issue, not a linking issue, this is more for one of the shading guys… @Brecht Van Lommel (brecht) assigned to you for now.

@Sergey Sharybin (sergey) am getting bunch of warnings in the console… Fact that it does not show in UI is most certainly a separate issue related to how reports are working in Blender, looks like they are not 'ready' to show up during launch time for some reason…

We do not handle user support on this tracker, only bug reports. User forums like blenderartists.org or blender.stackexchange.com and our devtalk should be used for that matter.

In rB23df1a774b5b70e5108e2d1b1901d2a204ca1d9e#235732, @Sergey Sharybin (sergey) wrote:

The initial idea of IFACE_ and TIP_ was to make it possible to translate interface (buttons, properties, etc) but have tooltips non-translated.

"m" is used both for "meter" and as a short for "mi" ("miles"). Has been that way since the first commit of units support in Blender it'd seem.

For Cycles, in Render settings, Performance panel, Threads section, you can switched to Fixed number of threads and then set it to your liking.

Thanks, committed as part of rB23df1a774b5b.

Note that there is same issue when adding new object into 'grand-child' collection as well.

Next time, please attach minimal .blend file to help reproducing the issue, it always saves us time…

Hmmmpf… reading code of that operator, it's not making much sense…

*sigh*

@Brendon Murphy (meta-androcto) Seriously. Please stop doing this.

@Brendon Murphy (meta-androcto) please stop closing tasks assigned to people without even checking whether they are still valid or not! Closing tasks for closing tasks is not useful at all, it just hides again known issues.

Confirmed, with and assert as a bonus/warnjng:

Thanks for the report, but there is indeed no bug here. It’s not the role of the mirror modifier to *remove* existing faces, it only *merges* items (be it vertices, edges or faces), never actually removes them.

@Sergey Sharybin (sergey) thanks, I’ll just go with P1000 then, yes. Besides time considerations, refactoring more convert to is not to be done now, we are too close to 2.80, and would rather solve issues rather than creating new ones! :P

Lost a lot of time in muddy waters here, think that first patch *should* be valid anyway (makes no sense without it really to take care of bevel/taper objects at all in curve_to_mesh_eval_ensure()?):

makes more sense. :)

I cannot reproduce the issue when 'keep original' is not enabled…

This is an active/selected issue with new objects, which makes poll function of convert to operator to fail once 'keep original' has been enabled…

@Sergey Sharybin (sergey) thanks, stealing back then. Yes, am pretty sure this fully covers case reported here, for all curve types.