If you're like me, you don't sit down and just click on the Launcher Icon and start playing. I have like 6 things running before I even click Play. I found occasionally my stick and throttle weren't being recognized so I call up Joy.cpl which I close after making sure they work. I also have EDMC, Voice Attack (which for some reason started crashing; sometimes in the middle of combat) so I wrote a small utility to monitor for this to restart VA it when it happened. So that's 4. And then there is my clock program that translates the time into local. And then a 6th program that will close itself and the launcher when it detects the main executable.
Starting with installing EDMC (Voice attack was my first add on), I figured there had to be a better way than clicking on VA, EDMC and then the executable. So I wrote a program that would call up all 3. After I added the clock, I figured that there had to be a better way than going back and adding to and recompiling my program each time. So I wrote a program that would call them up that could be easily configured. Hence AutoLaunch was born. Autolaunch by itself, launches everything in its run list (and it doesn't have to be Elite Dangerous related; AutoLaunch doesn't care. It just executes the run list) and then exits. Adding a /c (case insensitive) switch will bring up a configuration screen and I have included in the archive a shortcut just for that. Below is a screenshot for the config screen. There is no other screen to show. There's no user interface when it runs without the /c switch.
It's not usually that quite that wide, but I resized it to show the programs. I have also included the VAMonitor program in the archive for those of you who use Voice Attack. First run of that will show a File Open dialog so you can specify where your Voice Attack executable is and then run it. And yes, I have corrected the false positive concerning Windows Defender. I submitted the VAMonitor file to Microsoft for their analysis and they found no virus or malware. Windows Defender shouldn't flag it as a virus unless you are running with virus definitions that are 2 or 3 days old or more.
The EDRunChk program that closes the launcher and itself when it detects the main executable is a quick fix for me. It causes a not working error if tying to close it manually. But if you'd really like it, let me know and I'll send it to you. It has not been vetted by Microsoft, so it may show as a virus when downloaded.
You can click here to get the program. As with all new programs, smart screen will probably flag it as unknown and therefore potentially harmful. Nothing I can do about that. Just run it anyway.
The program, in config mode, creates one file in the same directory it is in, AutoLaunch.ini. This is a plain text file containing the run list, 1 item per line; the complete path including the executable.
VAMonitor creates one file, VAMonitor.ini in the same directory as the VAMonitor.exe file. This is a one line text file with the path to the voice attack executable.
Any problems and/or comments, let me know.
Starting with installing EDMC (Voice attack was my first add on), I figured there had to be a better way than clicking on VA, EDMC and then the executable. So I wrote a program that would call up all 3. After I added the clock, I figured that there had to be a better way than going back and adding to and recompiling my program each time. So I wrote a program that would call them up that could be easily configured. Hence AutoLaunch was born. Autolaunch by itself, launches everything in its run list (and it doesn't have to be Elite Dangerous related; AutoLaunch doesn't care. It just executes the run list) and then exits. Adding a /c (case insensitive) switch will bring up a configuration screen and I have included in the archive a shortcut just for that. Below is a screenshot for the config screen. There is no other screen to show. There's no user interface when it runs without the /c switch.
It's not usually that quite that wide, but I resized it to show the programs. I have also included the VAMonitor program in the archive for those of you who use Voice Attack. First run of that will show a File Open dialog so you can specify where your Voice Attack executable is and then run it. And yes, I have corrected the false positive concerning Windows Defender. I submitted the VAMonitor file to Microsoft for their analysis and they found no virus or malware. Windows Defender shouldn't flag it as a virus unless you are running with virus definitions that are 2 or 3 days old or more.
The EDRunChk program that closes the launcher and itself when it detects the main executable is a quick fix for me. It causes a not working error if tying to close it manually. But if you'd really like it, let me know and I'll send it to you. It has not been vetted by Microsoft, so it may show as a virus when downloaded.
You can click here to get the program. As with all new programs, smart screen will probably flag it as unknown and therefore potentially harmful. Nothing I can do about that. Just run it anyway.
The program, in config mode, creates one file in the same directory it is in, AutoLaunch.ini. This is a plain text file containing the run list, 1 item per line; the complete path including the executable.
VAMonitor creates one file, VAMonitor.ini in the same directory as the VAMonitor.exe file. This is a one line text file with the path to the voice attack executable.
Any problems and/or comments, let me know.
Last edited: