Search results for query: *

  1. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    Kenshiken said:
    That's sad and great at the same time. I don't feel like starting a new save today for sure.
    Where to read patch notes tho?
    Click to expand...

    TW posts beta hotfix notes under the main beta patch thread:
  2. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    From the Beta patch notes for the patch that went out today:

    Fixed an issue where newly created characters and other objects could get mixed up with each other. This created instability & possibly crashes. It was also responsible for broken companions and encyclopedia problems. The fix does not recover broken beta save games, but it should resolve the issue for new games. You can test this by checking if newly created characters or other objects have their own appropriate encyclopedia pages instead of another character’s or object's page.
    Click to expand...

    This could be a fix for our crash? Unfortunately it won't fix old saves.
  3. sidiust

    Closed Cannot Create Save Data

    AceNineStripe said:
    I’ve gotten an error where the game “can’t create save data”. I’ve tried running the base game, 1.1, 1.2, 1.3, with and without mods and I still get the error. I’m also using Windows antivirus in case that matters. I’m about to try uninstalling and reinstalling today to see if that works, but if anybody else has had this issue and fixed it, please let me know.
    Click to expand...

    Hey, I am having the same issue on some of my saves, and I found a not-so-great workaround that might help.
    If you go into your Game Saves folder (Documents\Mount and Blade II Bannerlord\Game Saves\Native) you will notice that the broken saves are almost DOUBLE the size of the working ones (76 MB vs 40 MB). If you load any normal sized saves from the same playthrough, you will be able to save again. So, you might be able to rescue your campaign, but you'll most likely lose a few hours of progress.
  4. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    greggho said:
    Ungh, same here, coupled with save game corruption ("save failed!" issue). Twice now, once in 1.2.0 and now same in 1.3.0 beta...

    This has been the most frustrating Early Access experience I ever had :sad:
    Click to expand...

    I'm having the save corruption issue as well. I just noticed that corrupted save games are significantly larger than the normal counterparts (76 MB vs 40 MB). If you go into your game save folder, you can identify which save is the last one that is not corrupted. Unfortunately, you'll most likely lose a few hours of gameplay just like I did :'(
  5. sidiust

    Locking troops into a formation

    Norseman13 said:
    I have all the time in the world to place them since the enemy never advances. what I want is the ability to advance my troop in an orderly fashion like real soldiers without having to command all of them individual they whole time.
    I understand how to control them, I just wanted to now if that technique was available and I didn't know. that being said I for one would want that to be an option
    Click to expand...

    Sadly, there is no "lock formation" option to keep them advancing in an orderly fashion in the way that you describe.

    The workaround that I use to achieve something similar is
    a) put infantry in shield-wall, set to follow me. I then move forward with the infantry until 150m or so out, at which point I either sit and wait while my archers do their thing, or I set the infantry to advance/counter-charge the enemy main body.
    b) put archers in loose formation, and manually advance them using f1-leftclick. These are the only units I will manually push forward, and that too only until they're around 125-150m away from the enemy. After that, I either delegate, or put them on 'advance' command.
    c) (only works if enemy is stronger or on-par) delegate cavalry command. The cavalry AI usually splits the unit into two, with each new unit protecting a flank. The cavalry advances slowly alongside your infantry, which is what you want. If the enemy is weaker, however, the cavalry will charge right away.
  6. sidiust

    Sturgian Shock Troop v. Veteran Warrior

    Shock troops are surprisingly one of the most effective T5 infantry units there is, thanks to their secondary weapon: the War Razor. It one-shots most heavy infantry. Check out this post which goes into much more detail: https://www.reddit.com/r/mountandblade/comments/g1ugwa/in_depth_sturgian_unit_testing/
  7. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    Rakean said:
    The Building- completing thing seems to be a possibility, since i noticed too something about buildings
    Click to expand...

    Ok, so it turns out I had an autosave from 5 game-days prior to when the crash was occurring. This time I parked myself in the settlement (Lageta) to check whether any building was completing on the crash day (day 266) in question. Unfortunately, the building wasn't even close to being completed (fortification lvl 3, 55 days remaining), so that theory is probably not correct.

    On the plus side, the game continued without crashing past day 266. So it must be some other player behavior that is causing the crash.
    EDIT: game crashed literally minutes later. Same error.
  8. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    dowellboss said:
    have both of you universalclose or CP installed? are there any mods in common with the ones cited here?



    edit: i highly doubt that the frameworks mods (bannerlib, modlib, mboptionscreens, livejasmine ads, missingmodulefix et ****ing cetera) are the cause. it's probably best to deactivate all mods, purge it all in vortex, verify the game integrity, which is about the same as my psychological's and delete (after backing up, of course) the mb2buggerloyd folder in the documents library before
    Click to expand...

    I had Universal Close and CP installed originally, and then I tried multiple times with various combinations of those patches on and off. Nothing helped.

    I've verified game files and even switched to beta 1.3, but that save game is still crashing at the exact same point.
  9. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    dowellboss said:
    i also noticed that it happens after i max every building. could be wrong and need testing but i'm the laziest person i know
    Click to expand...

    It happened to me even without maxing all buildings. Lageta was pretty underdeveloped when I got it. Though the crash might be happening just as one of the buildings is completed?
  10. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    dowellboss said:
    hold on guys, which launcher are you guys using? fixed launcher, bannerlord mod launcher which is way better or just the original one?
    i take you guys have sorted the mods correctly, because i did and voila: still getting the same crash
    one thing i noticed is that it only happens if i own a fief. did a playthrough with ~400 days just killing every single npc i could get my hands on and no crashes, then i decided to settle down with an evil lady in a city and boom, bannerlord decided to skyrim on me
    weird, really weird. i'll go check some of those mentioned mods source code and get back here if i find the culprit, then i'll inform you and xanax myself until a new update
    edit: hey hey people sset... so i think it's the showsettlement or settlementicons mod, since i couldn't find the source code OR the land grant for veterans/reconstruction patches from the community patch OR universal close (like ???????? but the diagnostic file says something about townmanagement and stuff and this exception is town related so idk, it could be or it could very well not be, just like my supposed biological father)
    Click to expand...

    Yes, it only happened after I got a fief in my last three playthroughs. Can't recall if it happened only after getting a town, or after a castle too. I've tried disabling each and every mod, but nothing helped get past the crash. I'm using Fixed Launcher.

    My last remaining wild guess is that keeping the SaveFix Module enabled all the time (like I do, because I'm too lazy to disable it) might be messing up the save games in the latest builds. IIRC the savefix module removes custom classes from savegames... perhaps the mod is removing a new class that TW added in the latest patches that is related to Settlements/Town Management? And then the game can't find that class in the daily tick and throws up an exception? Unfortunately I don't have any saves that I can test this theory on.
  11. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    Kenshiken said:
    Disabling "Community Patch" and "Settlement Icons" didn't help, yes. Alongside with "Changes settlement culture".
    And all other mods - didn't help at all.
    Click to expand...

    Yup, can corroborate that disabling Community Patch or all mods didn't help. Looks like yet another 300+ day campaign is toast. :'-(

    Still, I find it a bit difficult to believe that the crash is being caused by the core game itself, as I would expect this error to be WAY more common in the forums if that were the case.

    I have a feeling that the SaveFix Module isn't working quite right, and that its frying our save games somehow, but to be honest that's pure conjecture and I have no real idea what's causing the issue.
  12. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    sidiust said:
    I started a new save (still on e1.2.1) with far fewer mods enabled, but my game just crashed with the same error a few hundred days in.

    The only remaining mods in common are:
    missingmodulesavefix
    bannerlib
    modlib
    community patch
    settlement icon
    show settlement
    universal close

    Since the crash seems to be settlement related, I'm now thinking the error might be related to "Settlement Icon", since it does update the icons depending on whether there are missions/tourneys available. Will disable that mod and try again.
    Click to expand...

    Update: disabling Settlement Icons didn't help. I will try disabling Community Patch next.

    Kenshiken said:
    I have a lot. But disabling every one of them didn't fix this crash.
    I am praying to TW to fix this in hotfix or another big 1.3 patch, or I'm literally done. Can't bear it anymore and vanilla game is too boring to play right now anyway.
    Click to expand...

    That's really unfortunate. If none of the mods are the culprit, then I really hope they patch this up soon!
  13. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    Kenshiken said:
    Nope, have another crash like this with new save at 1.3, 400 days campaign

    looks like that's it for me, uninstalling Bannerlord for a year or so

    at TaleWorlds.CampaignSystem.Town.DailyTick()
    at TaleWorlds.CampaignSystem.Campaign.DailyTickSettlement(Settlement settlement)
    at TaleWorlds.CampaignSystem.MbEvent`1.InvokeList(EventHandlerRec`1 list, T t)
    at TaleWorlds.CampaignSystem.CampaignEvents.DailyTickSettlement(Settlement settlement)
    at TaleWorlds.CampaignSystem.CampaignEventDispatcher.DailyTickSettlement(Settlement settlement)
    at TaleWorlds.CampaignSystem.PeriodicTicker`1.PeriodicTickSome(Single timeUnitsElaped)
    at TaleWorlds.CampaignSystem.Campaign.Tick(Single dt)
    at TaleWorlds.CampaignSystem.Campaign.RealTick(Single realDt)
    at TaleWorlds.CampaignSystem.MapState.OnMapModeTick(Single dt)
    at TaleWorlds.Core.GameStateManager.OnTick(Single dt)
    at TaleWorlds.Core.Game.OnTick(Single dt)
    at TaleWorlds.Core.GameManagerBase.OnTick(Single dt)
    at DMD?31071611::OnApplicationTick_Patch1>(Module this, Single dt)
    Click to expand...

    You don't have any mods enabled?
  14. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    dowellboss said:
    same here and the only mods we have in common are:
    missingmodulesavefix
    bannerlib
    modlib
    community patch
    diplomacy reworked
    settlement icon
    show settlement
    cultured start
    universal close

    i do have a settlement culture changer mod on, but it's a different one from yours
    if you solved it already or have any idea as what could be causing it, share it here mate
    Click to expand...

    I started a new save (still on e1.2.1) with far fewer mods enabled, but my game just crashed with the same error a few hundred days in.

    The only remaining mods in common are:
    missingmodulesavefix
    bannerlib
    modlib
    community patch
    settlement icon
    show settlement
    universal close

    Since the crash seems to be settlement related, I'm now thinking the error might be related to "Settlement Icon", since it does update the icons depending on whether there are missions/tourneys available. Will disable that mod and try again.
  15. sidiust

    Resolved (Beta 1.3-1.4) Constantly crashing after long (237 day) campaign while traveling the map

    Are you using any mods? I'm getting the same error on e1.2.1.

    Here is my modlist... maybe we have some in common and that could help narrow down what's causing the crash?

    1. Aragas.SaveMissingModuleFix v1.0.1.227410
    2. AutoBlocker v1.0.7.227410
    3. BannerLib v0.0.9.227410
    4. BearMyBanner v0.6.2.227410
    5. BetterAutoCalc v1.0.0.227410
    6. Cheer v1.2.0.227410
    7. ColorblindCasualtyLog v1.1.0.227410
    8. CommunityPatch v0.0.2.227410
    9. CultureChanger v1.0.0.227410
    10. CustomBattle e1.2.1.227410 *Selected*
    11. DiplomacyReworked v1.2.10.227410
    12. DontSmeltLockedWeapons v1.1.0.227410
    13. FixedTradeHistory v2.2.0.227410
    14. KillBanditsRaiseRelations v1.2.2.227410
    15. KingdomColor v1.3.2.227410
    16. ModLib v1.0.1.227410
    17. Native e1.2.1.227410 *Selected*
    18. PartyAIOverhaulCommands v2.3.0.227410
    19. PartySorter v1.0.0.227410
    20. PersistentLock v1.0.0.227410
    21. Recruiter v1.3.0.227410
    22. ResetMapRotation v1.0.0.227410
    23. Sandbox e1.2.1.227410 *Selected*
    25. SavingOverhaul v1.1.1.227410
    26. Separatism v0.1.1.227410
    27. SettlementIcons v1.2.0.227410
    28. ShieldsBlockOnBack v1.0.0.227410
    29. ShowSettlement v1.0.1.227410
    30. SmithingHideUnknown v1.0.1.227410
    31. SoundTheAlarm v1.0.5.227410
    32. StoryMode e1.2.1.227410 *Selected*
    33. SummarizeCashflow v2.0.0.227410
    34. YetAnotherPartyOrganiser v1.2.0.227410
    35. yName v1.1.1.227410
    36. zBetterArmor v1.1.1.227410
    37. zBetterHorseCharges v1.4.0.227410
    38. zCulturedStart v1.1.6.227410
    39. zUnitFixes v2.8.0.227410
    40. zzFactionColorEnabler v1.0.1.227410
    41. zzzUniversalClose v1.3.0.227410
  16. sidiust

    Improving relations with lords in same faction by spamming Settlement Reassignment proposal

    The "Support Clan" button in the Kingdom screen costs 50 influence but only gives a paltry +1 or +2 relations (with charm skills/perks). This can be bypassed using the Settlement Reassignment vote, which probably wasn't intended. Calling for a Settlement/Fief reassignment costs 200 influence...
  17. sidiust

    Windows 10 launch issue

    sidiust said:
    I am having the same issue. Launcher won't launch. I've tried Steam, as well as the Taleworlds website version. I'm running Windows 10 v1803.
    Click to expand...

    After a whole day of twiddling, I finally got this to work.

    You need to manually create a rgl_config.txt file in your "[User]/AppData/Roaming/Mount&Blade Warband/" folder.

    Here are the settings I used to finally get the launcher and the game running:
    first_time = 0

    texture_detail = 70

    render_buffer_size = 15

    max_framerate = 60

    start_windowed = 1

    use_pixel_shaders = 0

    use_vertex_shaders = 1

    fake_reflections = 1

    show_framerate = 0

    use_ondemand_textures_ = 1

    use_ondemand_textures_mt = 1

    disable_music = 0

    disable_sound = 0

    disable_frequency_variation = 0

    cheat_mode = 0

    enable_blood = 1

    enable_edit_mode = 0

    force_single_threading = 0

    debug_mode = 0

    display_width = 1600

    display_height = 900

    display_bits = 32

    antialiasing = 0

    sample_quality = 0

    alpha2coverage = 0

    force_vsync = 0

    shadowmap_quality = 1

    shader_quality = 1

    postfx_dof = 0

    postfx_hdr = 1

    postfx_autoexp = 0

    flora_degrade_distance = 75.0000

    flora_lod_detail = 0

    use_instancing = 1

    use_secure_connection = 0

    max_number_of_connections = 16

    look_for_server_on_this_machine = 0

    music_volume = 0.4902

    sound_volume = 0.9265

    mouse_sensitivity = 0.3529

    invert_mouse = 0

    enable_lighting = 1

    enable_particles = 1

    enable_blood = 1

    enable_character_shadows = 1

    enable_accurate_shadows = 1

    number_of_corpses = 0

    grass_density = 10

    combat_speed = 0

    friend_combat_difficulty = 0

    adapter_format = 0

    reduce_combat_ai = 1

    reduce_campaign_ai = 1

    combat_difficulty = 0

    display_labels = 1

    display_targeting_reticule = 1

    display_attack_direction = 1

    turn_camera_with_horse_in_first_person = 2

    verbose_damage = 1

    verbose_shot_difficulty = 1

    battle_size = 1.0000

    attack_direction_control = 2

    defend_direction_control = 0

    lance_control = 0

    anisotropic_filtering = 0

    enable_environment_shadows = 1

    verbose_casualties = 1

    verbose_experience = 1

    realistic_shadows_on_plants = 0

    number_of_ragdolls = 0

    gamma = 2.0009

    character_detail = 1.0000

    character_shadow_detail = 0.4884

    control_mouse_movement_y_scale = 1.5000

    blood_stains = 0

    use_winmm_audio = 0

    enable_version_check = 1

    enable_aspect_ratio_control = 1

    realistic_headshots = 0

    auto_gfx_quality = 0

    enable_gamepad_vibration = 1

    Just copy and paste that into the rgl_config.txt and save. Then run the launcher.

    Note: This is AFTER I did all of the other things, including installing DX 9, uninstalling/reinstalling the game etc etc

    Hope this helps someone.
  18. sidiust

    Game Will Not Launch

    I'm having the same issue and nothing I do can get the Launcher running for me either. Not even versions from "alternative sources" will run.  :facepalm:
  19. sidiust

    Windows 10 launch issue

    I am having the same issue. Launcher won't launch. I've tried Steam, as well as the Taleworlds website version. I'm running Windows 10 v1803.
Back
Top Bottom