$begingroup$

Jump to Buying a controller? Or something else? - If you're looking to buy an XBox 360 controller to use, or any other Amazon items, please consider. Feb 10, 2019  As of macOS 10.11, Wireless Xbox 360 controller support causes kernel panics. This issue cannot be resolved with minor changes to the driver, and requires that the driver be re-written from scratch to resolve the issue. Due to an excess of caution, we have disabled Wireless Xbox 360 controller support as of 0.16.6.

Tattie Bogle12 Controller Driver Pc

I'm using a fork of the Tattie Bogle driver that has a signed kext. The System Settings panel shows all inputs correctly.

One axis is configured in Unity3D 5 like this:

Still, I don't see any input when the game is running. I also cannot configure Positive/Negative Buttons for any input in the Input Manager panel - clicking the input line edit and entering a keyboard key works fine, but pressing a controller button does nothing.

Tattie Bogle12 Controller Driver Free

What am I missing here?

2 Answers

In addition to the Tattie Bogle Drivers, you also need to use Unity-XboxCtrlrInput for Unity if you want to use your Xbox Controller on Unity.
It is working for both Unity 4 and Unity 5.
They have a working example project that you can download from the project page if you want to test your Xbox Controller with a working project.

After a bit of research it appears your biggest issue, assuming you have just plugged in and hoped for the best, is that (naturally) mac does not have the drivers to understand an Xbox controller.

A good rule of thumb: If you plug anything Microsoft into anything Apple and just hope for the best, your going to have a bad time. They just don't like talking to each other.These two sites gave me a bit of insight into connecting various original and third-party controllers. I assume if you follow the driver installation you have a good chance of that fixing everything, just remember that the driver is what the computer uses to understand the device. It is possible that a different driver will interpret the controller a little differently - this may go as far as swapping buttons on the player.

That said, the driver refereed to at jacobtomlinson.com (provided by tattiebogle.net) has come up in a few times in the past, so I would assume that is the general driver players would be using.

Also keep in mind that the drivers impact the identification of the buttons themselves, so you can not use native windows reference to the controller and expect the buttons to remain the same. This last link shows the button references on a Windows system, and the reference system used by the tattieboggle driver.

Not the answer you're looking for? Browse other questions tagged unitymacosxbox-controller or ask your own question.

Hello!

Gone Home’s system requirements are as follows:

Windows:

Tattie Bogle12 Controller Driver Update

• WindowsXP SP2 or higher
• 1.80GHz Processor
• 2GB Memory
• Video card with 512MB or greater VRAM
• (Note: Intel HD Graphics 4000 not supported on Windows 8)
• 2GB HDD space

Mac:

• OS X v10.7 Lion or higher
• 1.80GHz Processor
• 2GB Memory
• Video card with 512MB or greater VRAM
• 2GB HDD space

Tattie Bogle12 Controller Driver Windows 7

Linux:

• glibc 2.11 or newer
• 1.80GHz Processor
• 2GB Memory
• Video card with 512MB or greater VRAM
• 2GB HDD space

If you’re looking for your Gone Home data, including saves, options, and key binding files, they are located in different places depending on your OS:

• Windows Vista/7: /Users/<username>/AppData/LocalLow/The Fullbright Company/Gone Home
• Windows XP: /Documents and Settings/<username>/Local Settings/Application Data/The Fullbright Company/Gone Home
• Mac OSX: ~/Library/Caches/The Fullbright Company/Gone Home
• Linux: ~/.config/unity3d/The Fullbright Company/Gone Home

Here are some solutions or workarounds we’ve found to some problems our players have reported:

Tattie Bogle12 Controller Driver Windows 10

• For gamepad support on OSX, Gone Home only officially supports the Xbox 360 gamepad with third-party drivers. Please find the tattie-bogle OSX gamepad drivers here: http://tattiebogle.net/index.php/ProjectRoot/Xbox360Controller
• If your game is crashing at startup, and you are running on Windows 64-bit, try going into your install directory and running GoneHome32.exe. If it still crashes on startup, try renaming GoneHome32.exe to GoneHome.exe and GoneHome32_Data to GoneHome_Data, then run GoneHome.exe.
• Alternately, if the game is crashing on startup and your 3D accelerator card is of the Intel HD Graphics line, you may need to disable CMAA in Intel driver 3D settings.
• If you’re having problems with controls or input, please make sure you don’t have any extra joysticks or controllers plugged in. Gone Home supports the Xbox controller, but any other peripherals such as steering wheels, rudder pedals, or joysticks can cause input to be registered incorrectly.
• If you’re not seeing the lights turn on when you flip switches, please ensure you have installed the most recent drivers for your video card. (and, of course, that your hardware meets our minimum specifications for playing). Also check your NVidia or graphics card’s control panel software and make sure your dedicated graphics card is set to Default, so that Unity does not use a graphics card that might be integrated into your motherboard.
• If your performance is much worse than expected (for instance, low framerate even on lowest settings,) try going into your Nvidia or graphics card’s control panel software and make sure your dedicated graphics card is set to Default, so that Unity does not use a graphics card that might be integrated into your motherboard.
• If you can navigate the menus with the mouse, but the keyboard controls don’t work for you, try deleting the “UserBindings.sav” and “DefaultBindings.sav” files and reloading the game.
• Some crashes or blackscreens can be caused by other programs that grab the rendering device. Try stopping any other programs that are running before launching the game.
• We’ve discovered that Avast! Antivirus can cause problems with the game. If you’re seeing a crash immediately upon starting the game, please disable your antivirus entirely (“game mode” is not enough) and try again. As an alternative to disabling the software completely, you might also try the following: In Avast!, go to Settings -> Troubleshooting -> disable Hardware-Assisted Virtualization -> Reboot your machine.
• If you’re playing through Steam and seeing a crash, try right-clicking on the game, choosing “Properties” and unchecking the box next to “Enable Steam Community”
• If you are on MacOS, and experience a crash, and then have trouble getting your game to start again, try deleting the OS cache files in “Finder/Library/unity.The Fullbright Company.Gone Home.savedState” or “Finder/Library/Saved Application State/unity.The Fullbright Company.Gone Home.savedState” or “~/Library/Containers/com.thefullbrightcompany.gonehome/Data/Library/Saved Application State/com.thefullbrightcompany.gonehome.savedState”
• If you are seeing an error about Mono, please try (re) installing the Microsoft Visual C++ 2010 Redistributable Package? The 32-bit version is here: http://www.microsoft.com/en-gb/download/details.aspx?id=5555 and the 64-bit is here: http://www.microsoft.com/en-gb/download/confirmation.aspx?id=1463.
• If you are on Linux and experiencing movement issues, try this workaround from Arderath on the Steam forums:
  • – Right click on the game in Steam, select «Properties»
    – Click «Set launch options»
    – Enter: LC_ALL=C %command%
    – Click OK, and then Close.
  • (http://steamcommunity.com/app/232430/discussions/1/864976115284478645/#c864976115478302160)

If your issue isn’t covered here, please visit the Steam support forum. Membership is free:
http://steamcommunity.com/app/232430/discussions/1/