The uploader stopped halfway, so here's this:
For a reason I can not discern, some blueprints of mine were corruppted, and refused to spawn, showing only the square on the hud, which would dissappear after a moment. Curious, I headed into my blueprints folder and poked around some files, and found that the uncorrupted blueprints (Lets use my mining ship, GFS_Sokolov, for example) had a SMD2 file in the DATA folder called ENTITY_SHIP_GFS_Sokolov.0.0.0.smd2. Ok, nothing unusual there, but if we go to a corrupted blueprint (Repair_skiff), but istead of ENTITY_SHIP_Repair_skiff.0.0.0.smd2, Q0-BbGom4xK5MqLctEKe8ylJ.0.0.0.smd2 shows in the DATA folder. Well, there's the problem. Making a duplicate file called Repair_skiff_test, and naming the SMD2 file correctly, remedied the problem. Oddly, though, all my uncorrupted files were the ones I had exported.
Aside from asking you to check the difference between exported and unexported files, I can't help with the fix, but that's that.
For a reason I can not discern, some blueprints of mine were corruppted, and refused to spawn, showing only the square on the hud, which would dissappear after a moment. Curious, I headed into my blueprints folder and poked around some files, and found that the uncorrupted blueprints (Lets use my mining ship, GFS_Sokolov, for example) had a SMD2 file in the DATA folder called ENTITY_SHIP_GFS_Sokolov.0.0.0.smd2. Ok, nothing unusual there, but if we go to a corrupted blueprint (Repair_skiff), but istead of ENTITY_SHIP_Repair_skiff.0.0.0.smd2, Q0-BbGom4xK5MqLctEKe8ylJ.0.0.0.smd2 shows in the DATA folder. Well, there's the problem. Making a duplicate file called Repair_skiff_test, and naming the SMD2 file correctly, remedied the problem. Oddly, though, all my uncorrupted files were the ones I had exported.
Aside from asking you to check the difference between exported and unexported files, I can't help with the fix, but that's that.