Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: redsniper on September 24, 2003, 05:44:42 pm

Title: Direct 3D problems
Post by: redsniper on September 24, 2003, 05:44:42 pm

Ever since about the time fs_open_s and Launcher 2.0 came out I've been unable to get any version of FSO after and including 'specular' to work. When I try to run FSO from the launcher I get a blank error window titled 'Error Initializing Direct3D'. RandomTiger and I have been emailing back and forth about this but I thought the more coders I could tell about this the faster it could get fixed since RT seems really busy. RT has figured out that the problem has something to do with the antialiasing registry setting; when I try to pick an AA mode in the launcher the dropdown menu is blank.
Can anyone help :confused:

Title: Direct 3D problems
Post by: Liberator on September 24, 2003, 08:29:19 pm

Use the :V: Launcher to reset the Registry.
Then use the FSO Launcher to reset the other options.

Title: Direct 3D problems
Post by: Bobboau on September 24, 2003, 08:34:32 pm

I think I went a few rounds with him, he has a problem deeper than a mear registry problem

Title: Direct 3D problems
Post by: Liberator on September 25, 2003, 12:26:02 am

In that case...
da da da dum!

It's Re-inty time!:D

For me too as FS2 has recently been crashing on exit.  Replaced with Renegade for a quick runthrough but will proably reinstall this weekend.

Title: Direct 3D problems
Post by: redsniper on October 01, 2003, 09:12:26 pm

bump!

Title: Direct 3D problems
Post by: IceFire on October 01, 2003, 09:13:52 pm

Hardware specs and what driver versions would probably help us here.

Title: Direct 3D problems
Post by: redsniper on October 01, 2003, 10:06:00 pm

they're all over the place by now but anyway:
Pentium III 866 Mhz
256MB RAM
GeForce4 Ti 4600 (4403 driver)
Windows XP

Title: Direct 3D problems
Post by: Fry_Day on October 02, 2003, 02:17:33 am

Okay, open up regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Volition\FreeSpace2

There should be a key called VideocardFS2Open. If it does not exist, right click an empty part of the panel that shows all the keys and create a new string value.

If you want to run, for example, 1024x768x32bit, the value of VideocardFS2Open should be "D3D8-(1024x768)x32 bit" (without the quotes, of course). If you want to run 16 bit, delete the 'x32 bit'. If you want to run 640x480, change 1024x768 to 640x480. That's about it.

The launcher didn't work for me either, so I just peeked at the code to see how it reads the registry (which is in a very untolerant method).

Title: Direct 3D problems
Post by: redsniper on October 02, 2003, 06:23:38 pm

thanks for trying to help but my problem is a lot more complicated than that. Really.

Title: Direct 3D problems
Post by: Taristin on October 02, 2003, 06:24:53 pm

Want another copy of my registry?

It helped Setekh...

Title: Direct 3D problems
Post by: Deepblue on October 03, 2003, 09:50:34 pm

Would you mind posting it? I'm having issues and that might help.

Title: Direct 3D problems
Post by: redsniper on October 03, 2003, 11:51:42 pm

sure Raa, since RT seems to have disappeared of the face of the earth, I suppose that's all I can try for now.

Title: Direct 3D problems
Post by: redsniper on October 05, 2003, 03:38:09 pm

b-b-b-bump!

Title: Direct 3D problems
Post by: Taristin on October 05, 2003, 03:50:10 pm

Sorry, forgot about here...

http://freespace.volitionwatch.com/us/images/mods/snipes/fs2fixer.rar

Title: Direct 3D problems
Post by: redsniper on October 05, 2003, 11:05:28 pm

thanks, I'll let you know if it works.
EDIT: :sigh: it didn't work. I've got a bigger problem than last time.