black screen

[darkgod]

Ahah anta I was about to say exactly that

[darkgod]

Ok I have reverted the canSee change for now, I'll need a beter fix later :<

[Shoob]

here is my glewinfo.txt file

[Antagonist]

Heh, perhaps make an article similiar to the running with gdb one, just on getting glewinfo info. It will be needed for any graphics feature related bug, like power of two textures, shaders, framebuffers, etc.

What I've also see happen is when you have an advanced card with all the features you need, but the features are named differently so the app doesn't think you have support for them, such as with glFrameBufferARB and glFramebufferEXT, despite them both working the same way. So a glewinfo is also needed if you expect fancy features, but dont get them as well.

Course, once all the common issues are sorted they should stay that way, unless even more fancy features are implemented.

EDIT:
Shoob, I just checked your glewinfo, your card DOES support FramebufferEXT, tho not FramebufferARB, so your issue I dont think is the same as Gwai's. Also, the portion of the log you pasted doesn't seem to be the earliest error?

EDIT2: Argh, feel like an idiot. DG just above me said it is an issue with a canSee hack. Nevermind then.

[Gwai]

For some reason I'm not managing to attach any files to a forum post. Whatever extension I stick onto the glewinfo.txt file it says isn't valid. So I emailed it to the email you use to write the tome list, darkgod.

[darkgod]

Got it thanks

Your card does seem to support FBOs ad yet it does not display anything :/
Can you send me the log too (all of it from start to when map should display) ?

[Gwai]

Can do. Started a character and then emailed you the stdout file.

[darkgod]

Hum I did not receive anything

[Antagonist]

Gwai, your glewinfo only mentions your chipset, aka a P45 Eaglelake, but not what GPU it has. (P45 doesn't always come with an integrated one) Is it integrated? Non-integrated additional one? I need the code of it preferably.

[Gwai]

darkgod, that's very odd since it thinks it went to the same address as the glewinfo that you did receive. Maybe the mail was just held up by the system? I'll re-send anyway and see if that helps.

Antagonist, am not on that computer now so I can't check, but I will when I get home tonight. Last time I just went to the specs and they gave me the name (which is somewhere on the first page of this thread.) Still, my bet is that it's integrated, because I remember taking the cheap deal on the graphics card so that I could save my money for elsewhere. (Quad-core etc. is more fun if you ask me.)

[Shoob]

sorry antagonist, what got me confused what people posting out of topic... I noticed some people doing it, and then forgot about it

mine was a loading problem, not a blank screen problem.

[Antagonist]

Okay, Gwai, you said you had a G45/G43 chipset earlier, sorry I missed it.

I do however find it hard to beleive. Thats the X4500, an Intel card with actual OpenGL 2.1 support, which your glewinfo says you do not have.

If it IS your GPU, then you need a driver update. Should be simple from the Intel website.

I dunno what else to tell you.

If it still doesn't work even after a driver update I'll need to take another look at it.

[Gwai]

Wow, didn't think I had a card that would support much of anything, but that just shows what I know. I got new drivers, and am seeing the fancy version fine now. Thanks Antagonist!

[darkgod]

Ahah nice

[Antagonist]

Glad it worked.

Does worry me tho, your driver reported FBO capability when it had none. Theres no way for the game to detect that kinda stuff and switch off shaders when it happens.

But this is issue #2 solved with a driver update now. Should make it one of my first replies to graphics related issues from now on.