I liked your opinions,but main reason ı didnt back up the 2 diffrent armies; was the time management, its kinda brain melting to solve it when ı think of it like; especially in early game you both hunt bandits, now imagine how annoying it would be everything to stop in the middle of the game, then everything countunies, then everything stops again etc. .I also think that being in the same party in co-op mode is good but, I think it will be better if the co-op playing could be in apart parties. 2 people will be playing in other computers, and becuase of that they can play the same game in different start points with respect to their choices of their family and appearance. And also I suggest you to make time passing always(i.e. being in a war or in a town). This feature will make you able to supply my opinion that I told at start. Thus, the 2 player of this co-op mode will be playing in the same time schedule without connecting with each other. They will be connecting with each other like two lords in the game. They can be opponent, ally etc. If this could be done, playing with your best friend will be very fun. I wish you a good day.
reopened and it fixed,thx for helping also realized while verifying, some files were missing. ı think that was more like visual bug, whole things hard and long to explain but its fixed like no problemDelete the below file and see if it makes the mistake again.
A possible fix for GPU CrashesIf your PC has two different GPU adapters (Intel and Nvidia for example) or the game keeps crashing on GPU side players can change the graphics adapter that the game uses. This setting can also be changed in the in-game options menu.
- Locate “engine_config.txt” file at "C:\Users\YOUR USER NAME\Documents\Mount and Blade II Bannerlord\Configs" open it and find graphics_adapter value and change it to 0
nothing.What happens when you hit "ESC"?
I am experienced as welI and I too prefer the most realistic-hardest posibilities, but you dont stand a chance when you have a spear on your hand-no skill points in any melee category, and your teammate is a recruit while enemy group have both lord and highest level infantry.Yeah last i played had the opposite experience- tourneys being waaaay to easy to beat from lvl 1 on
I’m an old gamer but I’d much rather have the terminator AI then these cheese puffs
"what kind of moron skilled them up this way" good distortion of my words. we all make moronic desicions .and yes its my fault to say "who came up with this"It wouldn't be so bad, if it wasn't for the arbitrary restriction on skill learning rates that force players to actively avoid collecting experience in skills they don't need. You just look at them and think "what kind of moron skilled them up this way". Skill learning rate should simply be the same whether the character is level 1 or 30, full stop. But that's a different topic entirely.
Generally speaking nobles receive rigorous weapons training from birth, and therefore can be expected to use a variety of melee weapons that are suitable for any given situation. So I can buy that they can use all three melee weapon types; it's Khuzait nobles having crossbow skills that I don't get. Khuzait just don't use crossbows. If a noble has any sort of crossbow training, I'd love to know how they got it, when, and why. I mean, maybe they spent some time at an Empire court as a hostage, so the occasional outlier isn't an issue. (It was quite common to have foreign princes and princesses live at Imperial Roman courts in order to make sure that a peace agreement is actually upheld.)
All that aside - if you aren't able to beat a lord in a tournament, you're doing something wrong. They are more beatable than ever, if anything, since all tournament weapons are treated as blunt now. You used to have to actually use thrusting attacks or land blows to the head to hurt them, and if you glanced off the armor, you would lose half your HP on the backswing. Now armor might as well not be a thing at all, no matter if you're using a sword, an axe, or anything else.
ı am currently playing 1.5.9 . seems fixed so far. ty for your timeCan you switch to 1.5.8 live version and see if this issue persists there? We have a telemetry build but it is only on 1.5.8 at the moment. If you see this issue on live branch we can record a telemetry data to see what is going on.