And what are the significant differences between the profile for Elite Dangerous from the manufacturer of the Warthog, and the profile developed by You?
 
Hi @Meresiga

The 'manufacturer one' simply maps buttons and axis in the bind file and does not require the TARGET GUI (scripting engine) to be running.
It also only maps a subset of the switches available.
This is a good option to start with if you just want to plug it in and start playing.
You can add unmapped switches etc in the in-game Controller Settings as you go.
(this changes the profile name to "custom")

Aussiedroid's script adds a bunch of smarts along with tweaking the curves of the axes etc.
The smarts are listed on page one of this thread and a longer description can be found via the links to ADs Steam pages.
You must run the script via TARGET GUI prior to starting the game and in so doing, the individual controllers in Windows are replaced with a single controller called "ThrustmasterCombined".

I mention this specifically because if you start with the 'manufacturer' or standard Joystick profiles then spend a large amount of time setting all the binds to how you like them, then switch to a script based solution, two things happen.
1. Your bindings are made redundant and the 'Custom' profile will no longer work
2. You need to re-learn what everything does (ie new muscle memory)...and that takes time

Clicker
 
Last edited:
I bought pedals today in addition to my Warthog.
ThrustMaster TPR Worldwide USB pedals. I hope that they will be able to work together using Your script.
 
Hi guys. Strangest thing happened two days ago. All of a sudden, I get random "fire" actions. It happens with weapons, scanners, and also within the menu system of ED! Needless to say, the game is unplayable!
It started around the same time I upgraded to Odyssey. I am still using AD 4.3.0. I checked the joystick actions, and the hardware is fine. Something got messed up in my settings. I saw a setting somewhere that automatically opens context menus (or something like that), which I had turned on for "on foot" and in the buggy. But I changed nothing in the generic bindings. Those auto-context items (under "miscellaneous") have been turned OFF again, btw.
What gives? I have literally no idea how to fix this. Any help appreciated!
Cheers RD
 
Hi @RagingDoc ,

When this happens is it a short lived occurrence (ie flurry of random stuff) or a specific action happening all the time (like a 7 second periodic fire)?

Cheers
Clicker
 
It was a continuous fire / <select> flurry. Although the frequency was not always the same. It was generally once every 7-8 seconds, though.
I’m using past tense here, because I downloaded the 5.0.0 from github which seems to have solved the issue. An hour of game play last night, no troubles. So, looking good.
Thanks,
RD
 
@RagingDoc ,

This sounds a bit like you've inadvertently selected a 'Repeater Fire' mode.
I recommend you become familiar with this and other 'modifiable' functions of the script.

Cheers
Clicker
 
It does in a way, but the frequency was very low, it also occurred in the game menus and finally I did not chanfe anything in the conf.
It may remain a mystery, as the problem is gone after I started using 5.0.0.
 
Hi, can you tell me if version 5 still beta? I know AD has left the cause for now :)

Just not sure which file I should use - just reloading everything since been out of game (prob for simlar reasons) for quite a few months and a new PC later, jyust trying to set everything back up. I guess looking for the script to perform on both horizon and odyssey
 
Hi @mackster ,

Yes, v5 is still in beta and not being actively tested, so, use with caution and by all means if you encounter any issues you can report them here or on github.

Regards
Clicker
 
Hi @spivak ,

First step, are you able to run joy.cpl without the script running and confirm the switch is being seen by Windows.
Also, when you do run the script and try to use POV1, are there any messages being printed to the TARGET console?

Thanks
Clicker
 
I know it's not being maintained, but I still use this profile. I play in VR, and this binding works great for me (5.0.0). There is 1 issue I'm having, but can't narrow down what's causing it. Something in the profile (which I don't see), or because I use HCS Voice Packs with my game (which I think are the culprit). Whenever I jump to Supercruise or warp to a system, my UI (all the shiny things) disappear (CTRL+ALT+G), but I can't find that in the binding. I don't see an option to switch the binding. I checked and couldn't find it in the main menu where I can change bindings... so was wondering if maybe it could be my Voice Attack. Is there a way to change it in the bindings?
 
Hi @CJDJ ,

The Ctrl+Alt+G to turn the Cockpit UI on and off is hard wired and not available to change in the bindings.

However, you may have this doubled up and bound to something else inadvertently in your binds file.
If you open your bind file with Notepad (I use Notepad++), you should be able to search for "Key_G".
When found, check the next couple of consecutive lines in the file for modifiers...they'll look something like this if they exist...

<Modifier Device="Keyboard" Key="Key_LeftCTRL" />
<Modifier Device="Keyboard" Key="Key_LeftAlt" />

Hope this helps.

Clicker
 
Hi @CJDJ ,

The Ctrl+Alt+G to turn the Cockpit UI on and off is hard wired and not available to change in the bindings.

However, you may have this doubled up and bound to something else inadvertently in your binds file.
If you open your bind file with Notepad (I use Notepad++), you should be able to search for "Key_G".
When found, check the next couple of consecutive lines in the file for modifiers...they'll look something like this if they exist...

<Modifier Device="Keyboard" Key="Key_LeftCTRL" />
<Modifier Device="Keyboard" Key="Key_LeftAlt" />

Hope this helps.

Clicker
Thanks for the tip. I looked at the binds file, and those aren't listed together. The closest I can find is to throw a grenade (ALT+G). So, it looks like it is the Voice Attack profiles. Thanks for helping... I'll start combing through the VA profile to see what is triggering it.

Edit
It was the UserPrefs file. There's a setting that's turned on by default in the AD_EDUserPrefs_v5.0.0.tmh file in the "Warthog Scripts" folder. I guess I missed that when I was going through it. The whole point as to why I want that setting off, is because when the screens pop back on, the Exclusion Zone line goes missing on Stars. Doesn't help when I'm scooping after a warp-in.
 
Last edited:
Will this work with MFG rudder pedals?
I am having trouble getting the latest version of Aussiedroids. It does all the basic but does not follow more in the keybinds. So looking for something that will work.
 
Last edited:
Back
Top Bottom