A QW player named Retroactive is having a problem with EZQuake, goes like this:


I think this issue is the same to what another player I know who reported problems with FuhQuake. He sees console text in-game, but if he goes to console it is blank"


When in console ... no console text!

I have a friend back here in Brazil with the same problem! He is using a motherboard with chipset Intel 845G.

http://img158.imageshack.us/img158/5108/a9bh.jpg

Yeah, this is bothering me.

Well, here is my concern ... those stupid Intel cards come with a lot of computers, especially the cheap ones.

And Retroactive's computer is a laptop, so as far as I know, there is 0% chance of him ever upgrading.

And I'd bet that desktop computers that come with those play Quake 3 and Quake 4 just fine. Will those players buy a video card for their computer when all their other games work just fine?

Here is another thing of note, it is my understand that ancient old GLQuake doesn't have this problem on either of these player's computers.

I've got an Intel 865G and there's definitely something screwed up with the Intel chipsets, quake 3 and quake 2 run just about perfectly. However, it can't run GL Fuhquake or GL Ezquake properly, various issues/bugs include missing console text or the console/conback just flashes continuously...

At work i have the same problem, i'me goto advanced propertys of device and turn off almost all "extensions" like triple bufferising, texture compression etc, playable now, may be issue in one of this option but i not check this since i'm not really play at work. But this really strange/weird, cos q3 work ok without this trick, seems qw ogl engine contain some bug or something.

Hopefully, there is a commandline setting or cvar setting that fixes this.

Dell sells a lot of cheapo computers and I think all of them come with these (shitty) video cards. In fact, I would imagine all of the computer manufacturers sell a large majority of computers like these (except the AMD ones, of course).

Sure they could use software mode, but that's mighty ugly compared to how nice GL looks.

This happens on my work PC as well...

It is a microstar motherboard with onboard video

Do any of you with this issue have trouble running ZQuake (GL) or FTEQW in GL?

Just curious if this is an engine specific problem or if it affects multiple engines. I am going to guess it works perfect with ZQuake based on the comments that GLQuake runs fine.

I tried some different GL clients on an Intel on-board video laptop today.

EZQuake: Wouldn't Start
FuhQuake: Wouldn't Start
ZQuake: Wouldn't Start
MQWCL: Wouldn't Start
FTEQW: Started and seemed to work just fine.

This was done on an Intel 82852 Graphics Controller in a Dell computer that was 2 years old.

I was kind of surprised ZQuake and MQWCL didn't start. GLQuake worked fine so I expected those clients to work. Go figure.

Anyway, based on this, if someone has one of these on-board video display adapters that seems to hate FuhQuake and EZQuake in GL, FTEQW is definitely worth trying to see if it works ok.

ive got a crappy intel card as well, (82865G) and i was googling hoping to find a solution to the blank console issue, but it seems knowone has one :S
As for the console flashing problem, for some reason i think it has something to do with how many lines are in your autoexec file, because when i hid a line using # it didnt flash, and also when i added a command to the list. The console flashed when I had 22 working commands in my autoexec file and didnt when i had 21 or 23.

I have the same problems. WinXP SP2, Intel 82865G, FuhQuake 0.31 Build 650.

First I had a problem with the flickering console and menu. I realized that this only occurs in 32bpp mode, so I am stuck with 16bpp. No flickering problems now, but not without a price. Then I ran into the blank console problem. Console is fine at startup. Console is fine while in observer mode. Console "breaks" upon entering the game. No text, just conback. Console is back to normal when I die, return to observer mode, or disconnect. I have no solution for this, besides buying a new video card.

I have no idea what the crosshair has to do with the console text not appearing, but after I applied a crosshairimage I am no longer experiencing this problem. If you have an Intel graphics card, try it for yourself and tell me if it works for you. If you need a crosshair image, you can use this one that I made, just download it to the appropriate directory (in my case it was c:\quake\fuhquake\crosshairs\). Then you'll need to set a few variables:

crosshairimage "reticle"
crosshairsize 3
crosshairalpha 0.5

As soon as I issue the crosshairimage command the console text shows up, and when I remove the crosshairimage, it goes blank again. *shrug*

interesting, sounds like some blending issue with the drivers

It's hard for me to tell if it's a driver problem or software bug. I'm gonna say driver problem, but others have said Q2 and Q3 work fine for them. I can't confirm this myself, though.

The crosshairimage thing also seemed to cure the same glitches I was getting with Qrack. I can't say for EZQuake, it doesn't run right at all on this system. ; ) But if anything, give this a try and tell me if it works for you Intel graphics card sufferers, I mean users.

Oh and why isn't there a con_alpha cvar in FuhQuake? (or am I blind) : (

scr_conalpha

I'll see if I can get someone I know with the problem to confirm this solves it, if someone else doesn't beat me to it.

Nice work 8)

Thanks Peppe.

Thanks Baker, it seems like a stretch to say that this little workaround is going to work for anyone else but me, but it's worth a try.