I think I misread your query mate sorry.

Yes, you can use the software startup feature to start ED when you run the script, but this seems to only work in Windows 7 these days. If you are running Windows 10 it may not trigger.
 
I think I misread your query mate sorry.

Yes, you can use the software startup feature to start ED when you run the script, but this seems to only work in Windows 7 these days. If you are running Windows 10 it may not trigger.

Is it possible that the TARGET software needs to run as administrator under Win10?
 
I think running as Admin has been attempted. A few pages back in this thread there was some investigation done into it and the user also contacted TM support who didn't have an answer. It seem like either a TM bug/issue or some restriction/security feature on MS side. I've moved back to Win7 a few months back so I cannot test it out anymore unfortunately.
 
This is awesome!
Only, I found out one year late :(
I will give it a go nevertheless. Perhaps my brain can still readjust, adapt to this new control scheme.
 
This is awesome!
Only, I found out one year late :(
I will give it a go nevertheless. Perhaps my brain can still readjust, adapt to this new control scheme.

Thanks!

As they say, better late than never lol :)

No doubt its probably a lot different, but a few hours in the cockpit should start getting you used to things I hope. Few sessions and should start to lock things into memory. Any questions, feel free to ask.

Software startup feature?

Yes, TM scripting language allows for starting software from within the script. I have this coded in with a few of the popular add-ons. You need to enable it under the user preferences (as its disabled by default) & ensure the paths are correct in the main script depending on where you have installed things. The guide covers this in some more detail too & also in the comments within the script.
 
Yes, TM scripting language allows for starting software from within the script. I have this coded in with a few of the popular add-ons. You need to enable it under the user preferences (as its disabled by default) & ensure the paths are correct in the main script depending on where you have installed things. The guide covers this in some more detail too & also in the comments within the script.
Sorry to be so dim, but where is the relevant user preference? I can't see it in the Script Editor. Sorry, but I've never used this stuff except for running your script!
 
It's no problems. In my user guide across on Steam there is a section that covers all the user preferences and where to find them. They are found in the AD_EDSettings file. The preference you want is 'StartSoftware'. Change this value from 0 to 1.

In the main script file AD_ED_v3.0.0 file you will see a section near the top that has the start up section. In here there is a number of lines that are commented out at the start of the line with a '//'. Remove this to enable whichever one you want to run at the start. Be sure to check that the path is correct. If you installed ED to another location you need to have the script match otherwise it may not run or cause an error. The lines you are looking for are like this:

// system("spawn -w "C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous" "C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\EDLaunch.exe"");
 
Last edited:
Thanks a lot for that.
If I've done it correctly, I just get the error shown on attachment.
 

Attachments

  • ad.JPG.gz
    269.7 KB · Views: 102
No worries! :)

That seems like it is suggesting that the path used is not correct. Just to double check, is that where the EDLaunch.exe file is located on your computer?

I've just checked it again on my end with v3.0.0 and it seems to be starting the launcher correctly under Windows 7.

Are you running Windows 7 or 10?

AD
 
