[Johnmike]

Alright, I have an AMD Athlon 2100+, 1.7 Gigs.  Video card is Inno3D Geforce FX 5200, sound is a Sound Blaster Live! 5.1 MP3+.  I'm using FS2 Open 3.5.5 with the launcher at version 3.1.  (If there are any later releases, save for alphas and betas, tell me).  I'm using the media VP's and using high-res textured.  

I have two problems.  First is the minor one, then the serious one.

In Direct3D, I can't see my primary weapon shots.  They work fine under OpenGL.  Now, the hard one.  I've tried changing command line options and messing around with the video settings tab.

In OpenGL, the game sometimes crashes when loading a mission.  It seems that it only happens with some missions, as I've had it happen to me twice and passing the mission under Direct3D fixes it.  The crash minimises the game and tells me that it has an error with the W32 pixel format.  Again, this only happens with two missions so far.  The one I'm up to is the one after Enif Station, first deployment of the Collosus.  

Oh yar, I also have another problem.  It won't recognise -t32, even though it's listed in the launcer.  It recognises 32bit, though.

I'm using:

C:\Freespace2\FS2\fs2_open_r.exe -fps -d3dmipmap -cell -phreak -multilog  -32bit

If you can, tell me what command line options and what video mode will give me the best looking results.

[redmenace]

they are working on it, if you look in the faq sub forumy you will see. there are some other bug threads you can read through. You ought to do a search. Also if you have problems email me at redmenace[nospam]@Hardlightproductions.com remove no spam from address.

[Johnmike]

I don't know if it's my own stupidity, but I can't find anything...

Edit:

The exact error is:

Error

                    Unable to set Pixel Format for OpemGL W32!

[RandomTiger]

It sounds like you have an old build, keep an eye on this thread.
http://www.hard-light.net/forums/index.php/topic,19016.0.html

If you still have the problems check if they happen with and without the flags you where using and post the results here.

[redmenace]

Originally posted by RandomTiger
It sounds like you have an old build, keep an eye on this thread.
http://www.hard-light.net/forums/index.php/topic,19016.0.html

If you still have the problems check if they happen with and without the flags you where using and post the results here.

after  posted I was figuring that was the case.

[phreak]

the other other problem is that your card may not support a 24 bit z-buffer, which is hella doubtful with an FX.

[Trivial Psychic]

If you're not seeing the primaries, and you're using the VP with the 32-bit effects I think I know what the problem is.  Are your background nebulae missing?  Is the warm-up glow for beam cannons missing?  These 32-bit effects are in tga format, which needs the -t32 flag to be displayed.  The problem is that any build before _t won't recognize this tag.  I would suggest you don't use the _t build, since it requires the -htl tag.  I would suggest you use either the fs2_open (no letter extension) or the 11_18_2003 build to use the 32-bit features... either that or remove the 3.5.6 VP file and revert to the 3.5.5 VP.

Later!

[Johnmike]

The new build works great, and the -t32 command line option is accepted.  I'll test out Direct3D soon.   I could always see background nebulae and warmup glow.  

Update:  Direct3D weapons work fine.  However, OpenGL missle trails flicker.  Before it was just Direct3D primary weapons, now it's OpenGL missle trails.  Gets annoying at close range..

[RandomTiger]

I think trails do have a few issues at the moment, should be fixed up for the next full build.

[Johnmike]

Okay.  What do you recommend, OpenGL or Direct3D at this point?