normaly it starts with rising conect bars, up to 50% from the screen
mostly someone else disconnect and the error message come up
afterwards the connect bars go down and all works as normal.
the hole process is about 4-8 sec. long

i know this message very well since old demo times
it change a bit how often i see it,
from 2-3 time per hour up to once in a week.
never had the prob that i lost the connect myself.

other experience?
anyone knows what "MP replay out of stash space" means?
is it a client failure, server side or a bug?
every else info is welcome

The "MP replay stash" is the multiplayer stack which stores the information used to create an mpr. When this needs to be recovered its (probably) because the stash is about to overflow. Therefore you can work it out as a client side thing.

Out of interest, how much RAM do you have in your machine?

sounds logical that is client side with the mpr stash,
but why mostly someone else disconnect at the same time?
is it maybe some "bytes" from the server are wrong
and messed it up for everyone, most survive it, some not?
possible?

since a short time I have 1 GB ram, before 512.
duno if its better with more ram, never compare it really.

There used to be an old old bug which sounds very similar to this - but in theory it was fixed.

Are you using Patch P2? Has S2 always done this for you? Which processor, and OS are you running?

Edit:
Do you also get extreme lag when this occurs?

Probably a stupid question as you will have already checked, but are you running other memory or CPU intensive apps at the same time?

I always close stuff in the system tray I dont need and always close all foreground apps (IE, Firefox etc can use a bit of memory sometimes).

Although sounds daft with 1GB ram, should be fine!

Good luck.

yep, P2 and win-xp on amd-xp with barton core.
but i know this since demo times 2.5 years ago
and had some hardware changes over the time.
i have a own win-game-install were i disable every unnessary things,
so nothing in backround.

to be honest, i never thought it was on my side because
mostly others have probs at the same time too (disco).
i will try it with less ram and with disabled replays next days
to see whats happens.

edit:
normaly it was one very small lag before the connect bars go back down,
similar to the old pit lag.

I am sorry about opening this thread after that long time, but LFS suddenly started to give this message to me. I got and error "MP Replay: Out of stash" and after a while another. "MP Replay: Stash restored(or something like that)". When this message appears, I lose connection to server with messages "<racername>: Sync error"

The only change I made in my system is replacing the Kerio Personal Firewall by Kerion WinRoute firewall, because I have a network at home now.

I will try to disable the firewall and see if it can help.

My spec:
P4E 3.2 GHz
1GB RAM DDR2
GF6600GT
Asus i915 chipet MoBo
WinXP Pro SP2 + latest patches

I don't think it's the firewall. I've been racing for a while now, online, and just the last few days it happens to me to. I wonder what's causing it, I think it happens in a race, with too many laps, and too many cars, for the replay to handle.

Is the replay saved on the server as well? Because it seems only to happen if a lotta things have happend in the race. If it's a very quite race, it most likely won't happen. We need a dev on this, I think.

yeah, had this one b4 2, happens from time to time...maybe theres a limit of the size of the mpr, so it will recover b4 overwriting itself...

btw: whuz that : bug: too many physics objects

Sorry to open this up again

I am running 2 servers and this problem is now showing itself up on one of them

This server "[CD] ConeDodgers Racing" is always busy bit I have noticed that its only happens when the server is full or almost full and never when there are say 15 racers on

If this is client related should it not happen all the time?

I had this message today for the first time, on the Redline Aston Club FOX server.
Only thing I changed was set the save replay to automatically. Could that be the cause?

I have plenty of HD space, and 2 Gb memory.

nope - i think the fault is server-side