搜索结果: *

Hi, sure, here it is. This is one of the broken saves: https://app.box.com/s/4ovihhzepv8n37wyp6ajzqzt81jugtyq

However I was able to reload it and lead an attack during a siege with no errors. Maybe this is something it got fixed for the 1.3 update?

I did verify the game files on Steam and it seems that the issue is gone for now. Thanks!

It will be great to understand if this topic is being picked up by the development team since the game got unplayable for me due to this issue. Thanks.

Also, letting you know that this is only happening since the 1.2.1 update.

elysebluemoon 说:

Hi, can you please check if your version of Windows and your drivers are up to date and try verifying your game files' integrity through Steam?

点击展开...

Thanks for your answer, but yes, both my Windows Updates and NVIDIA drivers are up to date. I use GeForce Experience to automatically update the graphic drivers, so no issue there.

What I have been noticing for the combat polygons is that they show up when I get close to the enemies, for example, they will be brownish when approaching looters, but grey/purple when approaching sea riders during the combat 3rd person camera.

I haven't identified a clear pattern for the map polygons, however, they tend to show up while zoom is 2 positions before the max zoom.

Also, letting you know that this is only happening since the 1.2.1 update.

Still no updates on this?

I have noticed that during the combats the polygons start to appear when the amount of troops (mine plus the enemy troops) reaches around 20 or more units. For small fights the polygons do not show up.

And as for the map, it is still quite random.

I love the game and I have invested more than 100 hours on it, but it is just impossible to play like this:




Could you please help?

A brief update here. I was able to siege a city alone with my troops on an old savegame where I didn't belong to any faction. Could it be that the issue is related to the Vlandian faction?

Interesting to see that your error happens with the Vlandian faction, mine does too as showed on the images from my crash report. Maybe just a coincidence, maybe not.

Is there anything I can do from my end to speed up this process? Please, let me know, I'm more than happy to collaborate.

This sounds familiar. I've also posted this topic with similar issue. I do play vanilla, no mods added. I was able to reproduce the error not only when joining an existing siege, but also when starting a siege myself alone and myself with an army.

PS. How do you manage to get those records? I can only see the crash report window.

Any news on that? I was able to recreate the same error with multiple conditions:

1. The error appeared again when besiegeing a city alone with my own troops.
2. The error appeared again when besiegeing a city with my army (the troops from my party plus the troops from other noblemen in my army).
3. The error appeared again when besiegeing a castle alone with my own troops but joining an existing siege lead by noblemen from my same faction.

This bug is stopping me from playing because it basically doesn't allow you to make use of a basic functionality in the game: to siege castles/cities.

I play vanilla, no external mods added into my game, just the default stuff.

In my opinion, it is extremely urgent to patch it. Specially, since I am not the only user with this error, at least two more users were having the same problem on the Discord community.