AD,

Can you confirm the file at moddb.com is your 3.3 or is it the 3.2 as it is stated in the text?

AD is hopefully sleeping down there.. And servers went down anyways, so I'm just enjoying a mid day beer and having a few laughs when reading the Frontier forums. Keep up the great work!
 
AD is hopefully sleeping down there.. And servers went down anyways, so I'm just enjoying a mid day beer and having a few laughs when reading the Frontier forums. Keep up the great work!

..yeah.. just played a bit around. there´s a ton of new keybindings, which arent in my current 3.2. just added that new switch combat <--> explo mode button -.- and the new FSS scanner needs also alot of bindings, as well as that DSS....

...holy...im out for today :)

cheers^^
 
Last edited:
IT'S UP!

Hey All,

Sorry for the delays. Patch dropped at a bad time for Australian players.

Will post full patch notes later today (my time) but for now, the new version has been uploaded.

Go hard guys/gals and let me know if you find any bugs. Wasn't able to test it much in the live build this morning before work.

Cheers, AD
 
Last edited:
Yeah. Tried that. But will look at it again.
I too know the code is fine because I have had it working properly for a year, or so. So, as you say, it's only TARGET that is failing to pick it up. I could
(more or less) understand it if it was just going to forward only, but going from off to max at the smallest movement of the throttle is just weird, ie, digital off-on.
Of course, it might be a fault with the throttle body electronics, if I can't get anywhere soon, I will contact Thrustmaster.
I will try removing ALL pc usb connections and starting with warthog, then putting the others back in.
Annoying, because I haven't been playing much and just got my muscle memory working :-( .
I am using USB 2.0 sockets (onto a Rampage Extreme IV board), not mixing USB 2.0 and USB 3.0
I will let you know if there is any positive news.
Cheers AD

Sorry I can't be of much more help man!

Could see if there are any updated mainboard drivers, chipset, usb drivers and the like. Make sure its all up to date.

AD
 
G'day AD,

Did you get the NAVBeacon toggle working?

Cheers
Clicker

Hey Clicker,

Unfortunately I ran out of time to figure it out. Report Crimes made it though. Same with a number of Fighter Launch macros that another user shared to me, but had issues with reliable function. Hope to get back to trying it for a future build though.

Cheers, AD
 
December Update!

Update 3.3.0: BEYOND CHAPTER 4


** IMPORTANT - v3.3.0 Requires the latest 2018 (v3.0.18.328 or higher) Update for TARGET Software, Drivers & Firmware to be installed. **


-> A big update for a big update! Final installment of Beyond is here, including many new commands and a multitude of improvements. This new update aligns with latest build, including all Chapter 4 GUI improvements & new modes, plus a range of enhancements & new features (many provided from fellow CMDRs). There is a significant increase in user preference options to support some of the new features below. Please be sure to check them out before you start :)

New to the script? Be sure to also check out the new Beginners Reference Map in the download pack.



List of Changes:

NEW: Support Added for the new Thrustmaster TPR Pedals (Thanks to CMDR Mettius for coding/sharing!).
NEW: PVP Macro for toggling Report Crimes Against Me (Mapped to OSD (FPS/Bandwidth) Toggle + Pinky Modifier) (Thanks to CMDR Clicker for coding/sharing!).
NEW: LED Controller Function introduces some Bling! When enabled will provide a short visual 'flashing' transition for the LEDs when a toggle is used. User Preference has also been added to disable (as required). Function will also perform a startup visual sequence as it initialises! (Thanks to CMDR Clicker for the inspiration/base code)
NEW: Customisable Secondary Fire (Pinky Button) (S3) from the user preferences. If you prefer the dual-stage trigger for primary/secondary or do no need the independant secondary fire, then this new option will free up the easy access button and allow you to remap a short and long press of your choosing. (Thanks to CMDR Axsom for the idea/request)
NEW: Autopilot Engage Button (APENG) on the Throttle can now be customised in the user preferences. (Total of Six possible mappings, using Short/Long presses & Modifiers)
NEW: Streamline your boot times! Windows Batch File Script to Auto-load multiple 3rd Party Apps + ED in one shortcut PLUS make a backup of your bindings file automatically on Win7/10. (Optional) (More info on this can be found in the batch folder Readme in download pack)
NEW: Swap PIP Management Hat Switch with CMS Hat Switch User Preferences added (EXPERIMENTAL!) (Requires Manual remapping of UI Hat Switch to DMS Hat Switch) (Thanks to CMDR Braxhunter for the idea/request)
NEW: Added ALL the New Chapter 4 bindings for the FSS, DSS, UI Enhancements & Night Vision (Quick List below):

