At least in previous releases, plugins always need re-compiled between
minor versions (e.g a plugin for 10.0v1 will work in 10.0v2, but not
10.1v*). They might work without source code changes (i.e the API is
same), but the binary compatiblity is broken
(somewhat tangentially, anyone know why this release is 10.5v1 not
10.1v1? Seems.. confusing going from 10.0v5 to 10.5v1..)
On 10/12/16 06:53, Deke Kincaid wrote:
Does anyone know if Nuke 10.5 breaks backwards compatibility with
plugins? The manuals & release notes do not mention this.
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
ben dickson
2D TD | [email protected]
rising sun pictures | www.rsp.com.au
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
