MolecularNodes: Problem with the Atomium instalation on windows?

I get the error below when trying to import a pdb-file, online or localy.

I have followed the steps in the instalation guide: I run Blender as an administrator on Windows 10, and after installing the add-on, i click the button to install Atomium. I get a confirmation that Atomium is successfully installed.

In the MolecularNodes panel i click the “Download” / “Open” button and get the error below. I assume the it is because the Atomium library is not properly installed.

Python: Traceback (most recent call last):
  File "C:\Users\Jonas\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\molecular_nodes\__init__.py", line 1401, in execute
    sna_func_import_structure_EE5B6(bpy.context.scene.sna_pdb_code,
  File "C:\Users\Jonas\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\molecular_nodes\__init__.py", line 1134, in sna_func_import_structure_EE5B6
    pdb = atomium.fetch(pdb_id)
UnboundLocalError: local variable 'atomium' referenced before assignment

location: <unknown location>:-1

I am very curious to try this amazing add-on, hope that you can help resolve the issue.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 36 (17 by maintainers)

Most upvoted comments

0.3.8 release worked for me aswell, and probably there is no need to run Blender as administrator.

emalacs on Apr 28, 2022

Success 😃 The 0.3.8 release of the add-on resolves the issue. At least on my Windows 10 installation. I removed the old version of the add-on in Blender. Restarted as administrator, and installed version 0.3.8 of the add-on, following the normal procedure. After that I was able to download pdb-files. Opening local files also works. Running Blender as a regular user afterwards also works.

Do we now have Atomium installed two places, or is the add-on just loading Atomium from the other install location?

chromascope on Apr 28, 2022

Ah yes I the path will just need re-registering every time I try to use it.

The 0.3.8 release should fix that! Thanks for all of the detailed feedback so far 😃

BradyAJohnston on Apr 28, 2022

From the Blender 3.1 Release Notes:

Python has been upgraded from version 3.9 to 3.10, there are some changes that may impact script authors.

Might be that there is a change in how python handles these things itself, that is causing the issue.

BradyAJohnston on Apr 28, 2022

Okay that is an interesting development!

Some of the nodes might not work in 3.0.1, but once you have imported the structure you should be able to open it up inside of 3.1 without issue. Atomium is only used for the initial import step.

BradyAJohnston on Apr 27, 2022