Dear Draw Things Team,
I am writing to highlight a number of serious issues I have encountered with Draw Things, specifically regarding model storage, import, and management—particularly when using an external SSD—and to seek your assistance or clarification.
Here is a detailed summary of my experience:
1. Using an External SSD for Models
I initially configured Draw Things to store all downloaded models on an external SSD via the app’s built-in settings. While this setup appeared to function correctly at first, after updating to the latest version, the app no longer listed the downloaded models, even though the files remained present on the external drive.
2. Re-importing Converted Models
In response, I attempted to re-import the models from the external SSD. However, the app refused to re-import them. These models had originally been downloaded and converted by Draw Things itself, so I expected the app to recognise and allow their re-importation. Unfortunately, this was not the case.
3. Use of Symlinks as an Alternative
I considered using a symbolic link (symlink) to redirect the model folder to the external SSD. I understand that if the SSD is disconnected, the symlink points to a missing location, resulting in access issues. Nevertheless, on macOS, the symlink itself remains visible even when the drive is unplugged; it does not disappear or ‘break’, but simply becomes non-functional until the drive is reconnected.
4. Limitations of the App’s Model Management
Using Draw Things’ built-in folder setting to point to an external drive has proven to be an unreliable long-term solution. After updates or a macOS reinstall, models vanish from the app’s list, and re-importing previously downloaded and converted models is impossible. Users are therefore left with no choice but to re-download hundreds of gigabytes of data, which is both highly inefficient and extremely frustrating.
5. Lack of Direct Support Contact
I attempted to report these issues using the email address listed on your website, only to find that the mailbox does not exist, rendering it impossible to obtain direct support.
6. Critical Failures in Model Storage Handling
If users store models externally by pointing the app to an external folder, the app forgets all installed models after the next update. The same issue occurs when symlinking to an external drive rather than using internal storage. This effectively forces users to either sacrifice significant internal drive space or risk a complete failure of the app’s model handling with every update. It is wholly unacceptable that such a fundamental flaw has not been properly investigated or addressed.
7. Misplaced Priorities and Poor Model Organisation
Rather than prioritising the stability and reliability of the core application, your focus appears to be on releasing new models and features, while the fundamental foundation of the app remains broken. Furthermore, the management of models and their related files is chaotic: all files are dumped into a single folder, with dependencies scattered and poorly named, making it impossible to determine which files belong to which model. Every model should be stored in its own clearly defined directory, with its dependencies contained within it. This is basic, industry-standard software practice, and your failure to implement it demonstrates a serious lack of regard for user experience and system integrity.
8. Memory Management Issues
The application’s memory management is equally poor, compounding the frustrations that users already face.
Summary of the Issues:
• Draw Things does not allow the re-import of previously downloaded and converted models.
• Models stored on external SSDs disappear from the app after updates or system reinstalls.
• The app’s internal database management appears fragile and fails to reliably track models stored outside its own folder structure.
• Symlinks do not solve the core problem of model recognition and may introduce additional risks if the drive disconnects.
• The app’s model storage is poorly organised, with dependencies scattered, making maintenance impossible.
• The application’s memory management is substandard.
• No working support contact is available.
At this point, I am extremely dissatisfied with the app and its repeated failures to function correctly. I am asking clearly: do you intend to address these serious problems with the urgency they deserve?
Draw Things remains a promising tool, but the current approach to model handling and system management significantly undermines its usability, particularly for those relying on external storage.
Thank you for your attention to these matters. I look forward to your response.
Dear Draw Things Team,
I am writing to highlight a number of serious issues I have encountered with Draw Things, specifically regarding model storage, import, and management—particularly when using an external SSD—and to seek your assistance or clarification.
Here is a detailed summary of my experience:
I initially configured Draw Things to store all downloaded models on an external SSD via the app’s built-in settings. While this setup appeared to function correctly at first, after updating to the latest version, the app no longer listed the downloaded models, even though the files remained present on the external drive.
In response, I attempted to re-import the models from the external SSD. However, the app refused to re-import them. These models had originally been downloaded and converted by Draw Things itself, so I expected the app to recognise and allow their re-importation. Unfortunately, this was not the case.
I considered using a symbolic link (symlink) to redirect the model folder to the external SSD. I understand that if the SSD is disconnected, the symlink points to a missing location, resulting in access issues. Nevertheless, on macOS, the symlink itself remains visible even when the drive is unplugged; it does not disappear or ‘break’, but simply becomes non-functional until the drive is reconnected.
Using Draw Things’ built-in folder setting to point to an external drive has proven to be an unreliable long-term solution. After updates or a macOS reinstall, models vanish from the app’s list, and re-importing previously downloaded and converted models is impossible. Users are therefore left with no choice but to re-download hundreds of gigabytes of data, which is both highly inefficient and extremely frustrating.
I attempted to report these issues using the email address listed on your website, only to find that the mailbox does not exist, rendering it impossible to obtain direct support.
If users store models externally by pointing the app to an external folder, the app forgets all installed models after the next update. The same issue occurs when symlinking to an external drive rather than using internal storage. This effectively forces users to either sacrifice significant internal drive space or risk a complete failure of the app’s model handling with every update. It is wholly unacceptable that such a fundamental flaw has not been properly investigated or addressed.
Rather than prioritising the stability and reliability of the core application, your focus appears to be on releasing new models and features, while the fundamental foundation of the app remains broken. Furthermore, the management of models and their related files is chaotic: all files are dumped into a single folder, with dependencies scattered and poorly named, making it impossible to determine which files belong to which model. Every model should be stored in its own clearly defined directory, with its dependencies contained within it. This is basic, industry-standard software practice, and your failure to implement it demonstrates a serious lack of regard for user experience and system integrity.
The application’s memory management is equally poor, compounding the frustrations that users already face.
Summary of the Issues:
• Draw Things does not allow the re-import of previously downloaded and converted models.
• Models stored on external SSDs disappear from the app after updates or system reinstalls.
• The app’s internal database management appears fragile and fails to reliably track models stored outside its own folder structure.
• Symlinks do not solve the core problem of model recognition and may introduce additional risks if the drive disconnects.
• The app’s model storage is poorly organised, with dependencies scattered, making maintenance impossible.
• The application’s memory management is substandard.
• No working support contact is available.
At this point, I am extremely dissatisfied with the app and its repeated failures to function correctly. I am asking clearly: do you intend to address these serious problems with the urgency they deserve?
Draw Things remains a promising tool, but the current approach to model handling and system management significantly undermines its usability, particularly for those relying on external storage.
Thank you for your attention to these matters. I look forward to your response.