安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
They're ancient. Far older than those racing wheels.
I haven't updated to Win10 2004 yet, but I'll post here when I do and let you know how much of my legacy logitech stuff it breaks.
Sounds great! Thanks for the help in confirming this with any other legacy hardware.
I'm willing to give it the old college try again. I've got multiple logitech devices and multiple machines running different versions of windows. I've already tested the gamepad and joystick on build 1903 and can confirm they work (tested them in older games though, so no comment yet on if the freedom 2.4 is affected by the high cpu utilization related input latency issue).
I plan on updating my media center PC to build 2004 (since it just needs to play videos and not games, it'll be the guinea pig) and continuing testing there. That may have to wait until later today.
after windows 10 has finished installation and you successfully logged, reboot computer once more. at next login, plug your racing peripherals and compare with OP's experience.
But the same issue of course came with other people I spoke to on Discord who got the update through Windows Update, so as far as I can tell, it's not an issue related to updating to the new version, but the new version itself since this issue is with my current clean install of Windows 10.
Also, I made this exact same post on Toms Hardware Forums, and a moderator over there has tagged the resident Logitech reps for the forums to see if they can offer any advice or help so crossing fingers for anything to come from that as well.
Its my go to flight stick and has worked just fine in windows 10 since release along with an equally old usb pedal set from a now defunct no name.
Would be a shame (and for me a reason to avoid the 2004 update all together) if they have broken older controllers or things that rely on early versions of direct input.
It has nothing to do with that. The software and the wheel work fine bro.
Wheel gets seen in the software, and works in test mode in the advanced properties through the software.
The issue lies with the fact that games don't see the devices anymore like they should.
Not a single game.
Please understand what is being talked about before saying things, especially don't say something like "run in compatibility mode" so matter of fact as if you know exactly what the issue is and how to fix it because you've done all the leg work yourself to troubleshoot and do testing with the issue at hand.
The software itself installs and runs fine and so do the drivers.
And if you really knew what you were talking about, you would know that the software won't even install when running the installer in compat mode for Windows 8, and you would also know that the software itself when installed will not run properly if you try to run it in compat mode for Windows 8.... suffice it to say, Windows 8 is not supported.
Respectfully,
- Pengwen.
I get what you're saying, but unfortunately it's not a choice thing.
I didn't opt into this version of Windows, it's already baked into Windows 10 now and is what you get when creating an install media using Media Creation Tool.
It's not hard to manually get a hold of the previous version for install though.
My main issue at this point now is that I don't want to do another clean install and have to re install programs and stuff again LOL.
And soon enough Microsoft will roll the update out to everyone through Windows Update and then we'll all be screwed no matter what unless either Microsoft or Logitech do something about it. *sigh*
ms knows drivers are their biggest issues, why push a update that wipes them all?
What are you reading?
MS says from their own lips, not to update to 2004 until they fix the bugs. They release these feature updates as-is so people can try them and report the problems. They been doing this ever since 1809 which made a change to Windows Updates, making 1903 and above "optional"
Hmm, I wonder WHY they made feature updates optional? To stop law suits from people trying to do "work" and shouldn't be forced to update in that moment when MS feels like it's a good time to push BS down your throat.