cRPG

cRPG => cRPG Technical problems => Topic started by: Bushido Brown on January 11, 2012, 06:54:57 am

Title: Crashing every time I enter a server.
Post by: Bushido Brown on January 11, 2012, 06:54:57 am

Title explains it. I get a "Mount & Blade Warband has stopped working..." message. Any idea how to fix this?

Title: Re: Crashing every time I enter a server.
Post by: Meow on January 11, 2012, 12:20:22 pm

First i would:
Download the latest launcher: http://www.c-rpg.net/cRPGLauncher.exe
Run that in repair mode.
Then try launching.

After that if it still crashes, try switching from DirectX9 to DirectX7 (in the warband launcher where you select the module and get into the options) and try launching.

If the DX7 thing works try switching back to DX9.
Also let us know how it goes so we can help further.

Title: Re: Crashing every time I enter a server.
Post by: Bushido Brown on January 11, 2012, 04:04:21 pm

The launcher keeps freezing on random parts of its update :[

Title: Re: Crashing every time I enter a server.
Post by: Meow on January 11, 2012, 04:57:24 pm

I remember multiple people having that problem but sadly i do not remember if or how they fixed it.
Try disabling your firewall for the update i guess.
Also some AVs will give a false positive on WSELoader.exe so might wanna kill those for the duration as well or whitelist it so it does not get deleted when you start the game with it.

No worries, there is no harmful software included in any of this.

Title: Re: Crashing every time I enter a server.
Post by: Bushido Brown on January 11, 2012, 07:05:52 pm

Blegh, tried both and still no luck :\

Guess I'll just wait for the MB repository release.

Title: Re: Crashing every time I enter a server.
Post by: Bushido Brown on January 12, 2012, 05:35:05 am

I managed to fix it by downloading the outdated MB Repository file, extracting it, then repairing with the cRPG launcher thing. Thanks for the help!

Title: Re: Crashing every time I enter a server.
Post by: Meow on January 12, 2012, 11:13:01 am

Thanks for letting us know, never figured out what cause the real problem :(

Now we got a workaround! :mrgreen: