Automatic Sdf Downloading Is Disabled Or Failed. [work] Now

Enabling the feature didn’t solve things; it just changed the error message. Now, instead of silence, I get a pop-up: “Failed to download SDF data for [asset name]. Check connection or repository URL.”

Until the automatic SDF downloading works reliably – or at least fails gracefully with user-friendly diagnostics – I cannot recommend this software for any serious workflow that depends on external SDF data. The manual workaround exists, but it’s so tedious that it negates the software’s efficiency gains elsewhere.

Let me break down the experience.

SDFs are crucial for representing 3D shapes, collision detection, or visualizing molecular surfaces. In this software, the ability to fetch SDF data automatically from a remote repository or database is a advertised as a time-saver. Instead of manually locating, downloading, and importing .sdf files, the program should handle it seamlessly in the background.

Please prioritize a hotfix. Make auto-download default ON, and add a connection test tool. Users shouldn’t have to become network engineers to load a basic SDF asset. automatic sdf downloading is disabled or failed.

First, I noticed that nothing was happening when I tried to load assets that clearly required SDF data. After digging through three levels of nested menus, I found the culprit: Why? There’s no clear explanation in the documentation. Is it a security precaution? A bandwidth-saving measure? A licensing issue? The user is left guessing.

I toggled it to , expecting relief. That’s when the real problems began. Enabling the feature didn’t solve things; it just

I’m keeping it installed and checking for updates. The moment this feature is fixed, my rating jumps to a 4 or 5. But as of today, it’s a frustrating bottleneck that should have been caught in QA.