This is very strange I was messing around with some of my old blueprints on the dev build and noticed when it spawned it only spawned a nav marker and nothing else but when I tried this with new blueprints it worked perfectly fine. All blueprints in the catalog from before a few updates back are affected. Not sure if this is replicateable or the blueprints from older patches somehow got corrupted but it is very bothersome.
Description
Details
- Task Type
- Bug
- Affected Gamemode(s)
- Singleplayer
- Reproducible
- uncertain
- Last tested (version)
- 0.198.476
- Category
- none/unspecified
- First occurrence (version)
- 0.198.471
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- Intel
- Video Card Model
- Intel
- Try to spawn in a blueprint from the catalog that is a few updates old.
Not sure if this is isolated to my copy of the game or not.
Related Objects
- Mentioned In
- T2419: Ethereal Entity / Ghost Ship
Event Timeline
-Feedback-
Looking at your logs, it doesn't spawn because the ship has no ship core. This is something that would only occur if you're trying to load a chunk 16 blueprint into a chunk 32 build. It is however a smd3 file so something must have gone wrong during conversion.
Is there a chance that you have used these blueprint/this installation folder in one of the dev builds right before the release of chunk 32?
Before 0.199.132
In that case, most likely all your blueprints were converted when it still wasn't working properly, and are now marked as converted. It's something that is already fixed.
Go check your starmade folder and look for a compressed file named CHUNK 16 Blueprints or something similar like that.
If you have one, take a back up of your blueprint folder, then delete what is inside.
Extract the chunk 16 blueprints into your blueprints folder and then boot up the game again. It should convert them when trying to load SP and then check if they work or not.
EDIT: Your first occurence and last tested versions are ...confusing. Both are before chunk 32 and the log you've sent is from 0.199.176
-rejected-
Must have been a conversion error, which was reported and resolved close after its release. No feedback so I'm assuming it's fine now.