Splintert said:Vornne must have forgotten to put in the changelog that he applied a death clock so people don't play too much
Yep, -10 degrees celcius, get the sun bed out!BlitzKrieg-BoB said:But it's so bright outside... I might even get a tan with all this snow!
Shinobido said:What are you talkin about! Germany feels like Stalingrad at the moment. A few weeks ago it was alright and we didnt had to turn the heater on 4-5 which is pretty much full power.
Damn good old times throwing snow at everyone and everything
Conceivable, but I crash and I have never glitched, nor have I used an item intended for a higher class.Nimueh said:We were thinking some of the glitches could be causing the clients to crass. I'm not a python guru but one thing out of wack could cause the issue. It just makes it hard because you haven't crashed on your end yet.
Splintert said:It doesn't matter how good a computer someone has, 32-bit applications can never use more than 3GB of RAM (which is why it crashes at 2.9GB).
Go for it.Splintert said:Also, are there any restrictions on editing the default map and releasing it as an extended version or something? I've always personally liked the overall layout, it just needs a few tweaks. Most of the playerbase hasn't even seen it by this point.
I wondered about that, but haven't seen anything conclusive to support that guess yet.BlitzKrieg-BoB said:Now I don't necissarily crash everytime I am mounting a horse myself, but I am curious if it might have something to do with the new animations?
Can't see the thread; but in any case I have no interest in developing a new game for money. PW development is done just for fun, and I want to keep it that way.Aldric said:Crpg is fund raising to get their own game. While it's not similar to PW4 it's interesting to see how they plan this.
OK, thank you for trying.BlitzKrieg-BoB said:This was on a non-steam version I downloaded to test that theorie. MYTH BUSTED!!! .... .... yeah, it still sucks though.
Has the beta6 default scene ever caused you to crash?BlitzKrieg-BoB said:It would also explain why some maps have the error and others don't.
Nimueh said:I am having alot of complaints about clients crashing as soon as they join the server now. I don't really know what to tell them. Everything was fine until we moved to beta6.
Nimueh said:The crashing is getting very bad, it has killed our population, and no NA server has any players besides our 16-26 who say they crash sometimes but can still stay on for a while. I don't know what to do. Should we roll back to beta5 until this is worked out?
That sort of moaning is very annoying: I stated in the release announcement that I expected bugs, so servers that didn't want to test it should not update, and then restated it in this thread more recently. If you don't want to help test, leave new versions alone, don't come whining to me.Nimueh said:Ok we are going to rollback. Beta6 is totally unplayable for 68% of people. lame.
S0mebody said:
Crashed at that point.
ongre said:There you go, crashed at ~2900mb each time too.
Ahh, that's a starting point. I finally got the same problem after about 3 or 4 hours connected to a server (only 10 - 20 players though, less around in the evenings at my time zone).S0mebody said:One hour 27 minutes then:
Server had 39 players. Higher player count appeared to accelerate the leak.
While your and other people's testing has been very helpful, the problem has definitely not been pinpointed yet, only hinted at generally - the module system does no memory management, so it is a case of trying to work out what combinations of module system operations trigger previously unrevealed engine bugs. Since it has been reported that disabling all the added meshes doesn't prevent the crashing, I am getting the sinking feeling that the agent modifier operations have never been tested with long running missions, and might cause memory leaks: basically all other code added is standard stuff of the same type that has been used before without problems. Meaning that a major part of the last version that took a lot of difficult work might need to be entirely dumped: the ability for any troop to pick up any weapon or armor for looting or trading purposes . But then again, it runs on the server as well, so should cause that to crash even faster. Hmm, maybe the new music playing system is the cause? It only runs on the clients.BlitzKrieg-BoB said:Since we seem to have pinpointed the crashing problem now, I was wondering if we could expect a hotfix for this?
I have 8 GB RAM and a fully 64 bit Linux system, but the limitation probably depends on how Warband is compiled, since I also crashed after leaking to about 2.9 GB, as said above.BlitzKrieg-BoB said:It seems that the majority of players are affected by this, apart from a small group of big spenders who have ****loads of RAM installed in their PC.
Splintert said:It doesn't matter how good a computer someone has, 32-bit applications can never use more than 3GB of RAM (which is why it crashes at 2.9GB).
It's getting lower. Here we hate snow, the entire country goes to a panicking standstill, I for one see old women relentlessly attacking the snow with walking sticks... to no appease. When it rains, we call it normal life and everyone goes out to town and does their shopping. When it's sunny, it's unusual and in the minds of the government it means we will die of thirst, so they place restrictions preventing civilians from using hosepipes for 3-4 weeks, then a humungous storm comes and flooding occurs, which makes people casually pile sandbags in front of their doors. Hmm, well I hope for heavy snow tomorrow, there's some particular people I would very much like to pelt.Armie_knock said:-10? Lucky bastard, I would kill for a warm winter like that.
Could you test watching the memory usage until it is nearly going to crash, then disconnect from the server and see if that clears the leak (memory usage drops down again). I will make some patches to disable music and whatever else I can think to try, later; maybe some other ideas to test as well (can't think very well yet, in the morning).BlitzKrieg-BoB said:I am willing to crash some more with various settings en-/disabled and report results. It's just that I am slowly running out of ideas of my own atm...
Highly unlikely to be the cause, didn't change in last version, and the disable faction option only switches a few lines of simple and common code.BlitzKrieg-BoB said:Also, if the problem is really caused by by the faction showing as default in nametags, would that mean it could be solved or relayed by playing with/without nametags?
TDC_Overlord said:It's getting lower. Here we hate snow, the entire country goes to a panicking standstill, I for one see old women relentlessly attacking the snow with walking sticks... to no appease. When it rains, we call it normal life and everyone goes out to town and does their shopping. When it's sunny, it's unusual and in the minds of the government it means we will die of thirst, so they place restrictions preventing civilians from using hosepipes for 3-4 weeks, then a humungous storm comes and flooding occurs, which makes people casually pile sandbags in front of their doors. Hmm, well I hope for heavy snow tomorrow, there's some particular people I would very much like to pelt.Armie_knock said:-10? Lucky bastard, I would kill for a warm winter like that.
Vornne said:Could you test watching the memory usage until it is nearly going to crash, then disconnect from the server and see if that clears the leak (memory usage drops down again). I will make some patches to disable music and whatever else I can think to try, later; maybe some other ideas to test as well (can't think very well yet, in the morning).BlitzKrieg-BoB said:I am willing to crash some more with various settings en-/disabled and report results. It's just that I am slowly running out of ideas of my own atm...