Hi guys,
It seems that there is a general consensus for all non-windows users to completely ignore the whirlwind attack feat... Unfortunately I cannot do this as it hurts to see a feat wasted on my Weapon Master!!!
Ok then, is there any sort of fix out there for Whirlwind attack on Linx? I don't care if it's not official and community created or whatever, it's just really frustrating me!
For those that don't know about this, the bug I am referring to is where after using Whirlwind attack in some condition* the player character is unable to make any actions (i.e. attack). This bug was fixed in the windows version of NWN, but it hasn't been fixed in the linux and I believe mac versions...
* some people have said if you use it on only one enemy it will cause the bug, others say if you try and start another whirlwind attack before the previous one has fully finished causes it. While in my experience it is if you try and use it in consecutive rounds...
The apparent fix is to just log out and then try logging back in, which unfortunately doesn't work in my case as I'm playing through the Original Campaign on single player. Where my only option is to revert to a previous save!!!
I would really appreciate it if somebody could provide/point me to some sort of fix for it on linux! Or at worst be the bearer of bad news...
Cheers!
Whirlwind attack bug - linux
Débuté par
Seveneyes
, juil. 23 2010 10:50
#1
Posté 23 juillet 2010 - 10:50
#2
Posté 29 juillet 2010 - 01:04
I only experienced this bug when hasted - i.e., when wearing boots of speed or after drinking a potion of speed or any other form of haste applied to my character.
There is, AFAIK, no fix whatsoever for this bug nor will there ever be :-(
Greetings
Skildron
There is, AFAIK, no fix whatsoever for this bug nor will there ever be :-(
Greetings
Skildron
#3
Posté 30 juillet 2010 - 08:14
Thanks for your reply. I have just done some more testing on it and am getting the bug EVERY time I use the skill now. I don't have the character hasted as well....
#4
Posté 31 juillet 2010 - 03:14
Mac here. Same. It's a real pain. I have a fix though: I simply forgot about it, and started drinking instead.
Maybe I'll blame NWN some day...
Maybe I'll blame NWN some day...
Modifié par jmlzemaggo, 31 juillet 2010 - 03:15 .
#5
Posté 31 juillet 2010 - 04:04
Its said, toggling that steath/search mode will fix it, but never tried that actually.
#6
Posté 31 juillet 2010 - 06:39
http://www.nwnx.org/...light=whirlwind
I'm not sure if that will help at all. There's lots of supposed fixes but none of them seem to be completely reliable. If anyone ever comes up with a reliable Linux patch for WW attack I'd definately be interested in seeing it.
I'm not sure if that will help at all. There's lots of supposed fixes but none of them seem to be completely reliable. If anyone ever comes up with a reliable Linux patch for WW attack I'd definately be interested in seeing it.
#7
Posté 02 août 2010 - 11:39
Ok I have figured out exactly why whirlwind attack now bugs for me. It is whenever I do any sort of action in the same round as the whirlwind attack. If after I complete the whirlwind attack, I don't press anything and wait for the PC to attack again it never bugs out.
Whereas if I do some sort of action before I do the next attack/end the round it will bug out!
This is good as although it is not a fix, I am now able to use it without triggering the bug! Also if there are any programmers around, it may help to understand the bug and fix it
I've tried that and it doesn't work. I had a save that had hit the bug and I tried everything I could think of/find on the web to no avail...
Whereas if I do some sort of action before I do the next attack/end the round it will bug out!
This is good as although it is not a fix, I am now able to use it without triggering the bug! Also if there are any programmers around, it may help to understand the bug and fix it
ShaDoOoW wrote...
Its said, toggling that steath/search mode will fix it, but never tried that actually.
I've tried that and it doesn't work. I had a save that had hit the bug and I tried everything I could think of/find on the web to no avail...





Retour en haut






