A molecular model can be ready to explore while the workstation is not. An unsupported operating system, an unavailable OpenGL feature, or a missing Linux library can stop SAMSON before you reach the structure you want to work on. Checking these basics first can save time—especially when preparing a new computer, troubleshooting a launch problem, or setting up a shared teaching lab.
Use this preflight guide to identify the most common compatibility issues before installing or launching SAMSON.
1. Check the operating system
The current support matrix lists Windows 10 and Windows 11; Ubuntu 22.04 and newer; Fedora 42 and newer; CentOS and similar Linux distributions; and macOS Tahoe (26), Sequoia (15), Sonoma (14), Ventura (13), and Monterey (12). The listed macOS versions support both Intel and Apple Silicon.
“May work” is not the same as “tested”: older platforms are not part of the currently tested support matrix. If you are diagnosing a problem on an older system, first establish whether your operating system is among the versions listed above. That gives you a useful starting point before investigating drivers or application settings.
2. Verify the graphics path—not just the computer’s age
SAMSON requires a 64-bit operating system and a graphics card that supports OpenGL 4.1. For NVIDIA or AMD GPUs, the documentation recommends using the latest drivers. A machine can meet the operating-system requirement and still fall short if its graphics hardware or driver does not provide the required OpenGL support.
This check matters particularly on virtual machines. If you run SAMSON in a VM, enable hardware GPU acceleration. Without it, the OpenGL features SAMSON needs may be unavailable. In other words, a VM’s ability to start an operating system does not by itself confirm that its graphics path is ready for molecular visualization.
3. Treat Linux libraries as a separate check
On Linux, some libraries may need to be installed before the application runs correctly. For Ubuntu-like systems, the documentation lists these packages as possible requirements:
|
1 |
sudo apt install libxcb-cursor0 libatomic1 |
For CentOS-like systems, it lists:
|
1 |
sudo dnf install xcb-util* |
These are conditional suggestions, not a guarantee that every installation needs the same packages. If OpenGL libraries are missing or incorrectly configured, use the documentation’s Linux OpenGL driver instructions to continue troubleshooting.
4. Use a simple order of operations
- Confirm the platform: check that your operating system and version appear in the supported list.
- Check graphics capability: verify OpenGL 4.1 support and, where applicable, update NVIDIA or AMD drivers.
- If using a VM: confirm that hardware GPU acceleration is enabled.
- If using Linux: check whether the listed libraries are needed, then investigate OpenGL configuration if the issue remains.
- Only then continue setup: make sure you can access your account and installer on SAMSON Connect, and follow the installation guide.
This order helps separate three different questions: Is the platform supported? Can the graphics system provide the required OpenGL support? Are any operating-system libraries missing? Keeping them distinct makes troubleshooting clearer and helps avoid changing unrelated settings.
For shared workstations and teaching labs
Before deploying across a group of computers, test the graphics path on a representative machine. Check the operating system, GPU and driver situation, and any VM configuration, then confirm that SAMSON launches. A small test before broad deployment can reveal a graphics or dependency issue while it is still easy to investigate.
For the complete requirements and platform details, see the SAMSON requirements and platforms page.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.