Night Vision = Forward on China Hat Switch on Throttle (Orbital Lines now needs + Pinky Modifier) (Enabling will also dims LED backlights on Throttle :))
Switch HUD Mode = Double Tap Pinky Trigger
UI Next Page = Pinky Trigger + Target Hat Switch Right (On Joystick)
UI Prev Page = Pinky Trigger + Target Hat Switch Left (On Joystick)
Open Discovery Codex = Pinky Trigger + Mic Switch Down
Discovery Scan / Honk = Primary Trigger (On Joystick) (Firegroup Mapping + Analysis Mode HUD UI)
DSS Front/Back View Swap = Hold the Pinky Trigger
FSS ON/OFF = Pinky Trigger + Mic Switch Up (On Throttle) (Can also exit with usual UI Escape/Back combo)
FSS Camera Pitch & Yaw (Digital) = Trim Hat Switch (On Joystick)
FSS Camera Pitch & Yaw (Analog) = Joystick X/Y axes (The same as Galaxy map etc movement)
FSS Zoom Into Target = Target Hat Switch Up (On Joystick)
FSS Zoom Out = Target Hat Switch Down (On Joystick)
FSS Zoom Stepped In = Coolie Hat Switch Down (On Throttle Arm)
FSS Zoom Stepped Out = Coolie Hat Switch Up (On Throttle Arm)
FSS Target Current Signal = Pinky Trigger + Target Hat Switch Up
FSS Radio Tuning (Analog/Absolute) = Throttle Axis
FSS Radio Tuning (Analog/Directional) = Slew Left/Right (**Recommend Re-Mapping to Rudder Pedal Axis if Available**)
FSS Radio Tuning Increase (Digital) = Target Hat Switch Right (On Joystick)
FSS Radio Tuning Decrease (Digital) = Target Hat Switch Left (On Joystick)
FSS Show Help = Master Mode Control Button (Red Button on side of Joystick)


IMPROVEMENT: Thrustmaster Rudder Pedal Axis Curve can now be changed based on the Joystick Curve Preset Toggle position & also enabled in the FAOff Hold. (Enable in user preferences). Useful for FAOff pilots wanting more precise control. (Thanks to CMDR sw33tp34 for coding/sharing!)
IMPROVEMENT: Inverse Mode for Microphone Push-To-Talk Button on Throttle Arm introduced. When this special mode is enabled, this will disable VoiceAttack automatically when PTT is activated for Discord (or other voice comms) and visa-versa. To use, change 'ExternalMicInverse' to 1 in User Preferences. (Note: You need to have VA listening enabled before first press to ensure alignment) (Thanks to CMDR Axsom for the idea/request)
IMPROVEMENT: Reformatted Script Start-Up Printout/Readout. Easier to read. Should have better alignment in across Script Editor & GUI.
IMPROVEMENT: Both Ship & SRV External Camera buttons now mapped to same key on Joystick (Pinky + Target Ahead / F1). Previously SRV was needed to have different exclusive mapping so used the CMS hat switch forward + Pinky.
IMPROVEMENT: Swapped Ship Launch Fighter Dock & Ship Launch Fighter Attack/Focus commands on the Target Management Hat Switch.
IMPROVEMENT: Beginners Reference Map now included in download pack. This includes ONLY the essential ship & UI control, to help new users to ED and the script to cut through the massive number of mapped controls in the full reference maps, and to learn the fundamentals first.


