5
« on: 2025-05-14, 15:50:26 »
Other way round Avi, a file made in new Corona crashes old Corona :)
Thing is, Corona 12 had significant changes to the VFB, tone mapping, automatic exposure, lightmix, and more. This is why it isn't as simple as F10 to reset settings, as there are things that the old Corona just know what to do with.
BTW, rather than "change to a different render engine and export", you can just save with Corona and try merging the new scene into the old version of Corona rather than loading it, because then Corona shouldn't try to read all the new things it doesn't understand (though you may still lose some settings, parameters, features, etc. in doing so).
If someone is making models to share (rather than scenes), it should be less of an issue than for sharing a whole scene, and they can carefully avoid using any new features to maximize the chance that it can be merged into an old Corona.
Beyond that, they'd then just make the judgment call - do they want to take advantage of new features in the latest version of Corona getting some results that couldn't be achieved any other way while narrowing the users who can use it, vs. do they want to maximize who can use it but give up on some new features that could make the model/scene better, and based on that choose to develop the model in an older or newer version of Corona (the multiloader makes it easy enough to be able to run Max with different Corona versions, so no need to be installing and uninstalling all the time).
The only way to "fix" it would be to stop working on Corona 13 or 14, and go back and edit code in 11, 10, 9... where would we stop too? Since development time is limited, that isn't going to happen (and indeed no software I know of does this).