Hi,
Over the past day or so of compiles, my map has started displaying a couple of strange behaviors.
i) Sometimes thin dashed/dotted white lines appear along the floor, flickering as you move around and look at them. Normally I would expect them to be the result of poorly-joined brushes for the floor, but in this case they are actually lines in the middle of one-piece, unbroken brushes. I do think that they may be aligned with other, adjacent brushes a few feet away in the map, e.g. a section of wall.
ii) More weirdly yet, I am getting sections of floor which have a different texture when playing than in Hammer. There is absolutely no other brush beneath the floor; there's no other texture fighting for that area of the floor. I have no idea why the floor is taking on some of the wall texture there.
Screenshots:
In-game (wrong) --
In Hammer (right) --
My compile is not coming up with any errors -- I ran it through interloper's logchecker.
Any thoughts on this? Has anyone else seen this? Could this be the result of a recent Hammer update, or perhaps a byproduct of a separate bug?
Cheers,
Mokagogo
Over the past day or so of compiles, my map has started displaying a couple of strange behaviors.
i) Sometimes thin dashed/dotted white lines appear along the floor, flickering as you move around and look at them. Normally I would expect them to be the result of poorly-joined brushes for the floor, but in this case they are actually lines in the middle of one-piece, unbroken brushes. I do think that they may be aligned with other, adjacent brushes a few feet away in the map, e.g. a section of wall.
ii) More weirdly yet, I am getting sections of floor which have a different texture when playing than in Hammer. There is absolutely no other brush beneath the floor; there's no other texture fighting for that area of the floor. I have no idea why the floor is taking on some of the wall texture there.
Screenshots:
In-game (wrong) --
In Hammer (right) --
My compile is not coming up with any errors -- I ran it through interloper's logchecker.
Any thoughts on this? Has anyone else seen this? Could this be the result of a recent Hammer update, or perhaps a byproduct of a separate bug?
Cheers,
Mokagogo