FIXED: Cargo Scoop Throttle LED getting stuck ON in some situations. (Thanks CMDR Clicker)
FIXED: ECM Button functionality, removing the pulse action to allow full sequence timings. (Thanks CMDR Mettius & Clicker)
FIXED: Autodock Macro to align better to new Ch.4 UI Panels.
FIXED: Added Missing MFD Panel mappings (SYMU & SYMD) & cleaned up order of buttons in function (Thanks CMDR Braxhunter)



[alien] Fly Safe CMDRs! [alien]


** Please visit the ModDB link to get the latest version *** Steam Guide can be found here **
 
Last edited:
Hey AD, I'm a fairly new player, been playing for a few weeks with the standard out of the box target config for the hotas warthog, I'm currently only using the throttle and joystick. Have had very few problems but I wanted to give your script a shot as it seems well thought out with a lot of functionality. However I can't seem to get the script to see my joystick? Everything on the throttle seems to have mapped fine, the scripts work etc. But zero input from my joystick with your script running. I'm not sure what's wrong exactly, hoping you or other forum users might be able to help me troubleshoot this?

tia guys o7
 
I forgot to mention as well, in trying to follow your guide, there is a lot of information which is.. outdated? Like the video guide is from 3 years ago or something, and you explain that you load the fcf file in the target gui, but there is no fcf file included in your download? So I've been running it from the script editor.. I'm really unsure this all very very confusing.
 
Hey AD, I'm a fairly new player, been playing for a few weeks with the standard out of the box target config for the hotas warthog, I'm currently only using the throttle and joystick. Have had very few problems but I wanted to give your script a shot as it seems well thought out with a lot of functionality. However I can't seem to get the script to see my joystick? Everything on the throttle seems to have mapped fine, the scripts work etc. But zero input from my joystick with your script running. I'm not sure what's wrong exactly, hoping you or other forum users might be able to help me troubleshoot this?

tia guys o7

Hey ATARI-,

Thanks for checking out the script!

To check, are you running the latest software/drivers/firmware?

CMDR Clicker a few comments back hit the same issue, and found, IIRC, starting up Event Viewer or Device Analyzer before running the script seemed to fix it. Believe he also has a trouble ticket with TM for it. System restart/unplug/reinitialise etc may be worth a try too. Not really sure what causes it. Only happened once to me and I did a fresh reinstall to fix it.

Cheers, AD
 
I forgot to mention as well, in trying to follow your guide, there is a lot of information which is.. outdated? Like the video guide is from 3 years ago or something, and you explain that you load the fcf file in the target gui, but there is no fcf file included in your download? So I've been running it from the script editor.. I'm really unsure this all very very confusing.

Video guide??

I've never made a video about it :) Got a link?

Information on the Steam Guide should be fairly accurate still.
 
Last edited:
Hey ATARI-,

Thanks for checking out the script!

To check, are you running the latest software/drivers/firmware?

CMDR Clicker a few comments back hit the same issue, and found, IIRC, starting up Event Viewer or Device Analyzer before running the script seemed to fix it. Believe he also has a trouble ticket with TM for it. System restart/unplug/reinitialise etc may be worth a try too. Not really sure what causes it. Only happened once to me and I did a fresh reinstall to fix it.

Cheers, AD

Thanks for getting back to me, yeah I am running all the latest firmware and drivers. I'm going to try a complete reboot and have another go. I did run the event viewer and device analyser but on both of them the stick and all its buttons were showing zero input. There is something I don't really understand, like, I can run the script from the script editor, but there is no fcf file included in the download, so is running from the gui not possible? Or do I need to do some sort of compile to turn the scripts into a fcf?
 
Thanks for getting back to me, yeah I am running all the latest firmware and drivers. I'm going to try a complete reboot and have another go. I did run the event viewer and device analyser but on both of them the stick and all its buttons were showing zero input. There is something I don't really understand, like, I can run the script from the script editor, but there is no fcf file included in the download, so is running from the gui not possible? Or do I need to do some sort of compile to turn the scripts into a fcf?

