The curve loses its Geometry settings. In the example file the curves have depth and a full Fill Mode to them but once imported they switch back to the default settings of newly created curves.
The curve type is switched to paths instead of bezier.
Wed, Jan 16
Tue, Jan 15
I think the best solution for the studio right now would be to have the option to export curves as meshes like already mentioned here: T51311
Mon, Jan 14
Thu, Jan 10
Yes, would be useful indeed.
Yes. Those options would come in handy when selecting components in edit mode as well.
@Wo!262 (wo262) A while back there were big performance problems because both versions were visible a the same time while sculpting. So now only one is shown in Sculpt Mode. In Eevee the other one is shown (except with the wireframe overlay).
I believe this used to work fine a couple of 2.8 versions back. idk what happened, or why it works on lookdev but not on solid
Wed, Jan 9
Hey, I wanna make a patch and submit for review but this problem is happening when I try to build blender for debugging.
I wanna make some changes to sculpt.c, should I just ignore or it can cause problems?
Tue, Jan 8
@Julien Kaspar (JulienKaspar), try updating your Blender again. There was an error in the studio build scripts, making it build an old version.
I can't reproduce it, can you create an example file?
Mon, Jan 7
Ok, so it is render. In fact, can reproduce it now on my computer. Looking into it.
@Milan Jaros (jar091), i've worked around the crash by tweaking an actual object which was causing OpenSubdiv to crash. We are looking into a more robust solution, but that'd take a bit of time.
Sun, Jan 6
You can check the results on your server. I used BVH2 with primitive=LINE_SEGMENTS, but it happens without those parameters too.
It happens on render. I tried it on commit from Jan 4.
Sat, Jan 5
Thu, Jan 3
Did a completely clean build today (rebuilt the dependencies and everything), the problem seems to be gone.
Dec 19 2018
Right, there are snapshots but only changed chunks of memory are stored.
Fixed in rBe113b402bd.
IIRC, the undo system save snapshots of the scene data (not diffs). So the more complex objects will add more to memory, yes.
Note that this was caused by additions to transform callback which don't use active-tool code, causing dial to be drawn even w/ overlays disabled.
Dec 18 2018
Aaaaand my bad, little oversight that was completely my own fault.
In my case, both the background colour and the shading are pure black.
Attached is a screenshot of rendered mode with film transparency and the problem.
This is at the studio in Linux build 08e6948da50, so it does have the same problem as my 9149e894210 build on Windows at home.
It can't really be a driver thing afaik, since this is not using GPU rendering.
Fair enough, makes sense.
Is it normal though for undo steps to take up more memory when the complexity of said objects increases? Even if the datablocks are linked from another library?
A cube, for example, adds kilobytes. A forest of linked trees adds tens of megabytes each time.
I can't reproduce this, as long as the Film > Transparent is off, I see a background color.
This adds undo steps which use memory, unless the memory usage increased significantly since 2.7x it's not a bug.
Dec 17 2018
@Jacques Lucke (JacquesLucke) At a random point while setting up the simple blend file the cube got the bug as well. Trying to reproduce it didn't work unfortunately.
I couldn't pinpoint it in other files as well.
I can reproduce it in this example but don't reallly understand what is happening. Were you able to reproduce it in any other file as well?
Dec 14 2018
Presumably solved by rBd3e0d7f0825f: Fix broken particle distribution after recent fix.
ok, the problem are hair particles. Probably caused by 7e6288cfe.
I can't reproduce it. Can you make a simple .blend file that shows the problem?
Dec 12 2018
I don't think it happens exactly like this in 2.79. There is selection syncing when you click on the channels, but not when you click on the keyframes as far as I can tell.
In this file just click on some keyframe and the bone gets deselected.
We need steps to redo the issue, otherwise the bug tracker policy is to close bugs.
Extra space was added and the clickable zone was made smaller. Considering this resolved.
Dec 11 2018
Dec 8 2018
Dec 6 2018
Thanks for the system-info.txt (it helps in identifying the GPUs with this same problem).
This problem has been fixed along with this rBffdd5b3699e3.
thanks for helping , yah sure
I think I know what's happening.
Could you attach the system-info.txt?
Dec 5 2018
Dec 4 2018
Pretty much sure this has been fixed as a part of T58117 (at least my interpretation of steps got fixed).
@Brecht Van Lommel (brecht) that might be the case, I can't reproduce it myself anymore either. Thanks!
A related issue with actions (I assume), in case it helps with finding the cause:
Nov 30 2018
Nov 28 2018
Nov 27 2018
I can confirm the bug. It happens systematically to me when following these steps:
Nov 26 2018
I can't reproduce this in a simple .blend. If you can, can you attach it.