This has been a very troublesome program. Cool looking when it works but I have not been able to verify how useful it is in game.
I had it running many times this morning while I troubleshot my bindings problems. It was frequently slow to move beyond the matrix screens. Occasionally it would start right away, other times it would take up to minute for the proper displays to come up. The first run of the day hung up on downloading listing.csv. But started after that. Now its back to matrix screens again with a quick flash of text appearing beforehand. So fast I can't read it on the tiny display.
I never could figure out why the bindings wouldn't take. I used the quick key assign, save and go, save. It would back up my binds file but in game it didnt seem that anything had been changed in the control setting. Using Target Event Tester the MFD's were sending keys competly different from what elite was expecting to get. Elite expected L for landing gear but pushing the mfd button yielded C.
So I am tired of this for today. Totally taking up my playing time making me grumpy.
I’m sorry to hear about your problems. Let’s see if we can work through them one by one.
When the app starts it performs a few tasks. One of these is enumerate through and test every voice on your system. It will then save this as SAPI.INI. This can take 30 seconds or so.
If you copy paste this file in it will speed up future new installs because it won’t need to recreate it.
Next, the registry is read to check the schedule for EDDB download. If you find this is taking too long (slow internet) change the settings on the explorer module (or change the registry). This will save 4 minutes of startup time for a fresh install.
The flash of text is probably the message saying journal out of date - which is due to the program waiting for a new entry in the journal files.
I’ve spent much of today looking at the code for this. If your system is running in a region with daylight savings on it potentially could affect reading the journal. The next release will have some improvements in this area - debugging the journal entries. There is a setting on the commander log settings tab to enable live journal (top check box in misc section). This option shows what entry is being read from the journal. In your version it is shown if the entry was successfully processed. In the next release it will be added weather or not it is processed.
My guess is that the journal is being read but status. Json is not. It’s this file which is responsible for setting the state of the app and switching between the screens.
I have an emulator which I wrote which creates status. json and writes journal events. I use this everyday to speed up development but I’m happy to share with you if you feel it helps workout why it’s not responding.
Similarly, the web site troubleshooting page has a tool that you can download to read key presses. It works like Elite does and consumes WM key messages. It looks similar to event tester but fundamentally different technically.
The key binding end up in XML files. Check that they contain the values you expect. Once they do, then the quick key assign can merge those changes into elites bindings file. It’s important not to rebind the Controls in elite after.
It seem unfortunate that you are having all these issues together. I’ve had a few people (earlier versions) with one of these issues but never like this.
Can you tell me if your running version 1.2?