Release Aussiedroid's Enhanced Thrustmaster Warthog Script

[Aussiedroid]

Hey MRated,

UPDATE for VA issue:

I checked the default mapping in VA and it seems to be mapped now to ALT+F2. Could you please confirm if this is/was the same at your end?

Also, looking into the VA manual, I can see there is a checkbox in the Global Hotkey screen which says 'Do not allow key to be passed through'. If this is selected, then any key used in a modifier sequence like ALT+V will not be passed through to VA profile. That should prevent Heatsink firing in the short term. This seems to be disabled by default my end, which is odd for a Global Hotkey.

What I would also recommend if ALT+F2 is/was mapped at your end is to change this in the EDKeyMap file:

[COLOR=#1e90ff][B]define[/B][/COLOR] ToggleVoiceAttackGlobal                 L_ALT[COLOR=#ffffff]+[/COLOR]USB[COLOR=#ffffff][[/COLOR][COLOR=#ffffff]0x19[/COLOR]]            [COLOR=#32cd32]// ALT+V

[/COLOR]To:

[COLOR=#1e90ff][B]define[/B][/COLOR] ToggleVoiceAttackGlobal                 L_ALT[COLOR=#ffffff]+[/COLOR]USB[COLOR=#ffffff][[/COLOR][COLOR=#ffffff]0x3B[/COLOR]]            [COLOR=#32cd32]// ALT+F2[/COLOR]

If all works, I will update this to the default key in my next update, so people do not need to mess around with it.


EDIT UPDATE 2 for Rift:

For the Rift centering mapping, I believe the default key used in the Rift software is F12. This conflicts with Steam Screenshots, so was updated in the script to CTRL+HOME.

If you only updated the ED Bindings in game back to F12, then this will mis-map in the script as this will still reflect CTRL+HOME and not work via the HOTAS.

2 Options to resolve this for you; one is to remap ED Bindings back to CTRL+HOME and then update this in the Rift software to align accordingly. Two, is to change the mapping in the script to F12 (assuming you do not use Steam). To note, if you do change to F12, you will need to update this manually in future updates you download, but this will also allow the Steam Screenshot button to double as the Center key for you as well, which may be a handy alternative to the toggle.

This mapping can also be found in the EDKeyMap file. The value to change is:

[COLOR=#1e90ff][B]define[/B][/COLOR] ResetHeadOrientation                 L_CTL[COLOR=#ffffff]+[/COLOR]USB[COLOR=#ffffff][[/COLOR][COLOR=#ffffff]0x4A[/COLOR]]         [COLOR=#32cd32]// CTRL+HOME[/COLOR]

To:

[COLOR=#1e90ff][B]define[/B][/COLOR] ResetHeadOrientation                 USB[COLOR=#ffffff][[/COLOR][COLOR=#ffffff]0x45[/COLOR]]               [COLOR=#32cd32]// F12[/COLOR]

Which ever way you choose to go, this should align the mappings across all profiles/scripts/programs.

Let us know how you go!

Cheers,
AD

 

[whisper2shade]

Hi,
first of all, mega awesome script and bindings, though after doing a brand new installation of the 2.4.3 version, my galaxy map button doesn't work at all and system map only half of the time. It worked perfectly in 2.4.1.
I tried to rebind it in elite just to check if the binding wasn't off, but it was correct. Though still, it doesn't work at all.
Another issue i have is the docking request... it works maybe 15% of the time even though i am on the first creen of the left panel all of the time.

Thanks

 

[Aussiedroid]

Hey whisper2shade! Thank you very much!

Hmm, that is some strange behavior. Both of the buttons you are having issues with haven't been changed since 2.4.1.

Firstly, if you haven't already tried, I would generally recommend a shutdown of the PC, do a full restart & reload the profiles (just in case it didn't initialise correctly). Go into ED & Apply the 2.4.3 bindings as well after you select them.

Before you get into ED though, are you seeing anything trigger when you view the button presses in Event Viewer? You should see a single keypress for the galaxy/system maps & a macro sequence fire for the autopilot (on long or short presses). If this is triggering then it should indicate the script is running correctly, and may point towards the bindings file not loading/applying properly in ED.

Could also try clearing the galaxy/system binds, then rebinding again in ED & save/retest.

Is everything else working ok when testing it out?

Cheers,
AD

 

[whisper2shade]

Hey whisper2shade! Thank you very much!

Hmm, that is some strange behavior. Both of the buttons you are having issues with haven't been changed since 2.4.1.

Firstly, if you haven't already tried, I would generally recommend a shutdown of the PC, do a full restart & reload the profiles (just in case it didn't initialise correctly). Go into ED & Apply the 2.4.3 bindings as well after you select them.

Before you get into ED though, are you seeing anything trigger when you view the button presses in Event Viewer? You should see a single keypress for the galaxy/system maps & a macro sequence fire for the autopilot (on long or short presses). If this is triggering then it should indicate the script is running correctly, and may point towards the bindings file not loading/applying properly in ED.

Could also try clearing the galaxy/system binds, then rebinding again in ED & save/retest.

Is everything else working ok when testing it out?

Cheers,
AD

This is my analyzer output:

Key Press: LSHF
Key Press: ;
Key Release: ;
Key Release: LSHF
Key Press: BSP
Key Release: BSP
Key Press: ;
Key Release: ;

For the map button (forward, mid and back). They look alright, but still the galaxy map doesn't work in game for some reason.

The autodock macro is a bit bigger, but it shows up in the event viewer as well.

 

[whisper2shade]

Addendum: Not even the keyboard shortcut works. But when i double-click the keyboard shortcut it opens the galaxy map: Shift + twice the ; in quick succession.

 

[Aussiedroid]

Ok, it looks like the script and Warthog are firing the buttons correctly, but it is not registering this in the game. This is pointing to the bindings file being the root cause here, especially considering that direct key presses didn't work either; this suggests that the mappings are not aligned/working in ED.

Could you confirm if you tried remapping the galaxy & system map buttons in ED? Just remove the existing mappings by selecting and pressing ESC, then remap these to ';' and ':' accordingly - save and retest. It seems to me that these are not triggering even though they are mapped (both HOTAS and KB direct), so a fresh remapping may resolve the issue. Alternative to try would be to delete the existing file in the bindings folder and re-download a fresh one in case there is something corrupted in the binding file.

Let us know how you get on

 

[drag0nfire]

Hi. New to ED and to the Warthog. I can't believe all the work that's been put into this script, it looks incredible. I've been trying to get it up and running, but I keep getting an error message in the TARGET script editor. Wondering if any one else has seen anything similar, hope I'm not missing something obvious.

Running script: AD_ED_v2.4.3.tmc
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
Errorinternal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0404"
Errorinternal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0402"
USB HID device with hardware id "VID_044F&PID_B10B" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Script stopped!
Done
Device name set to Thrustmaster Combined

Runtime Error: STOP request received while running main on line 63 in "C:\Users\Jonathan\Downloads\temp\Aussiedroid-ED-Warthog-Script-2.4.3\Warthog Script\AD_ED_v2.4.3.tmc"
Error:Script run timed out!

I've already tried uninstalling/reinstalling, no change. If anyone has ideas, would love to hear them. Thanks in advance!

 

[Aussiedroid]

Hey there drag0nfire! Thank you, but I'm sorry to hear you are having issues getting it going.

I haven't seen this before myself, but reading the output it seems it is having issues creating the virtual device. This is where it combines the Thrustmaster devices you have plugged in into a single device and maps the script accordingly. Line 63 error looks like it might be having issues combining the TFRP Rudder pedals into the virtual device. Are you using rudder pedals? Win 7 or 10?

Some ideas to try to help trouble shoot:

- Ensure firmware is up to date in each Thrustmaster device
- Unplug any other game controllers, and then ..
- Try cycling the USB plugs used (ie use different ones), unplug, shutdown, restart and plug in devices again. (See around post #225 where there is some previous discussion around this that may be relevant to your situation too - specifically the order they are registered in windows can impact virtual device creation)
- Try older version of software (this was a suggestion I found via google)
- Driver updates for your USB controller on mainboard? (may be relevant if running an older PC)
- There is a registry fix by reddit user here (use at own risk!)

There are several posts I came across stating a reinstall finally fixed their issues, so may be worth another try and make sure you do a full shutdown and restart before retesting.

A successful run on my end looks like this by the way:

Currently plugged USB HID devices[2]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\5&2E6C26E8&0&14) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\6&25E4CD86&0&2) selected
USB HID device with hardware id "VID_044F&PID_B10A" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device with hardware id "VID_044F&PID_B679" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done

Cheers,
AD

 

[CMDR Corleone]

Finally got the plate I needed for my stick, second time lucky!

Spoiler

Fits the stick...

Spoiler

Fits the VESA 100 bracket (with wingnuts for easy removal!)...

Spoiler

And fits the cockpit!

Spoiler

Ignore the cabling, it is just because I spun the chair around to take the shots.

Very pleased with the outcome, the Warthog with this script and VoiceAttack really are a perfect set up and mounting them this way is ideal for VR.

Fly safe CMDRs, and always fly with rebuy!

 

[Aussiedroid]

Awesome work CMDR Corleone!! That looks like a pretty comfortable setup you have there ... ready for many more hours of ED

 

[CMDR Corleone]

Thanks, it is a game changer! I have an extension on order, then I think I'll call it a day on financial investment into this game!

 

[drag0nfire]

Some ideas to try to help trouble shoot:

- Ensure firmware is up to date in each Thrustmaster device
- Unplug any other game controllers, and then ..
- Try cycling the USB plugs used (ie use different ones), unplug, shutdown, restart and plug in devices again. (See around post #225 where there is some previous discussion around this that may be relevant to your situation too - specifically the order they are registered in windows can impact virtual device creation)
- Try older version of software (this was a suggestion I found via google)
- Driver updates for your USB controller on mainboard? (may be relevant if running an older PC)
- There is a registry fix by reddit user here (use at own risk!)

Thanks so much! I managed to get it working some how after a few hours of mucking around. I'm still not actually sure what did the trick... some combination of unplugging extra USB devices, uninstalling extra background processes, cycling USB plugs used for the Warthog, reinstalling the drivers, and rebooting several times.

I wanted express my appreciation for your helpful suggestions. Seeing the output from a successful run was actually very useful as well.

 

[Aussiedroid]

Thanks so much! I managed to get it working some how after a few hours of mucking around. I'm still not actually sure what did the trick... some combination of unplugging extra USB devices, uninstalling extra background processes, cycling USB plugs used for the Warthog, reinstalling the drivers, and rebooting several times.

I wanted express my appreciation for your helpful suggestions. Seeing the output from a successful run was actually very useful as well.

Happy to help!

The Warthog can be a bit stubborn at times. Once its working its rock solid, but sometimes, just sometimes it doesn't want to play nice. Seen it a few times now since sharing my script.

Thanks for popping back by to let me know its all working

Fly Safe CMDR!

 

[Hobson's Choice]

Well. Having bought a Warthog hotas and a set of TM pedals, I thought 'Why not. I will try out this fantastic looking script. So I installed target software. Loaded, compiled and ran scripts. Selected the aussiedroid keybinding file.
Started game and IT ALL WORKS! FANTASTIC!
I do have two problems.
1. I need to remap the pedals bindings each time I start the game.
2. I am working around the many and varied key combos. But, I must be missing a step. How do I open the various control panel subsystems? E.g. comns, srv/fighter, left transaction screen, right systems screen. I am ok once inside them, if opened by keys 1 2 3 4 but have no idea how to do it with the joystick/hotas.
Any help much appreciated.
Cheers

 

[Aussiedroid]

Well. Having bought a Warthog hotas and a set of TM pedals, I thought 'Why not. I will try out this fantastic looking script. So I installed target software. Loaded, compiled and ran scripts. Selected the aussiedroid keybinding file.
Started game and IT ALL WORKS! FANTASTIC!
I do have two problems.
1. I need to remap the pedals bindings each time I start the game.
2. I am working around the many and varied key combos. But, I must be missing a step. How do I open the various control panel subsystems? E.g. comns, srv/fighter, left transaction screen, right systems screen. I am ok once inside them, if opened by keys 1 2 3 4 but have no idea how to do it with the joystick/hotas.
Any help much appreciated.
Cheers

Congrats on the new Warthog Hobson's Choice! Glad you are liking the setup

Regarding your questions, lets see if we can get to the bottom of them:

1. Once you remap, I assume they are working OK in the game? The only thing you should need to do is ensure you click the 'apply/save' button at the bottom of the config panel. If that is done, it should save the updates to the pedal mappings. If that is not happening then, can you check the file in windows and see if it is updating the last saved date (ie check if it is actually writing the update to the bindings file). If it is not then the only thing that comes to mind is that the file cannot be access by the game/read only or something weird. Could you also perhaps try re-downloading the file again and copy across deleting the old one, just in case there is any corruption of the file.

Edit: Also to add, I've seen controls are 'removed' when the controller is not recognised when you start up ED. For example, if I was still using my X55 Saitek HOTAS, and started the game without it plugged in, all my mappings would get blanked out, even if I plugged in afterwards. May not be the case here, but I would also try cycling your PC (shutdown, unplug power, unplug controllers, restart, plug back in and try other USB port combos if you can).

2. Ah this would have slowed you down Fairly straight forward, but let me explain in a bit more detail as it is key to many of the other commands too. To use the subsystem panels, it is mapped to the same key as the lateral thrusters (left thumb / hat switch). Normally, with just the hat switch pressed, the thrusters will fire, but if you hold down the CMS Hat Switch Modifier (#2 on the reference map / right thumb) then press a direction it will fire the appropriate panel display. Do the same again to stop looking at panel or use the back combo (Pinky Trigger + CMS Hat Switch).

This modifier / combo button technique is used throughout the setup. In the reference maps on the guide, you will see some commands with a [1] or a [2] listed before the command. This means you need to hold another modifier key as highlighted in yellow bold plus the button to trigger. Very easy to get used to, but does make things a bit more complex to learn from the get go

Let us know how you get on or if I can help any further to resolve your issue.

Cheers,
AD

 

[Hobson's Choice]

Congrats on the new Warthog Hobson's Choice! Glad you are liking the setup

Regarding your questions, lets see if we can get to the bottom of them:

1. Once you remap, I assume they are working OK in the game? The only thing you should need to do is ensure you click the 'apply/save' button at the bottom of the config panel. If that is done, it should save the updates to the pedal mappings. If that is not happening then, can you check the file in windows and see if it is updating the last saved date (ie check if it is actually writing the update to the bindings file). If it is not then the only thing that comes to mind is that the file cannot be access by the game/read only or something weird. Could you also perhaps try re-downloading the file again and copy across deleting the old one, just in case there is any corruption of the file.

Edit: Also to add, I've seen controls are 'removed' when the controller is not recognised when you start up ED. For example, if I was still using my X55 Saitek HOTAS, and started the game without it plugged in, all my mappings would get blanked out, even if I plugged in afterwards. May not be the case here, but I would also try cycling your PC (shutdown, unplug power, unplug controllers, restart, plug back in and try other USB port combos if you can).

2. Ah this would have slowed you down Fairly straight forward, but let me explain in a bit more detail as it is key to many of the other commands too. To use the subsystem panels, it is mapped to the same key as the lateral thrusters (left thumb / hat switch). Normally, with just the hat switch pressed, the thrusters will fire, but if you hold down the CMS Hat Switch Modifier (#2 on the reference map / right thumb) then press a direction it will fire the appropriate panel display. Do the same again to stop looking at panel or use the back combo (Pinky Trigger + CMS Hat Switch).

This modifier / combo button technique is used throughout the setup. In the reference maps on the guide, you will see some commands with a [1] or a [2] listed before the command. This means you need to hold another modifier key as highlighted in yellow bold plus the button to trigger. Very easy to get used to, but does make things a bit more complex to learn from the get go

Let us know how you get on or if I can help any further to resolve your issue.

Cheers,
AD

Very many thanks for your most prompt, illuminating and comprehensive reply , AD!

All is sorted now!

To provide more illumination on the subject...
I am a 'leftie', having used T16000m stick, mouse and keyboard since game release (and keyboard/mouse in the 1980-90 Elite game series. I had been looking for a year or so for a 'leftie-appropriate' throttle block. Eventually, I decided to plunge deep, and got the Warthog hotas set with TFRP pedals.
So, I am relearning the whole flying thing. from left to right hand, using pedals for first time (axis mapped to roll - for now), using throttle block for first time. Aarghhh! .
PC is a mod/high spec, running Windows10 (not adding any spec detail here - probably not relevant).

1. Once remapped the pedals are working. I am not sure what was wrong...
Only change is that I am now running ED in Administrator mode. I will check program, directory and drive permissions, in case my security protocols have affected write capability (very probably it was human error).

2. The panel switching problem is ok now (always was, I suspect). I simply had (remember I am a 'leftie') moved the CMS switch to one side before pressing it, hence the switch was not moving down. Doh! yep. Another human error.

New Problems.
Important.
a./ However, I may not be understanding the UI nested toggle (which is a no mod press down on the TMS?). I want to change the Turret Weapon Mode, I navigate to the Functions subsystem, move down to Turrent Weapon Mode, but when I press the UI Nested Toggle or the primary trigger - UI Select on that option, nothing happens. Primary trigger UI select, works on other options in that subpanel, but those options are only on/off.
Edit **Ah. It may be that I don't actually HAVE any turreted weapons in the ship I am Currently flying** Doh (again).

Minor.
b. Playing with script settings, exe run. I had settings to run Market Connector, EDDiscovery, Voice Attack, EDEngineer and ED. When I compiled and ran the script I had an error on EDMC (sorry - not got exact error message - something like - log file directory not found). I can run everything external to the script, via an autohotkey script, so might just call that instead.

Questions.
Not a problem, just a question.
I have two ED accounts, so I was temporarily compiling and running two different settings scripts, depending upon which CMDR I wished to use. A bit messy so I was wondering if it was possible to create a popup with 'select cmdr a','select cmdr b' options.
I can forsee some issues as it would require an
if 'a'
process line containing folder address for fileset cmdr a, call ed.exe
if 'b'
process line containing folder address for fileset cmdr b, call ed.exe
endif
and the target script does not lend itself to creating popup boxes for user-input.

Observation.
Finally, just a comment regarding panel states. I also use the Roccat Power Grid app. This does not check for and revert to original state. My solution was to note the keypresses required to action the command I required and then, after taking that action, include a set of keypress commands in reverse, to take me back to the original (native) state.
so for example (not an actual operation) to turn on preflight... 4,rightx4,downx8,enter, upx8,leftx4,exit
This seems to work. I use this approach for srv and fighter launch, switching on and off additional SCBs (to remain within power limits), selecting power plant as a subsystem target (this works most of the time :-( ).
I haven't looked into the target scripting language at all, so am not sure if this would help, or not.

Second finally, Thanks so much for an awesome script. When I get into it I am sure it will cover almost all situations.

Cheers

Paul

 

[Aussiedroid]

Very many thanks for your most prompt, illuminating and comprehensive reply , AD!

All is sorted now!

Awesome! Great to hear. Sounds like you have your work cut out for you learning different hands, different hotas, pedals & different layout .. patience be with you!

Minor.
b. Playing with script settings, exe run. I had settings to run Market Connector, EDDiscovery, Voice Attack, EDEngineer and ED. When I compiled and ran the script I had an error on EDMC (sorry - not got exact error message - something like - log file directory not found). I can run everything external to the script, via an autohotkey script, so might just call that instead.

I can replicate the same error my end When I added the software system calls, it did work. I know there has been a few updates since then for EDMC, but I have also moved to Windows 10 recently so was not able to narrow down the cause my end (was thinking it might be a security thing in Win10 or something, but maybe completely wrong). For me, I also run TrackIR, but that is also not firing up now, so it seems all the software won't start for me even though the code in the script fires. Are you running Win10? I've tried the running as Admin but didn't help in my case.

Wonder if I might have to do the same via autohotkey or something, but I am not sure how to do that really.

Not a problem, just a question.
I have two ED accounts, so I was temporarily compiling and running two different settings scripts, depending upon which CMDR I wished to use. A bit messy so I was wondering if it was possible to create a popup with 'select cmdr a','select cmdr b' options.
I can forsee some issues as it would require an
if 'a'
process line containing folder address for fileset cmdr a, call ed.exe
if 'b'
process line containing folder address for fileset cmdr b, call ed.exe
endif
and the target script does not lend itself to creating popup boxes for user-input.

I might need a bit more info to understand what you are trying to accomplish . What are the differences between the scripts you run between the two CMDRs? Is it just the software or different mappings as well? Something else?

Cheers

Finally, just a comment regarding panel states. I also use the Roccat Power Grid app. This does not check for and revert to original state. My solution was to note the keypresses required to action the command I required and then, after taking that action, include a set of keypress commands in reverse, to take me back to the original (native) state.
so for example (not an actual operation) to turn on preflight... 4,rightx4,downx8,enter, upx8,leftx4,exit
This seems to work. I use this approach for srv and fighter launch, switching on and off additional SCBs (to remain within power limits), selecting power plant as a subsystem target (this works most of the time :-( ).
I haven't looked into the target scripting language at all, so am not sure if this would help, or not.

Thanks for the info! I have incorporated that into the Autodock function already in the script, but haven't really considered its use outside of that. Good idea with using that for a macro for the SRV/Fighter etc. Will look into the feasibility of it in a future release & see if it may enhance any existing features further

How do you find the Roccat Power Grid if you don't mind me asking? Been meaning to get a tablet and set it up one day on my rig.

Second finally, Thanks so much for an awesome script. When I get into it I am sure it will cover almost all situations.

Cheers

Paul

My pleasure mate. Any other questions/suggestions are always welcome.

Cheers,
AD

 

[Hobson's Choice]

Autohotkey is quite simple. just a dos-type batch file at it's simplest, subsequently compiled as an exe and assigned to a keyboard combo. I have one as a process kill switch for while I am learning this new layout.
I would recommend Roccat Power Grid. There are two free slots for screen layouts. It is easy to work with and if you can use graphics software (eg. Fireworks) you can make up your own icons quite easily. The edit menus are well planned and allow for some sexy scripting if you felt it necessary. I would recommend only using sufficient icons to fill one screen. Although you can drag the window across, it does get tedious. I used mine for wings and for fighter control (not needed now, with your great scripting). Still worth a look, though.
As for the dual commanders. I couldn't work out how to run both on one machine until I contacted fdev. They said I had to have two different email/password logins. So, I have installed both in the same (Games) directory. In effect that is two copies of the EDLaunch branch named for each commander. (When I update ED, I need to do so twice). I have two different pilot log files, two different EDLaunch.exe files etc. Not sure if that explains it any better :-(.
I currently run Windows10 64bit, have an Acer triple monitor spanned setup, plus one (for auxillary apps, EDDiscovery EDMC EDEngineer etc.). Nvidia GeForce GTX 1080, Intel i7-3970x, 16bgRam on a Rampage 4 extreme MoBo - all of this is running slow for stability. I do get very frustrated with the Nvidia control panel which frequently loses config and requires ten minutes to sort it all out again. even DisplayFusion doesnt help. might try daisychaining the triple monitors.

 

[Aussiedroid]

Hey there! Yes, that does help explain what you are trying to do with the 2 CMDRs. Thanks. Frontier really need to sort out multiple CMDRs on one account

I don't think there is an option for a pop-up or a menu as such to select at the start of the script running. What could work, would be to add both ED Launchers into the script software section and run both when you run the script, then just close the one you do not want to use. Else might need an individual bat file or autohotkey script to run the selection.

It would not be too hard to add a variable into the user preferences to choose what to run based on which CMDR (if CMDR 1 run this, if CMDR 2 run that), but the caveat would be that you would need to go in and select/change the CMDR variable each time which would probably defeat the purpose some what. The other way to look at it would be to have 2 copies/versions of the script. Make the software path changes for each copy of the script and run the appropriate one. Should only need to modify the main script file, all the others could still be shared in the same folder.

Cheers,
AD

 

[certhas]

I hope i can get some help here, i've stumbled across this setup file when i was searching for a method to use the secondary trigger button for either shoot weapons maped on second trigger in game or to use it as a macro button for the dss honk (like you pull the trigger to the first stage it starts scanning or firing, if you pull it further to the second stage and let it go it scans / fires automatically for a set amount of time).
i've tried to figure this out by looking at the files but i cant