- User Since
- Jun 2 2006, 5:16 AM (572 w, 4 d)
Please attach a sample file as per the bug tracker instructions.
Thanks for the file. It's not ideal to report multiple issues in the same report, but I can confirm the (first) bug.
It actually works, it's just really, really heavy to the computer:
Please create a proper patch in https://developer.blender.org/differential/diff/create/ using arcanist. Closing for now, but refer to this task when creating the patch so developers can read back the discussion.
The Property sensor expects a raw value, not a property for comparison. In your case you can change your sensor by an "Always" sensor, and replace the "And" controller by an "Expression" controller: prop > max
Confirmed. In fact it happens for any operator in the viewport in object mode. Another way of reproducing this is:
- Write some text
- Do some operation (e.g., Duplicate Object)
Please, as per the bug report guideline attach a file even if it's super simple.
Design tasks are reserved for developers willing to implement a feature. This is not the case. It's a feature request in fact, which we don't accept in the bug tracker even though that is a nice feature request (along side with "multi-border" render). That said, Blender read those values at render init to prevent crashes coming from users change the data (e.g., render border) while rendering is happening.
Just to complement:
(...) I'd be willing to try to compile Blender from source (...)
Your file shows that the object is missing from it. So technically it's corrupted. There is nothing we can do without having a way to reproduce this. I'll close for now, but if you can reproduce this from scratch with reliable steps we can re-open it, or report it as a new report.
Closing then. Thanks for the report, and hi @Sacha Goedegebure (sago) :)
Please attach a sample file.
Fri, May 19
Did you want blender 2.8 bugs to be reported or not at the moment?
Barely :) We just don't have the dev-power to handle triaging for 2.8 bugs at the moment.
(For the records, console shows: Error: Tangent space can only be computed for tris/quads, aborting)
This fixed the selection problems in weightpaint mode with hidden geometry, thanks :)
In the future please split those in individual commits ;)
@Sergey Sharybin (sergey) could you re-profile this, to see if creating/destroying the buffers is still a bottleneck?
The modern wasn't using modifiers, while the legacy is. The whole point of keeping Blender internal around for longer is to allow developers to see complete blender models. And even that, only until depsgraph is capable to deal with modifiers and deliver this for the draw manager.
Too early to take 2.8 reports unless there are easily reproducible (which is not the case, it seems). Unless we have a sample file we can reproduce or a backtrace log there is nothing we can do at the moment. If you're building your own Blender and could attach a backtrace of the crash with a sample file I will be glad to re-open this.
Thu, May 18
Fixed on rB90aff807ab9c - it is still a bit slower, but manageable now.
No strong feelings here. Agree on the issue with shared VBOs though, so +1 for the functionality.
Wed, May 17
The "priority" and triaging process is reserved to the development team. We leave a task as "Needs Triage" until a developer can reproduce it with the info provided.
Tue, May 16
I was reading @Clément Foucault (fclem) and @campbell discussion on IRC and would like to share my 2 cents.
Mon, May 15
@Gaia Clary (gaiaclary) can you take a look at that?
This is supposed to be working. If the problem persist please attach a simple sample file that can be used for debugging and I can re-open this.
The bug was introduced on rBb641d016e1ba5fa4c1608d8655dae9d66b92fadc
Added to the VSE TODO: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Editors#Video_Sequencer
For sample file:
@Campbell Barton (campbellbarton) could you take a look at this or assign to someone else that may be familiar with this area? It should be an easy fix, and it's very easy to reproduce.
The problem is that the active node of the materials is not the "Bake" image texture. You can see that if you look at the "properties" panel in the nodetree and see which node is shown there.
This is a known issue. A limitation of our skinning system.
This doesn't happen on Linux. And it would be really time consuming to work in a non isolated file. Can you can build a debug version of Blender and paste the backtrace of the crash when running from MSVC?
@Carlo Andreacchio (candreacchio) can you test if the problem is still there? We moved to core profile last week, so build bot builds (builder.blender.org) are expected to behave differently as before.
@Mike Erwin (merwin) can you reproduce this? For Linux at least, builder bots are building fine (core profile and all).
Just confirmed that it also works in Linux.
Sat, May 13
Fri, May 12
Open this file: