Author Topic: Server crashes after changing track  (Read 1030 times)

Me and Megaguy made a track, and well, when it's time to change the track, instead of normally fading away to show up a new track, the game turns in to a black screen, and if I don't wait it just crash, but if I wait, I go back to the main menu, and I get that message

And I really don't know what to do, I tried a lot of things but this is the only problem I'm having

Did you use any non-default bricks in the track? Have you checked that the speedkart track file hasn't got anything wrong in it?

Did you use any non-default bricks in the track? Have you checked that the speedkart track file hasn't got anything wrong in it?
uses all default bricks


I was there. Your server isn't crashing.

Your new track, Big hills (or what ever it was called) is a huge track! It took me almost 2 minutes, but it finally loaded the track, same with un loading. It took so long, I was actually in the start box with the light already green when I was finally able to move again.

The timeout means it shut down cause you lagged forever.

Take out your new track and it should all work again. (Even though I loved it)

this isn't about the server crashing this is about getting the track to work.

There is just so much in the track. Lots of bots, and bricks. You'll have to down size a little. Find some 8x8's and replace them with 16x16's. Just little things like that.

It's pointless to have the track if the server doesn't work. What do you have to lose?

Try cutting down on bots first.

There is just so much in the track. Lots of bots, and bricks. You'll have to down size a little. Find some 8x8's and replace them with 16x16's. Just little things like that.

It's pointless to have the track if the server doesn't work. What do you have to lose?

Try cutting down on bots first.
I reduced most of that stuff on the last time

I reduced most of that stuff on the last time

Is it still crashing?

Yes - Reduce more or remove the track entirely
No - Hooray

The map cycle feature seems pretty inefficient.

The map cycle feature seems pretty inefficient.
Yeah that's probably the problem

I reduced the brick count, removed a few bots, fixed some stuff on the track, the "TimedOut" problem still persists, *sigh*...

Yea, I actually have this problem on a track I made. But it's only on that one. I made a second one with about 7000 bricks and it loads.

I think it occurs when bricks get to far away from spawns. This is just a guess but seems to be the issue for me.


Console.log please
No wait, type trace(1); in console and then try to change tracks.
If it crashes, please attach console.log