In T87263#1142819, @Tomasz Kaye (bitbutter) wrote:

With the new change, if i have 'Use Factor' turned on, i expected 'start delay' and 'frames' values to be ignored. but currently the animation (driven by the Factor value) only happens within the part of the timeline specified by the 'Frames' and 'Delay' values.

Fixed rB0c0e9390d1caec7858eb95ea2641cbf6d54e5e1f

With the new change, if i have 'Use Factor' turned on, i expected 'start delay' and 'frames' values to be ignored. but currently the animation (driven by the Factor value) only happens within the part of the timeline specified by the 'Frames' and 'Delay' values.

Initial impressions and suggestions:

Can confirm, assume rB50782df42586: Render: faster animation and re-rendering with Persistent Data is the culprit

Please always attach a simple .blend file (or .blend files in this case).

This might be a memory leak in Grease Pencil somewhere. Can you try and use the 2D animation template to increase the RAM usage once more? You can use the blender_debug_log.cmd in the Blender installation directory to create a log file. After Blender becomes slow, save the file then exit. Then upload both the log file and the .blend file here (e.g. via drag & drop).

I can confirm the crash in 2.92.0. Not sure if we can call this a bug. But imo this shouldn't crash even if the file was saved in a never (Alpha) version.

This is caused by rB6524ceb8cfa5: Cleanup: Remove ptr For Owned Children.

Committed as listed above.

Bisecting this atm (and keep separate from T87252 for now)

@Dalai Felinto (dfelinto), the proposal sounds fine to me. Then this patch mainly needs code review node.
When it is done, I'll try to get breadcrumbs working before bcon3.

• improve toggle in header
• cleanup

This feature was implemented as described in T78988, so I will close this patch.

In D10909#278180, @Sergey Sharybin (sergey) wrote:

Is probably fine, but this system is rather cryptic to me. Mix of hash and linked list.. Just make sure you aren't fighting race condition here, because that'd require different solution.

Address comments.

Use BLI_ghash_haskey to check if key exists in cache

It has not been discussed, and yes, i'll try to implement it!

In T83130#1142759, @Stanley Obiagwu (N3TBUG) wrote:

Hope this helps you guys... After multiple test downloads, I found that you get the GPU error when you download through the installer, a "fix" would be to use the Portable version instead, they work perfectly.

If you don't know how to get them, they are on the Official Download Page (ONLY for the current version). Previous versions of Blender are located here https://download.blender.org/release Choose your version and select to download the Portable version (.zip)

My GPU is a "Sapphire NITRO+ RX 590 AMD"

I find placing this in the Preferences a weird choice, especially since it's an operator, not a Blender setting. It could be placed in the hamburger on the lower left, or in the app menu in the top-bar (with the Blender icon).

Besides the two things mentioned below, this looks good. Thanks.
We could probably cut down the code duplication a bit, but it's fine :)

While I didn't test this, the approach seems fine.

It still crashes in the most basic setup:

Thanks for creating a separate report.
Given that the issue affects all node group types, I think this patch can go in anyway.
I'd say you can commit it without the change in node_free_type. That could be committed separately, if necessary. Obviously, it would be better to just fix the underlying issue..

In T83068#1140414, @Scott Wilson (propersquid) wrote:

• It looks like the the motion paths are only for poses and objects. Are there any other types that I need to make sure this works with?

I think so, yes, because in the C code I only see ANIMVIZ_RECALC_PATHS used in the context of objects and bones. In any case if something was missed I'm sure users will complain about it soon enough, and you can add support for that to the code as well ;-)

This example is working, thanks!

The solution seems fine for the time being. I was just thinking about how this can be improved and wondered if we should refactor InstancesComponent a bit.
How about structuring it like this:

Hope this helps you guys... After multiple test downloads, I found that you get the GPU error when you download through the installer, a "fix" would be to use the Portable version instead, they work perfectly.

This looks like the same as T87252: 2.93 file output node broken with more than 4 inputs

Caused by rB50782df42586: Render: faster animation and re-rendering with Persistent Data

In D10197#277133, @Brecht Van Lommel (brecht) wrote:

I think both the "Use Proxies" and "Always Add Modifier" options are useful, regardless of their relation to Cycles features.

• Use Poxies: being able to see bounding boxes rather than full geometry or nothing is helpful in complex production scenes. This is a standard feature in other 3D apps.

In T87265#1142716, @Falk David (filedescriptor) wrote:

@Ludvik Koutny (rawalanche)

So you are implying that data loss is more or less fine? And Blender should not help the users here, but punish them instead? That's it?

No, we have rules on the bug tracker. As Bastien has said, this would not classify as a bug because the code is working as intended. So the bug tracker is just not the place to have this discussion. That doesn't mean it's not welcome, it is! Just not here. A better place would be devtalk.

Will confirm for now, looks like Alpha Clip is not evaluated correctly if the tree is slightly more complex than a simple Mix Shader (where it is still working fine).

@YimingWu (NicksBest) If this is a know limitation, I'm going to tag this task report as this subtype.

Thanks so much Hendrik!

Has this design task been discussed with the UI team prior to creating this ticket?

So you are implying that data loss is more or less fine? And Blender should not help the users here, but punish them instead? That's it?

In T87270#1142616, @TheRedWaxPolice (TheRedWaxPolice) wrote:

Hmm, did you try clicking the icons on the right?

In T87275#1142705, @Georg Bernhard (gogo) wrote:

It was working in 2.97 so i don't consider it a feature request; maybe it's a degradation?

You have made use of the "Viewport clipping" feature which limits your view of the objects in your scene to a select section/angle. The way you activated this was by press Alt+B then clicking and dragging to make your selection. You can disable it with Alt+B. You can also access this function through the top of the 3D viewport by selecting View -> View Regions -> Clipping Region.

It was working in 2.97 so i don't consider it a feature request; maybe it's a degradation?

You have made use of the "Viewport clipping" feature which limits your view of the objects in your scene to a select section/angle. The way you activated this was by press Alt+B then clicking and dragging to make your selection. You can disable it with Alt+B. You can also access this function through the top of the 3D viewport by selecting View -> View Regions -> Clipping Region.

Seems to be a problem with Alpha Clip in this case, Alpha Blend is fine

You have a lot of double vertices (this then has zero-length edges which will mess up the simulation).