Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
I installed this today and had a similar difficulty--GeForce 660M, Windows 7, game was only willing to notice my Intel 4000 HD and didn't see the nVidia card. This seems to have fixed it for me:
- Open up the nVidia control panel
- Under "Manage 3D settings" --> "Program Settings," click "Add" to manually add a program to customize.
- In the resulting popup window, select "X3AP," then click "Add Selected Program" below.
- Under "2. Select the preferred graphics processor for this program:" pick "High-performance NVIDIA processor" rather than the default "Use global setting." This ought to force X3:AP to use your graphics card instead of your integrated graphics.
One thing I have no idea about: is it defaulting to integrated graphics because of a power setting? Enh, dunno; could easily check. In any case, I'm glad I spotted this way to force a program to use one adapter or another.
Some motherboards come with utilities [e.g. Asus ROG ] that allow you to set up specific card selection within Windows. I haven't seen this problem with the ATI Catalyst drivers. Hopefully it is an NVidia only issue.
I really hope it is a BIOS/driver issue as another possibility is that your trouble could be temperature related. For that; reseating the Graphics Card is a good first option.
You can force it to always use the Nvidia card by either disabling the Intel card in device manager, or setting the preferred gpu to Nvidia instead of Auto in the Nvidia control panel
Many motherboards also have onboard graphics too. Especially with the improved onchip graphics from Intel CPu's like the i3770k and others. Sometimes the BIOS is one developed on other boards and made to fit. Sometimes that fit is not quite right.
When the BIOS fails to make proper use of the hardware you get timing issues that can cause software to fall over.
It's a bit like when you want to take a car off a car park with an automatic barrier. If you wait too long the poorly designed barrier will come down on your car. If you try to leave too fast you will hit the barrier. When dealing with two cars the barrier needs to 'see' both vehicles or it would let one car follow the other out without dropping, and people might try to do that to avoid paying. On a motherboard the various parts of the machine are given processor time through 'Interrupts'. Failure to handle the Interrupts correctly can cause Operating Systems to fall over during boot. They still usually boot, but part of the hardware is either not recognised or identified wrongly.
So.... one thing to try when hardware glitches is to open and close the Operating system fully without running any other software in between. That way the software of the Operating System can sometimes align properly with the BIOS. You may have noticed that your machine soemtimes boots up differently from others. Unfortunately with the latest Operating Systems they tend to autoupdate often and this can lead to problmes when each time the machine boots it is having to realign everything.
Try doing at least 2 cold boots - with no other software booted in between. Just open and close the Operating System. A cold boot means a complete close down,... power off too.
If a machine is more than about 3 years old it is worth also thinking about renewing the motherboard battery. Once those batteries fail they can introduce similar timing faults.
Having said that.... in this case it does look like its a GPU BIOS/Driver issue. Perhaps the Driver is failing to interface between the Operating System and the BIOS on the motherboard.