Mistral wrote:Dont remember exactly though, but i had to rewrite some code months ago cuz the gettracklist (or similar) call to the dedicated made it go wild when too much tracks were requested at once. felt like a bug

Right, so every time Aseco needs to fetch the entire track list from the server, it does that in chunks of 300 tracks. If it works fine with 368 tracks on my server, I can't imagine why that method would cause a problem on cow's server with 395. In fact it's designed to work with
any number of tracks precisely because the list is fetched in reasonably-sized chunks.
cow wrote:thought i'd mention.. windows
win aseco "crashes" i mean it goes to time out error which i have at 180 seconds.. i could increase the time but when aseco doesnt crash which is most of the time.. it boots everyone.
Increasing the script timeout wouldn't make a difference. Its default is 60 seconds and if some operation doesn't complete within that time, it rarely will -- but even if it does, something isn't right as it shouldn't have take that long in the first place.
I'm aware that none of this helps you any further, but that's all I can offer so far.
Xymph