The Cache of Sapphire node disappears. (Resolved)

Hi,

I have a issue for a few years with OFX Sapphire. This issue is specific to V17 and V18. Both Fusion Studio and Fusion Page.

When using Sapphire with Fusion, the RAM Cache is deleted periodically. Moreover, only the cache of the Sapphire node disappears and other nodes are not affected.
Recently, I finally found the trigger for the cache to disappear. It is during "save".
The moment I type Ctrl+S, the cache of the Sapphire node disappears. The reason it happens regularly is that there is an "autosave" working behind the scenes. The task manager shows that the main RAM and GPU RAM are purged a bit at the moment of saving.

Some people seem to have no cache issue, and I don't know the underlying cause. BorisFX says the cash is managed by Fusion. But this issue is only for Sapphire.

Is anyone else having the same issue?

Is anyone using Sapphire in fusion? Or does no one have a problem?

I have always had some problems with Fusion and Sapphire for almost 20 years. I am surprised at the lack of response.

I tested on my old MacBook Pro (7gen Core i7 / Intel Iris Plus 650).

To my surprise, the same thing happened. The cache of the Sapphire node is purged the moment it is saved.

I think this issue is not caused by my environment, but by Fusion v17 and v18! It is a wonder no one has faced this issue.

May this topic be brought to the attention of the dev team.

I suspect you're one of the few who uses Sapphire. I've never considered it worth the price. We did have one license at Muse, but it was very rarely employed because a comp that used it couldn't render on the farm. I think we only had it because a client had fallen in love with one very specific lens flare or something like that.

I don't use it all the time, but whether it's worth it depends on who you are. But I seem to be in the minority.

This issue will be resolved in the near future, sorry for doubting Fusion.

Thank you.

I've been watching this bug since version 16 of Fusion. There is a suspicion that this happened without using Sapphire in the scene. Perhaps he indirectly influenced this. This is one of those unpleasant moments that kept me from switching from the 9th version of Fusion to the new versions. Recently, something has changed and this cache reset bug has become much rarer, mainly after autosaving an open scene.

The cache bug has been resolved in Sapphire 2023.5.

Fusion Studio v18.1.3 / Windows 10.