417 replies to this topic

[Skyforya]

Hey there^^

So i have downloaded the SB 2.0.1 and installed it - so far so good... But even with the Simple3.3 i can barely configure the axis. I got it showing me the raw-data and it barely gives out bits so it´s not possible for me to calibrate it right...

Also my MW4-version doesn´t work, got some errors within the tool shown. Updating MWO atm, didn´t play till beginn of the closed beta

P.S.: Sorry for my english, but i´m from germany... Sometimes i have problems understanding some things *ehe*
P.P.S.: Does it make a difference, if i use the 1st oder 2nd Generation of the Controller? got the 1st gen here with green buttons

Edit: Had my MW3 running with it, but i circle around and got a instant full reverse that doesn´t get away... Does anybody have a cs-file of mw3 for me?

Edit2: Just tried the MWO3.3 - didn´t work for me... circling around again...

Greets,
-Sky-

Edited by Skyforya, 31 August 2013 - 11:29 AM.

[Golden Gun]

Okay wow! I thought this thread was closed so I hadn't seen all the new work you have put into it. GREAT STUFF!

I've been piddling around with the .CS file also and went in a slightly different direction. The toggle switches seem to be the only "constant press" buttons on the controller so I use those for things like have weapons group 6 hard wired into the VT-Location Measurement switch and only use that group for TAG. I also will be using one for the "Q" key. I donno, I just like to see what is going on with my allies.

You also increased the resolution of the right joystick from 0-255. HOW THE $%#@^* DID YOU DO THAT??!?!?!? Because I think you might just have fixed another issue I was attacking... I'll report more on that when I check it out.

I'm currently trying to figure out how to hardcode instructions into each gear on the gear lever. I know it can be done as it is on the MW4.cs file but I don't quite understand the syntax to get it to do what I want it to do. My idea is to have each position be coded to a throttle percentage from the keyboard. So when it is done, if I move the gear shift to, say, 3, it will send button press for 60% throttle. 4=80% N=FULL STOP etc etc. I want to have send a single press instead of a constant, that way you can still use the peddles and the gear shift would be more of a cruse control.

Also, do you know how to make a button a constant press? IE, I push "Washing" and release but it continues to send a "press & Hold" signal until I press it again? Being able to do so would release the toggles as the only thing on the controller that has a "constant press" output and open up new doors into programming for the game.

Oh, I may be a bit getting back to you as I just had ACL replacement surgery (right knee) and working the peddles = NOT FUN!

Tanks again for all you've done!

Golden Gun

PS- here is the main thread I stared a while ago about the few things I'm looking to change on the SB controller.

http://mwomercs.com/...ick-support-20/

PPS- I have 4 of them; Several modded Xboxes: Hosted a few SB:LOC parties = I'm in it for the long run

Edited by Golden Gun, 04 September 2013 - 06:20 PM.

[HackNFly]

What cs file are you using?

In the beginning of most of the configuration files floating around, you'll find a section with a bunch of statements like these:
controller.AddButtonKeyLightMapping(ButtonEnum.Washing, true, 3, Microsoft.DirectX.DirectInput.Key.C, true);

The last boolean indicates whether or not you want it to send the signal once or continuously. However both modes will stop sending the signal as soon as you release the button.

The exception would be if its been hardcoded to do otherwise, i.e.


// Free Look Latch
if (controller.GetButtonState(ButtonEnum.FunctionF3))
{
if (freelook == 1)
{
controller.sendKeyDown(Microsoft.DirectX.DirectInput.Key.LeftControl);
freelook = 3;
}
if (freelook == 0)
{
controller.sendKeyUp(Microsoft.DirectX.DirectInput.Key.LeftControl);
freelook = 4;
}
}

if you use something else in your code, you can manually use the sendKeyUP and sendKeyDown statements to press keys without actually binding them to anything. That might be whats going on. Sorry I've been inactive. Been busy with other projects i.e. work.

[Merix]

Having some trouble and am wondering if anyone can help.

I get in game and all of my buttons work, but only the left thumb joystick works, the rest don't do anything.

