Textures gets messed up depending how closed you are

MasterM · Post by **MasterM** » Sat Jul 11, 2009 7:09 am

Hey all, i was going to start a demo of my first game and i loaded the mesh and applied a texture to it but when i quickly ran it to see if everything is fine i noticed that the texture on the mesh gets screwed when i go far and when i close in it fixes itsself.

Here are the tree pictures i have taken to show the possibly bug :
close

medium far

further

and my code is simple, it looks like this :

Code: Select all

#include <irrlicht.h>


using namespace irr;


using namespace core;
using namespace scene;
using namespace video;
using namespace io;
using namespace gui;


int main(int argc, char** argv)
{


    IrrlichtDevice *device =
        createDevice(EDT_OPENGL, dimension2d<s32>(640, 480), 16,
            false, false, false, 0);


    IVideoDriver* driver = device->getVideoDriver();
    ISceneManager* smgr = device->getSceneManager();
    IGUIEnvironment* guienv = device->getGUIEnvironment();


    IMesh* mesht = smgr->getMesh("board.obj");
    IMeshSceneNode*node = smgr->addMeshSceneNode( mesht );
    node->setMaterialFlag(EMF_LIGHTING, false);
   ITexture *text=driver->getTexture("lolgf.PNG");
   node->setMaterialTexture( 0, text);



    smgr->addCameraSceneNodeFPS();


    while(device->run())
    {
        driver->beginScene(true, true, SColor(0,200,200,200));

        smgr->drawAll();
        guienv->drawAll();

        driver->endScene();
    }


    device->drop();

    return 0;
}

Halifax · Post by **Halifax** » Sat Jul 11, 2009 8:23 am

What version of Irrlicht are you using?

FuzzYspo0N · Post by **FuzzYspo0N** » Sat Jul 11, 2009 3:32 pm

looks like mip map artifacts, weird

MasterM · Post by **MasterM** » Sat Jul 11, 2009 4:01 pm

I am using Irrlicht version 1.5

MasterM · Post by **MasterM** » Sat Jul 11, 2009 6:09 pm

[edit]I have the Nvidea ati radeon 9550

I think that's the problem cause its also doing it with the standard irrlicht tutorial 1
[edit]and it only does it with opengl(cant use directx cause its gcc), software render doesnt flip like that :/

sio2 · Post by **sio2** » Sat Jul 11, 2009 6:24 pm

Code: Select all

createDevice(EDT_OPENGL, dimension2d<s32>(640, 480), 16,false, false, false, 0);

Hmmm. Is your mesh a very slim box? Are we seeing the reverse side because of 16bit depth precision?

Try a 32bit depth buffer instead of 16. Or better values for near/far planes (push Near out as far as possible and move Far in as close as poss).

MasterM · Post by **MasterM** » Sat Jul 11, 2009 6:37 pm

Well i tried tutorial 1 with 3d bit depth and my graphics card set at factory defaults and it still looks screwed

, here's a pic to demonstrate

twilight17 · Post by **twilight17** » Sat Jul 11, 2009 6:50 pm

Code: Select all

driver->setTextureCreationFlag(E_TEXTURE_CREATION_FLAG::ETCF_CREATE_MIP_MAPS, false);

Try that, also try to disable biliniear filtering

MasterM · Post by **MasterM** » Sat Jul 11, 2009 7:05 pm

Thanks Twilight17, that worked...For everyone else having this problem tried what Twilight17 said.

sio2 · Post by **sio2** » Sat Jul 11, 2009 7:45 pm

Wow. Not quite "solved" yet, as I think something is strangely broken there. Is your texture a power-of-two?

Halifax · Post by **Halifax** » Sat Jul 11, 2009 7:58 pm

sio2 wrote:Wow. Not quite "solved" yet, as I think something is strangely broken there. Is your texture a power-of-two?

Yes, I agree. I don't think it's not solved yet. And that's what the problem appears to be, a NPOT texture.

MasterM · Post by **MasterM** » Sat Jul 11, 2009 8:14 pm

Sorry but whats a power of two texture?

twilight17 · Post by **twilight17** » Sat Jul 11, 2009 8:15 pm

Halifax wrote: And that's what the problem appears to be, a NPOT texture.

No, it's not that because the sydney example also has this problem. I'm guessing it's just something with his graphics card, incompatibility of some sort. Try updating your drivers by the way!

FuzzYspo0N · Post by **FuzzYspo0N** » Sat Jul 11, 2009 8:35 pm

if mip maps false is true and its fixed it might be something way deeper, it might even be an engine issue. Though, it seems pretty driver specific to me (i had meshes in a game that for some reason had missing polys on an ati)

Halifax · Post by **Halifax** » Sat Jul 11, 2009 8:41 pm

twilight17 wrote:No, it's not that because the sydney example also has this problem.

Don't forget, that's using the software renderer.

Either way, we really need more information, and he should really try Direct3D 9 to see if there is a difference. I have always heard that ATI's OpenGL support is rather shoddy.