Hey! Right now I'm trying to change the textures to better represent the years when the IRL went to Nazareth. Its not totally accurate, but its a big improvement. Anyways, I have the sponsor billboards changed to the way I want them but I get this problem after I changed a couple of them, nbridge.mip and nscore.mip to be exact.
I did a test to see how well the tracked looked after the changes. It looks fine from far away but as the textures got closer, they suddenly blurred out. I've never seen this before.
I uploaded some pics to show you guys what I'm talking about. "Before" is when my car was further away, "After" was when it got nearer. What could be the problem here?
You may know that a mip is not one picture but a bunch of them thrown into one, from very small to normal size. The smaller ones are used when the object is far away and the bigger ones are loaded when the object gets closer to you. This is called LOD [Level Of Detail] and it's done to put less strain on the computer. It looks from the pictures that the smaller version[s] in the .mip file is ok, but the bigger ones are corrupt.
I will take a wild guess and say that you are using Winmip? You might want to look at trying another tool to convert the .bmp files to .mip. I have always found that Robert Szikszo's Last Chance tools offer better quality over WinMip. But there are other tools too. Hope this helps and good luck.
I've used Winmip for everything and never had a problem. Why does the bridge seem to have different colors in each picture? Is this the same bridge?
Also, just a suggestion but did you make sure you saved the mip in the right direction? I know this is a longshot but I remember working on a mip that I had to turn in the right direction and then forgot to turn it back. Sometimes it won't let you save it but a "square" mip will save no matter what.
I'm reaching way out on this but tough to see why you're having this problem because I don't recall having it. Got to be an easy fix.
this isn't something I see out of winmip2 very often, but winmip 1 and papybmp both cause it. in winmip2, the LOD is called sub_im for sub images. your computer hardware can affect how winmip2 saves the sub images. you can try changing the sub_im setting to 0 on the mip and see if that helps. Also, try saving the bmp to mip and then reopen the mip and change the sub_im to the max. That sometimes helps me with M16 files that don't want to register a good sub_im the first time around.
