Re: Server Crashing on encounter at mos entha

spud wrote:

What is the rotation you are running? and what size maps? to get 24 hours without crashing. We still cannot get a full rotation without crashing. We run two maps, 2 rounds each okay then crashing on 3rd map. We have removed Taooine altogether but still crashes on 3rd map.

We are running Endor, Mos Entha then we had Taooine, it crashed there. Removed it and had Battle as 3rd one now but still crahes on that 3rd map.

Same thing here 3rd map crash Endor, 3rd map crash Tatooine, 3rd map crash Mos eppa.

http://i237.photobucket.com/albums/ff316/Terry7144/terry1copy3ou3ox.jpg
http://i237.photobucket.com/albums/ff316/Terry7144/untitled-2.jpg
http://www.game-monitor.com/server-stat-image/0/FFFFFF/000000/0000FF/000000/206.196.124.10:16567.png

Re: Server Crashing on encounter at mos entha

Oh well crashing every 3rd map is making it impossible to keep running (2142 is not rock solid either) so the guys voted for running BF2 for awhile.

Re: Server Crashing on encounter at mos entha

I've really only just got First Strike running on Linux with it set to 32 slot and have seen a couple of crashes, unfortunately I didn't check the logs for all of them.

However the last crash was with 24 out of 32 on Tatooine, the following is the last thing logged if it's any use:

Debug assertion failed!
Version: 1.08.21.0 Build date:implement unix date here
Module: Object
File: Scene/Object/ObjectManager.cpp
Line: 244
Expression: !(object->getParent())
Text: Object doesn't have a parent, template: imp_support
Current confile:(0)

Before that entry is just normal SetIsManDown entries.

Re: Server Crashing on encounter at mos entha

spud wrote:

Oh well crashing every 3rd map is making it impossible to keep running (2142 is not rock solid either) so the guys voted for running BF2 for awhile.

I know what you mean if I can not figure out how to keep the server going I will have to switch it to something else.


It is a shame no Dev have even tried to help in this thread!

http://i237.photobucket.com/albums/ff316/Terry7144/terry1copy3ou3ox.jpg
http://i237.photobucket.com/albums/ff316/Terry7144/untitled-2.jpg
http://www.game-monitor.com/server-stat-image/0/FFFFFF/000000/0000FF/000000/206.196.124.10:16567.png

Re: Server Crashing on encounter at mos entha

BoC_Terry7144 wrote:
spud wrote:

Oh well crashing every 3rd map is making it impossible to keep running (2142 is not rock solid either) so the guys voted for running BF2 for awhile.

I know what you mean if I can not figure out how to keep the server going I will have to switch it to something else.


It is a shame no Dev have even tried to help in this thread!

I think that's a bit unfair. The Devs (As well as the tester team) have been all over these forums trying to work with people on a 1 on 1 basis in order to resolve the issues the mod is having with server crashes. If you look around these forums, a number of us have stated that we are aware of the Entha crashing bug, but have been unable to track down the source of the problem.

This is a mod, not a professional game, yet we give support better than most commercial retail products I've seen out there. We're doing our best to fix the problems, so please bare with us.

http://img95.imageshack.us/img95/3958/kamphersig4si.jpg

Re: Server Crashing on encounter at mos entha

we can not just Magic up a hey presto abracadabra fix

the lack of a Debugger means we need to find and replicate teh problem in real time and then try to figure out why it's doing it and how to fix it.

This is time consuming and can take weeks.

I don't know what more we can do than continue to work until we fix it?

http://i193.photobucket.com/albums/z261/The_Preacher1983/1c1e0ba0.jpg

Re: Server Crashing on encounter at mos entha

No offence guys, we know you worked hard on this and it is a mod. We are just posting the problems we are having trying to compare notes. I must admit though we did get a bit frustrated.

We are going to start it up again and run a day or two and see what happens. One thing we are going to try now is just run two maps and see when and if it crashes.

We do appreciate all your work