Ok here’s a weird one for you. I have a single tile grid that cannot be spawned into. When I try and spawn my pc into the tile grid all I see is black and my character is unable to move. It’s almost like I have spawned into an area that had no tiles painted down even the map is totally black.
Here’s the kicker, if I spawn into the tile right next to the faulty tile everything works fine and the area behaves like it’s suppose too. I’m able to see and walk around, even walk around the tile that is faulty.
Yes I have baked and yes I have tried replacing the tile. Even tried using a deferent tile but with the same result.
Any idea’s?
Single Faulty Tile Grid
Débuté par
Alupinu
, sept. 01 2012 04:51
#1
Posté 01 septembre 2012 - 04:51
#2
Posté 01 septembre 2012 - 06:22
Yes that's odd. Is the area size the same as the grid size?
#3
Posté 01 septembre 2012 - 06:36
rjshae wrote...
Yes that's odd. Is the area size the same as the grid size?
Well if I understand your question correctly then no. Grid size is just one square that just one tile would fit in. The area itself is about 18x20 if I recall.
#4
Posté 02 septembre 2012 - 12:56
you should have a border of 1 empty square around the area border?
#5
Posté 02 septembre 2012 - 01:26
Morbane wrote...
you should have a border of 1 empty square around the area border?
I do and the spot where the grid square is acting up I have two squares from the boarder.
#6
Posté 02 septembre 2012 - 02:20
No idea except maybe too many placeables made the area unwalkable?
#7
Posté 02 septembre 2012 - 02:56
Was it an illefarn tile with two doors? I had trouble with that tile, and ended up removing it from my area. It was talked about a while back.
Weird Bug!
Weird Bug!
#8
Posté 02 septembre 2012 - 08:23
Well I think I have fixed the problem. This is what happened, in desperation I made a duplicate copy of the area. The problem suddenly disappeared. So I deleted the original copy and changed the file name of the duplicate area to the file name of the first copy. (i8_shallows) but as soon as I changed the file name the problem reappeared. “What the hell” I thought. So… I tried changing the file name back to the way it was. (i8_shallows1) and suddenly the area is working fine. What, where, why that happened I have no idea but for some reason the name of the file seemed to make all the deferent’s.
Modifié par Alupinu, 02 septembre 2012 - 08:24 .
#9
Posté 02 septembre 2012 - 10:57
Could the toolset have crashed at some point, and left a heap of temporary files in some obscure system folder somewhere? I've had that happen to me, whereby none of my script changes were showing up when I ran the module directly from the toolset. The temporary files were overriding things somehow.
I now run the disk cleanup utility (right-click on C: drive) on a regular basis. It gets rid of any leftover temporary files floating about after the toolset has crashed.
I now run the disk cleanup utility (right-click on C: drive) on a regular basis. It gets rid of any leftover temporary files floating about after the toolset has crashed.
#10
Posté 03 septembre 2012 - 12:08
DannJ, not that I can remember. I haven’t had a ts crash in a long time. (Knock on wood) but that would make sense.
That’s a good idea I should get in that habit as well.DannJ wrote...
I now run the disk cleanup utility (right-click on C: drive) on a regular basis. It gets rid of any leftover temporary files floating about after the toolset has crashed.
Modifié par Alupinu, 03 septembre 2012 - 12:08 .





Retour en haut






