Aarik D

Hey guys, I am still unable to reproduce this issue. Could someone please upload a save and an output log? Thanks

Hey wbc889, This is still an open issue. So it hasn't been fixed yet.

Thank you ironhideforeve. I have written up a report and added your files.

Hello Solostarian, Welcome to the forums and thanks for joining us. What build are you currently on?

Hey Andrea, Thanks for bringing this to our attention. I wrote up a bug saying that the combat log is not showing the proper damage type as raw. There is also another bug that Trigger Immunity isn't actually immune to raw damage. Which is why Take the Hit is not getting immunity from it. Thanks a bunch!

Hey Gromnir, What seems to be the problem? It appears to be working fine in the new 3.02.1008 beta build which was released about 2 hours ago. Try that new update and see if that resolves the issue. Thanks! P.S. Its been fixed

Hey Kaylon, I went to investigate this issue and fighting spirit is triggering just fine in the latest 3.02.1008 beta build which was released today. Thanks!

Hey guys, Both issues has been fixed in the 3.02 beta! Keep on rockin!

Hey Reent, Thanks for bringing this to our attention. There might have been some changes made to charm where it will break on attack, I will confirm if that is the case. Combat however, should not restart when doing so. I have written up a bug on the issue and added it to our database. Thanks a bunch!

Hey everyone, We just branched the latest patch to the beta. Check out 3.02.1008!

Patch notes are out!!! https://forums.obsidian.net/blog/7/entry-192-update-notes-302/ We also updated the beta branch with a new patch! Thank you guys so much for your patience!

That would be great! Please include a dxdiag file as well. Thanks!

Hey dam, Not all quests give the same amount of turns. We give more turns per quest in PX2 since there are less quests in PX2 than PX1. When you are given turns it is possible to get decimals of turns. The stronghold system will keep track of these and add up an additional turn when it reaches a full number. I hope that clears that up for you.

Hey Reent, Thanks for bringing this up to us. I'm not sure if that much range is intended. I written up a bug and added it to our database. Thanks a bunch!

Hey Panda Baby, Are you playing on the beta branch? It should be fixed already. Thanks.

Hey PugPug, Glad you were able to resolve your issue. But just in case, if you are playing on Steam, make sure to verify your game cache. Thanks!

Hey guys, Yeah, we still have a open bug on this. It happens with modals that activate on combat and when you assign actions on pause, it will make the character stuck. You can just assign another action and the character will move freely again. Thanks!

Oh you're right! Haha, my bad. I'll fix the title. Thanks for looking out!

Hey Harpagornis, Thanks for bringing this to our attention. Fortunately, I we are aware of the issue and is fixed in 3.02. Thanks a bunch!

Try uninstalling your video drivers and getting a fresh download and install that.

Hello ironhideforever, Welcome to the forums and thanks for joining us. Have you tried verifying your game cache in Steam? Try that and see if it resolves your issue. Thanks!

Hey Ingvalion, Welcome to the forums and thanks for joining us. Just so you know, your first 5 post have to be approved, so thats why you weren't seeing your posts. As for your issue, try verifying your game cache and see if that works. In your Steam library, right click PoE > Properties > Local Files > Verify Integrity of Game Cache. Thanks!

Hey NobleHelium, Welcome to the forums and thanks for joining us. Could you please upload your output log as well? It seems the issue is only directly related to your save. I loaded up a different save and Urthal and his men were doing the appropriate damage. Thanks!

Try verifying your game cache in Steam as well. I notice some errors in your log. In your steam library, right click PoE > Properties > Local Files > Verify Integrity. Thanks!

Hey gruelest, Welcome to the forums and thanks for joining us. Apologize for the delay. Fortunately we are aware of the bug and currently working on a fix. Thanks a bunch!