搜索结果: *

Hi
I upgraded ram to 16gb now and I've got 10more fps but game still stutters when army start fighting and Yes my CPU is still at 100% and gpu is about 50% ...
My version of the game is 1.4.0 main branch
Thanks for responding

I tested now.
When I enter in game and change resolution to 60Hz it also change in the engine_config. But when I exit the game it automaticaly roll back to 40Hz in engine_config. I start game again and it is default desktop resolution but still in the engine_config it says 40.0000 and I have to manually change to my resolution with 60Hz and it works also in config.
The only bug or something is why it changes back to 40Hz in config when I exit the game.
I hope you will understand me.
Thanks for responding.
Regards

My computer name is Rijad-Pc.
My account user name is Rijad.
@elysebluemoon

@uçanbiblo
I can confirm that still fps drops to 1 when I give charge command
I assaulted the castle and everything was fine when army was assaulting the walls and using siege equipment , btw I had only ladders, but when I pressed charge army stuck charging and fps drop to 1 . I think we need to have these commands from the begining the siege battle : Assault the walls
Use siege equipments
Those commanda works perfectly

I thinik it's about AI pathfinding , because when you start the siege they already have commands like Infantry is using the siege equipments, and Infantry is assaulting the walls , those commands given by itself are working fine and no lagg , I have more fps on sieges now than on the field battle lol , but when you give order that Infantry is following you or holding the position or what is the worse CHARGE , their pathfinding is bad and they all stuck charging and causes drama drop fps , but only when full 500 man on the battle i think...

And could you also find fix , when I set resolution in game, when I start again the game it always set it on Default ,and again I have to choose the resolution ...

Hope this works @elysebluemoon
Still didnt find fix for this , on my display settingi it is set 60Hz I can take the screenshot...

Is it possible that devs give us the PC discription on which they test the game and play it smoothly on 1000 man battle size , so I can buy that particular pc...
Thanks
Regards

My GPU is about 30% and the CPU is at100% , I dont know why they dont fix that or explain why is that so.
Ryzen 7 3750h Laptop
GTX 1660ti 8gb
8GB ram
win10
1.3.0 v

I tried in custom siege battle with siege towers and battering rams, it seem that there is no fps drop, I will inform you when I go in campaign sieging and I will try the commands, I started new game after 1.3.0 update
Thanks for responding
Regards

Same things happens to me, what I've noticed that it only happens when the battle is in village and it happens when I attack someone or someone attacks me and immidietely black boxes appear.
1.2.0 version

It is unforgivable that in 10 years of development they release unplayable game with fps stutters, many things not working at all, and they charge it for 50$ because they have faithfull community who love this game , but that same community dont deserve this... I think modders will fix the game sooner than the devs and we should pay the modders for the game not the devs...
Sorry TaleWorlds , 10 years and still warband is much better with Jeremus by my side ....

Im on 1.2.0 , and still cpu 100% and the gpu is around 60% while in battles, in Main menu , its 60% cpu and 30%gpu...

Man I bought brand new laptop for this game, more than 1000$ , and I cant play it right, Im so dissapointed, and I have only SSD 512gb and only that game and no other program installed, and 1.1.0 run smoothier than 1.2.0 , I tried everything but fps always drop in battles of 500 units and sieges unplayable...

I have the game on SSD but still sttuters in combat and in world map while lot of parties appears
I didnit notice the usgage of ssd , but I have 100% usage of CPU and I think that is what make fps drop.
My laptop : Gtx 1660ti , ryzen 7 3750h 8gb ddr4 ram

When I am in battle , my cpu is 100%
Im on 1.1.0 version
Which version you fixed this?