安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
此主題已被鎖定 
討論區規矩與守則
檢舉此篇文章
(there is another thread here on the forum with the technical details)
The correct thing to do is use Elite Dangerous deadzones to compensate for any drift on a controller.
Also, in order to reach the proper controller settings, do this:
(the calibration tab will not show up without the proper drivers installed)
Windows System -> Control Panel -> Devices and Printers -> Right click your device
Game Controller Settings -> Properties -> Settings -> Calibrate...
(OP has also already answered this)
It's generally a bad idea to use 3rd party software with controllers.
Might be time to close this thread before we have to get the holy water. xD
I fully agree with you.
In windows properties more and more functions dissapear and change the position, it is dissapointing, and every "function update" it is even worser than before, especially for gamers.
Why the controller numbers change everytime you plug in a device?
in win7 it was easier
Run joy.cpl as an administrator.
Close Joy.cpl, click the Windows button, type joy.cpl and when joy.cpl shows up in the list, right-click it and select "Run As Administrator".
Now when you click on the "Properties" button, the Properties window should open.
Thank You! :)
You sir are a gentleman, and a scholar!
Answer is very obvious. They don't want the consumer to access those controls. And more generally, they don't want the consumer to be "smart" about their computer (THEIR as in Microsoft's). What they want is to turn PC users into mobile users - i.e. mindless drones who don't know or care how stuff works and control their "devices" by fingerpainting like Kindergarten kids. This kind of user is helpless before the real owner of the device - its actual producer and operator.
Oh, they don't just remove the controls outright straight away. They hide them, and limit them, and slowly "retire" them, reducing accessibility, lowering support levels, replacing actual controls with big fancy buttons that don't allow deep access. They force you to download updates, then make update download automatic, then don't even notify you when your computer suddenly starts downloading and installing something you didn't expressly authorise. Same with reports - first you do it manually, then they offer to do it for you, then it's done by default with possibility of refusal, until finally it's done in the background with no authorisation or notification.
Next OS version rolls out, user agency gets reduced even further. Until we finally have OS No. Omega where EVERYTHING is controlled server-side, ALL user actions are tracked and reported, and user has NO control over what his device actually does. In fact his device isn't even his anymore, it's operated by proprietary software that belongs to the corporation, and the user pays to have his device operated by said software.
Once you look at the evolution of operating systems and similar programs this tendency becomes quite obvious. Of course, the next generation of consumers would be conditioned to accept it as perfectly natural order of things. Same with the Internet being put under control, TV and printed media, etc. Brave New World right at our doorstep, lads.
I'm sorry but this is flat wrong (use ED internal deadzones), especially if you have an older flight stick with center slop and high-mileage sensors. I've had very good results with using DIView from upthread (DXTweak2 pukes on one of my Lots Of Axes HOTAS). DIView provides much more precise control over DX-based controllers which may not have internal calibration, which is also a problem BECAUSE Windows' Built In Calibration Wizard will cause you to *overshoot* your endstops, meaning your throttle slider will never reach zero or 100% and stay there!
I've found the optimum to be to set the calibrated end is just inside the actual throw by 1-2 values, so that the slider/throttle handle reaches full saturation slightly before it reaches the mechanical end stop, so you can reliably reach 100%/0% input, at a sacrifice of such a small amount of travel that just resting your hand on the control will lose the difference in noise
Did you figure this out?