Tag for Blender performance related tasks.
I think an interesting idea would be to allow Custom Properties to be set to non-animatable.
Thu, Oct 10
Just wondering if it's possible to estimate whether there will be global undo performance improvements to be expected in 2.82 and which bcon phase? Thanks!
I hope that this partial switch to tbb does not bite us in some unexpected ways… would have rather switched entirely…
Tue, Oct 8
Mon, Oct 7
By adding animation to the modifier stack you effectively make it so the modifier stack depends on time (since animation depends on time, and modifier stack depends on animation).
Fri, Oct 4
These settings will enable hardware acceleration -hwaccel auto and this one -tune fastdecode will allow a much faster playback in Blender(going from 20 fps to 30 fps on my low spec computer) and this one will use all threads: -threads 0 I don't know which ones are enabled in the Blender build of ffmpeg lib, but I know from testing alternative codecs for proxies, that these settings will make a difference in encoding/decoding speed(though some of them may be h.264 only).
That's a discussion better held elsewhere, this task is only about solving a specific performance issue in undo.
@Charlie Jolly (charlie) yeah, maybe but to be honest, personally I wouldn't change its default behaviour. It works as people expect. The only issue I think people have, is with the performance. That's my opinion at least.
@Nick Moutafis (sinokgr) I see your point but that might be better managed by using frames and groups
Nodes selection is very common to be stored in the undo and it is very useful in many cases, especially on huge scenes where they will be very slow to navigate and you may have had to manually select many objects and you might accidentally click somewhere that will lose your current selection.
Undo also stores unnecessary things. E.g. node selection is stored.
Thu, Oct 3
(This affects playback performance at the studio! 👀)
I can confirm.
I don't know if this is a known issue or maybe there really is some unnecessary update.
Thanks Germano! I will note that I don't know if it's necessarily a workbench issue (see 3:23pm comment: seems to be the same thing going on with eevee, partially related to color space transform, etc.)
Wed, Oct 2
Tue, Oct 1
Face count by default makes more sense to me.
Mon, Sep 30
I don't see why don't use the face counts when Zremesher uses face count by default.
I would say keep ratio as default, as Brecht already mentioned. QuadriFlow simply needs to get smarter and not overshoot the amount of quads it can produce. ZRemesher on average produces around 120-150k verts when used on a human looking model at max settings, which should be a decent goal to set for QuadriFlow. Trying to go beyond that will make it too taxing on pretty much any computer.
Like an artist I vote for face count, is the first thing that I do every time.
Sun, Sep 29
Some profiles from a 3 million poly mesh after the latest optimizations.