Render Cache Starts Over When Switched to Proxy Resolution

When you have the smart render cache enabled and it has rendered sections of a timeline in the background, if you switch to a proxy resolution the cache it disabled. If you switch back, it restarts from scratch as if the frames were never rendered. Is this be design or a bug in 15 beta 2? It seems to me that these files could be temporarily unused when proxy mode is on, and then enabled again when switched back to full resolution. Or they could take precedence over half or quarter resolution proxy versions, as they are pre-rendered frames, usually in ProRes/DNx/Cineform so reasonably easy to play. I'm new to resolve as of version 15 beta 1, so maybe this is the way it's designed. If so, this is just a suggestion, if not, it's a bug report.

This is still the case in 15.0.1.003 (OS X). Pretty frustrating, if you ask me.

When I stabilized the footage it also delete all the cache which was not great fun. Also had a few cases where I added a new node and the cached nodes needed to be redone for no reason.

This is still the case in 15.0.1.003 (OS X). Pretty frustrating, if you ask me.

Very frustrating. what is the point of the cache if you have to stay at full res to use it or risk having to wait again for the timeline to be cached?

When I stabilized the footage it also delete all the cache which was not great fun. Also had a few cases where I added a new node and the cached nodes needed to be redone for no reason.

For stabilization that makes sense to me since it is processed before nodes are, so anything down the pipeline from the stabilization is affected by stabilization.

When I stabilized the footage it also delete all the cache which was not great fun. Also had a few cases where I added a new node and the cached nodes needed to be redone for no reason.

For stabilization that makes sense to me since it is processed before nodes are, so anything down the pipeline from the stabilization is affected by stabilization.

Hm, but wouldnt it make sense to do the stabilization later in the chain at least as an option?
/Andreas

When I stabilized the footage it also delete all the cache which was not great fun. Also had a few cases where I added a new node and the cached nodes needed to be redone for no reason.

For stabilization that makes sense to me since it is processed before nodes are, so anything down the pipeline from the stabilization is affected by stabilization.

Hm, but wouldnt it make sense to do the stabilization later in the chain at least as an option?
/Andreas

Possibly! I'm not sure about that.