When Target is not running, the joystick control panel shows both the Thrustmaster Joystick and Thrustmaster Throttle.
Assuming both of these are configured to be used within the script (which they are in Aussiedroids script), then, when the script runs, these are both replaced by Thrustmaster Combined device within the Joystick Control panel...this is normal.
If you ever change your mind and wish to use this script, we would be happy to assist.
so.... I'm danish, and i got a danish keyboard. and i get this error: "Runtime Error: Symbol not found: KB_DA in main ( line 78 in AD_ED_v4.3.0.tmc )" ive tried, DNK DKK DA DAN DK nothing... same line same error, please assist a viking in need <3
Target script only recognises 3 different keyboard languages.
Unfortunately, Danish keyboard is not supported.
The only longshot solution would be to ask if someone has already built a custom defines.tmh and target.tmh to support Danish keyboard over on the HOTAS/HOSAS/SIMPIT discord ( in the Thrustmaster Community Q&A area)
Yes, you should be able to leave it as KB_ENG and see what works (and what breaks).
Whilst you may not be using the keyboard much directly, the script sends keyboard keystrokes.
The keys used are all defined within AD_EDKeyMap_v4.3.0.ttm file in Aussiedroids script bundle.
These all need to be included in the .bind file within the game options/controllers...so if you change anything, you need to change in both places.
It's been a while since I have logged into the forums!
Firstly, thanks CMDR Clicker for helping everyone out .. I see you have been busy over here!
I've been away from ED for a while awaiting the Odyssey release, but have prepped a beta across on GitHub to start updating it once we get our hand on it. Expect given the addition of first person mode there will be quite a lot to update. During the beta, I will not be releasing a new version but the latest beta builds will be available on GitHub directly. Obviously, these will be a WIP so may contain errors or issues but for early adopters you can give it a try. Feedback, issues etc during this phase are greatly appreciated, please report them on GitHub to ensure they are captured before public release. Likewise if you have any improvement suggestions or requests for the current build but have not raised them, now will be the time to ensure I can review before the next release.
@spivak - Thanks for reporting your issue. I doubled checked the code and cannot find any specific issues. I suspect if FAOff is being triggered quickly/frequently there may be something odd going on, maybe some ghosting or polling issues on the USB side resulting in the misalignment. Changing USB ports, disabling power management / suspend on the USB via Windows may assist, but will also add to my to-do list to see if I can add an override like I have done for some other toggles/buttons so it can be corrected in game using a modifier. Also would be good to know if you are using the hold or toggle action when you are seeing the issue.
@Clicker - Thanks for the reminder! I'll take another look into the status.json improvements. I noted you added some info here on the forums which makes a bit more sense than when we were chatting about it some time back. Back then it just wouldn't sink in and looked too complicated / too much work to retrofit but will revisit before I finalise my next public release
PS - Best place to get my attention these days is either on Steam via the guide or via GitHub, sorry to all of you sending me private messages here on the forums not getting a response for months!
I've been busy at work getting an updated version of the script ready for the Odyssey release. Lots of improvement & enhancements! Testing is going well, but given my limited time to play I appreciate any feedback from the community too if you are keen to get an early look at v5.0.0 release. Hoping to have this is a good place ready to add the new Odyssey bindings when the alpha drops so if you can, let me know your experience.
Check out the Changelog.txt for a list of the current changes.
A couple things to mention if you would like to try the beta script:
Please update to the latest v188.8.131.526 Target Software build.
Check User Prefs, there are some new ones, particularly you need to set a file path for status.json file else script will not run.
Things to try/test.. Many toggles have been rewritten, there are also many new messages output to the Target Window, both which need further validation. Many commands are now configured to only fire when in the right state so if you get commands not working let me know. Few new macros to try too. Any issues around status.json file reading or exceptions I am keen to know about too as this is a major feature of the new version.
Happy to help out if I can. First point would be to follow the installation instructions in the guide to get the script and binding files to the right locations and cover a few other things to be aware of/set up. Can I ask if you have gone through these yet, or if you are getting stuck on any particular point? If you have any specific questions please let me know.