Translucent creatures

[Legacy_Proleric]

               In some situations, I find that creatures become translucent, i.e. visible but the player can see through them like a ghost.


It might be a line of sight issue, as it mostly happens when a creature is on a platform or behind a buttress, especially in custom tilesets.


Can't find anything on this after a quick search - any thoughts?
               
               

               
            

[Legacy_Failed.Bard]

               

It sounds like there's no direct LoS to them, but they can still be "heard", and it's treating them the way it would if they were stealthed and heard but not seen by the player.

               
               

               
            

[Legacy_Pstemarie]

               

It sounds like there's no direct LoS to them, but they can still be "heard", and it's treating them the way it would if they were stealthed and heard but not seen by the player.

 

Wonder if there is a way to check this through scripting.

               
               

               
            

[Legacy_Failed.Bard]

               

LineOfSightObject( object oSource, object oTarget ), though it might have to be checked in both direction to verify.


I'm assuming that it checks from aurorabase to aurorabase, so it's hitting the LoS blocking wall surface based on a straight line between feet.

               
               

               
            

[Legacy_Pstemarie]

               

@ Proleric, using that function FB mentioned, you might be able to make some debug checks to check if LOS exists from the PC to the creature.

               
               

               
            

[Legacy_Proleric]

               

In the example above, though there appears to be a line of sight from the kneeling PC to the sitting judge, LineOfSightObject() returns FALSE. As predicted by your helpful comments, the judge is ghosting.

However, when the judge is standing in the same position, LineOfSightObject() returns TRUE, and the ghosting ceases:



In the case, it seems that sitting on a platform is the issue. Moving the chair nearer to the PC, or having the PC stand, makes no difference whatsoever. The platform tile is tcd01_p36_01 from Classic Dungeon (same issue with the Project Q version).

This one I can live with (the judge looks OK standing up).

I'll post other cases as I find them (e.g. the buttress wall, where arguably the player doesn't have line of sight, even though their camera does).
               
               

               
            

[Legacy_Pstemarie]

               

I'll have to look at the Q version of that tile and check the walkmesh - I've found faces on other tiles in that tileset that were set to "obscurring" and not "stone" like they should be.

               
               

               
            

[Legacy_Failed.Bard]

               

It looks as though the NPC is also further back when they're in the seated position, vs standing, in those screenshots.  Is it possible to just move the chair further up, in that case, to work around it?

               
               

               
            

[Legacy_Proleric]

               No, moving the chair makes no difference.
               
               

               
            

[Legacy_cervantes35]

               

I'm not big into building placeables but could it be the PWK that is obscurring your LOS as in your pictures it only occurs when seated.

               
               

               
            

[Legacy_Pstemarie]

               

Proleric, see if this works. I fixed some issues with the walkmesh and changes the "transparent" face material to no walkable. If this doesn't work, I think I know what has to be done.

 

https://www.dropbox...._p36_01.7z?dl=0

               
               

               
            

[Legacy_Proleric]

               

Proleric, see if this works. I fixed some issues with the walkmesh and changes the "transparent" face material to no walkable. If this doesn't work, I think I know what has to be done.
 
https://www.dropbox...._p36_01.7z?dl=0

Thanks, but it still has the same issue.
               
               

               
            

[Legacy_Pstemarie]

               

Ok, I think I know what might be wrong. The walkmesh has a slope leading up to the dais from the front and on both sides, even though the geometry on those faces is perpendicular to the floor. I'm thinking Maxam might once have intended these areas to be steps leading up to the dais. The dais is also higher than the typical dais height use in standard Bioware tilesets. Its possible that the height of the dais combined with the slope is choking the  algorithm the engine uses to determine LOS. 

 

I'll try a few more tweaks and see what we get...

               
               

               
            

[Legacy_Pstemarie]

               

Still working on this - right now....I AM STUMPED!!

               
               

               
            

[Legacy_Failed.Bard]

               

Without seeing the tile in question, the only thing I could think of that might do it would be if one of the vertical surfaces had an obstructing material, or, if at an engine level, LoS paths that travel "outside" the mapped tile are immediately considered to have no LoS.

  The latter could likely be tested with a simple tiered, all walkable, tile replacement.