Also my trigger only works on alpha, it does not fire the selected group.

Also, my left (full stop/jump jet) works but only full stop not jump jets, but none of the others.

Edited by Merix, 17 September 2013 - 11:26 AM.

[Golden Gun]

Setting up the SB controller takes several steps and it sounds like you may have missed one or two. Just to verify, did you:

1) Start up Steelbattalion-64
a) Load BvP-Simple-3.0.cs file (If you are using your own .cs file, this one is still very good for calibrating)
b) click start
c) make sure controller's lights flash five times
d) Leave Steelbattalion-64 open and maximized

2) Start up Windows USB controller config
a) select and calibrate controller
b) use the output diagram to make sure all ranges react properly
c) IF OUTPUT DOES NOT WORK PROPERLY, DO IT AGAIN! (I have to calibrate twice every time)
d) Leave Windows USB controller config open

3) Go back to Steelbattalion-64
a) Stop running BvP-Simple-3.0.cs file
b) Load BvP-MWO-3.1-uac5.cs file (or your own .cs file)
c) click start
d) make sure controller's lights flash five times
e) minimize Steelbattalion-64

4) Start up MWO
a) Sign in
b) go to settings
c) make sure your inputs are set to the correct axis (use Windows USB controller config for reference)
d) test out in the training fields
e) if working good, close Windows USB controller config

As a side note, you'll also want to make sure you have the updated info in your user.cfg file for MWO. If not, your sticks may not respond as well as they could.

GOOD LUCK and let us know how it works out.

Edited by Golden Gun, 17 September 2013 - 01:03 PM.

[Merix]

I am unable to configure the Windows USB controller config. No controller shows up to be configured.

Forgot to restart vJoy. I have a vJoy device but nothing seems to configure.

Edited by Merix, 17 September 2013 - 03:24 PM.

[Golden Gun]

Okay, then a few questions.

Have you downloaded all the needed packages and installed them? Which guide are you following to install? Please provide a link.

Are you running Windows in "Test Mode"?

I followed the installation guide on the Steelbattalion-64 wiki page: https://code.google....ki/Installation

Make sure you follow it in order or you will have all kinds of issues.

[Merix]

Golden Gun, on 17 September 2013 - 03:28 PM, said:

Okay, then a few questions.

Have you downloaded all the needed packages and installed them? Which guide are you following to install? Please provide a link.

Are you running Windows in "Test Mode"?

I followed the installation guide on the Steelbattalion-64 wiki page: https://code.google....ki/Installation

Make sure you follow it in order or you will have all kinds of issues.

thanks for the help. Restarted using that guide and I am configuring now. I'm in the middle of the calibration but can't seem to find the Z axis. Nothing I do effects the Z axis.

Got it working now except for one problem. My aiming joystick requires me to move my joystick all the way to the edges before it moves. Is there any way to change this?

Edited by Merix, 17 September 2013 - 03:50 PM.

[Golden Gun]

Yes there is!

there is a config file called user.cfg in your MWO folder. This file lets you configure the sensitivity and all that for the game. If you skip back to page 10 of this thread you'll see some awesome work done to better the inputs of your sticks. All you have to do is copy that info over the current info in the file, save it and yer done!

MUCH easier then all the other steps.

[Merix]

Golden Gun, on 17 September 2013 - 04:23 PM, said:

Yes there is!

there is a config file called user.cfg in your MWO folder. This file lets you configure the sensitivity and all that for the game. If you skip back to page 10 of this thread you'll see some awesome work done to better the inputs of your sticks. All you have to do is copy that info over the current info in the file, save it and yer done!

MUCH easier then all the other steps.

One last question. Where is the user.cfg? I can't seem to find it.

[Golden Gun]

do a search for the folder: MechWarrior Online

It's in there.

Oh, and I'd save the original file as user-old.cfg just in case you need to switch back.

[Merix]

Golden Gun, on 17 September 2013 - 04:44 PM, said:

do a search for the folder: MechWarrior Online

It's in there.

