It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
When my male character gets hit the game seems to play the female grunt, or atlest it sounds like it. Is this normal? Also if I pick the female character model, everyone still addresses me as a boy etc. Would be nice to get a fix or something for this.
This question / problem has been solved by schwixxerimage
The female Sound Bug is known already and will be fixed afaik.

The option to play a female character was added through the patch and was not part of the original game. Thus the dialogues will stay the same whatever character model you chose. It's only a cosmetic choice.
Post edited April 15, 2021 by schwixxer
avatar
Hurlum: When my male character gets hit the game seems to play the female grunt, or atlest it sounds like it. Is this normal? Also if I pick the female character model, everyone still addresses me as a boy etc. Would be nice to get a fix or something for this.
when you are in the character creation screen do not toggle to female and back to male or you will get this bug. if you do not you will make no sound at all. I noticed this with my scout during combat practice. but when I recreated him it did not occur. but the tutor shouted when I hit him but my character made no sound at all when i was hit by him. he only sounds like a girl when I toggle from male to female and then back to male.
I posted this on the Steam forums and it worked for some people.

The original siege.ini file had the following in it

[Character]
AttackSounds=StaffMiss
PainSounds=malegrunt2,malegrunt4,malegrunt5
DeathSounds=malekill5,malekill7
Resource=Player
avatar
Hurlum: When my male character gets hit the game seems to play the female grunt, or atlest it sounds like it. Is this normal? Also if I pick the female character model, everyone still addresses me as a boy etc. Would be nice to get a fix or something for this.
This bug was addressed with today's 1.02 patch.