Okay.
Anything that needs to be downloaded once to setup vs-dedoldify should end somewhere below the vsdeoldify folder.
This way, I can make a torchAddon with all the stuff in it.
Anything that is generated during runtime should be in a configurable folder.
So that if Hybrid is normally installed, this can be by default set to the temp folder (or in newer versions the engine folder) and changed by the user.
vsdeoldify should throw an error is it can't write to somewhere where is need to write and not silently quit, so that Hybrid and the user can know whats happening.
Cu Selur
Anything that needs to be downloaded once to setup vs-dedoldify should end somewhere below the vsdeoldify folder.
This way, I can make a torchAddon with all the stuff in it.
Anything that is generated during runtime should be in a configurable folder.
So that if Hybrid is normally installed, this can be by default set to the temp folder (or in newer versions the engine folder) and changed by the user.
vsdeoldify should throw an error is it can't write to somewhere where is need to write and not silently quit, so that Hybrid and the user can know whats happening.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.