Question About Xpadder and Camera/Mouse Settings

[Rabbit Heart]

Hi and thanks for helping!

I downloaded the last freeware version of Xpadder, and was able to run it (I have Windows 7, 64-bit) by opening it via the "Troubleshoot Compatability" option, which was suggested by someone for the Windows 7/Xpadder demo version incompatability issue.

From what I can see, almost everything works perfectly - I was able to map the buttons I wanted to, and was able to set the left analog stick as character movement, instead of the switched conundrum found in the game's default settings.

However, I'm still having difficulty connecting the right analog stick to camera movement. Using the settings option next to the right analog stick, I selected default mouse movement, which I thought would give me what I wanted (as I thought the default keyboard settings for the game had the camera controlled by the mouse).

The problem is, it connected the right stick successfully to the mouse pointer, but instead of moving the camera, it just moves the visible pointer around on top of the screen, doing nothing in-game.

I have a feeling this is an easy fix that I'm missing - I know sometimes you need to click the window or screen of a game to get the mouse active in a game's controls, but clicking on the game screen didn't solve anything.

I'd greatly appreciate any help and suggestions - the sticky topic explains quite a bit, but I couldn't find a solution there that matched my issue.


Thank you again!

[Boxcutter]

DMC3 has zero mouse support. Also, the camera is fixed in most places, and is fine with default angle and lock-on. The game can recognise xinput controllers, so the only buttons they need to map througn xpadder are analog triggers, everything else can be tinkered with through ini.

[Rabbit Heart]

Yeah, I just would like to be able to control the camera when possible, and since the default controller setup assigns one of the analog sticks (although in reverse) to camera control, I was hoping to figure out a way to assign that appropriately.

[Boxcutter]

Well, did you fiddle with the config.ini like the sticky suggests? Your solution might restrict you to 8-directional movement, which is likely very lousy for performing stingers and launchers and such. Default camera controls on pc are bound to arrow keys.

[Rabbit Heart]

Originally posted by Boxcutter:

Well, did you fiddle with the config.ini like the sticky suggests? Your solution might restrict you to 8-directional movement, which is likely very lousy for performing stingers and launchers and such. Default camera controls on pc are bound to arrow keys.

Yes. The problem is (once you follow some of the additional links in the sticky about getting the controller configuration launcher to work, etc.) that I have a Microsoft Xbox 360 controller, which is the one controller for which the configuration file is essentially useless. By default, the game will map a few keys to the controller, but only a few, and the analog sticks are reversed (the fixes for that problem also exclude 360 controllers). As others have pointed out in the sticky thread, if you try using the game's controller configuration (or the .ini file) to switch around the buttons assigned to the 360 controller by default, the alterations won't work - instead of switching the bound keys around, you'll get two actions bound to each button, resulting in alternating jumping and gun firing, for example.

By charting everything through Xpadder I have everything set up as needed, except for camera control. If the directional arrows on the keyboard are the default setting for the camera in-game, I can try mapping them to the right analog stick. Oddly, mapping WASD through Xpadder to the left analog stick works quite well, so I'm not worried about not putting the full rotation of the analog stick to use for the camera.

For some reason I thought I'd tried the arrow keys thing already, but I'll give it another shot and post the results.



(Just to lump this in there, my only other main problem at the moment is screen-tearing, which is also something I noticed mentioned by someone else in the sticky thread but there was never really a solution - I have an AMD card, as he did).

[Boxcutter]

What are you even talking about. Sticky has configs specifically for 360 pads, it has a bunch of replies mentioning successfully working 360 pads, and it's the one I use myself. Maybe yours identifies itself weirdly, then you just gotta find the right name in the hardware monitor.

[Rabbit Heart]

There are also a bunch of replies where it doesn't work for people. I tried each of the ways suggested in the sticky - I used the original name given, and I also tried using the exact name given in the Devices & Printers section.

[Rabbit Heart]

OK, so I figured it out. In my case, I had to delete everything in the original .ini file, and save it blank. Then, using Xpadder, I mapped the action keys (by looking at the default keyboard settings) to my controller buttons.

The missing piece for camera movement was the arrow key thing, which I thank you for (there's no option to change default keyboard settings for movement or camera control, so I had no idea which keys were set to control the camera). As the camera only seems to swing left to right anyway, using Xpadder to map the arrow keys to the right analog stick does the trick.

**For anyone else reading this, who has similar problems getting a Microsoft controller working, the biggest thing is to get Xpadder (the existing freeware versions, if you have Windows 7 or another version that doesn't meet the programs standards, can still be run by selecting "Run Program with Compataibility Mode" after right-clicking the Xpadder .exe file). You then want to delete everything in the original DMC3SE.ini file, and save it blank.

Then - this was the clincher with me! - have Xpadder running, but leave your controller unplugged when you start the game. Escape through the opening credits, and wait to plug it in until the game's menu is on-screen. Otherwise, even with the .ini file erased, the game will force specifc actions onto certain controller buttons, on top of what you already have set with Xpadder.**

Would be happy to try to help anyone with similar problems - now to try to get help with my screen tearing! :-(