Jump to content

Cant Invert Y Axis


16 replies to this topic

#1 Xustalax

    Member

  • Pip
  • Bad Company
  • 16 posts

Posted 28 January 2013 - 03:15 PM

Im using the joystick T.16000M and when i play i cant invert the y-axis
Is there any chance in getting this fixed?
Thanks in advance

#2 Loc Nar

    Member

  • PipPipPipPipPipPipPipPip
  • 1,132 posts

Posted 28 January 2013 - 03:47 PM

Xustalax,

I have sweet TARGET scripts for the t16000 (including lines to invert the y axis if you can't do it in the client options menu) if you are interested. I'm out and about at the moment, but can get it to you later if you're interested. The beauty of using a Thrustmaster T16000, Warthog, or Cougar is using TARGET, which makes using your stick with MWO particularly easy, especially the whole dialing it it in part...

#3 Xustalax

    Member

  • Pip
  • Bad Company
  • 16 posts

Posted 29 January 2013 - 05:17 AM

View PostLoc Nar, on 28 January 2013 - 03:47 PM, said:

Xustalax,

I have sweet TARGET scripts for the t16000 (including lines to invert the y axis if you can't do it in the client options menu) if you are interested. I'm out and about at the moment, but can get it to you later if you're interested. The beauty of using a Thrustmaster T16000, Warthog, or Cougar is using TARGET, which makes using your stick with MWO particularly easy, especially the whole dialing it it in part...


I'd appreciate that really much <_<

#4 Xustalax

    Member

  • Pip
  • Bad Company
  • 16 posts

Posted 29 January 2013 - 07:36 AM

View PostXustalax, on 29 January 2013 - 05:17 AM, said:


I'd appreciate that really much ;)



I downloaded the target program and inverted the axis
Thanks for letting me know, i didnt even know that it existed xD


By the way, is there any chance of increasing the sensibility of the joystick? Both the x and y axis only work when im holdin the joystick like 80% to the sides or front/rear and doesnt react gradually. This makes it really hard for me to aim.

Edited by Xustalax, 29 January 2013 - 07:38 AM.


#5 evilC

    Member

  • PipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 1,298 posts
  • LocationLondon, UK

Posted 30 January 2013 - 04:38 AM

That is a "deadzone".
It is either the game settings (an option in user.cfg) or stick settings.
Be aware though, if you use stick for turning (or even if it is bound to turn, and the stick is plugged in - it matters not if you use it) and turn off the deadzone in MWO's user.cfg, unless your stick reports EXACTLY centre (ie 50 of 100 for that axis) with NO WOBBLE then you will endlessly turn.
The only fix for that at the moment is to program a deadzone using the software that comes with your stick, or using a script.

Edited by evilC, 30 January 2013 - 04:38 AM.


#6 Xustalax

    Member

  • Pip
  • Bad Company
  • 16 posts

Posted 30 January 2013 - 04:46 AM

Its the game settings. In MW mercenaries it works perfectly.

My joystick has a sensor indicating when its activated to a direction (a LED light) it only glows when i touch it so i guess its always exactly at center. Could you explain me how to disable deadzone on user.cfg? Its the first time I hear about it :blink:
thanks

#7 Loc Nar

    Member

  • PipPipPipPipPipPipPipPip
  • 1,132 posts

Posted 30 January 2013 - 08:48 AM

Quote

By the way, is there any chance of increasing the sensibility of the joystick? Both the x and y axis only work when im holdin the joystick like 80% to the sides or front/rear and doesnt react gradually


I have a few things to do on it (as well as write up instructions on use/button mapping) and I've been swamped the last few days with other things so haven't got it ready juuuuust yet, don't start goofing with your .cfg/.xml files if people start giving you non-TARGET advice here. You have one of a very few sticks that does not require you to do this (outside of 2 simple lines in .cfg which I will provide in the instructions), and it will make things harder. Standby...

Since you've already downloaded and started messing with TARGET in the meantime though, to increase axis sensitivity is pretty easy actually. Pull up your TARGET script (I assume your using the TARGET GUI) and get into the profile you have started. Select the axis you want to mess with and it gives you parameters to adjust. The one you are interested in is called 'zoom', and increasing the value there increases axis sensitivity.

#8 Xustalax

    Member

  • Pip
  • Bad Company
  • 16 posts

Posted 01 February 2013 - 04:51 AM

View PostLoc Nar, on 30 January 2013 - 08:48 AM, said:


I have a few things to do on it (as well as write up instructions on use/button mapping) and I've been swamped the last few days with other things so haven't got it ready juuuuust yet, don't start goofing with your .cfg/.xml files if people start giving you non-TARGET advice here. You have one of a very few sticks that does not require you to do this (outside of 2 simple lines in .cfg which I will provide in the instructions), and it will make things harder. Standby...

Since you've already downloaded and started messing with TARGET in the meantime though, to increase axis sensitivity is pretty easy actually. Pull up your TARGET script (I assume your using the TARGET GUI) and get into the profile you have started. Select the axis you want to mess with and it gives you parameters to adjust. The one you are interested in is called 'zoom', and increasing the value there increases axis sensitivity.



I tried it out and fixed the problem with the deadzones, but it goes from 0% to 100% instantly, this makes it unaccurate when i aim (when i want to turn a litlle i have to tap it as if it was a button).

Is there a way it will move accordingly to the movement of the joystick? Or should i wait until the game is updated and play with the mouse intead.

#9 evilC

    Member

  • PipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 1,298 posts
  • LocationLondon, UK

Posted 01 February 2013 - 07:21 AM

Whilst I 100% agree with Loc Nar's comment that if you are able to solve your problems using the Thrustmaster software you are probably better off doing so - if you have any problems you should also be able to solve them using my Universal Joystick Remapper.

Edited by evilC, 01 February 2013 - 07:22 AM.


#10 Loc Nar

    Member

  • PipPipPipPipPipPipPipPip
  • 1,132 posts

Posted 01 February 2013 - 01:16 PM

Quote

Is there a way it will move accordingly to the movement of the joystick? Or should i wait until the game is updated and play with the mouse intead


Sorry, didn't have time to finish it up till this morning, but it's ready now.

I still need to make a proper diagram showing the button mapping. You may prefer adjustments to the x/y axis, and that is easy peasy once you have the script up and running, and either I can tell you how to do it or I can just tweak it for you.

When using this stick, your kbm are still active, so you can chat if you like, or grab the mouse at any point if things get too goofy. Here is the diagram with the button mapping:
Posted Image


Installation instructions:

1. Open TARGET Script Editor (not GUI)
2. *click Menu and select 'new' and select TARGET .tmc file and fill in the name blank and click 'open'
3.delete entire contents of the page that comes up, and copypasta the TARGET script below in it's place
4. Save current script (click folder symbol between fwd/back arrows and joystick at upper left)
5. Run script
6. open your MWO user.cfg folder (C:\Games\Piranha Games\MechWarrior Online\user.cfg) with Notepad and add the following 2 lines:
cl_joystick_throttle_range = 0  //fwd/x/reverse
cl_joystick_invert_throttle = 1  //fwd=fwd

7. close notepad/user.cfg and save edits when prompted
8. Open the MWO client and go to Menu>options and scroll down to bottom of 'configure controls' list. (be the controls are set to default at this stage)
9. click the far right cell for Throttle, and move the thottle on the stick to bind that axis, click yes when asked if you want to remap controls and save/exit.
10. Enjoy!






//**************************************************************************
//	  UNOFFICIAL MECHWARRIOR JOYSTICK SUPPORT
//			For the Thrustmaster T16000
//
//
//				  Written by Loc Nar
//	 (http://mwomercs.com/forums/user/190978-loc-nar/)
//
//  MechWarrior Online Joystick -> Mouse/Keyboard override
//
//**************************************************************************
 
include "target.tmh"
int main()
{
Configure(&HCougar, MODE_EXCLUDED);
Configure(&Joystick, MODE_EXCLUDED);
Configure(&Throttle, MODE_EXCLUDED);
Configure(&LMFD, MODE_EXCLUDED);
Configure(&RMFD, MODE_EXCLUDED);
 
if(Init(&EventHandle)) return 1;
 
SetKBRate(32, 50);
SetKBLayout(KB_ENG);
 
////////////////////////////////////////
//////MOVEMENT
////////////////////////////////////////
 
 
//Turning
SetSCurve(&T16000, RUDDER, 0, 10, 0, 0, 0);
KeyAxis(&T16000, RUDDER, 0, AXMAP2( LIST (0, 45, 55),
'a',
0,
'd'
));
 
//JOY Y
MapAxis(&T16000, JOYY, MOUSE_Y_AXIS, AXIS_REVERSED, MAP_RELATIVE);
SetSCurve(&T16000, JOYY, 0, 5, 0, 7, -9);
 
//JOY X
MapAxis(&T16000, JOYX, MOUSE_X_AXIS, AXIS_NORMAL, MAP_RELATIVE);
SetSCurve(&T16000, JOYX, 0, 0, 0, 7, -8);
 
//Throttle
MapAxis(&T16000, THR, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
SetSCurve(&T16000, THR, 0, 10, 0, 0, 0);
 
//Jump Jets/Center Torso
MapKey(&T16000, B9, SPC);
 
////////////////////////////////////////
//////STICK MAPPING
//////////////////////////////////////////Firing Weapons
MapKey(&T16000, TS1, '1'); //Fire Weapon 1
	MapKey(&T16000, H1L, '2'); //Fire Weapon 2
MapKey(&T16000, H1U, '3'); //Fire Weapon 3
MapKey(&T16000, H1R, '4'); //Fire Weapon 4
MapKey(&T16000, H1D, '5'); //Fire Weapon 5
MapKey(&T16000, TS2, '6'); //Fire Weapon 6
//MapKey(&T16000, TS1, '\'); //Alpha
 
 
//Targeting/Toggle ECM
MapKey(&T16000, TS4, PULSE+'r');
//Display Team Info/Toggle Chainfire
MapKey(&T16000, TS3, 'q');////////////////////////////////////////
//////BASE MAPPING, Primary Functions
////////////////////////////////////////
  
	//Freelook
	MapKey(&T16000, B9, L_CTL);
  
	//Heat Vision
	MapKey(&T16000, B10, PULSE+'h');
	
	//Night Vision
	MapKey(&T16000, B5, PULSE+'n');
  
	//Zoom/Advanced Zoom
	MapKey(&T16000, B6, PULSE+'z');
  
	//Jump Jets/Center Torso
	MapKey(&T16000, B7, SPC);
  
//////////////////////////////////
//////Shift Layer Functions
//////////////////////////////////
  
	SetShiftButton(&T16000, B8, 0, 0, 0, 0);
  
	//Firing Weapons
MapKeyIO(&T16000, TS1, USB[0x31], '1');	   //Alpha Strike
  
	//Weapons List Navigation  
MapKeyIO(&T16000, H1L, PULSE+LARROW, '2');	//left arrow
MapKeyIO(&T16000, H1U, PULSE+UARROW, '3');	//up arrow
MapKeyIO(&T16000, H1R, PULSE+RARROW, '4');	//right arrow
MapKeyIO(&T16000, H1D, PULSE+DARROW, '5');	//down arrow
MapKeyIO(&T16000, TS2, PULSE+R_CTL, '6');	 //select/deselect weapons
//Toggle ECM
MapKeyIO(&T16000, TS4, PULSE+'j', PULSE+'r');		   //toggle ECM
MapKeyIO(&T16000, TS3, PULSE+BSP, 'q');	//toggle chainfire
//Advanced Zoom
MapKeyIO(&T16000, B6, PULSE+'v', PULSE+'z');	//advanced zoom//Center Torso
MapKeyIO(&T16000, B7, PULSE+'c', SPC);	//center torso
//Toggle Chainfire
MapKeyIO(&T16000, TS3, PULSE+BSP, 'q');	//toggle chainfire
 
  
/////////////////////////////////////////////////
//////BASE MAPPING. Secondary functions
/////////////////////////////////////////////////
  
	//Power
	MapKey(&T16000, B14, 'p');
  
	//Battlegrid
	MapKey(&T16000, B15, PULSE+'b');
  
	//Toggle Missile Doors
	MapKey(&T16000, B16, PULSE+'/');
  
	//Heat Shutdown Override
	MapKey(&T16000, B13, 'o');
  
	//Scoreboard
	MapKey(&T16000, B12, TAB);
  
	//Cockpit Light
	MapKey(&T16000, B11, PULSE+'.');
  
printf("ALL SYSTEMS NOMINAL!");   }
int EventHandle(int type, alias o, int x)
{
DefaultMapping(&o, x);
}

Edited by Loc Nar, 01 February 2013 - 07:01 PM.


#11 Xustalax

    Member

  • Pip
  • Bad Company
  • 16 posts

Posted 02 February 2013 - 08:56 AM

View PostLoc Nar, on 01 February 2013 - 01:16 PM, said:


Sorry, didn't have time to finish it up till this morning, but it's ready now.

I still need to make a proper diagram showing the button mapping. You may prefer adjustments to the x/y axis, and that is easy peasy once you have the script up and running, and either I can tell you how to do it or I can just tweak it for you.

When using this stick, your kbm are still active, so you can chat if you like, or grab the mouse at any point if things get too goofy. Here is the diagram with the button mapping:
Posted Image


Installation instructions:

1. Open TARGET Script Editor (not GUI)
2. *click Menu and select 'new' and select TARGET .tmc file and fill in the name blank and click 'open'
3.delete entire contents of the page that comes up, and copypasta the TARGET script below in it's place
4. Save current script (click folder symbol between fwd/back arrows and joystick at upper left)
5. Run script
6. open your MWO user.cfg folder (C:\Games\Piranha Games\MechWarrior Online\user.cfg) with Notepad and add the following 2 lines:
cl_joystick_throttle_range = 0  //fwd/x/reverse
cl_joystick_invert_throttle = 1  //fwd=fwd

7. close notepad/user.cfg and save edits when prompted
8. Open the MWO client and go to Menu>options and scroll down to bottom of 'configure controls' list. (be the controls are set to default at this stage)
9. click the far right cell for Throttle, and move the thottle on the stick to bind that axis, click yes when asked if you want to remap controls and save/exit.
10. Enjoy!






//**************************************************************************
//	  UNOFFICIAL MECHWARRIOR JOYSTICK SUPPORT
//			For the Thrustmaster T16000
//
//
//				  Written by Loc Nar
//	 (http://mwomercs.com/forums/user/190978-loc-nar/)
//
//  MechWarrior Online Joystick -> Mouse/Keyboard override
//
//**************************************************************************
 
include "target.tmh"
int main()
{
Configure(&HCougar, MODE_EXCLUDED);
Configure(&Joystick, MODE_EXCLUDED);
Configure(&Throttle, MODE_EXCLUDED);
Configure(&LMFD, MODE_EXCLUDED);
Configure(&RMFD, MODE_EXCLUDED);
 
if(Init(&EventHandle)) return 1;
 
SetKBRate(32, 50);
SetKBLayout(KB_ENG);
 
////////////////////////////////////////
//////MOVEMENT
////////////////////////////////////////
 
 
//Turning
SetSCurve(&T16000, RUDDER, 0, 10, 0, 0, 0);
KeyAxis(&T16000, RUDDER, 0, AXMAP2( LIST (0, 45, 55),
'a',
0,
'd'
));
 
//JOY Y
MapAxis(&T16000, JOYY, MOUSE_Y_AXIS, AXIS_REVERSED, MAP_RELATIVE);
SetSCurve(&T16000, JOYY, 0, 5, 0, 7, -9);
 
//JOY X
MapAxis(&T16000, JOYX, MOUSE_X_AXIS, AXIS_NORMAL, MAP_RELATIVE);
SetSCurve(&T16000, JOYX, 0, 0, 0, 7, -8);
 
//Throttle
MapAxis(&T16000, THR, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
SetSCurve(&T16000, THR, 0, 10, 0, 0, 0);
 
//Jump Jets/Center Torso
MapKey(&T16000, B9, SPC);
 
////////////////////////////////////////
//////STICK MAPPING
//////////////////////////////////////////Firing Weapons
MapKey(&T16000, TS1, '1'); //Fire Weapon 1
	MapKey(&T16000, H1L, '2'); //Fire Weapon 2
MapKey(&T16000, H1U, '3'); //Fire Weapon 3
MapKey(&T16000, H1R, '4'); //Fire Weapon 4
MapKey(&T16000, H1D, '5'); //Fire Weapon 5
MapKey(&T16000, TS2, '6'); //Fire Weapon 6
//MapKey(&T16000, TS1, '\'); //Alpha
 
 
//Targeting/Toggle ECM
MapKey(&T16000, TS4, PULSE+'r');
//Display Team Info/Toggle Chainfire
MapKey(&T16000, TS3, 'q');////////////////////////////////////////
//////BASE MAPPING, Primary Functions
////////////////////////////////////////
  
	//Freelook
	MapKey(&T16000, B9, L_CTL);
  
	//Heat Vision
	MapKey(&T16000, B10, PULSE+'h');
	
	//Night Vision
	MapKey(&T16000, B5, PULSE+'n');
  
	//Zoom/Advanced Zoom
	MapKey(&T16000, B6, PULSE+'z');
  
	//Jump Jets/Center Torso
	MapKey(&T16000, B7, SPC);
  
//////////////////////////////////
//////Shift Layer Functions
//////////////////////////////////
  
	SetShiftButton(&T16000, B8, 0, 0, 0, 0);
  
	//Firing Weapons
MapKeyIO(&T16000, TS1, USB[0x31], '1');	   //Alpha Strike
  
	//Weapons List Navigation  
MapKeyIO(&T16000, H1L, PULSE+LARROW, '2');	//left arrow
MapKeyIO(&T16000, H1U, PULSE+UARROW, '3');	//up arrow
MapKeyIO(&T16000, H1R, PULSE+RARROW, '4');	//right arrow
MapKeyIO(&T16000, H1D, PULSE+DARROW, '5');	//down arrow
MapKeyIO(&T16000, TS2, PULSE+R_CTL, '6');	 //select/deselect weapons
//Toggle ECM
MapKeyIO(&T16000, TS4, PULSE+'j', PULSE+'r');		   //toggle ECM
MapKeyIO(&T16000, TS3, PULSE+BSP, 'q');	//toggle chainfire
//Advanced Zoom
MapKeyIO(&T16000, B6, PULSE+'v', PULSE+'z');	//advanced zoom//Center Torso
MapKeyIO(&T16000, B7, PULSE+'c', SPC);	//center torso
//Toggle Chainfire
MapKeyIO(&T16000, TS3, PULSE+BSP, 'q');	//toggle chainfire
 
  
/////////////////////////////////////////////////
//////BASE MAPPING. Secondary functions
/////////////////////////////////////////////////
  
	//Power
	MapKey(&T16000, B14, 'p');
  
	//Battlegrid
	MapKey(&T16000, B15, PULSE+'b');
  
	//Toggle Missile Doors
	MapKey(&T16000, B16, PULSE+'/');
  
	//Heat Shutdown Override
	MapKey(&T16000, B13, 'o');
  
	//Scoreboard
	MapKey(&T16000, B12, TAB);
  
	//Cockpit Light
	MapKey(&T16000, B11, PULSE+'.');
  
printf("ALL SYSTEMS NOMINAL!");   }
int EventHandle(int type, alias o, int x)
{
DefaultMapping(&o, x);
}



Awesome! thank you very much

#12 Loc Nar

    Member

  • PipPipPipPipPipPipPipPip
  • 1,132 posts

Posted 02 February 2013 - 01:15 PM

Quote

Awesome! thank you very much


You're quite welcome. Once you get it operational with MWO, it is quite easy to further tune it to suit your taste, and without needing.xml/.cfg tweaks! The relevant parameters of the x/y axis are quite easily manipulated in TARGET, and can also be done while your MWO client is running, meaning no need to restart it between adjustments. If you like the axis parameters where they are, even easier, but curve, upper/lower deadzones, and sensitivity are stupid easy to adjust from here so it's no bother if you want to refine it further.

It will even be trivial if you wanted to swap out which axes do what function; like if you wanted stick twist to move your torso aim and roll to turn your legs instead of the arrangement it is now -no problem. This. This is what makes TARGET capable sticks the obvious choice, particularly for things like MWO with no real support...

#13 Hammerhai

    Member

  • PipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 998 posts

Posted 23 February 2013 - 07:11 AM

May I say thank you to Loc Nar for his script. Saved me a ton of research on setting up my Joystick Axes on the warthog. Haven't gotten my head around it yet, but then what did I have a Spectrum back in the day, if not to teach me how to ...script. We called it programming back in the day.
Viva Sinclair basic!

#14 Loc Nar

    Member

  • PipPipPipPipPipPipPipPip
  • 1,132 posts

Posted 24 February 2013 - 03:07 PM

Quote

May I say thank you to Loc Nar for his script.


You are quite welcome, and I will be sure to pass along your thanks to the actual author of that one, Crescent Fresh. Shortly he and I will be posting our scripts up in an easier to access form so others may more easily take advantage of the groundwork already laid.

On the subject of these scripts, I have been working with a complete new script that I haven't translated to a Warthog (T16000 update coming!) version yet but if you are interested I can get it done in pretty short order. It's been simplified in most regards, but made more complex in others. Early on once I found the sensitivity setting that works best I found myself not wanting to change it, except when I'm zoomed but in practice it's a bit fiddly on the Cougar to use the analog pot that sets it, although I'm not sure how practical it is on the Warthog since I do not have one to play with.

My new script does away with the analog adjustability and just by default has the same sensitivity I have found to be juuuust right fixed at that parameter. This allowed me to tie other known/tested sensitivity parameter settings to zoom levels to toggle between, so now when I zoom in once, it automatically bumps the sensitivity down accordingly, and when I zoom again it does the same, and the third time I hit zoom and restore normal zoom levels, the sensitivity likewise returns to normal. I have also tied advanced zoom to the same function, and it is also scaled accordingly.

I'm currently happy with the zoom levels as they really do feel in scale with the change in FOV and overall I am very pleased with this arrangement, but there is one drawback so far that is kinda annoying. Whenever the zoom level changes, it resets the reticule back to 0/0 (center screen). Not a big deal, and it's easy to roughly trim the aim to rough position using the digital aimer functions (china hat or d-pad) and to get to the range for using the stick for fine tune aiming, but once I adapted to this tendency it wasn't too difficult to plan accordingly. In practice, range sniping just got a lot easier with a stick. This same functionality would also be very useful for those who use mouse if an emulator like Evil C's emulator or some other autohotkey solution were applied.

There are more additions as well, since I use a shift layer on mine to control secondary functions like weapons list navigation using primary buttons on my stick. Makes it super easy to setup new loadouts exactly how I want them mapped, even while running at full speed. I used to just use the keyboard, but this is much easier. I also have torso centering, comm/ptt, battlegrid, etc on the shift layer, but it's actually very intuitive to use despite sounding complicated.

#15 GROG13

    Member

  • PipPip
  • Legendary Founder
  • Legendary Founder
  • 20 posts
  • LocationSomewhere in Arizona

Posted 25 February 2013 - 07:03 PM

Wow you guys are on the ball here. I tried the TARGET software but it does not support the T flight HOTAS
which is also bereft of any software ;) any ideas for an old Mech pilot who needs his JS to work(numb left hand)

#16 evilC

    Member

  • PipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 1,298 posts
  • LocationLondon, UK

Posted 26 February 2013 - 03:43 AM

View PostGROG13, on 25 February 2013 - 07:03 PM, said:

Wow you guys are on the ball here. I tried the TARGET software but it does not support the T flight HOTAS
which is also bereft of any software :lol: any ideas for an old Mech pilot who needs his JS to work(numb left hand)

What do you need to do?
If you need to invert an axis and cannot do it through editing of game config files, UJR will let you invert the axis.

#17 GROG13

    Member

  • PipPip
  • Legendary Founder
  • Legendary Founder
  • 20 posts
  • LocationSomewhere in Arizona

Posted 26 February 2013 - 06:00 PM

I tried that prog and my comp didn't like it(damn windows 7/Vista) had to run in test mode(ran wierd)I will try it again and PM you
Sry to jack your thread Xustalax.
GROG OUT





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users