7 réponses à ce sujet

[Dann-J]

Has anyone ever experienced this problem before?




For some reason, three entire tiles in this 8x8 outdoor area are refusing to show more than one texture. The missing textures show up in the toolset, on the mini map and on the area map - just not in the actual game window.

There are only three textures being used in this entire area at the moment. Originally only one tile in this area was having this problem (although it was outside of the walkable area). Now two more have joined it.

Re-baking has no effect. I also tried exporting the area as an ERF and importing it into a new blank module. It still won't cooperate. There aren't many placeables either - just a few static houses, a few 'environmental object' rocks, and some trees in the distance. I wouldn't think they'd have any effect on the terrain texturing anyway.

There is a lot of water though (mostly outside of the walkable area). Yet I've made much larger areas than this, with more water and textures, with no problems before.

Is it just a case of the toolset moving in mysterious ways?

Modifié par DannJ, 22 août 2011 - 10:57 .

[kamal_]

I've seen weird things like that when the toolset decides it's missing one of the 6 potential textures. If you look at the list of textures used, it might have texture 1 (mud05), texture 2 (blank), texture 4 (grass43), for example. The fix is usually to swap some textures until you have a proper list. Then you can swap back to what you want.

Modifié par kamal_, 23 août 2011 - 12:51 .

[Dann-J]

Thanks, I'll check that out. I'm also going to try using TerraCoppa to see if I can shock the area into working properly.

My current theory is that it's a sahuagin plot to prevent me from making a darfellan village...

[Lugaid of the Red Stripes]

It's been a while, but I remember a weird bug where the toolset wouldn't properly overwrite the terrain file used by the game. You can get around it by duplicating the area, saving it under a new name, and then deleting the old. Then you can go back and re-name it to the original name.

[Dann-J]

Another good idea. Previously I'd just exported the area and re-imported it into a new module. It never occured to me to just duplicate the area in the same module (which would also force a rename for the area).

Come to think of it - I originally gave the area a two-word name with a space in it. I wonder if that may have initiated the problems?

[Morbane]

i have spaces in area names all the time - that probably is not the problem

[Dann-J]

I tried quite a few things, like swapping textures, copying and renaming the area, and using TerraCoppa to clone it into a new blank area, all to no avail. I systematically deleted all placeables, environmental objects and plants, and removed the water and texture tints. The result? The problem spread to more tiles!

I finally bit the bullet and retextured the entire area. Instead of starting with the wavy sand texture as the base and adding grass textures over the top, I used a grass texture as the base and added the wavy sand instead. So far the area is behaving itself again, so that seems to have fixed things.

It seems there are textures that like to be on top, and those that like to be underneath (lets call them "pitchers" and "catchers"). Apparently forcing a pitcher to be a catcher is a bad idea...

Modifié par DannJ, 23 août 2011 - 10:24 .

[kamal_]

Don't feel too bad, look at the beautiful screenshot thread and you can see it in one of the Misery Stone shots in the first post.