hi,
how did you did it? straight in the game or using TARGET?
also, what were the buttons you assigned them to on your Warthog?
if you press the target next/previous shiip corresponding keyboard keys, does it works?
Community Event / Creation Thrustmaster Warthog Configuration & Sheets
- Thread starter MikeyTT
- Start date
hi,
how did you did it? straight in the game or using TARGET?
also, what were the buttons you assigned them to on your Warthog?
if you press the target next/previous shiip corresponding keyboard keys, does it works?
Just completed the "fun" task of configuring my Warthog with Target script.
I now have "power profiles" defined for all possible S/E/W settings, with bingings assigned on the throttle keys for my favourites, "Guns Up", "Head to Head", "I smell Blood", and "Brace for Impact".
I've also set the flaps switch to change between a "full range" and "forward only" throttle, using custom curves and AXMAP stuff.
Happy to upload these somewhere if anyone is interested (and I can figure out how)
... and yes, today I have a lot of spare speech mark to throw into posts randomly.
I now have "power profiles" defined for all possible S/E/W settings, with bingings assigned on the throttle keys for my favourites, "Guns Up", "Head to Head", "I smell Blood", and "Brace for Impact".
I've also set the flaps switch to change between a "full range" and "forward only" throttle, using custom curves and AXMAP stuff.
Happy to upload these somewhere if anyone is interested (and I can figure out how)
... and yes, today I have a lot of spare speech mark to throw into posts randomly.
TARGET profile
Hi MikeyTT,
I've just read carefully this thread and first of all many thanks for sharing your Warthog experience with the community. May I request a favor, I don't see any link available to download your TARGET GUI file (.fcf). As a newbie it would pretty handy to me to use your good job.
I'd be so grateful for that.
Regards
Hi MikeyTT,
I've just read carefully this thread and first of all many thanks for sharing your Warthog experience with the community. May I request a favor, I don't see any link available to download your TARGET GUI file (.fcf). As a newbie it would pretty handy to me to use your good job.
I'd be so grateful for that.
Regards
Hi MikeyTT,
I've just read carefully this thread and first of all many thanks for sharing your Warthog experience with the community. May I request a favor, I don't see any link available to download your TARGET GUI file (.fcf). As a newbie it would pretty handy to me to use your good job.
I'd be so grateful for that.
Regards
That file is linked to in the op, along with the custom binds file and 2 PNG files, all dated 23/12/14.
I've just purchased ED, awesome game, and glad I can make use of my Warthog again! It has been collecting dust for too long. This setup with TARGEt makes things pretty easy too, being able to print off PDF's of layouts.
Thanks for that MikeyTT.
EDIT: links are updated and I have a .zip to my public dropbox folder for the bindings.
EDIT2: I have updated information on how to use the different layers UPM and the O/I input options and I now highly recommend using AutoHotKey as your primary macro creator as it is much easier to test and setup. I have not edited the .png files or the macros yet.
Hi MikeyTT and others.
Thank you so much for this thread and for all the work put into it. I have now spent 5 hours experimenting with target finally and though I would add some of my experiences to assist newcomers to a much better TARGET experience, hopefully only spending 2 hours in setup instead.
I am using a Warthog HOTAS with no rudders with my yaw setting set to the thumb button on the joystick (specifically H4L = DX18
and H4R = DX16; this makes precision aiming very easy and all steering is focused on the same hand-coordination stick).
Here's a link to my bindings and configurations based on MikeyTT's OP post: https://dl.dropboxusercontent.com/u/20306/ED-bindings.zip
As always:
.binds files go to \Users\Username\AppData\Local\Frontier Developments\Options\Bindings\
(hidden folder, access it through copy-pasting the in the explorer filepath)
.fcf file you can put where ever, though I suggest in your documents or something (oh, remember to copy it and rename it to something personal for your own bindings so you have both files available).
Joystick bindings PNG:
Throttle bindings PNG;
A checklist to make as few errors as possible with the overall TARGET experience:
1. Download and install the TARGET GUI: http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_v1.0.exe
2. Download Mikeys Warthog profile, custom.binds and warthogtarget_v.fcf
3. Make sure that you have set up your non-target bindings and rename the custom.binds within c:\Users\USERNAME’\AppData\Frontier Developments\Elite Dangerous\Options\Bindings’ (AppData is hidden so you need to click the address bar in Explorer) to your own config, for example Warthog_No_Target.binds. This circumvents any unforeseen problems you would encounter if the custom.binds for some odd reason gets deleted or is changed.
4. Launch the TARGET GUI (make sure that Elite is not running)
5. Run the Target Script and launch Elite.
Elite Dangerous will immediately not recognize your HOTAS (simply removing it from the preset configuration list in the game -—> options --> controls). Open up the ‘empty’ configuration and start map the bindings to keyboard keys (those that you set up in Target) and using button presses (all bindings that work fine without having to be mapped to keyboard keys).
6. Test your setup and go back to bullet 4, 5 and 6. When it works and while your Target script is running, go to ‘c:\Users\USERNAME’\AppData\Frontier Developments\Elite Dangerous\Options\Bindings’ and rename the new custom.binds to your own liking, e.g. WarthogTarget.binds. This will ensure that if you forget to launch the Target script for whatever reason, Elite will default to Warthog_No_Target.binds and not leaving your controls be messed up. NOTE: DO NOT MULTITASK OUT OF ELITE AND STOP THE SCRIPT! IT WILL CAUSE ELITE PROBLEMS WHEN YOU MULTITASK BACK TO ELITE AND YOUR TARGET PROFILE AND KEY BINDINGS WILL BE CORRUPTED. Always shut down Elite before editing your TARGET configuration. Slow, but necessary.
Setting up events
Associating custom key presses to new events is done by locating the button on the throttle or joystick representation on the left side of the edit configuration screen (you have to press ‘next’ twice to get there):
1. Double-click the button and you will be sent to the event editor.
2. Name the Event you want the button associated with (e.g. Extract Landing Gear) and associate a keyboard key or a DX value. You cannot add an event before this is done.
3. Press ‘add event’. You will now see the button value pop up in the right- most column of the GUI.
4. Add more keypresses if you want the button event to do more. Note that all keypresses will activate simultaneously and you should set a delay (between 75-100 ms) between each keypress. (I have not experimented with the "sequence" mode yet, so if you find out if or how that works, please post here asap ). I highly recommend to stay completely clear of using the Target software for actual button press macros. Instead, map your desired macro to a key button and make an AutoHotKey script to care care of the advanced macros (such as docking sequences or creating text to role play). I will give out more detail later for how to make this work.
5. Use ‘pulse’ for a single click, ‘hold’ for simulating holding the key down, ‘release’ for release said button (should be mapped to a new button on the throttle or joystick). DO NOT USE ‘PRESS’ SINCE IT WON’T WORK. Also do not confuse this with the ‘press’ and ‘release’ below the ‘layers’ headline. These simply determine the timing of when the event will be fired (on ‘pressing’ the button or on ‘releasing’ the button). I recommend simply using ‘press’ timing like MikeyTTs configuration.
6. Note on setting the layer to ‘I’ (IN) or ‘O’ (OUT) or the UPM layers: This is in the event that you have many more macros or events mapped on the same buttons. By default, when you press the Joystick Pinky button (S4 = DX4, default set to Flight Assist) the TARGET software will automatically interpret all other presses to activate on releasing the Pinky button (all buttons set to the ‘O’ layer). This is important because if you have set the FA pinky button to ‘hold’ this will cause issues. Make sure to remove or set a non-used button to activate the I/O layer instead. I have personally (not in the explained setup) set the SPDB button to 'hold' on the U layer to make room for additional PWR settings macros and subsystems cycle macros.
If you plan to use MikeyTTT's or my own (now deprecated) settings, make sure to delete/remove the [O] in front of each event you configure. This is important because you may experience that if you press any trigger set to an [O] event while also holding the default S4 button, the events will not fire. However, they will fire if you click the 'I' in the layer twice and save the event afterwards.
7. Make sure to set as many buttons to key button presses, especially when they are non-macro or non-throttle related events (see below). However, with the exception of the TG1 button (joystick trigger set to DX1). If the TG1 button is set to a keyboard click you will not be able to select items in the UI Panels in the spacecraft, since TARGET will override Elite’s settings. See the description of DX values below for more info.
8. When creating macros, for the love of all that is good and mighty: use AutoHotKey for these macros. It is easier it means that you have to set most buttons on the Warthog to keyboard buttons and setting these up in Elite but once you have done this you can simply multitab to the AutoHotKey script from Elite, edit it and reload it to test your macros. If you write your macros directly in Target you have to save and exit Elite (which is really CUMBERSOME).
Setting up DX keys
I have had to use the following forum post for more information on the key mappings:
http://simhq.com/forum/ubbthreads.php/topics/3429294/New_Warthog?_Here's_the_TARGET
The forum post is fairly script centric but the most important part here is the values put in quotes below, since you will need them. Note that the DX values are the same for the JOYSTICK and the THROTTLE and Elite will misunderstand this if you map all throttle and joystick non-macro events to DX values. You will have to map ONLY DX values to the joystick buttons and leave keyboard key values to all Throttle-related events, macro or not.
Use the values below to know which values correspond to which button. It is important to know both the Button name and DX value for those bindings that you will use in Elite for macro purposes. This means that the ‘Trim Control’ top hat (H1 buttons) can be left non-mapped in Target and manually mapped in Elite with no consequences, but e.g. the trigger button TG1 will have to be set to DX1 value to work in a macro with Target, and so forth.
My Macros (old setup without using AutoHotKey)
I have configured the following macros:
a. Request docking - LDGH
1. switch to target panel (designated key press)
2. switch to right tab twice (DX4 x 2 with 100 ms delay between each)
3. select first target (DX1, 300 ms delay)
4. request docking (DX1, 400 ms delay)
5. switch to left tab twice (LARROW x 2 with 100 ms delay between each, starting a 500ms)
6. deselect UI focus (S2 = DX2 in my case)
Note that the last three macro events are set this way to go back to the navigation tab in the target panel to make sure that it fires correctly all the time. You also need to make sure that you do not deselect UI focus with another tab active as the macro will do funny stuff in this case.
b. Toggle landing gear - PSF, PSM, PSB
The landing gear is the only setting that does not respond to "hold" and "release" events so far. This means that for it to work properly you will have to live with assigning it to a two-stick switch, like APENG or APUON/APUOFF. However, I want to have landing gear and full shield pips immediately so I am not accidentally surprised in the entrance, though I also want to differ and have full Engine pips when taking off from outposts. This effectively requires a three-setting switch like the PSM, PSP and PSM switch:
PSB event (for landing at stations):
1. toggle landing gear (pulse on keypress assigned to landing gear - ‘l’).
2. activate LED (they are cool but not visible due to the throttle, darn it).
3. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
4. 2 pips in shield (DX14 x 2 with 100ms delay between)
PSF event (for taking off from outposts):
1. toggle landing gear (pulse on keypress assigned to landing gear - ‘l’).
2. activate LED (they are cool but not visible due to the throttle, darn it).
3. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
4. 2 pips in engines (DX11 x 2 with 100ms delay between)
PSM event (for deactivating landing gear from any station or outpost, needs pips in shield in case takeoff is from a station):
1. toggle landing gear (pulse on keypress assigned to landing gear - ‘l’).
2. activate LED (they are cool but not visible due to the throttle, darn it).
3. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
4. 2 pips in shield (DX14 x 2 with 100ms delay between)
c. deactivate thrusters - SPDB
When smuggling or needing to ice up your ship, I need a macro for quickly turning off/on thrusters in case I drift to far when entering the station and need to correct or adjust the approach vector:
1. select UI systems panel (assigned keypress)
2. switch to right tab once (DX4 with 100 ms delay)
3. toggle thrusters (DX1 with 200ms delay)
3. switch back to left tab once (LARROW with 300 ms delay)
4. deselect UI focus (S2 = DX2 in my case)
d. engines to full - APPAT
1. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
2. 2 pips in engines (DX11 x 2 with 100ms delay between)
e. shields UP - APALT
1. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
2. 2 pips in shield (DX14 x 2 with 100ms delay between)
e. power distribution balanced - APAH
1. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
PS: this post is written on my working computer and as such I do not have the config files or binds files, though I will link to these ASAP if you’re interested. However, due to forum rules about newcomers not being able to link to files I think this is pretty much impossible
EDIT2: I have updated information on how to use the different layers UPM and the O/I input options and I now highly recommend using AutoHotKey as your primary macro creator as it is much easier to test and setup. I have not edited the .png files or the macros yet.
Hi MikeyTT and others.
Thank you so much for this thread and for all the work put into it. I have now spent 5 hours experimenting with target finally and though I would add some of my experiences to assist newcomers to a much better TARGET experience, hopefully only spending 2 hours in setup instead.
I am using a Warthog HOTAS with no rudders with my yaw setting set to the thumb button on the joystick (specifically H4L = DX18
and H4R = DX16; this makes precision aiming very easy and all steering is focused on the same hand-coordination stick).
Here's a link to my bindings and configurations based on MikeyTT's OP post: https://dl.dropboxusercontent.com/u/20306/ED-bindings.zip
As always:
.binds files go to \Users\Username\AppData\Local\Frontier Developments\Options\Bindings\
(hidden folder, access it through copy-pasting the in the explorer filepath)
.fcf file you can put where ever, though I suggest in your documents or something (oh, remember to copy it and rename it to something personal for your own bindings so you have both files available).
Joystick bindings PNG:
A checklist to make as few errors as possible with the overall TARGET experience:
1. Download and install the TARGET GUI: http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_v1.0.exe
2. Download Mikeys Warthog profile, custom.binds and warthogtarget_v.fcf
3. Make sure that you have set up your non-target bindings and rename the custom.binds within c:\Users\USERNAME’\AppData\Frontier Developments\Elite Dangerous\Options\Bindings’ (AppData is hidden so you need to click the address bar in Explorer) to your own config, for example Warthog_No_Target.binds. This circumvents any unforeseen problems you would encounter if the custom.binds for some odd reason gets deleted or is changed.
4. Launch the TARGET GUI (make sure that Elite is not running)
5. Run the Target Script and launch Elite.
Elite Dangerous will immediately not recognize your HOTAS (simply removing it from the preset configuration list in the game -—> options --> controls). Open up the ‘empty’ configuration and start map the bindings to keyboard keys (those that you set up in Target) and using button presses (all bindings that work fine without having to be mapped to keyboard keys).
6. Test your setup and go back to bullet 4, 5 and 6. When it works and while your Target script is running, go to ‘c:\Users\USERNAME’\AppData\Frontier Developments\Elite Dangerous\Options\Bindings’ and rename the new custom.binds to your own liking, e.g. WarthogTarget.binds. This will ensure that if you forget to launch the Target script for whatever reason, Elite will default to Warthog_No_Target.binds and not leaving your controls be messed up. NOTE: DO NOT MULTITASK OUT OF ELITE AND STOP THE SCRIPT! IT WILL CAUSE ELITE PROBLEMS WHEN YOU MULTITASK BACK TO ELITE AND YOUR TARGET PROFILE AND KEY BINDINGS WILL BE CORRUPTED. Always shut down Elite before editing your TARGET configuration. Slow, but necessary.
Setting up events
Associating custom key presses to new events is done by locating the button on the throttle or joystick representation on the left side of the edit configuration screen (you have to press ‘next’ twice to get there):
1. Double-click the button and you will be sent to the event editor.
2. Name the Event you want the button associated with (e.g. Extract Landing Gear) and associate a keyboard key or a DX value. You cannot add an event before this is done.
3. Press ‘add event’. You will now see the button value pop up in the right- most column of the GUI.
4. Add more keypresses if you want the button event to do more. Note that all keypresses will activate simultaneously and you should set a delay (between 75-100 ms) between each keypress. (I have not experimented with the "sequence" mode yet, so if you find out if or how that works, please post here asap
). I highly recommend to stay completely clear of using the Target software for actual button press macros. Instead, map your desired macro to a key button and make an AutoHotKey script to care care of the advanced macros (such as docking sequences or creating text to role play). I will give out more detail later for how to make this work. 5. Use ‘pulse’ for a single click, ‘hold’ for simulating holding the key down, ‘release’ for release said button (should be mapped to a new button on the throttle or joystick). DO NOT USE ‘PRESS’ SINCE IT WON’T WORK. Also do not confuse this with the ‘press’ and ‘release’ below the ‘layers’ headline. These simply determine the timing of when the event will be fired (on ‘pressing’ the button or on ‘releasing’ the button). I recommend simply using ‘press’ timing like MikeyTTs configuration.
6. Note on setting the layer to ‘I’ (IN) or ‘O’ (OUT) or the UPM layers: This is in the event that you have many more macros or events mapped on the same buttons. By default, when you press the Joystick Pinky button (S4 = DX4, default set to Flight Assist) the TARGET software will automatically interpret all other presses to activate on releasing the Pinky button (all buttons set to the ‘O’ layer). This is important because if you have set the FA pinky button to ‘hold’ this will cause issues. Make sure to remove or set a non-used button to activate the I/O layer instead. I have personally (not in the explained setup) set the SPDB button to 'hold' on the U layer to make room for additional PWR settings macros and subsystems cycle macros.
If you plan to use MikeyTTT's or my own (now deprecated) settings, make sure to delete/remove the [O] in front of each event you configure. This is important because you may experience that if you press any trigger set to an [O] event while also holding the default S4 button, the events will not fire. However, they will fire if you click the 'I' in the layer twice and save the event afterwards.
7. Make sure to set as many buttons to key button presses, especially when they are non-macro or non-throttle related events (see below). However, with the exception of the TG1 button (joystick trigger set to DX1). If the TG1 button is set to a keyboard click you will not be able to select items in the UI Panels in the spacecraft, since TARGET will override Elite’s settings. See the description of DX values below for more info.
8. When creating macros, for the love of all that is good and mighty: use AutoHotKey for these macros. It is easier it means that you have to set most buttons on the Warthog to keyboard buttons and setting these up in Elite but once you have done this you can simply multitab to the AutoHotKey script from Elite, edit it and reload it to test your macros. If you write your macros directly in Target you have to save and exit Elite (which is really CUMBERSOME).
Setting up DX keys
I have had to use the following forum post for more information on the key mappings:
http://simhq.com/forum/ubbthreads.php/topics/3429294/New_Warthog?_Here's_the_TARGET
The forum post is fairly script centric but the most important part here is the values put in quotes below, since you will need them. Note that the DX values are the same for the JOYSTICK and the THROTTLE and Elite will misunderstand this if you map all throttle and joystick non-macro events to DX values. You will have to map ONLY DX values to the joystick buttons and leave keyboard key values to all Throttle-related events, macro or not.
Use the values below to know which values correspond to which button. It is important to know both the Button name and DX value for those bindings that you will use in Elite for macro purposes. This means that the ‘Trim Control’ top hat (H1 buttons) can be left non-mapped in Target and manually mapped in Elite with no consequences, but e.g. the trigger button TG1 will have to be set to DX1 value to work in a macro with Target, and so forth.
My Macros (old setup without using AutoHotKey)
I have configured the following macros:
a. Request docking - LDGH
1. switch to target panel (designated key press)
2. switch to right tab twice (DX4 x 2 with 100 ms delay between each)
3. select first target (DX1, 300 ms delay)
4. request docking (DX1, 400 ms delay)
5. switch to left tab twice (LARROW x 2 with 100 ms delay between each, starting a 500ms)
6. deselect UI focus (S2 = DX2 in my case)
Note that the last three macro events are set this way to go back to the navigation tab in the target panel to make sure that it fires correctly all the time. You also need to make sure that you do not deselect UI focus with another tab active as the macro will do funny stuff in this case.
b. Toggle landing gear - PSF, PSM, PSB
The landing gear is the only setting that does not respond to "hold" and "release" events so far. This means that for it to work properly you will have to live with assigning it to a two-stick switch, like APENG or APUON/APUOFF. However, I want to have landing gear and full shield pips immediately so I am not accidentally surprised in the entrance, though I also want to differ and have full Engine pips when taking off from outposts. This effectively requires a three-setting switch like the PSM, PSP and PSM switch:
PSB event (for landing at stations):
1. toggle landing gear (pulse on keypress assigned to landing gear - ‘l’).
2. activate LED (they are cool but not visible due to the throttle, darn it).
3. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
4. 2 pips in shield (DX14 x 2 with 100ms delay between)
PSF event (for taking off from outposts):
1. toggle landing gear (pulse on keypress assigned to landing gear - ‘l’).
2. activate LED (they are cool but not visible due to the throttle, darn it).
3. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
4. 2 pips in engines (DX11 x 2 with 100ms delay between)
PSM event (for deactivating landing gear from any station or outpost, needs pips in shield in case takeoff is from a station):
1. toggle landing gear (pulse on keypress assigned to landing gear - ‘l’).
2. activate LED (they are cool but not visible due to the throttle, darn it).
3. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
4. 2 pips in shield (DX14 x 2 with 100ms delay between)
c. deactivate thrusters - SPDB
When smuggling or needing to ice up your ship, I need a macro for quickly turning off/on thrusters in case I drift to far when entering the station and need to correct or adjust the approach vector:
1. select UI systems panel (assigned keypress)
2. switch to right tab once (DX4 with 100 ms delay)
3. toggle thrusters (DX1 with 200ms delay)
3. switch back to left tab once (LARROW with 300 ms delay)
4. deselect UI focus (S2 = DX2 in my case)
d. engines to full - APPAT
1. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
2. 2 pips in engines (DX11 x 2 with 100ms delay between)
e. shields UP - APALT
1. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
2. 2 pips in shield (DX14 x 2 with 100ms delay between)
e. power distribution balanced - APAH
1. reset power pips (quick way to move pips to default and set to joystick DMS - H3D = DX13)
PS: this post is written on my working computer and as such I do not have the config files or binds files, though I will link to these ASAP if you’re interested. However, due to forum rules about newcomers not being able to link to files I think this is pretty much impossible
Last edited:
I use the speed break switch for throttle reverse. Forward (locking) to keep in reverse, pull back (momentary) to act like a speed break.
Have boost/FSD on the red throttle button. Short press for boost, long press for FSD. Throttle pinky switch changes the FSD mode from hyperspace, standard (i.e. depending on destination) and cruise.
Crash to desktop when key binding
Hi all and firstly, big thanks to Mikey for the good work!
Now a cry for help....I've been trying to get this procedure cracked and am following the text and Mikey's video to every last detail, yet for some reason I cannot work out, each time i start to keybind in ED itself after loading the script in TARGET, ED crashes to desktop. Doesnt matter which key i try to bind, every sigle time it crashes. I can select the keybind I want, but as soon as I press the buttin or switch on the Warthog, I crash.
Keybinding without TARGET running is no problem. I have set all required programs to run as admin but no luck.
I'm probably doing something obvious wrong, I've scoured the forums for advice but no one else seems to be experiencing this same issue. I would be grateful for any of your input on this.
I know that plain keybinding is still great with the Warthog and I'm loving that. I would just like to add the extra finesse of not having to double tap switches for certain functions.
Hope someone can help,
Thanks once again!
Hi all and firstly, big thanks to Mikey for the good work!
Now a cry for help....I've been trying to get this procedure cracked and am following the text and Mikey's video to every last detail, yet for some reason I cannot work out, each time i start to keybind in ED itself after loading the script in TARGET, ED crashes to desktop. Doesnt matter which key i try to bind, every sigle time it crashes. I can select the keybind I want, but as soon as I press the buttin or switch on the Warthog, I crash.
Keybinding without TARGET running is no problem. I have set all required programs to run as admin but no luck.
I'm probably doing something obvious wrong, I've scoured the forums for advice but no one else seems to be experiencing this same issue. I would be grateful for any of your input on this.
I know that plain keybinding is still great with the Warthog and I'm loving that. I would just like to add the extra finesse of not having to double tap switches for certain functions.
Hope someone can help,
Thanks once again!
Apologies for not monitoring this thread as much as I should have. I've not been playing ED, since I created the video and updated the bindings in December, so I've not really found any of the issues myself. And for some reason the forum reset my thread notification, so I wasn't getting emails; just figured the thread was dead anyway ;-)
My better half is out all Sunday, so I'll have a look through the bindings and double check that they are correct. Looks like there have been a few updates since the launch in Dec, so I'll check all is still well with the control bindings.
If anyone is still experiencing any issues then please post up and I'll actually respond this time ;-)
- - - - - Additional Content Posted / Auto Merge - - - - -
My system is Win 8.1 64-bit and I've never had any issues with the target software itself. So I'd say give it a try, compared with the default config FD provides and you can decide which suits you best...
My better half is out all Sunday, so I'll have a look through the bindings and double check that they are correct. Looks like there have been a few updates since the launch in Dec, so I'll check all is still well with the control bindings.
If anyone is still experiencing any issues then please post up and I'll actually respond this time ;-)
- - - - - Additional Content Posted / Auto Merge - - - - -
My system is Win 8.1 64-bit and I've never had any issues with the target software itself. So I'd say give it a try, compared with the default config FD provides and you can decide which suits you best...
Sounds like there is some fairly big gremlin in your system. It's an old bit of advise, but I would uninstall the target software, reboot and re-install it to start with. Might be worth trying one of the free flying games to make sure that the target software is working, like World of Warplanes. It's a bit basic for the warthog, but with target running, see if you can bind controls in that. If you can then you know it's likely to be an ED problem.
Might be worth doing an uninstall/reinstall on ED if the problems persist. Would also be worth renaming the "C:\Users\%username%\AppData\Local\Frontier Developments\Elite Dangerous" folder temporarily to see if that fixes the control binding issue.
If you wanted to PM me I'll give you my email address and you can send them over if you wanted. When I check stuff over on Sunday I'll see if I can integrate the macros too, or at least provide an optional target profile with the macros in.
Mike...
Hi MikeyTT,
you have the blank chart for the joystick twice and have no link for the blank throttle chart.
I found it, it's at http://www.tr7v8.com/elite_dangerous/Elite Dangerous - Thrustmaster Warthog Chart - Throttle.png
Could you update your post?
I'm using MikeyTT's setup now, thanks a lot for that proposal.
I made the following minor changes:
1. I use "UI back" a lot! It is a big timesaver when you are in long menus such as the market and want to get out. I mapped it to button 19 (depress CMS on joystick) and use button 1 for "UI select". It's possible to map "UI select" to a button that is already mapped for something else (i.e. in this case, "fire primary weapon") without problems.
2. The configuration was missing the "switch hard points group" or whatever that is called exactly. I put it on the throttle on button "push" mic switch (button 2 according to the gif).
I made the following minor changes:
1. I use "UI back" a lot! It is a big timesaver when you are in long menus such as the market and want to get out. I mapped it to button 19 (depress CMS on joystick) and use button 1 for "UI select". It's possible to map "UI select" to a button that is already mapped for something else (i.e. in this case, "fire primary weapon") without problems.
2. The configuration was missing the "switch hard points group" or whatever that is called exactly. I put it on the throttle on button "push" mic switch (button 2 according to the gif).
Thanks MikeyTT, reinstall of target did the trick!
Hi guys! Thank you so much MikeyTT without you i would not have bought the thrustmaster warthog or even gotten it to work! Anyway... I have the same problem as the guy I quoted. But ive switched from USB port 2.0 to 1.0, and nothing is happening. I still flip a switch and for exactly 5 miliseconds the damn thing wont work. Joystick or thruster. It is more like 5046 miliseconds or something. I checked in the event tester and that confirmed it. I just dont know how to fix it. Any suggestions?
Yours truly, xod
Good spot. That's what copy and paste gets you ;-)
I've updated it now tho, so you should see both throttle and joystick blank sheets.
Kewl.
Glad you kept an eye on the thread (seeing as I did spent much of my afternoon writing my post). Do feel free to link or quote it in the OP post.
Ok, so seeing that many of you have PM'ed me to send you my customizations, I will make sure that they come online asap.
In the meantime I have just ordered and received an EDtracker from edtracker.org.uk and it works amazingly. Now I have more buttons free to do what I want, which begs the question of asking you guys for advice on new bindings for boat switch buttons (BSB, BSM and BSF)?
In the meantime I have just ordered and received an EDtracker from edtracker.org.uk and it works amazingly. Now I have more buttons free to do what I want, which begs the question of asking you guys for advice on new bindings for boat switch buttons (BSB, BSM and BSF)?
Last edited: