Ok, I didn't see this one in the pages so far. When I had 2.1, everything was ok. Now that I have 2.2.1 my screen flickers when entering a map. Once I alt-tab out of nex and then alt-tab back in, the screen is ok. I'm running on a 2 gig pentium machine with 504 megs of ram and an intel 82845G vid card, which runs opengl. Considering upgrading video card tho...... Anty help would be much appreciated.

Maybe you should rather require Intel's help

No serious, you will never be the lucky one with an onboard VGA. you shoulnt just consider upgrading the VGA, just do it, almost everithing thats available atm is better than what you have right now.

I'm not aware of changes in 2.2.1 that could produce flickering.. However there is a option mentioned in the changelog scr_stipple that DOES flickering as a fun effect but that is NOT on by default NOR is it in the menu. If thats the case just set that variable back to 0
Also i'm not sure if Nexuiz does still have problem with dual monitor on windows. In older releases that could also lead to flickering. But i think it was fixed..

I also have this problem on the 3 PCs I use with some fiends at work to play during pauses

version 2.1 worked perfectly

version 2.2.2 as soon as I enter a map starts to flicker

on the 3 PCs I have integrated Intel graphics 82915G

Hi Requim. Welcome to the forum.

Seems this is a issue with those intel graphic chips. Could you maybe test if 2.2.1 also produces flickering for you (like it did for Genegineer)? As he did not yet answer your info will help to narrow down to changes that might produce that flickering.

Genengineer: Are you sure problems start with 2.2.1? If it was just a typo and problems started with 2.2.2 you (and requim also) could test the startup parameter -notexturenonpoweroftwo

Hmm on windows its probably easiest to just use the windows explorer, right click on nexuiz.exe, choose 'create shortcut', then right right click on the new shortcut, choose properties and add that paramater to the end of the 'target' line. Make sure there is a space between the old thing in the line and the parameter you add.

Newer versions of Nexuiz use that OpenGL extension and i just learned that other systems report that extension but seem to screw it up (mac for example..) and maybe intel also makes this error.

esteel wrote:Hi Requim. Welcome to the forum.

Seems this is a issue with those intel graphic chips. Could you maybe test if 2.2.1 also produces flickering for you (like it did for Genegineer)? As he did not yet answer your info will help to narrow down to changes that might produce that flickering.

Genengineer: Are you sure problems start with 2.2.1? If it was just a typo and problems started with 2.2.2 you (and requim also) could test the startup parameter -notexturenonpoweroftwo

Hmm on windows its probably easiest to just use the windows explorer, right click on nexuiz.exe, choose 'create shortcut', then right right click on the new shortcut, choose properties and add that paramater to the end of the 'target' line. Make sure there is a space between the old thing in the line and the parameter you add.

Newer versions of Nexuiz use that OpenGL extension and i just learned that other systems report that extension but seem to screw it up (mac for example..) and maybe intel also makes this error.

Thank you really much for your reply.

On monday I'll test your suggestion and write here the results.

I did some quick test with the

-notexturenonpoweroftwo

switch you asked to try.

Unfortunately the problem was not solved.

I went from a 2.1 to the 2.2.2 version, without trying 2.2.1.

I'm downloading the 2.2.1 for some more testing.

Here I am again...

Just tested with 2.2.1

Same problem, tested with and without the switch.

I tested both the SDL and the standard version of the executable.

Back to 2.1 and the problem goes away.

I didn't say it previously, I'm using Nexuiz on XP SP2.

Hmm interesting.. does v_hwgamma 0 help?
Either entered into the console or used as startup parameter

Code: Select all

+v_hwgamma 0

esteel wrote:Hmm interesting.. does v_hwgamma 0 help?
Either entered into the console or used as startup parameter

Code: Select all

+v_hwgamma 0

I just did a quick test and it seems to work

I'll do some more testing tomorrow.

Thank you

_requiem_ wrote:

esteel wrote:Hmm interesting.. does v_hwgamma 0 help?
Either entered into the console or used as startup parameter

Code: Select all

+v_hwgamma 0

I just did a quick test and it seems to work

I'll do some more testing tomorrow.

Thank you

it does not work, after some more testing I can confirm that it does not work