FleetOps wont play on Nvidia GTX 570/580

posted on January 25th, 2011, 11:26 pm

It'll be fixed next patch, so I don't think that warnings will help too much 

will add that to table.

posted on January 25th, 2011, 11:35 pm

Just that if the problem was on Nvidia's end i wasn't holding out too much, and that people looking to buy newer cards, not to currently if wanting to play FleetOps.

However thats great news, and i like others with this problem are very happy to here that it will be fixed. Looking forward to it.

Thanks.

posted on January 25th, 2011, 11:40 pm

will add that to table.

Sorry, on closer inspection I think I misunderstood - I thought this was in reference to the sprites-become-squares issue, so I guess Doca's previous comment of having to wait for a driver update have to suffice 

posted on January 25th, 2011, 11:56 pm

Damn  like i said in my previous posts i've tried at least 3-4 different driver version for my Nvidia GTX 580 and alas none have worked. I just dont agree with Doc Cola on that Nvidia will fix the problem with newer drivers, I've already been doing that 266.58 being the latest for the 500 series.

Like i said if this problem is related to these particular series of cards, could a sticky informing people that are thinking of upgrading to these newer cards, warn them that they simply wont currently work.

I've been wrong before, and who knows Nvidia may fix this problem, but my gut instinct tends to tell me that this problem won't  go away.

Thanks again for trying though. 

posted on January 26th, 2011, 1:31 pm

changed fixed status in table.

i doubt there is much doca can do about this, it sounds like the nvidia drivers are broken. hopefully nvidia will fix it, but i doubt it too.

[Adam_C]

posted on January 27th, 2011, 6:02 am

Last edited by Adam_C on January 27th, 2011, 6:21 am, edited 1 time in total.

I come baring gifts geforce 4/500 series owners


C:UsersnameAppDataRoamingStar Trek Armada II Fleet Operationsfodata.ini

change
D3D9=false
to
D3D9=true


Worked for me!

whoop whoop

posted on January 27th, 2011, 9:13 am

Just tried your suggestion and finally it worked 
but had to disable asychronous cursor, because it made my mouse cursor appear and disappear while moving not sure why, but now works great.

A great thankyou to you Adam_C for finding what caused the problem, just hope it works for others with similar problems.

Also to Myles you can now update the bugs topic hopefully to this problem now finally fixed.

Whoooo 

Thanks Again.

posted on January 27th, 2011, 12:43 pm

i love the fix. Turn on direct3d, why was it off, i thought fleetops always used direct3d? Maybe the drivers didnt tell fleetops they supported d3d?

2 ppl have proposed as fix. If 1 more person confirms it then i'll say its fixed. The community fixed its own bug lol.

posted on January 27th, 2011, 4:08 pm

setting this option enables an experimental directx9 mode INSTEAD of using armadas default direct3d8 graphics. it is not recommended to use this option. some features like screenshots, cursors etc may not work correctly with it. please do not expect support when using this option.
and just to be clear before this evolves into a forum wide secret directx9 'hack'...using this option as of now gives zero advantages over the stock directx8 engine, actually you are likely to get lower fps with it enabled.
it is interesting that it fixes the nvidia issues though. if nvidia fixes the texture problem one day i clearly recommend to go back in d3d8 mode.

posted on January 27th, 2011, 8:02 pm

I understand what you are saying Doca Cola, it's just that to me and probably others as well, that Nvidia doesn't exactly have a great track record of fixing what it breaks. Personally all i can think is that, because FleetOps is based on the original Armada 2, and that the game is several years old that Nvidia pulled support from it's drivers. Usually has you can imagine they are not likely to put it back in for this game.

So for me and eventually all of you unless you have an endless supply of older graphics cards, are going to face this problem and either find a way around it or simply wont be able to play.

I'm just thankfull that a sort of fix has been found, and that i can now finally play v3.15, by the way love the new Borg Torpedo sprite.

posted on January 27th, 2011, 10:22 pm

thanks for the explanation doca, that clears things up, i never knew a2 used direct3d 8.

i guess for those that cant use d3d8 cos of nvidia, d3d9 will have to do, just anyone who does use this shouldnt submit bug reports if the game crashes.

posted on January 27th, 2011, 11:22 pm

Nice to be getting somewhere on this issue,   interesting point by doca that this is not a fix just a undesirable fluky workaround.

When I first saw the problem with the game my initial thought was a shader problem, i think its likely the cause of the geforce 570 being unable to accurately emulate dx8 shaders.     Im just a novice though taking shots in the dark at this problem.
It seems the 570 is using sm5.0 natively (just a guess)

dx11 time doca

[Adam_C]

posted on January 31st, 2011, 7:18 am

Last edited by Adam_C on January 31st, 2011, 7:19 am, edited 1 time in total.

it is interesting that it fixes the nvidia issues though. if nvidia fixes the texture problem one day i clearly recommend to go back in d3d8 mode.

if nvidia are unable to fix this dx8 bug,  would u guys be able to support dx9 , beit on whatever capacity?

I imagin the next couple of geforce patches will be a indicator, i'll go fish for beta(s)

posted on January 31st, 2011, 7:48 pm

FO will eventually support later DX versions as far as I understand it

posted on April 26th, 2011, 11:28 pm

bug still present in 3.2.2 however with the workaround i dont notice any performance issues