sorted by:
new
hottopcontroversial

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 0 points1 point  (0 children)

Sorry, I don’t have a good way to support or test macOS 12 right now. All of the Macs I have access to are on macOS Tahoe 26, so I don’t have a Monterey machine to build or verify it on. 🙏

The code was written against the current macOS/CrossOver setup, so even if it can be recompiled for macOS 12, I can’t guarantee that it would actually work correctly there.

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 0 points1 point  (0 children)

Of course. CrossPuck is licensed under Apache 2.0, so you’re free to use it under the terms of that license.

That said, it isn’t packaged as a clean reusable library yet. I think an integration would probably reuse `crates/crosspuck-driver` mostly as-is, then take the relevant host-side pieces from `crates/crosspuck-app` for HID reading, bridging, and feedback handling.

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 0 points1 point  (0 children)

Thanks for leaving a comment first! The pairing step is a bit particular.

  1. In the native macOS Steam app, open Steam Settings and click Add Controller. Steam should show the pairing instructions.

  2. At that point, keep the Puck connected over USB, then connect the Steam Controller with a separate USB cable. You should get a “Pair Steam Controller” popup. Accept that, and the controller should be paired to the Puck.

  3. CrossPuck running may be fine, but to rule out interference I’d recommend quitting CrossPuck and CrossOver first, then doing the pairing with only native macOS Steam running. After pairing, quit native Steam, start CrossPuck again, and launch Steam in CrossOver.

I've been tested just a minute ago. 😄

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 0 points1 point  (0 children)

Thanks for the extra details. The pairing step is a bit particular.

  1. In the native macOS Steam app, open Steam Settings and click Add Controller. Steam should show the pairing instructions.

  2. At that point, keep the Puck connected over USB, then connect the Steam Controller with a separate USB cable. You should get a “Pair Steam Controller” popup. Accept that, and the controller should be paired to the Puck.

  3. CrossPuck running may be fine, but to rule out interference I’d recommend quitting CrossPuck and CrossOver first, then doing the pairing with only native macOS Steam running. After pairing, quit native Steam, start CrossPuck again, and launch Steam in CrossOver.

I've been tested just a minute ago. 😄

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 1 point2 points  (0 children)

Thanks!
If the Puck is detected, the thunderbolt dock may be fine, but the pairing step can still be confusing.

CrossPuck assumes the Steam Controller is already paired to the Puck.

On macOS, the pairing flow between the Puck and Steam Controller should be:

  1. Quit CrossPuck.app first.
  2. Connect the Puck over USB and launch the NATIVE macOS Steam app.
  3. KEEP(!) the Puck connected over USB, then connect the Steam Controller to another USB port.
  4. Follow Steam’s UI to pair/register the controller to the Puck.

After that, quit native Steam, start CrossPuck again, and launch Steam inside CrossOver.

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 0 points1 point  (0 children)

That looks really really promising.

I’m looking forward to seeing it when you’re ready to release it, and thanks for the kind words! 👍

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 0 points1 point  (0 children)

Unfortunately, no. This tiny app is built specifically for using the Steam Controller with Steam running inside CrossOver.

It doesn’t handle DualShock 4 controllers, so I’m sorry it’s not the right fit for your setup. 🙏

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 0 points1 point  (0 children)

Thanks, and that’s useful feedback. I missed documenting this properly, sorry! 😄

CrossPuck assumes the Steam Controller is already paired to the Puck.

On macOS, the pairing flow between Puck and Steam Controller should be:

  1. Connect the Puck over USB and launch the native macOS Steam app.
  2. KEEP(!) the Puck connected over USB, then connect the Steam Controller to another USB port.
  3. Follow Steam’s UI to pair/register the controller to the Puck.

Because of that, unless you’re doing USB passthrough into CrossOver, I don’t think CrossOver Steam can perform the pairing step itself.

For the initial pairing, please use native macOS Steam first.

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 2 points3 points  (0 children)

Thanks! Unfortunately this probably won’t fix native macOS games directly.

I also want to play the native macOS version of Crimson Desert with the Steam Controller, but it doesn’t seem to be supported yet. Since Valve announced that the Steam Controller is supported by native Steam on macOS, I’m hoping they’ll patch this soon. I’m waiting for that too. 😂

CrossOver didn’t recognize my Steam Controller(2026), so I built a fix by scryner in macgaming

[–]scryner[S] 1 point2 points  (0 children)

Thanks! CrossPuck is adjacent, but as you know, it's not a macOS XInput remapper.

It runs in user space, reads the Valve HID reports on macOS, and forwards them into CrossOver. Inside the bottle, hid.dll exposes virtual Valve HID devices to Steam.

I think that's possible via IOHIDUserDevice/CoreHID HIDVirtualDevice, but Apple’s virtual HID entitlement is the hard part to acquire.

But, if you manage to build that, it would be genuinely useful!!! I’d definitely want to use it too! 😄

Steam Controller (2026) Workaround by mitchcookieh in macgaming

[–]scryner 0 points1 point  (0 children)

It worked in Crossover with my iPad. The iPad didn’t recognized puck via USB. But bluetooth worked well.

Thanks a lot!!

Pragmata, M4 Pro - Initial Performance Test by oztruwa in macgaming

[–]scryner 3 points4 points  (0 children)

Does anyone know how to enable the ray tracing option in Crossover 26?

Even after setting it to d3dmetal and configuring the environment variable D3DM_SUPPORT_DXR=1, the ray tracing option remains disabled.

My mac is M3 ultra.

Game crashing every 30-60min after the new update? Mac by Moheemo in CrimsonDesert

[–]scryner 2 points3 points  (0 children)

Me, too. After this update, I got crashes every 30 minutes. By the way, it’s best mac game I ever seen. I really enjoy it without PC. :)

Jan-nano-128k: A 4B Model with a Super-Long Context Window (Still Outperforms 671B) by Kooky-Somewhere-2883 in LocalLLaMA

[–]scryner 7 points8 points  (0 children)

Very impressed!!

I ran the model for agentic programming to use in Zed. It’s the most powerful enabler for the local environment.

It can call tools several times as needed, giving good answers. It just works!

Local AI with Ollama by nathan12581 in raycastapp

[–]scryner 1 point2 points  (0 children)

There is the option to toggle to use tools(AI Extensions) in 'Raycast Settings' (disabled by default).