[Fafner]

Hi,
I encountered this weird problem with 32 bit colour in Freespace2 on my comp. I usually run in 16 bit colours, since when I started with Freespace long ago my comp back then was rather slow, and also because I never can tell the difference between 16 bit and 32 bit.

Anyway, I read somewhere that the difference between 16 and 32 bit is most evident in for example smoke, and I figured the nebula-effect maybe look better in 32 bit after all. But when I tried 32 bit it made the game hang when loading a mission, weird as I remember trying 32 bit when i started playing FS2. Messed around with different setting to no avail, until I tried to create a new pilot - and then everything worked.

So when I try to use any of my old pilots I can only run in 16 bit, but when I create a new one I can use 32 bit, how weird is that? It may be related to that the old pilots were created when I was gaming on my old comp (Celeron466+TNT2 U) while I play on a Athlon1200 + Voodoo 5500 now (and win98se), but still strange I think.

I have not yet been able to test for difference with the nebula effect between 16 and 32 since I have to replay the campaign to get to the nebula (what? try making a nebula mission in Fred?, uhhm, yea, only thought of it as I wrote this... :doh: )

Fafner

[Fury]

Yeah, there's much more than just the colours.
For example some mods may not be fully functional until you create a new pilot. Oh well, **** happens.

[Nuclear1]

Originally posted by Mr. Fury
Oh well, **** happens.

*remembers Forrest Gump*

Yeah!

[Petrarch of the VBB]

I jhad a strange problem with different graphics modes, sometimes, if I run in 32-bit, the mainhall animations jump a few pixels to the left when playing. SO when i move the cursoe over the options guy, he jumps to the left and then the "turning to face you" animation plays. Weird or what?

[Bobboau]

that is a bad typo you got there

[NotDefault]

Originally posted by Bobboau
that is a bad typo you got there

[CP5670]

I jhad a strange problem with different graphics modes, sometimes, if I run in 32-bit, the mainhall animations jump a few pixels to the left when playing. SO when i move the cursoe over the options guy, he jumps to the left and then the "turning to face you" animation plays. Weird or what?

I also get the same effect, along with many other distortions in the menus. (black lines cross through the screen at periodic intervals, everything is slightly blurry, etc.) What I have noticed is that if I turn on forced AA on the graphics card, it does this type of stuff, but it goes away if AA is turned off and a small change is made to FS2's registry settings. (if the registry edit is not done, the text appears all chopped up, but the setting needs to be changed to another value for the text to look right with AA) I keep the antialiasing on because although the menus and text look worse, the in-game models and stuff look much better.

[Fafner]

Yea,
its totally worth some blurry text, because like you say, in-game FSAA is priceless. Not only because it reduces jaggies, but because it get rids of crawling textures when viewing for example cap ships at a distance. With the Voodoo5 you can toggle the FSAA effect on/off with a hot key, useful if you want to see the menus without distortion.

I think that the typo Bobboau was referring to was "jhad" in Petrarch's post .

Been doing some comparison between 16 bit and 32 bit and the nebula now, and it does indeed look different. Dont know which I prefer yet, though, and have to try 22 bit aswell (a special ability of the Voodoo's).

[Setekh]

Originally posted by Fafner
like you say, in-game FSAA is priceless.

So true.

[killadonuts]

Originally posted by Fafner
Hi,
I encountered this weird problem with 32 bit colour in Freespace2 on my comp. I usually run in 16 bit colours, since when I started with Freespace long ago my comp back then was rather slow, and also because I never can tell the difference between 16 bit and 32 bit.

Fafner

Theres a lot more than color differences.  Look closely at 16-bit nebula scenes and compare them to 32-bit.

[FSW]

The following solution works for almost any graphical problem:
Find some spare £3000 and buy a real computer.

[Fafner]

Originally posted by killadonuts
Theres a lot more than color differences.  Look closely at 16-bit nebula scenes and compare them to 32-bit.

Originally posted by Fafner
Been doing some comparison between 16 bit and 32 bit and the nebula now, and it does indeed look different.

Fafner

[Fafner]

Originally posted by FSW
The following solution works for almost any graphical problem:
Find some spare £3000 and buy a real computer.

If you think that a Voodoo5 + Athlon 1200 is not enough to play Freespace then you need to do some research buddy...

[Reppyboyo]

PIII 450, Voodoo 5 5500 PCI

i seem to be unable to run in 32BIT
it wont detect it....as far as i can see anywayz
and i cant remember how to get the 22BIT post filter going...

[Fafner]

For Freespace to detect glide on my comp I have to set desktop colour to 32 bit, which is weird since glide runs in 16 bit. Once glide is detected I can change desktop colours back to whatever.

To enable 22 bit post filter on a Voodoo5 set 3D Filter Quality to high and Alpha Blending to sharper.

Tried out 22 bit in the Nebula now, and as predicted it looked something between 16 and 32 bit. I'm still not sure which mode i prefeer IQ wise. 32 bit lowers the framerate on my comp though so I probably stick to 16 or 22.

Fafner

[Redfang]

Originally posted by Fafner
it get rids of crawling textures when viewing for example cap ships at a distance.

 
Oh, FSAA also does that. Mip-mapping would also do that, but FS2 doesn't seem to have it. It's pretty annoying, and very noticeable on the Orion.

[Fafner]

Originally posted by Redfang
Mip-mapping would also do that, but FS2 doesn't seem to have it. It's pretty annoying, and very noticeable on the Orion.

Mip-map dithering? Will try to enable it through hardware to see if it works.