Maniaplanet 3.1.7
Moderator: English Moderator
Re: Maniaplanet 3.1 RC6
tell me if it's still the case after second launch. Like I said, the first one after update make the scan do all again + shaders to compile.
Re: Maniaplanet 3.1 RC6
that error you mention here Nerpson came to me two updates before, MP 3.0,dont know the exactly one..
was a bit strange with these 4-5 mins waiting time after clicking on the .exe,once it started,all was fine,and fast as it should be
but with 3.1 its gone for me..that bug
it seemed like after clicking on the exe the pc was saerching for sth to start it,but couldnt find ^^
dont know
seems like this bug is rare,none of my buddys had it..
whatever,good luck,that it is going away for you too,with this or the next update
was a bit strange with these 4-5 mins waiting time after clicking on the .exe,once it started,all was fine,and fast as it should be

but with 3.1 its gone for me..that bug

it seemed like after clicking on the exe the pc was saerching for sth to start it,but couldnt find ^^
dont know
seems like this bug is rare,none of my buddys had it..
whatever,good luck,that it is going away for you too,with this or the next update

Re: Maniaplanet 3.1 RC6
maybe a specific file in the cache. Maybe to clean it could be a thing, I don't know right now
Re: Maniaplanet 3.1 RC6
Maniaplanet is indeed really really slow since the last update. Starting up is still decent for me (~6s) but loading titles really takes MUCH longer now.
=3
Re: Maniaplanet 3.1 RC6
even on second launch? because it's normal when it compiles shader again?
Re: Maniaplanet 3.1 RC6
Nice to see updates 
and yes it is incredibely slow. my windows start faster then maniaplanet at the moment. It takes easyly a full 2 minutes to load between the click on Play of the launcher and the Connect page to appear.
I have relatively small cache 4gb and all the installation is in an ssd.

and yes it is incredibely slow. my windows start faster then maniaplanet at the moment. It takes easyly a full 2 minutes to load between the click on Play of the launcher and the Connect page to appear.
I have relatively small cache 4gb and all the installation is in an ssd.

Developper for The next generation, Clean and Powerfull controller eXpansion for your SM & TM server . Working on eXpansion² with full MP4 support and many other awesome features...
Re: Maniaplanet 3.1 RC6
My client was super slow as well until I noticed that my settings had been changed from very low to high. Luckily I had my settings saved as a default and could reset it quickly.
Now it starts in less than a minute, but it's sadly still a little bit slow
Entering titles the first time takes around 10sek for me, but I think I can live with that
Now it starts in less than a minute, but it's sadly still a little bit slow

Entering titles the first time takes around 10sek for me, but I think I can live with that

A nice person is a better person!
Did you participate in a Monthly Track Contest yet?
My Maniaplanet maps!
Did you participate in a Monthly Track Contest yet?
My Maniaplanet maps!
Re: Maniaplanet 3.1 RC6
Yes.Hylis wrote:even on second launch? because it's normal when it compiles shader again?
=3
Re: Maniaplanet 3.1 RC6
Before sending my second posting about deleting the local mods, I wanted to check my statement and renamed the Skins folder (to compare the loading times). After running ManiaPlanet (it started faster now) I deleted the empty self created Skins folder and renamed my old folder back to Skins.
After this, the problem doesn't occurred any more!
Now the mods are loaded/scanned only after entering a title (the correct behavior).
(Note: I am not really sure if temporarely renaming the Skins folder was the reason of fixing that problem)
So it looks like it is not a bug. Only a problem with the scan cache?
(I use Sysinternals Process Monitor to watch the events while loading.)
After this, the problem doesn't occurred any more!
Now the mods are loaded/scanned only after entering a title (the correct behavior).
(Note: I am not really sure if temporarely renaming the Skins folder was the reason of fixing that problem)
So it looks like it is not a bug. Only a problem with the scan cache?
(I use Sysinternals Process Monitor to watch the events while loading.)
Who is online
Users browsing this forum: No registered users and 1 guest