[neoterran]

Okay, this is weird but replicable.

If i have another application that uses OpenGL running and then I launch Freespace SCP, it won't take the antialiasing or image settings from the driver. I tried this with Foobar2000 player with the ProjectM panel vis (which uses OpenGL) and with it in the background, Freespace doesn't get antialiased, even if the driver is forcing it. Without the Foobar2000 running, the settings work correctly.

Thought someone might like to know.

[Goober5000]

Foobar2000

...

Do I have a long-lost relative?

[Mars]

Foobar2000 is a freeware audio player, I use it cause it plays every audio file imaginable, and the extensions play the others.

[neoterran]

www.foobar2000.com

It's simply one of the best players for windows. But a warning : only for power users.

[pecenipicek]

neoterran, i wish stabbity death upon you


winamp is the best tho. if we count out the hiccup with winamp 3.

as for the error, i managed to replicate it with winamp too, if the visualization window is open.

[Colonol Dekker]

All hail winamp, best skin and Visualisations support on the planet 

[pecenipicek]

ah, a fellow winamper



i just use the most basic skin as i still didnt find a minimalistic skin that doesnt make my eyes bleed nor hogs the memory...

by the most basic skin, i mean the winamp 2 skin

[Colonol Dekker]

Theres a gta one somewhere, all black with green tint, but i use this one to p1$$ my little bro off when he visits.

http://www.winamp.com/skins/details.php?id=146726

a bit of mazza kart!!

[pecenipicek]

my eyes. they bleed.

[neoterran]

Hey, this isn't a thread about winamp, it's a thread about a problem with freespace... let's not derail it please.

[Colonol Dekker]

Apologies, Have you (forgive me for this) tried updating all available drivers for your pc?

[neoterran]

I'm sure there is a technical reason why this occurs, i'd like to see taylor weigh in on it if he has time, since he probably knows enough about OpenGL implementations in windows to understand why it happens from the description.

[taylor]

I'm sure there is a technical reason why this occurs, i'd like to see taylor weigh in on it if he has time, since he probably knows enough about OpenGL implementations in windows to understand why it happens from the description.

Actually I don't have much to add on the subject.   I'm sure I've read about this before, and have a good answer for it, but it's locked in my brain somewhere, and I lost the key.

Whether this is a driver issue or just a WGL/context thing I can't remember.  It may be a fullscreen vs. windowed thing, where if you ran the game in a window it would use AA properly.  Perhaps when I finally add the anti-aliasing code to CVS this won't be much of an issue anymore.  Beyond that I can't really offer much else.