Blender is a popular 3D modeling software that offers a wide range of features, including the ability to import various file formats. However, sometimes the software may fail to import a file with no error message, leaving the user clueless about how to proceed.
In this article, we will show you how to get around a Dae import issue in Blender with a complete retread of Chris Sacca printing solution and a little extra detail for people who haven’t messed around in the shell before.
To begin with, let’s consider an example. Suppose you are trying to import a Dae file into Blender, but it fails to import, providing you with no information at all. In such cases, the solution is to manually edit the file you want to import.
To get an idea of what’s happening, we’re going to run Blender from the shell. To run it on a Linux distro, you won’t have any issues navigating using a shell. For Windows, it’s super simple; just go to the folder where Blender is installed, hold Shift and right-click. In Windows 10, select “Open PowerShell here.” All the windows are roughly the same, saying Shift+right-click shell.
Next, we’ll type “./blender” to boot Blender with the PowerShell running in the background so that we can figure out what the issue is.
Now, let’s try the import again. Go to “File,” then “Import,” and select “Colada Dae.” Try importing the same file again, and if you get nothing, this time, bring up the shell, and you’ll see a line that tells us what went wrong. In our case, it was “texture with the S ID map seven image not found in effect with ID default in material effects.”
We need to manually edit the file we’re trying to import, delete the effect that’s causing the issue and halting the importance, and save it. Luckily, most 3D formats are pretty much as XML files, so opening them up into a text editor and finding what you’re looking for is a breeze.
In our case, we made a copy of the file and opened it with Notepad++. Within the library effects tags, we identified the effect ID default material FX, which was causing the issue. We identified the entire block that belongs to this effect, highlighted it, and deleted it.
It’s worth noting that we kept the library effects tags intact over here because without them, you’re going to open yourself up to a whole different error.
Finally, we saved the file, closed it, and tried to import the new file that we created. This time, the problem was solved, and everything was working perfectly.
In conclusion, with just a little bit of manual editing, we managed to bypass Blender’s import issue. The version info is in the description, but obviously, the solution shouldn’t be that dependent on your Blender version as long as they can import the AE. Now that you’ve learned how to open Dae files in Blender, it’s time to get creative and let your imagination take over.