if you sava a .duf with v2 being active it will contain v2 data. the plugin _needs_ to re-append any of it's internal data to the a saved file whenever save happens, otherwise it won't contain any of its data; and of course it needs to convert old v1.20 octane data to v1.55/v2.12 in order to render it. unfortunately i don't see a way to avoid that.kraken wrote:What this means is that BEFORE you install the new version, make a COPY of your .duf file and label it v1 or v2 so that you can downgrade without losing your work. Opening a file and saving it as-is will make it incompatible.
it's of course always good idea to make backups.
if you lost something you can send me the .duf - i may either clean out the data so it loads in v1 (without crashing and without octane data), in addition v1 saves backups of the internal data into
%homepath%\OctaneRender\Backups
which may be reapplied to a v1 scene...