I keep getting this error message in firestorm when I try to upload a mesh
LOD Model has no parent
I have no Idea how to fix this, Does anyone?

When i get that i just open it in blender, save it (rename it if you feel like saving the original) without doing any changes. It then should "fix" that and be able to upload.

When i get that i just open it in blender, save it (rename it if you feel like saving the original) without doing any changes. It then should "fix" that and be able to upload.

Do you think you could maybe post a step by step the process please?
I tried Import DAE -> export DAE but i think the rigging gets a bit broken

Maybe i am missing a step somewhere thats relevant

Thank you!

@gilaraujo, you just joined this forum and now you having questions about step by step
read the rules and helps from step 1-6 everything what you need to know is in there, you can also search on youtube 

[To see links please register here]

Understandably so. Googling the Error mentioned in this thread brought me here, i did try to replicate the solution given, but got strange results, ence why i registered to ask the question

I do understand what you mean though.

I have the same issue for days and haven't been able to find a solution to it. Anything new?

in step 1-6 are the rules and most helps you need, also how to upload mesh
this is also handy to read, or use the search, 

most of the time it gives this error LOD Model has no parent then the dae file isnt ok,
what Tonix said is the best import it in Blender looks how it looks like, and save it, 
and try it again

I had this issue and found this thread ...  i realised after much messing around that the object I had exported to collada was parented to another object in Blender ... clearing the parenting and re-exporting fixed it for me ...

hope this helps

go to top task bar Advanced>>Show Debug Settings>>ImporterLegacyMatching and make sure it is set to true.. Your rigging stays intact.. You might also need to do this every time you relog, I have had to on 6.4.21.

@MzDemeaner Thanks! I had this error and your solution fixed my issues <3