Spells at target getting blocked in some dungeons [RESOLVED]

Post Reply
User avatar
Midknightprince
Posts: 835
Joined: Fri Aug 11, 2017 6:51 am
Location: San Antonio TX
Contact:

Spells at target getting blocked in some dungeons [RESOLVED]

Post by Midknightprince » Wed May 09, 2018 5:42 pm

I know this kinda happens in classic, but in these places you can't reliably cast spells at anything.
I've only found one place so far.
Totambu: The Tower of Ghirt, just northeast of Gentle Oracle of Zenithar, by the border.
I'm just playing vanilla here, so it's not the mods or textures.
Check out my YouTube Channel!

User avatar
Midknightprince
Posts: 835
Joined: Fri Aug 11, 2017 6:51 am
Location: San Antonio TX
Contact:

Re: Spells at target getting blocked in some dungeons

Post by Midknightprince » Wed May 09, 2018 6:16 pm

So I went to several other dungeons, and a few graveyards, I even went to another one that had the same room layout as in the vid (the big room with the pillars, and platforms etc), no problems, zapping works fine.
Just something, hope it helps.
Check out my YouTube Channel!

User avatar
Interkarma
Posts: 3608
Joined: Sun Mar 22, 2015 1:51 am

Re: Spells at target getting blocked in some dungeons

Post by Interkarma » Thu May 10, 2018 4:12 am

Thanks for the video. It looks like spell is being caught on player capsule - but that shouldn't happen as I exclude that collision in physics system. But it looks just like that.

Sorry to be a pain, but next time this happens can you save game and send me the save. It will save me from having to track down the location manually, I can just load up your save and go straight there. It saves me a little time. :)

User avatar
Midknightprince
Posts: 835
Joined: Fri Aug 11, 2017 6:51 am
Location: San Antonio TX
Contact:

Re: Spells at target getting blocked in some dungeons

Post by Midknightprince » Thu May 10, 2018 4:51 am

Got it, I'll try and remember.
Here's the save inside, just head out the door, and theres an archer on one of those ramp things.
I was casting AOE at point blank range, and the spells have no effect on even me sometimes, sometimes it works, and it does it pretty much in this whole dungeon., no matter where you're at.
Attachments
SAVE28.zip
(239.62 KiB) Downloaded 8 times
Check out my YouTube Channel!

User avatar
Interkarma
Posts: 3608
Joined: Sun Mar 22, 2015 1:51 am

Re: Spells at target getting blocked in some dungeons

Post by Interkarma » Thu Oct 11, 2018 2:54 am

Bumping this one, I've been able to reproduce and confirm.

Issue is related to a mesh collider for specific dungeon pieces (ID 58030 is one such piece) somehow triggering collisions even well outside of their vicinity. Trying to track down root cause and will update when I can.

User avatar
Interkarma
Posts: 3608
Joined: Sun Mar 22, 2015 1:51 am

Re: Spells at target getting blocked in some dungeons

Post by Interkarma » Thu Oct 11, 2018 10:25 pm

This is a problem with OnTriggerEnter specifically. I'm changing missiles to use OnCollisionEnter instead, which is more robust.

Edit: Fixed in next builds.

User avatar
Midknightprince
Posts: 835
Joined: Fri Aug 11, 2017 6:51 am
Location: San Antonio TX
Contact:

Re: Spells at target getting blocked in some dungeons

Post by Midknightprince » Thu Oct 11, 2018 10:37 pm

Interkarma wrote:
Thu Oct 11, 2018 10:25 pm
This is a problem with OnTriggerEnter specifically.

I'm changing missiles to use OnCollisionEnter instead, which is more robust.
So it's just the missiles, seems like it was a while ago but I haven't been casting spells in dungeons.
I'll check the save if you want me to.
Check out my YouTube Channel!

User avatar
Interkarma
Posts: 3608
Joined: Sun Mar 22, 2015 1:51 am

Re: Spells at target getting blocked in some dungeons [RESOLVED]

Post by Interkarma » Thu Oct 11, 2018 10:55 pm

It's an issue between a specific dungeon piece (e.g. 58030), spell missiles, and OnTriggerEnter. When the problem dungeon piece is present in scene, spell missiles will collide with that dungeon piece at any range (even a million units). It seems to be a quirk of how trigger system handles collisions (badly in this case).

Anyway, problem is resolved in next builds.

Post Reply