2.0 Issues Here

[ChillFactor]

Ok, so this topic is to post issues while running 2.0 Alpha...

And of course, 'cuz I got one already.

I followed all the steps, checked my DX version on dxdiag and checked all my DX Files, so it's not DX.
Game can't start because of "d3dx9_35.dll" missing. It cannot locat the file.

Tried reinstalling, yet asme problem shows up.

Any help, or I'm just too much of a grey-hat / white-hat baking consultant to know what's wrong here?

[Trompete]

Looks like it's a directx 9.0 file. Try installing this package from Microsoft:
http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displayLang=en

Or this site and click on "DirectX End-User runtime"
http://www.microsoft.com/downloads/en/default.aspx?pf=true

[NiteHawk]

I found out Drengin Debris is missing, I will fix this when I get home today.

[NiteHawk]

Also if you have DX 10 soemtimes you need to install DX 9 to add DX 9 files because microsoft stinks. I didnt want to stick to DX10 because then we'd be out XP and under for people.

[ChillFactor]

Done, worked. Testing now!

[NiteHawk]

I would guess that there is probably some way to have it toggle between DX9 and DX10, have to read up on it though and figure it out so that you don't need to install DX9. For the most case though, if you want to play alot of older games that are in the XP ERA, then you need it But will figure it out after

Make sure you update your SVN folders , i did add a patch just recently. (Right click folder you made and SVN UPDATE)

[Sandtrooper]

List of bugs I've found (some confirmed /w Nite, denoted by "C")

• Tractor location is wrong on Dreadnaught & Battleship, not known if BattleCruiser does this  (C)
• Terran Tractor color is Arcean colored
• Blockading certain planets is impossible (C)
• Orbiting certain planets invoke message spam (C)
• Targeting is very screwy, sometimes it is "locked" on a single target unless a flight instruction (such as BOOST) is received. I assume this is locked to "Follow" mode.
  
• Weapon "3d" images are placed wrong, may be a DX issue.
• Chat green square does not dissapears unless a message is sent, thus sometimes "impossible" to tell if you've toggled chat ON or OFF.
  
  
• Certain computers such as my (personal) shitty "Workstation" computer cannot run SF 2.0x Alpha at all, because of a "D3d ERROR INVALID CALL" message, telling the user the game cannot be run. This is due to "workstation GFX chipsets", which have next to none graphic processing power (even if they report 96 MB of GFX memory), this is being investigated as this post was being written.(C)

[ChillFactor]

Well, I've got one, not sure if it's a bug or what.

On AI Sol I can see ships flying on Qdrive, as in *go in - fly away at the speed of light carrying another ship - come back and drop outta Q*.

Also, game physics seem to have changed: Ships seem a lot heavier now.

[NiteHawk]

Well, I've got one, not sure if it's a bug or what.

On AI Sol I can see ships flying on Qdrive, as in *go in - fly away at the speed of light carrying another ship - come back and drop outta Q*.

Also, game physics seem to have changed: Ships seem a lot heavier now.

Heavier in what means? If you go test with 1.4 and 2.0,from 0.90C one way to 0.90C the other way, you will actually notice the game is a bit faster now, by a second or two.

I have a feeling that since we increased the smoothness, it also has a impact on our eyes now that we realize the ships are super sluggish. Prob will adjust this in the future (making ships more agile/speedy). But if you go do that test you'll realize there about the same on the one speed to another. With 16FPS, doesn't do justice at all for looking like its sluggish.

If its another problem lemme know. At the moments it is set so you can view Friendly warps, but not sure if people want to keep this. They shouldn't be warping with other ships though.

[Mars]

D3d ERROR INVALID CALL" message, telling the user the game cannot be run. This is due to "workstation GFX chipsets", which have next to none graphic processing power (even if they report 96 MB of GFX memory), this is being investigated as this post was being written.(C)


this is what is now going on with our computers i did install dx 9c and got past the first problem, now we cannot run the game do to this upper listed problem,  also the server will not allow you to sticky the button that says"  registar with the nexus that button just pops back to not there. 

can get to make the new player part but soon as i click anything i get the d3d error.  ?>>>

[Mars]

i have installed the direct x package re booted as listed still the hrc error we have done this for both machines and then got the 7 package still nothing.

[NiteHawk]

There seems to be an issue with older computers. I"m honestly wondering what your FPS will even be though.

For the most case what GPU you have? I need to fix that before anything. Right now im having a huge issue becuase theres no proper error being generated. Just a 'error/failed' standard message.

I'm guessing you both don't have very nice GPU's/older systems (Pre Geforce2 or around)

Do you get any specific errors? Any messages side what sand said?

[NiteHawk]

I need to see if I can find a older computer to test on. Going to be a hassle to figure this issue out. It's probably just a flag.. Just not sure what one yet.

Edit: Actually, I have an old laptop system I will grab it tomorrow and debug/figure out that issue everyones having with old graphics cards.

My todo list priorities for when I have free time:
-Fix DX issue on older graphics cards. (IMPORTANT!)
-Fix blockading/orbiting.
-Fix tabbing and chat window.

[Mars]

thank you nite!!!!   ren was able to get 2.0 to play on his laptop however my new asus and her p4 wont do sf at all we have followed all directions to the letter installing all that tromp said and tried every comp mode on vista and xp i dont know i have a flat screen on mine hooters has a older trinatron crt on hers both give the exact same error so being i could not find the log i decided to just post a screen shot of the error.   here goes maybee this will help some.


http://i775.photobucket.com/albums/yy35/planetmars101a/ScreenHunter_1e4001-4.jpg

[Trompete]

Mars,

I've been looking at some internet threads about the error, and they have a couple suggestions, but we're gonna need some info from you.

The first suggestion, which rarely works is to make sure you have the latest graphics driver for your motherboard/video card. Most people do, so this usually doesn't work.

When this doesn't work, do the following:
Start menu->Run (or start menu and type in the box on vista/windows 7):
dxdiag

When the gui comes up, click the "Save All Information" box on the bottom (or find something similar), save the text file to disk, and attach the file to this thread. It should be called DxDiag.txt or something.

Nite, we may be initializing CreateDevice() in a way that old video cards don't support.
http://cboard.cprogramming.com/game-programming/84679-dx-createdevice-d3derr_invalidcall.html

Brent