Oh, and I'd save the original file as user-old.cfg just in case you need to switch back.

My MechWarrior Online folder only has 2 cfg files. System.cfg and Systemoveride.cfg

[Golden Gun]

Then create the file by making a new .txt, paste the info into it and save it as: user.cfg

[evilC]

FYI, I responded to your thread on the vJoy forums about scale...

[Golden Gun]

evilC, on 18 September 2013 - 10:37 AM, said:

FYI, I responded to your thread on the vJoy forums about scale...

Yeah, I saw it. But I think you misunderstood what I was talking about. I was talking about resolution of the the joystick meaning how many points along it's axis it send a signal per position. Vjoy states 0-255 which doesn't translate well for the type of aiming I am trying to do.

I'm still pretty sure the Steel Battalion controller has a higher resolution then this, but haven't been able to figure out how to get to it. The two Xbox games it was made for seem to be able to access this higher resolution I'm talking about...

This might be moot though since the latest version of VonPilsner's .cs file might be able to provide what I'm looking for. Once I am well enough to get out of bed, I will get to testing it. I have a sinking feeling though that it will give the same amount of positions/resolution, but only in an exponential range.

If it still doesn't work smoothly enough, I may replace the right joystick with a Thrustmaster T16000M. Basically I would have two joysticks running at the same time; The Steel Battalion Controller minus the right stick and the T16000M internalized in the right controller block.

[HackNFly]

Thanks to your persistence, I just QUADRUPLED the resolution on the right stick!!!!

I didn't write the original USB parsing code. I fixed a few glitches I noticed along the way. I think I never assumed the axis were more than 255 levels since the original xbox controller only had axis that were 255 levels. Since its essentially just a USB HID device, the manufacturer can specify how they want things to be stored.

The whole scaling thing meant that it went unnoticed as I simply scaled 0-255 - 0 - 32K or something along those lines.

Anyways. I went back and looked, and I think all the axis might actually be 10-bit resolution !!!

For those of you still interested in MWO... This should mean a HUGE difference in how the controller responds. I'll see if I can put out an update this weekend. It should take me about 3 hrs or so to go through the code and test it. Again, thanks for your persistence.

~HackNFly

[Golden Gun]

DUDE!!!!!!

You rock!!!

Please let me know if there is anything I can do to help out. I still can't use peddles, but I can work the controller with a little effort.

[HackNFly]

I'll probably end up needing Von Pilsner to redo his settings, since at this point he has more in game experience at that level than I do. However other than that, its a pretty straight forward job to do. Still not sure if you're going to like using the throttle. Its "sticky" since its a sliding potentiometer rather than an actual lever. I could set up the red buttons up to control throttle presets. We'll figure something out for you. Unfortunately I won't get to it until this weekend due to work.

~Hack

[Golden Gun]

totally understand, I appreciate all you are doing for this small faction of the community.

[evilC]

Golden Gun, on 18 September 2013 - 04:05 PM, said:

Yeah, I saw it. But I think you misunderstood what I was talking about. I was talking about resolution of the the joystick meaning how many points along it's axis it send a signal per position. Vjoy states 0-255 which doesn't translate well for the type of aiming I am trying to do.

I'm still pretty sure the Steel Battalion controller has a higher resolution then this, but haven't been able to figure out how to get to it. The two Xbox games it was made for seem to be able to access this higher resolution I'm talking about...

This might be moot though since the latest version of VonPilsner's .cs file might be able to provide what I'm looking for. Once I am well enough to get out of bed, I will get to testing it. I have a sinking feeling though that it will give the same amount of positions/resolution, but only in an exponential range.

If it still doesn't work smoothly enough, I may replace the right joystick with a Thrustmaster T16000M. Basically I would have two joysticks running at the same time; The Steel Battalion Controller minus the right stick and the T16000M internalized in the right controller block.

The value AHK reports is floating point not an integer right?
ie not whole numbers between 0 and 255, but instead a number like 50.123456789

That is NOT "255 positions". It is still probably 32,000 positions, just they are spread over a decimal scale.