BobTheHunted

Ok, I managed to solve the issue (or at least I managed to make it go away for now) I was talking to some people in the terrain makers discord channel and trying to troubleshoot my issue. After a while I seemingly fixed the issue. Turns out it has nothing to do with my mask (other than the position of the textures). It was the texture itself (the one with the borders, not the textures in the border) Here is the message I sent in discord detailing the steps I had taken leading up to me solving the issue: Thanks to Lappihuan, Pennworth, Rhaonoa, HappyDuckie, and Ice for the help and input It still looks pretty weird to me :)

I think he means copy your original buildings model, paste it, give it a new name, and edit it in object builder to have whatever different textures and materials you want in that version. Then you save it and import that model into TB alongside the original model

Ok, it seems this problem has nothing to do with each individual cell. I have a properly set up mask with no cells that exceed the 5 texture limit and when I run the mask image through mask checker it reports no errors or cells with more than 5 colors. It seems this is only happening when the map itself exceeds the 5 (or 6, without the normalmap) textures. So the problem remains unsolved EDIT: No matter how many textures I have, this issue is still present, so it isn't connected to the mask at all as far as I can tell

http://imgur.com/0lJTH8W This is what the end result looks like. The grey lines are the grid (the guides are hidden here) The tile in the top left is imported from my layers folder and lined up to match It seems like there is a small offset that can be fixed if I simply lower the guides to line up with the bottom of the tile. EDIT: It actually lines up perfectly, I just accidentally shifted the image up at some point and didn't notice.

Ok, so I found a good way to get a 'grid' or some sort of visual representation of each cell of the surface mask and where they overlap (Or relatively close to it) Using pennyworth's tool you can see a debug map for all of the cells that exceed the texture limit. So, to get a basic idea of the layout easily, just do the following(in photoshop): 1. Create a new image (or layer) the same size as your mask image 2. Fill it with a random color. 3. Select filters > noise > add noise Settings: 400% Uniform Not monochromatic 4. Press ok and wait until the noise generates, then adjust the brightness and contrast so there are no pure black pixels 5. If there are any darker pixels, you could just use select > color range to find them and fill them with a different color 6. Save the file and launch the bat file to pennyworth's program, there will be a lot of extra colors (might be a performance issue, but it worked for me. If it is, you just need more than six colors per cell, or in this case the entire image) 7. When it's done, there will be a new debugmap.bmp in the bad tiles folder. Select that file and import it into photoshop 8. Select > Color Range > Color pick black and set the fuzziness to 0, press ok (You can also do this to make quick selections of all of one single color on your mask image, quicker than magic wand, stuff like that) 9. Cut the pixels, paste them to a new layer, name it 'mask grid' or whatever, and you can use it as a basic guide for editing your mask. You can now delete the 'noise' layers you made 10. Not sure if this will work, but you could create guides in photoshop and set them to the middle of each black line (as they are several pixels thick, so not accurate down to the pixel) and have a potentially more accurate guide. Also, if the guides created in photoshop seem too thick or slightly out of place when at different zoom levels, you can turn off anti aliasing on grids/guides/helpers etc in the photoshop preferences, which should help if that becomes a problem I will test out the accuracy of this and report back any issues, but hopefully it will work and be a quick method to use to determine cell boundaries in the future

I win

It's not a weird thing that the error is happening when it shouldn't be?

I will look into these. Thanks for the suggestions!

Ok, weird thing. I removed a texture on the mask and the problem is solved. Is the 6 texture limit for the entire map? I thought it was for each tile. If it is, how do I properly separate them in photoshop so I know where each cell ends? I thought I could just configure the grid to match the tiles and it would work, but apparently I am wrong. Maybe there is a rogue pixel in the wrong cell somewhere on the mask. How can I pinpoint it's location?

I am using my own texture addon but with BIS textures at the moment. Don't know if that's relevant, but I guess I should mention it

Unfortunately that isn't the case. I have only up to five textures per cell (which I have properly set up) and no more than that. I also have a normal map for the terrain, so I can only have five textures aside from that. Unless there is a single rogue pixel somewhere in the mask, I don't really know what could be causing this issue

I am noticing a really odd visual problem in my ground textures for my terrain. Everything seems to work fine, except in some areas I get weird 'outlines' or 'borders' around a certain texture type on my terrain. It is as if it is trying to fade into a different texture when it shouldn't be. For example: http://imgur.com/3xmh33A http://imgur.com/Kv1XMyA http://imgur.com/eFEWAMY

I am using it for my terrain. I am just trying to import my eden object layout into TB. Apparently xCam is able to do that correctly, but I guess that is not the case until BI fixes their tools. My goal was to import my mission objects into xCam and then export the TB file from xCam so the rotation/pitch/bank export properly to terrain builder. But it seems that still isn't possible at this point for some reason

Well after doing all that the rotation is still wrong on literally every object that isn't just in it's default position. I thought one of xCam's benefits was it's ability to properly export objects? Unless I am missing something. Will report back any discoveries

I found a potential workaround for the problem. I dissected the two different project files, one with an object place by xCam, and another with an object placed and inserted into xCam. The difference I noticed is the dat_# part of the project file. I noticed that the last string points to a .p3d model file for the object, but in the mission import project it just displays the classname again. When I edited the classname to the model so the structure matched the first project, when I exported to terrain builder it properly displayed the classname. So I guess I will just have to edit the project file manually. It works I guess