Filetexture not loading when Opening Gamma but doing it when F8-F5 recompilation

vvvv gamma question
7

I would take a closer look at this problem. I’m not sure, but for some reason I can’t find a node that can be guaranteed to open an image in a blocking style. As a result, there are constant errors related to the texture becoming NULL for a short time. It’s very hard to keep track of them. Also, as I said above, this node can’t be used in some cases because it needs to be constantly updated, otherwise the texture simply won’t go to the output in many cases.

I have a case that uses this node and managing the texture state is turning into a very difficult quest that I can’t solve. I need to make sure that all textures are loaded after something has changed in the file list, and only then perform actions. It turns out that I need to somehow deal with asynchronous behavior, but without an asynchronous api.