If the expansion interface is enabled, when the first control is pressed, it "presses" the home button on the PacLink interfaces. So, the I-PAC stores a flag at power-up which tells it that no controls have been yet pressed. This is not possible to do, in a cabinet. The issue is this: On an Xbox 360 the "Home" button needs to be pressed after power on, to initialise the controller and the host assigns an ID to it. We have had a couple of people report via email about the "all buttons pressed" issue, and I have replied by email and not heard back so assume the reply cured the issue. I tried everything with and without the USB connection, and there's something weird there - half the time with the Pac-Links attached, the iPac's LED would blink about 15 times and then shut off when the USB is connected. (3) Something I couldn't find an answer on was whether to reconnect the iPac's main USB connection, when using the Pac-Links. Unchecking that box corrects the problem, and down works normally. (2) Some weirdness about that checkbox in the utility: When it's checked and I have the main iPac USB connection plugged in (Pac-Link or no), pressing P1 down (down arrow keystroke) will cause it to repeat forever until I unplug the iPac USB connection. Does Gamepad refer to directinput support? Which firmware should I be using if I just want X-Input via the Pac-Links? I don't know if that relates to the Pac-Links or not, and whether I should use the version with or without gamepad support (1.34 or 1.44). (1) About the firmware, I do see a later version available but I'm not sure which to use, since I can't figure out what's being said on the Ultimarc page regarding Gamepad support. I've tried the mode switch button combo that's mentioned to switch from analog stick to d-pad, but it doesn't appear to do anything. Holding the Guide button down stops the freakout until I let it go, then it resumes. Connecting the P2 PacLink causes the button freakout that others have mentioned, as if the P2 Guide button is in a 'normally closed' state. No response from any other P1 input in the utility even after reconnection, except the Guide button on the Pac-Link itself. About a second later it stops working altogether. The left analog stick readout in the utility shows very erratic numbers when I move the P1 joystick (which is digital). I load up my xinput test utility to test. Unplugged iPac USB connection, attached the P1 Pac-Link, plugged in the Pac-Link's USB connection. Ran the WinIpac utility and checked the box specified for Pac-Link support and then confirmed that it programmed the iPac with that change. iPac LED is lit, tested all inputs as keystrokes, all's well, no problems. Connected iPac via main USB connection. This is on a fresh Windows 7 64-bit install. My goal is to use the iPac for X-Input only, no keystrokes, directinput not needed. The iPac is running firmware 1.33 that was stock with this iPac (see note 1). I have the MS driver for 360 controller support installed. So, starting from literally out-of-the-box: At this point the Pac-Links are not connected to the iPac, and both of their mode switches are set to X360. I figure I'd catalog everything I've done so far to get them working since I bought two of them and I'm starting to feel a little burned - I got these specifically because I was really starting to hate the clunkiness of the PS360's I was using for X-Input before. that are higher than the Xbox 360 controller.Yeah, another +1 here. However, it does not support buttons, sticks, etc. Therefore, it is possible to operate with the optimum operation method (assumed by the creator) without making any special key settings. The layout and vibration functions of the buttons and sticks are all unified in the form of the XBOX 360 controller. The format is based on the Xbox 360 controller. A format newly created and recommended by Microsoft as an alternative to DirectInput.DirectInput has been provided as a component for input control of Microsoft DirectX, but it has not been updated since DirectX 8 (around 2000).Depending on the controller and game implementation, there may be cases where the allocation is not successful. In addition, since the number and position of buttons and sticks are not fixed, it is necessary to set the key assignment according to the controller used by the user in order to operate with the optimum operation method. Therefore, it is necessary for the program side to support various types such as the number of buttons, the number of sticks, and the presence or absence of the vibration function of the controller. It supports various types of controllers, from game pads to complex control stick controllers used in steering wheel controllers and flight sims. A format that has been used on PCs for a long time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |