搜索结果: *

madnessario 说:

Until the game is finally released this is false in the sense that the intended design probably included companion/noble deaths.

点击展开...

Have you just pulled this factoid out of the air? Where was this explained as being the intended design? Doesn't make any sense to me personally and there's no precedent for it.

madnessario 说:

This ties to the previous argument. Without noble death, in combat (old age is still there), the world will reach a point where there are x3-x5 more nobles on the map when you are 80 years old (crude math, you get the point). This requires different balancing, something that can be done with a mod in my opinion.

点击展开...

No we are talking about companion deaths, not deaths in general or noble deaths. I liked the previous system where nobles could only die from old age or if the player executed them and companions couldn't die at all.

babelfisch 说:

Reversing the decision wouldn't make sense since this is the way the feature was advertised.
I am all for making it optional though:
a) no birth, no death
b) birth and death from old age
c) birth and death from old age and battles

点击展开...

Where was it advertised at all? This change came out of the blue completely for all the players I've been speaking to.

Antaeus 说:

Isn't it obvious that allowing deaths might also apply to other characters such as lords and companions?

点击展开...

Well no, and until recently this was not the case. Nor was it the case in WB.

It's great that you like it, but personally I don't and I would at least like the option to turn this feature off.

Philozoraptor 说:

This mod solves your problem Disable companion and player clan member death in battle for 1.5.5 at Mount & Blade II: Bannerlord Nexus - Mods and community. Works with 1.5.6 and 1.5.7 too.

点击展开...

Thank you so much - I would much rather the developers just reversed this decision though rather than have to download a mod.

Antaeus 说:

You want them to change the game because you told your in-game subordinate to run at a Sturgian shield wall and they died?

点击展开...

If this had been how the game was designed from the start, that would be one thing, but until recently it was impossible for companions to die in battle, so its not nearly as silly as your disingenuous comment is suggesting.

Apocal 说:

Just disable the death option when you start a new game.

点击展开...

This removes ALL deaths and births, I just don't want my companions dying.

Flesson19 说:

This is partially intended, they brought in death without telling anyone in a hotfix and left us not knowing anything for over 3 weeks, real nice huh. But this is intended, the problem is they are dying in player run battles only, not simulations, also the death rate is 10%, which is high they intend to change it to 2% which I still think will be too high but hopefully soon it is all worked out since they werent nice enough to leave old age death only in so we are stuck with no death or a terrible death mechanic for over a month.

点击展开...

This sucks, why introduce companion deaths at all? Gotta agree with OP.

I agree, developing my companions is one of my favourite parts of the game, it sucks that they can die at all when you can invest so much time and money into them, really hope this is reversed 'cause its kinda ruining the whole experience for me.

I have to agree, who thought it was a good idea to start killing off companions? I didn't see any option to disable this when I started a new campaign recently - there was an option to prevent deaths and births, but nothing about preventing companion deaths. I want to play the game the way it was until this update; with deaths and births 'on' but without my companions dying and having to constantly shop around for a new scout/doctor/engineer/etc.

Hey so after restarting my computer and steam and managing to complete the update, Bannerlord is now running fine! Thank you so much for your tips and help.

I found some GPU info in Task Manager, there's:
GPU 0
Intel HD Graphics 630
GPU memory 0.2/3.9 GB
DirectX version 12 (FL 12.1)

and

GPU 1
NVIDIA GeForce GTX 1050 Ti
GPU Memory 0.0/7.9 GB (4.0 GB Dedicated GPU memory and 3.9 GB Shared GPU memory)
DirectX version 12 (FL 12.1)

Not sure if this helps?

AnandaShanti 说:

I find using geforce experience to optimize BL after every version change is helpful. I barely know what any of the setting actually do though.
If you're on 1.5. beta it may need some work from devs still to run a smooth as before, but 1.4.3 version should be running better then older versions.

点击展开...

Thanks, how can I tell what version I am on? I have updated all my Geforce drivers, how do I optimise the game in Geforce as you suggest?

elysebluemoon 说:

Hi, can you please give me more info using the template below? If you sent a crash dump through the crash uploader, can you post the generated crash ID?

Summary:
How to Reproduce:
Quest/Settlement Name (if related):
Media (Screenshots & Video):
Version:
Installed community-made modifications:
Computer Specs:
OS:
GPU:
CPU:
RAM:
Motherboard:
Storage Device (HDD/SSD):

点击展开...

Thanks for your reply. I just loaded up the game, started a new campaign, it was running very slowly, I skipped the tutorial, headed to some villages and hired some peasants, still all running very slowly and laggy, went into the nearest city Poros and attempted to enter the tavern district when it crashed.

I honestly don't know the answer to a lot of these things but found this in system info which might help.

Processor: Intel Core i5-7300HQ CPU @ 2.5GHz 2.50 GHz
Installed Memory (RAM): 8.00 GB (7.89 GB usable)
System type: 64-bit OperatingSystem, x64-based processor

Where can I find the other info? I did submit a report but I don't have the crash report ID I'm afraid.

Thank you both for your help. I've verified the game files with steam and updated steam and restarted it, but I'm still having trouble with Bannerlord - it currently says Update Paused, but when I click Resume it just briefly says Starting Download, then Finalizing, then goes back to Update Paused. So I currently can't launch the game at all because it is stuck in a permanent state of updating.