From what I understand, the different extensions tell you what sort of script it is. The fcf I think will only run in the GUI, where as the other tmc file etc can be run from either.

If you load up Target GUI, there is a button in the top right that says 'Run Configuration'. Press that, and navigate to the AD_ED_v3.3.0.tmc file and double click to load. It will recognize the file type and start up. If you need to change any user preferences then you can open the files in the Script Editor or text editor then save and load up in GUI afterwards.
 
Okay so I've got it fixed I ~think~. Compiling and running the tmc file in the gui has fixed the issue. Thanks again for the help! Hopefully I can avoid annoying you again :D
 
Okay I didn't make it very far unfortunately, uhm, alright so I have VR which I plan to use eventually, but while I'm learning the game and configuring stuff I'm just trying to do everything normally. I don't have the rudder pedals, and I don't want to use track IR initially. Like I want to get the setup working without any bells and whistles and move on from that base. Is there a simplified version of this script that has the functionality mapped for example to look left and right without track ir? rudder controls remapped to not use pedals etc?

I dunno, it's like, there is so much going on with this script and so many interlocking parts with other applications mapped it's insane. But I don't need any of it really. And the script seems waaaay to complex for me to try and reconfigure it myself without completely breaking it.
 
Yeah its a lot to take in to start with. Beginners map should hopefully help a little there.

What you will need to do though, is just set a couple of the User Preferences in the AD_EDSettings file, specifically:

HeadtrackPref to 0 or 1 depending on what you want to use.

Then, as you do not have Rudder Pedals, you need to map a few things quickly. These are covered in the Legend section of the guide under 'Other Mappings / Pedals. The main one there you would want to map straight away is the Roll axis, perhaps to the Slew (or swap out with Yaw on Joystick and put Roll on the Joystick instead). There are a few others to map but that should get you started out.

You can ignore most of the advanced commands for now. Most of those are behind a modifier key anyways, so should be minimal chance of pressing something by accident. The high frequency commands should be fairly easy to find. It tends to look a bit more complicated than it actually is once you start using it, the basics should hopefully start falling in place.

Think that is all that you need to do besides copy over the non-MFG crosswind bindings.

AD

Edit: Sorry I should add, that headlook is mapped already if you do not use TrackIR.
 
Last edited:
AD, thanks so much for being understanding with a simpleton. So I did go through the settings, made some basic modifications, resaved and recompiled, and I also brought over the non mfg bindings.

I think I am just not correctly understanding how to read your graphical layouts, like I'm not seeing or understanding what keypresses trigger what modifier. I see that headlook is mapped but I have no idea how to do it hahahaha. This is making me feel like RPing a monkey shot into space would be easy for me.
 
Oh man, with such a button heavy game like ED, I think we all feel that one at some point or another! Even for someone who get the layout quickly, really it is like going back to Flight School for a couple hours and feeling awkward and uncoordinated till the layout sinks in. Ah fun times lol.

Headlook Analog is mapped to the Slew when headlook is enabled. Enabling Headlook is on the Target Management Hat Switch (Down direction + Modifier 1, which is the Pinky Trigger on Joystick).

Where ever you see a [1] or a [2] before the description, that means you need to hold down the Pinky Trigger or the CMS Hat Switch button plus the button or toggle in question. Holding both Pinky and CMS Button together (Squeeze) is back/exit on UI etc too by the way (that one can confuse people till they fire it once).

Best place to practice is in dock with the 4 cockpit panels and moving around the UI. Once you get the feel for it, hopefully the strange logic in my brain starts to become clearer lol.
 
Last edited:
Okay so I'm starting to understand the diagrams and make a bit of progress, thanks again for your patience. I've got most things working as far as i can tell!

edit: nvm, got it, it's all making sense!
 
Last edited:
Back
Top Bottom