Client side and torch crash in SWSE
Hello, this is Palpatine, the owner of this mod, SWSE and the accompanying community and server cluster. We operate 20 servers and use nexus to connect them.
We are currently suffering from a bug that I caused in a recent mod update to do with planets.
The crash doesn't happen to everyone and it doesn't happen all the time, hence why it got pushed live.
Now we have around half of our players unable to join the server and of that half that can many are taking 5-10 tries to get into the server at witch point its completely random when they crash out again.
The text of the crash doesn't clearly specify where the issue is at or give hints any of the other modders or myself were able read.
In the attached SWSE_log file you can find my player logs and the torch logs from the live dedicated server where the problem was present, I started a torch running only SWSE that has a few planets in it, I attempted to join off a fresh load of my game and zipped up everything after the crash to send here.
Any direction as to where the problem may be would be greatly appreciated so I can move forward without a large roll back on mod development, thank you in advance for your time in reading and any advice your able to provide.
-Palpatine.
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards
Keen Software House
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards
Keen Software House
Hello, Sheev Palpatine,
I am sorry you are experiencing this issue. Here are my suggestions to figure out where the problem is:
Thank you for letting me know what were your findings.
Kind regards,
Keen Software House: QA Department
Hello, Sheev Palpatine,
I am sorry you are experiencing this issue. Here are my suggestions to figure out where the problem is:
Thank you for letting me know what were your findings.
Kind regards,
Keen Software House: QA Department
It was spiders! I found it by doing line by line checks on every reference in the planets to make sure I didn't have any mistakes.
We had very old modified spiders that were never used and I thought I cleared all their references out but somehow they made it back onto one of the planets, upon removing them logs started generating normally and I was able to see a single letter mistake in a voxel material reference in another planet. After fixing both of those there were no more errors and everything works as intended.
In conclusion for this report, there was an instance where a missing reference to a spider led to debugging not working witch hid the actual crash reason, a misspelled voxel reference.
Sorry for the confusion, it was totally my mistake but not being able to see what the mistake was just kinda strange.
It was spiders! I found it by doing line by line checks on every reference in the planets to make sure I didn't have any mistakes.
We had very old modified spiders that were never used and I thought I cleared all their references out but somehow they made it back onto one of the planets, upon removing them logs started generating normally and I was able to see a single letter mistake in a voxel material reference in another planet. After fixing both of those there were no more errors and everything works as intended.
In conclusion for this report, there was an instance where a missing reference to a spider led to debugging not working witch hid the actual crash reason, a misspelled voxel reference.
Sorry for the confusion, it was totally my mistake but not being able to see what the mistake was just kinda strange.
Hello, Sheev Palpatine,
I am glad you managed to find the root of your problem :) I will close this thread now since there is no assistance from me needed anymore. But please do not hesitate to contact us again.
Happy engineering!
Kind regards,
Keen Software House: QA Department
Hello, Sheev Palpatine,
I am glad you managed to find the root of your problem :) I will close this thread now since there is no assistance from me needed anymore. But please do not hesitate to contact us again.
Happy engineering!
Kind regards,
Keen Software House: QA Department
Replies have been locked on this page!