Help With Bad Dif Mipmapping

#1 It's not a mipmapping issue; it's actually more subtle (specifically, the engine swaps out the bottom part of the mipchain when it thinks models are out of range). Out of curiosity, did you scale it when you placed it in game?

#2 I did i fit it to the side. Its really the only way to do it in quark. The texture tool is otherwise impossible to use so i just fit it.

#3 I'm interested in this issue as well... is there any way to _tell_ the engine when the models are out of range? Is it based on the LOD pixel size at all?

#4 I went into the code to take out the mipmapping section and still not affect.
Before
After

#5 Usually changing the texture size will help fix this. I can never remember if you should make it larger or smaller but a few simple tests should determine it.

#6 Bryce, did you remove mipmapping or the small texture check? It's the latter you need to poke at.

#7 I went in a removed the useSmalltextures( cont bool t) { return };

still having a problem with the texture.

I will however test the size to see if a les detailed or more detailed works.
Testing.... please standby....
0%.....

#8 You wannt to blase the lines that say:

TextureManager::setSmallTexturesActive(true);

There's one, on line 927 of interiorInstance.cc.

#9 // We need to decide if we're going to use the low-res textures
Point3F camPoint = state->getCameraPosition();
Point3F closestPoint = getRenderWorldBox().getClosestPoint(camPoint);
F32 dist = (camPoint - closestPoint).len();
if (dist != 0.0)
{
F32 length = dglProjectRadius(dist, 1.0f / pInterior->mAveTexGenLength);
if (length < (1.0 / 64.0)) <----------------------------------------------------------------- Increased
{
TextureManager::setSmallTexturesActive(true);
}
}

#10 Still testing....
12%....

#11 Changing that number may do nothing for you. Best way to be sure is to comment out the call.

#12 I went in a removed the useSmalltextures( cont bool t) { return };

still having a problem with the texture.

I will however test the size to see if a les detailed or more detailed works.
Testing.... please standby....
0%.....

#13
Once i increased that number to 64 from 16 it was good as gold.

For others the line i modified is listed above.

#14 I had the same problem but it works now..

thanks.

#15 Excelente post, me ayudó a resolver el mismo problema que tenía. Thanks!!!