• Check out the results of the Techtree Contest #19!
  • Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!

[General] Doodad not in sight problem

Jumbo

Hosted Project GR
Level 20
Joined
Jun 22, 2007
Messages
1,341
Hi,

I have searched the forums first and didn't find my problem anywhere. You see in the screenshot how one of the rocks is out of LOS for some reason even though it is right there on the same position as the surrounding rocks which are in sight. When I move my unit slightly suddenly the rock is within sight (i.e. not ugly and blackened out).

Under the rocks the only thing that is there is regular pathing blockers. Nothing that should block vision.

I have tried to set the terrain for the whole place to same height and elevation level but to no avail. The bug persists and it looks ugly.

Can anyone help me with how to fix this?
 

Attachments

  • doodadLOSproblem.jpg
    doodadLOSproblem.jpg
    288.6 KB · Views: 30
Sorry, internal developing. Anyway, I'll probably figure it out eventually.
Maybe you could copy the contents to a new map? You can drag and select "everything" (terrain, doodads, etc) and copy them from one map to another. Imports might be a pain but it might be worth spending the 5 minutes to get an extra set of eyes on the problem.
 
A few things worth checking come to my mind:
1) Fat Line of Sight setting in Object Editor of surrounding objects. If this option is ticked the game 'blocks' the vision behind the objects themselves. This might affect the situation, even if the objects have no collision. I am not sure, worth checking out.
2) Faulty terrain calculations - sometimes shadows and lines of sight might get buggy. In this scenario it's best to recalculate shadows and try to copy and paste the underlying terrain from another part of the map to 'reset' what the editor thinks is underneath.
3) Issues with the model itself: it is possible the model of the rock itself has faulty normals or extents, but this is unlikely if the model performs properly elsewhere on the map.
 
Back
Top