• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

'NVidia Question'

I run my 8800GTX with AA & AF on in the game and Enhance application in Nvidia Control panel.
 
Well I only speak in general terms here.....

And it does all come down to the users abality to settle on what is acceptable.......

But with my off the shel PC AA and AF were to hard a hit on its slim processor,so I used none and all was *fair* for a couple years...


Once I got a rig that could run FS9 / FSX is when I had to start playing with all the control panel stuff.....

That was my point......


But I agree...It all comes down to what we accept as good,or as good as it gets.....



And this guy is fun....I agree on that.....:bs:


And this one too.....:friday:



And to clarify I was not meaning one man build two identical rigs that both handles Flight Sims differently.....

There are many here with all but the same specs,and all have different struggels.....Point being this is mostly absurd..Why can a game not be made to just install and run...Thats what most want...Who wants to get a total education in computers and how they work just to have to use third party software to try and make things better that should already be good... Not me really...For the 65 some odd dollare I paid for the soft ware I expected it to install and work well...It does not nor will it ever I feel.......


Thats like going to a car dealership,paying through the nose for a new car,and having to repair it before it leaves the lot........


Or going to a restuarant and ordering the biggest steak dinner they have for 25 bucks...And after you eat your meal,the chef comes out and says,sorry,but that steak was harder to cook than I thought,so it will now cost you 35 dollars....


Hey...I got dozens of these...But I will quit.....
 
Still....
No reason as to why my system powers off upon starting FSX with any driver new than 169.21 :isadizzy:
 
Panther_99FS said:
Still....
No reason as to why my system powers off upon starting FSX with any driver new than 169.21 :isadizzy:
Click to expand...

Hey P can you describe exactly what takes place. Do you get a warning message? Does your screen go goofy on you first? OH yes and what video card do you have?
Ted
 
txnetcop said:
Hey P can you describe exactly what takes place. Do you get a warning message? Does your screen go goofy on you first? OH yes and what video card do you have?
Ted
Click to expand...

No warnings, no messages, no nothing....when I go to select a plane...POWER OFF!!! :censored: And I do NOT use beta- drivers.

512mb 8600GT
 
Panther, I use the 178.13 drivers on my two SLI 8800s. I always have AA on in both nHancer and FSX.

Pictures from my rig will show you why. Maybe some fellows get better from just having AA on in nHancer or the nvidia Control Panel, but I'll let the screens do the talking.

No AA in FSX:

fsx_mnoaa.jpg


AA in FSX:

fsx_aa.jpg


Caz
 
Non-beta 178 drivers = my system powers off. :censored:

I'm telling you...
I've tried EVERY SINGLE NON-BETA driver newer than the 169 series and all of them cause my system to power off in FSX...:censored:
 
Are you using nHancer? Also check your processes to see if anything looks out of place from what you had before you installed the Nvidia drivers. One more thing, run msconfig and check your boot.ini and startup

Ted
 
txnetcop said:
Are you using nHancer? Also check your processes to see if anything looks out of place from what you had before you installed the Nvidia drivers. One more thing, run msconfig and check your boot.ini and startup

Ted
Click to expand...

Nope, I've never touched nHancer. System runs fine EXCEPT for FSX..

noddy said:
Have you made sure all traces of the old drivers have been taken off the system.
Click to expand...

Yep - Use DriverCleaner...
 
All I know is that after the 169 series nvidia started including their PhysX technolory..........


No real clue as to that being a culprit or not..But thats the only difference in the drivers I know about.....

Maybe its a DirectX conflict with backwards compatible...


This is way out of my league...Sorry...Wish I had a better answer....
 
Panther_99FS said:
One last NVidia question....

Why is it that ANY DRIVER new than the 169.21 series causes my system to POWER OFF as soon as I try a flight in FSX....:censored::banghead:
Click to expand...

PSU too weak, CPU too hot, bugged OS, bugged card...

Do other games work?


- Edit: Does your PSU deliver 18A on the +12V rail?



Mr.Mugel said:
I am running 180.70 here, and used a lot of beta and leaked drivers, and they all worked for me, sometimes if I use something that is intense on resources screen goes black and FS restarts, but I guess that´s no graphics card issue...
Click to expand...

PSU too weak? CPU too hot?

- Edit: VCore too low?
 
txnetcop said:
Are you using nHancer? Also check your processes to see if anything looks out of place from what you had before you installed the Nvidia drivers. One more thing, run msconfig and check your boot.ini and startup

Ted
Click to expand...

Ted, I have found that it is best to uninstall nHancer before changing forceware drivers and re-install after the new forceware drivers are installed. In one instance I did not do this and nHancer from an original install did not recognize the new drivers. An uninstall and re-install of nHancer and it did fine.

Caz
 
Cazzie said:
Ted, I have found that it is best to uninstall nHancer before changing forceware drivers and re-install after the new forceware drivers are installed. In one instance I did not do this and nHancer from an original install did not recognize the new drivers. An uninstall and re-install of nHancer and it did fine.

Caz
Click to expand...

yes you are correct and then reinstall thanks for adding that.
Ted
 
I can't help but constantly try to tweak settings. Seems like I am forever in search of the "perfect" video card setting, and I will never be satisfied!!! It's never fast enough, and it's never clear enough!

NC
 
You must log in or register to reply here.
Back
Top