I thought you may be on Windows 10 from the pop up window from the screenshot. Unfortunately, as I mentioned in my patch notes it doesnt seem to work anymore under Win10. Not sure if its a TM issue or a MS issue but it seems to block it from running. :(

The alternative if you are starting up multiple programs with ED, is to create a batch (.bat) file to start up all the programs you want to run. A google search should give you some more info on how, but here was one link that might get you started (https://www.makeuseof.com/tag/launch-multiple-programs-single-shortcut-using-batch-file/). Doing this would start all the programs, Target included, but then you would just need to open the script & run (so still a little manual but might streamline it a bit for you).

AD
 
I think running as Admin has been attempted. A few pages back in this thread there was some investigation done into it and the user also contacted TM support who didn't have an answer. It seem like either a TM bug/issue or some restriction/security feature on MS side. I've moved back to Win7 a few months back so I cannot test it out anymore unfortunately.

I'm on Win10 and it (spawn) doesn't work from the script. I don't think TM will take too long to fix it, the spawn.exe launches apps from the command line fine, although the syntax seems different. I played with it a bit and it launched EDDiscovery with just the path to the EDDiscovery executable, no -w switch or the software directory was required.

The manual doesn't appear to provide much detail about system() or spawn besides how to use them to launch software.
 
Just found this. Looks like a solidly done setup! While I'm not a Warthog user, I'd love to use some of the features such as PIP management for my Thrustmaster FCS. I haven't bothered with the Target software yet, however. Are there any odd stumbling blocks you can point out I ought to watch out for?
 
Just found this. Looks like a solidly done setup! While I'm not a Warthog user, I'd love to use some of the features such as PIP management for my Thrustmaster FCS. I haven't bothered with the Target software yet, however. Are there any odd stumbling blocks you can point out I ought to watch out for?

Hey Nilt,

I don't know how many stumbling blocks I hit learning all this scripting stuff lol! So many! Not sure where to start :)

I think in essence the code in the script could be retrofitted to use other TM devices as long as they support the TARGET Script. Some of the mappings for the buttons you may need to change to match your device but the logic should work the same. PIP management would probably be one of the easier things as its got no internal/direct mappings within the function. Essentially just need to setup the variables (ED_Settings file), copy in the function (ED_Functions file), and map your keys to the function (eg. MapKey(&Joystick, H3U, EXEC("initPIPManagement();")); ).

As a general bit of advice, go slow and setup one thing at a time once you have the basic script structure setup. Test & make sure everything is working before moving onto the next thing. Most commonly for me, I would misplace a bracket or miss an end of line ';' or something sloppy. I'm not a programmer so took a bit of training to drill that out of me. Target isn't always very clear with the error messages returned so if you have just coded up 100 lines it can be tough to isolate the issue - I've wasted many an hour scratching my head on the most simple of things. Printf command can come in handy to help trace an issue or see what code is firing too. Although the help guide by TM is pretty basic, it does cover most things and can help you work through more technical challenges (along with a google search or two).

Most of my coding has comments throughout to help explain what it is doing, so that may help you get your head around what is what and how it is structured (should basically be the same for other devices so even though wont work for your device might be a good reference for you).

AD
 
Last edited:
Hey Nilt,

I don't know how many stumbling blocks I hit learning all this scripting stuff lol! So many! Not sure where to start :)

I think in essence the code in the script could be retrofitted to use other TM devices as long as they support the TARGET Script. Some of the mappings for the buttons you may need to change to match your device but the logic should work the same. PIP management would probably be one of the easier things as its got no internal/direct mappings within the function. Essentially just need to setup the variables (ED_Settings file), copy in the function (ED_Functions file), and map your keys to the function (eg. MapKey(&Joystick, H3U, EXEC("initPIPManagement();")); ).

Are you running your own script already?

AD

I had some AutoHotKey scripts I used for a few things combined with my old X56's software which pretty well automated a few things. Having an all-in-one solution would be handier. I'm a little off this weekend fighting a cold so I didn't dig into the code yet other than a glace. It seems relatively straightforward. It'd be nicer if Notepad++ colorized it for me but what can ya do? :D
 
I finally found the time to try out this scripting with my Warthog, using v3.0 One issue I have is that my vertical thrusters are at max, pushing the ship up at 278 m/s.

Any idea what would cause this? The nib seems to be centered, the device panel shows the X & Y controls at midrange of 512 each.
 
I finally found the time to try out this scripting with my Warthog, using v3.0 One issue I have is that my vertical thrusters are at max, pushing the ship up at 278 m/s.

Any idea what would cause this? The nib seems to be centered, the device panel shows the X & Y controls at midrange of 512 each.


Hey Brian,

Sounds like a stuck button (or glitched during compiling). In this version of the script I didn't make any changes to the vertical thrust as I recall, but will double check when I get home from work. As well as the analog nub, vertical thrusters are also on the digital hat switch on your thumb on the throttle. It is used in the new Take Off Sequence though, but don't see how that could be firing unless you are holding down Modifier 2 (CMS Hat Switch) and using the landing gear toggle. I would double check the digital vertical thrusters on the throttle, and failing that (assuming you have already tried to reload the script), shut down the PC and restart and try loading again.

Let us know if you are still having issues and will double check things my end later today.

Edit: Does the Event Viewer show any repeating or stuck buttons as well?

Cheers,
AD
 
Last edited:
Hey Brian,

Sounds like a stuck button (or glitched during compiling). In this version of the script I didn't make any changes to the vertical thrust as I recall, but will double check when I get home from work. As well as the analog nub, vertical thrusters are also on the digital hat switch on your thumb on the throttle. It is used in the new Take Off Sequence though, but don't see how that could be firing unless you are holding down Modifier 2 (CMS Hat Switch) and using the landing gear toggle. I would double check the digital vertical thrusters on the throttle, and failing that (assuming you have already tried to reload the script), shut down the PC and restart and try loading again.

Let us know if you are still having issues and will double check things my end later today.

Edit: Does the Event Viewer show any repeating or stuck buttons as well?

Cheers,
AD

I figured it out. Turns out the combined Warthog wasn’t well calibrated. I went into the USB control panel and calibrated the Y axis for the nib.

Not I need to figure out if I want to make any changes, especially the keybindings. My keyboard has custom labels on the keys and I haven’t decided if I want redo the labels or modify the scripts.
 
Back
Top Bottom