Be advised: this thread is not for serious in-depth discussion of weighty topics (we have a link for that), this thread is not for anything Culture War related. This thread is for Fun. You got jokes? Share 'em. You got silly questions? Ask 'em.
- 105
- 1
What is this place?
This website is a place for people who want to move past shady thinking and test their ideas in a
court of people who don't all share the same biases. Our goal is to
optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.
The weekly Culture War threads host the most
controversial topics and are the most visible aspect of The Motte. However, many other topics are
appropriate here. We encourage people to post anything related to science, politics, or philosophy;
if in doubt, post!
Check out The Vault for an archive of old quality posts.
You are encouraged to crosspost these elsewhere.
Why are you called The Motte?
A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently,
it's an element in a rhetorical move called a "Motte-and-Bailey",
originally identified by
philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial
but high value claim to a defensible but less exciting one upon any resistance to the former. He likens
this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for
the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired
propositions to which one retreats when hard pressed."
On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.
New post guidelines
If you're posting something that isn't related to the culture war, we encourage you to post a thread for it.
A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts
such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a
submission statement. A submission statement is required for non-text sources (videos, podcasts, images).
Culture war posts go in the culture war thread; all links must either include a submission statement or
significant commentary. Bare links without those will be removed.
If in doubt, please post it!
Rules
- Courtesy
- Content
- Engagement
- When disagreeing with someone, state your objections explicitly.
- Proactively provide evidence in proportion to how partisan and inflammatory your claim might be.
- Accept temporary bans as a time-out, and don't attempt to rejoin the conversation until it's lifted.
- Don't attempt to build consensus or enforce ideological conformity.
- Write like everyone is reading and you want them to be included in the discussion.
- The Wildcard Rule
- The Metarule

Jump in the discussion.
No email address required.
Notes -
Weird. Are you seeing anything change in Device Manager when you plug in or unplug the controllers? If there's no sound or tree reloading behavior, that points to an issue with the USB hardware on the motherboard. If there are changes, set up an event manager filter to track down what they are; unknown device IDs can also point to hardware issues (usually a past short-from-D+-to-5V). If it's a desktop, switching to different USB ports or to a PCI(E) motherboard might be a cheap way to get back up and running.
When I plug in the controller, I hear a "USB connected" sound, and then every five seconds on loop a "USB disconnected" sound. After every "USB disconnected" sound, Device Manager does an update flash as if something changed, and a "USB device connected" icon appears for a split second in the Taskbar. But following the procedure laid out in the linked Reddit post does not cause Event Viewer to show any Kernel-PnP or Kernel-Pnp-Rundown events corresponding to these happenings.
The problem occurs regardless of whether I use a front USB port (belonging to the case, connected indirectly to the motherboard) or a rear USB port (belonging directly to the motherboard).
Oof. Do you have similar issues with other USB devices in the same physical ports? Keyboards, mice, usb thumb drives, especially anything with higher power draw or running in faster USB modes? Or is it just controllers, nothing else?
Do you know your motherboard? If not, grab CPU-z and check the mainboard tab, then check for BIOS updates from the manufacturer. Especially AMD motherboards have had sometimes-very-weird issues with specific USB modes in early BIOS releases.
It's a bit of a hail-mary, but try unplugging the connection from the motherboard to the front side panel (they're keyed, so it's pretty easy to reinsert the right direction when you're done testing). In humid environments, I have seen bad connections there cause problems all across a hub. PCI(E) expansion cards are cheap as another try if you've got the available slots, but unfortunately most physical stores that stock them will charge an obnoxious premium.
I haven't had any problems with other USB devices (including the aforementioned first-party controller), even in the same ports. (Possibly relevant: The first-party controller uses a USB A to Micro-A cable, while the two third-party controllers use USB A to C cables. But I've connected phones and GoPro cameras with USB A to C cables previously without problems.)
It appears that my AMD motherboard had USB problems that were fixed by BIOS updates around year 2021. I already was using a 2022 BIOS version, and now have updated it to the latest non-beta version from year 2024. This did not fix the problem.
This did not fix the problem.
I guess I have no other option.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link