[Jackson]

No matter what resolution or bit depth i use with direct 3d 5 or 8, i always get this error, normal FS2 starts up fine, debug:

DBUGFILE Active: Root 06/14/03 17:51:04
OS: Windows XP Release, C:\Pelit\FreeSpace2\latestrelease.exe
[2d.cpp,1033] About to init 102
[GrD3D.cpp,2645] gr_d3d_init start
[GrD3D.cpp,2764] Mode: 0 x 0 x 0 bit
[GrD3D.cpp,2774] Failed to create hardware vertex processing device, trying software
[GrD3D.cpp,2781] Failed to create software vertex processing device
[2d.cpp,1053] Bad startup

I use the "custom" launcher.exe from your site

[RandomTiger]

What OS and gfx card are you using?

[Jackson]

XP Home edition and Geforce4 Ti4600

[Bobboau]

were you running it in windowed mode by any chance?

[HotSnoJ]

What OS and gfx card are you using?

OS: Windows XP Release

[RandomTiger]

Originally posted by Jackson
XP Home edition and Geforce4 Ti4600

Thats very odd, almost the same setup as me.
What make is your gfx card?
Are your drivers up to date?

[FreeTerran]

I get now that error too

Code: [Select]

DBUGFILE Active: Tobias 06/16/03 18:46:06
OS: Windows XP Release, E:\FreeSpace2\latestrelease.exe
[2d.cpp,1033] About to init 102
[GrD3D.cpp,2645] gr_d3d_init start
[GrD3D.cpp,2764] Mode: 0 x 0 x 0 bit
[GrD3D.cpp,2774] Failed to create hardware vertex processing device, trying software
[GrD3D.cpp,2781] Failed to create software vertex processing device
[2d.cpp,1053] Bad startup


i have win xp pro geforce ti 4200 at all hardware the newest drivers

any ideas ?

[FreeTerran]

I have fix the problem.....

i have delete all registry entries and then have i start the orginal fs2 launcher.....and now it works fine...

[vyper]

I've said it before - the launcher is "FUCT" (Feirce User Computer Tension)

Dinnae like the registry

[FreeTerran]

With the launcher from scp works it fine too

[RandomTiger]

Originally posted by vyper
I've said it before - the launcher is "FUCT" (Feirce User Computer Tension)
Dinnae like the registry

Well that was constructive, I hope you taken the time to document any problems you've had in buzilla because wordplay like above isnt going to help anyone fix any bugs.

I'm in a difficult situation here since I dont know what happened in the DX8 merge, I dont have a copy of the code and dont know what UP has and hasnt changed. So UP if you are listening your angle on this would be valuable.

I have spotted one problem with the launcher that could be, or not be the cause of this one. The way the launcher works is it simply detects which D3D modes are avaliable and stores the chosen mode value in the registry to be picked up by the game.

Problem is my monitor detection changes. Sometimes it caps the modes properly at 1280 and other times it allows up to 2048. This changes the numbers and sometimes makes the chosen mode invalid. What I should have done is use V's system of storing the mode in text and redetecting it when the game runs.