...OK, so lets say for the sake or argument (and I paid for the ten minute version), one who is working in 4.5 and can load any previous filetype (even .daz) which upon saving gets converted to .duf (hopefully without the shaders getting messed up in the process). Meanwhile lets say a new environment set is released that is in .duf format. Now, as I am using 126.96.36.199 Advanced 64bit basically this says to me the application will not be able to read the file if I try to load it, correct?
So, the way I interpret this is it means if I don’t upgrade to 4.5 (the new “beta” of the Studio app.) I just wasted my money on the new set.
This is what is termed in the automotive and durable goods industry as “planned obsolescence” .
Okay, let’s say for the sake of argument that a new environment set is released in .daz format created in 188.8.131.52. You wouldn’t be able to open that in 184.108.40.206, either. It’s not the switch to .duf that makes DS scene files not backwards compatible, .daz files never were. .duf files will be backwards compatible, so if you use 4..5.0.114 you can open scenes made in 220.127.116.11.