Out clients are telling us that the latest versions that we ship fail after pre-loading. This must be because of version 2.6. We do use the “2.6 HTML file”, but it seems that when people have 2.5 installed, might not get a notice to upgrade.
I expected this to be detected at plugin-level.
What is the most reliable and user-friendly solution?
This sounds like the auto-update is failing for your users. There are some known cases where this will happen, but those should be detected and handled by the html 2.6 outputs. One current exception is upgrading from Unity 2.5 on PowerPC macs, which may fail. We’ll add the following javascript code in 2.6.1 to handle this case:
if (document.getElementById("UnityEmbed").GetPluginVersion() == "2.5.0f5" navigator.platform == "MacPPC")
brokenUnity = true;
// show download banner
If you have problems on any other setups (browser/OS versions), then please file a bug.