Search results for query: *

****ty thread.

Firstly, a lack of technical progress almost always comes from management. It's not developer fault if they don't work effectively – it's up to management to make them productive (or fire them on the way). Firing the scapegoat aftermatch won't do anything – at best it will only make the situation worse.

Secondly, I think that it's going well and they get M&B2 formula pretty good. The game is still mount and blade on steroids, the mod support is one of priorities, the patches came fast and fixed game to the point where it's playable.
I mean, compare it to well known disasters like, for example Duke Nuke Forever – which lost it's formula during one of engine changes.

Barst said:

Game is still crap. I am trying to play every patch , but i just find new problems x). They are fixing quests to be worse or other stuff like graphics but of course not necessary things as i noticed. One + they blocked expansion of kingdoms on early game.

Click to expand...

early? There isn't any other good way to train recruits outside the looter grinding.

Stolen from reddit - ridiculous!

Keep up with good work Taleworlds, looking forward for fix ^^.

spacecaose said:

Just bring back looters only causing injury and i'd be happy, even if they never fixed the auto-resolve. At least i'd be able to train my troops in some what decent way.

Click to expand...

+1
I'm winning the "battles" against the looters without any causalities if I simply use the F1-F3 combination, meanwhile in simulation they are able to kill multiple elite units.
It's not fun – it's just a burden, a boring chore, wasting my time that I would spend in any better way. I usually lost around ~2 minutes for every battle like that (including loading the dialogue screen, terrain, pressing buttons, and just waiting). And it's pretty much obligatory since it's the only way to train troops (since training them in garrisons don't work).

I've noticed minor stuttering issues as well (kubuntu + proton) - on previous patch the game was running smoothly as butter. No crashes although – same as last time.

Keep up good work guys!
(and make multiplayer work on linux, I've installed battleeye by accident and now I can't run it. Dayum)

Is there any easy way to remove battleye (beside annihilating the prefix, obviously)? I installed it by accident and now I can't play multiplayer :/

YellowSolEk said:

They honestly need to make a native Linux port as they did with Warband. We have Vulkan and stuff now. After the full release there won't be any excuse for the devs not to do it.

Click to expand...

I would be fine with playing the game through proton – as long as the multiplayer works. Poorly made and hasten port is worse than wine.

Not sure if it is worthy report since it's coming for linux but I had mentioned problems with stuttering on the global map – it disappeared after installing the latest update (proton + dotnet472). Game works nice and smoothly now.

After the new update the game is (AT LEAST!) working nice and smoothly. No lags, no stuttering, no crashes – I played fine for two or so hours.

I've "installed" the proton-ge with dotnet72 on top – it is working nice and smooth without any stuttering… but crashing every 5-10 minutes.

decompression_sickness said:

>installed GE's proton build
>booted the game up, saving still takes forever at this point
>protontricks 261550 annihilate (this removes everything installed other than the game itself and proton, basically clean slate)
>protontricks 261550 vcrun2019
>protontricks 261550 dotnet48

Click to expand...

Interesting thing – https://forums.taleworlds.com/index.php?threads/installing-missing-necessary-dependencies.407126/ lists dotnet 4.7 as a dependency, not 4.8 one. Maybe this is a cause of many stability problems?

it is working smoothly for me – almost. There is some heavy stuttering on the global map, making the game almost unplayable.

Other than that turning on the vsync and setting the graphic details to highest prevents the sudden FPS drops for me (outside the global map obviously).

uçanbiblo said:

Hi, I've informed the developers about this issue and we will find a fix as soon as possible. In the meantime, please update me if the new patch e1.0.1 has solved the issue.

Click to expand...

some people on linux/wine has this issue as well – it is related to dotnet48. https://github.com/ValveSoftware/Proton/issues/3706#issuecomment-608463685. Maybe you'll find it helpful.