搜索结果: *

  1. Resolved Game breaking bug: on beta 1.3 branch lords will never siege.

    wtid 说:
    i was searching this bug report i also saw multiple times ai never conquer any fief they leave sieges like %99 .
    点击展开...
    YES, this happened on multiple fronts at same time too, so you would think you would for sure lose at least SOME of the castle's right? i started getting suspicious because i personally saw multiple sieges happening at same time that were supposed to be so unfair..only to lords apparently be like "nope, keep your stinky castles" i think they may starve for some reason....However if they never take cities sturgians can never stabilize as AI might think we are fine and keeps going against 4 factions at same time.

  2. Resolved Game breaking bug: on beta 1.3 branch lords will never siege.

    So im playing on sturgians as usual, 5 days in and our kingdom decides to go to war against EVERYONE. enemy lords come to lay the siege 300vs 30 men and then just leave, they never acsually take the castle.see this image

  3. In Progress CRITICAL ISSUE - The game doesn't start.

    look i wish i could just share my game files for people since my instalation is working fine, but i think that is against TOS. it would be easy way to fix this but its kinda illegal.

  4. In Progress CRITICAL ISSUE - The game doesn't start.

    gasznak 说:
    64 bit windows
    点击展开...
    its worth the try, to mess with these settings.

  5. In Progress launch crash

    you guys have 32 bit systems? i would even try to install this game on another drive and see if it fixes.

  6. In Progress CRITICAL ISSUE - The game doesn't start.

    are you running 32 or 64 bit windows atm, there have been few games that simply don't work with 32bit anymore. I mean im running gtx 1070,i-7300,16gb of ram. and it was running out of box for me even without windows activated. edit: kernel 32.pdb seems very much like this might be the issue here.

  7. Game crashes to deskop

    Game crashes after 1-2 rounds on multiplayer, so i took a peek on windows error log and here is what it shows Faulting application name: mb_wfas.exe, version: 1.0.0.0, time stamp: 0x4e1da256 Faulting module name: mb_wfas.exe, version: 1.0.0.0, time stamp: 0x4e1da256 Exception code...
后退
顶部 底部