Before an Extension Stops Loading: A Practical Guide to SAMSON Versions

A molecular modeling session can depend on more than the SAMSON application itself. You may also rely on extensions for particular tools or workflows. If an extension was built for a different SAMSON SDK version, it may not load in your installed application—or it may not receive an available update. Knowing which version numbers matter can help you diagnose the problem before it interrupts your work.

Three version numbers, three different jobs

SAMSON uses a public version and an internal version. The public version is the one you may see described as 2026 R1. Internally, SAMSON and its SDK use a three-part number such as 11.0.0, following a semantic versioning format: major.minor.patch.

The internal number describes changes to SAMSON and its SDK. In general, a major change signals a non-backwards-compatible update; a minor change adds functionality while remaining backwards-compatible; and a patch change is a backwards-compatible bug fix. During the beta period, the numbering rules are different, so check the versioning guidance rather than assuming the standard pattern applies.

Extensions also have their own version numbers. That number can tell you that an extension has been updated, but it does not by itself establish whether the extension can run in your copy of SAMSON. For compatibility, SAMSON checks the SDK version that was used to build the extension.

The key compatibility check

According to SAMSON’s compatibility rule, the SDK and SAMSON must have the same major version, and the SDK minor version must be lower than SAMSON’s minor version. In practical terms, an extension built with an SDK from a different major version should not be expected to load. An extension built with a newer minor SDK version may also rely on functionality that an older SAMSON release does not have.

For example, the documentation explains that an extension built with SDK 1.5.2 can load in SAMSON 1.7.8, because the major versions match and the SDK minor version is earlier. By contrast, SDK 1.8.5 is not compatible with SAMSON 1.7.8: the SDK is from a later minor version and may include functions that the installed application does not provide.

This distinction is useful when troubleshooting. If an extension is missing or fails to load after an application change, check the installed SAMSON version and the SDK version used to build that extension. The extension’s own release number is not a substitute for the SDK build version.

What automatic extension updates do—and do not do

When an internet connection is available, SAMSON can automatically update extensions at startup when compatible versions are available on SAMSON Connect. The application does not simply install the newest extension release regardless of compatibility: it considers whether the SDK version used to build that release is compatible with the SAMSON version you have installed.

Suppose your application is SAMSON 1.7.8 and your extension was built with SDK 1.5.2. If a compatible release built with SDK 1.6.4 becomes available, SAMSON can update the extension. But if SAMSON 2.0.0 and its SDK are released, an extension built for that new major version will not be installed as an update for someone who remains on SAMSON 1.7.8. The existing compatible extension can remain in use instead.

A quick check before changing your setup

  • Find your SAMSON version. The public release label and internal SDK version are different identifiers; the current documentation lists public version 2026 R1 as internally based on 11.0.0.
  • Check the extension’s build SDK. Compatibility is based on this version, not just the extension’s own version number.
  • Keep SAMSON updated when practical. Updates can provide fixes and new features, and can make compatible extension releases available to you.
  • When developing extensions, consider the users’ installed versions. A release built against a newer SDK may not work for users who have not updated SAMSON.

These checks can help distinguish an extension update from an application-version mismatch, and make it easier to plan updates around the tools your modeling workflow depends on. For the full rules and examples, see the SAMSON versioning documentation.

Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.

Comments are closed.