Version 0.95 has great recognition for dictating star systems, thanks very much!
Awesome news. From a star system dictation perspective, I'd love if people would report in if they are speakers of:
-Spanish
-French
-German
I can probably check for all of these conflicts in ocellus and offer that as a hint back to the voice attack profile. Then if you try and do a "plot route" command it can gracefully decline and say the bindings need to be non-conflicting.
I'm working on getting the non-US keybindings working first and once that's done and working i'll declare "1.0" and start on items like this.
I'm working on getting the non-US keybindings working first and once that's done and working i'll declare "1.0" and start on items like this.
Why don't you have the setup read the Keybinds file so you don't have to code for all the keyboard layouts? Wouldn't this be easier? In Switzerland, we have at least 6 keyboard layouts that are used. German, Swiss German, French, Swiss French, Italian, Romansch. I can only imagine other countries could be as bad.
--------------
It would also allow us with heavily customized binds use Ocellus.
Last edited:
Yup, I figured it out. Your FAQ can be a bit confusing... the picture only shows the Next & Previous Panel Tabs, while you must also have no competing keybindings for 'UI Left' & 'UI Right' in the Galaxy Map.
All commands are working fine. The star system recognition is cranky, as you say... looking forward to trying out 0.95!
After a certain time of running (30 min +), I'm getting 'Exceptions thrown' errors and have to restart Voice Attack to clear it. Not sure whether it's Voice Attack or Ocellus.
A list of all keybindings and their settings , too allow Ocellus Route Plotting too work ?
@nomadyow
Since verision 0.95, I've been getting an increased occurrence of "Exception has been thrown by the target of an invocation" messages. It happens shortly after I dock and the (now apparently automated) EEDN update. Once it occurs, the message comes repeatedly with even simple keypress commands and the profile/plugin is completely unresponsive.
Based on its behavior, I think I'm safe in assuming this is an Ocellus issue?
Quitting and restarting VoiceAttack clears the problem.
Since verision 0.95, I've been getting an increased occurrence of "Exception has been thrown by the target of an invocation" messages. It happens shortly after I dock and the (now apparently automated) EEDN update. Once it occurs, the message comes repeatedly with even simple keypress commands and the profile/plugin is completely unresponsive.
Based on its behavior, I think I'm safe in assuming this is an Ocellus issue?
Quitting and restarting VoiceAttack clears the problem.
For some reason my post was stuck in moderation, so let's try this again...
Since updating to 0.95, the plugin has been crashing with "UNABLE TO INVOKE PLUGIN DUE TO EXCEPTION: Exception has been thrown by the target of an invocation." shortly after docking and the plugin auto-updates with the Frontier server. The error repeats for even simple keypress commands and doesn't clear until I close and restart VoiceAttack.
Since updating to 0.95, the plugin has been crashing with "UNABLE TO INVOKE PLUGIN DUE TO EXCEPTION: Exception has been thrown by the target of an invocation." shortly after docking and the plugin auto-updates with the Frontier server. The error repeats for even simple keypress commands and doesn't clear until I close and restart VoiceAttack.
That's not the problem I'm experiencing.
Typically, shortly after I've docked, I start getting "exception thrown" messages associated with profile commands that involve Ocellus keypress commands. For example, if I say "focus game", no problem. But if I say "landing gear", then 'exceptions thrown' and the command is not executed. It feels like the keypress handling routine(s) are getting corrupted in the plugin. Closing and re-opening Voice Attack, which in turn restarts Ocellus, clears the problem until the next time.
Anecdotally, isn't "Exception has been thrown by the target of an invocation" a typical .NET error?
The concept is very awesome, but it's very much in beta and the numerous crashes of the plugin can be frustrating.
The biggest road block I see is the developer not presenting a sustained presence in this thread. For example, I mentioned many days ago about the plugin consistently crashing with "exception thrown" messages. Not a peep from the developer. He has a group of folks willing to 'beta test' and he's squandering a bunch of good will by not communicating.
@nomadyow,
FYI, I drilled down this weekend on the 'exception thrown' error and determined it's occurring right after a "Request Docking" voice command. Hard to understand how one of the keypress commands in the macro is the culprit, but that's for you to figure out. I'm close to being done with your plugin and moving on... just too many crashes with no consistent support.
Also, I received a PM from @Maddavo...
"Hi @Hoodathunk, I have seen some EDDN messages that I think have been transmitted by you using a tool called Elite: Dangerous Assistant_0.95 . I think some of the data that this tool sends to EDDN is a bit malformed so I am trying to contact the author. Would you please be able to point me to the place where you downloaded the tool? Is there a forum thread for the tool or a web address? Tks, Maddavo"
I gave him your info, so you should be hearing from him.
Cheers
I've had some time to play with 0.95, and one thing I've found is that it seems to lose track of where I am. Saying, "where am I", will often return the system that I was previously in instead of my actual location. This makes it difficult to plot a course back there since "plot route to" doesn't accept the 'current' system as a valid input.
Possibly related to this, the plugin seems to be failing to connect to the Frontier servers quite a lot. I have to re-enter my credentials using "configure plugin" to get API-based commands to work again.
Possibly related to this, the plugin seems to be failing to connect to the Frontier servers quite a lot. I have to re-enter my credentials using "configure plugin" to get API-based commands to work again.
Still can't get Ocelus to tell me where I am etc. I checkout of the debug, and it looks like it should know where I am, the system names and galactic co-ords are there. But for some reason it tells me there is a problem with the frontier API. Route plotting recognises my voice fine, but doesn't do anything other than sometimes open the galaxy map and then close it, there certainly isn't any quick input, or other VA like action going on.
Any ideas as to what's not working or why?
Any ideas as to what's not working or why?
Hmm - I'll check into this. The Frontier API is not super robust, but I can probably do more to handle those situations.
Hey Nomanyow,
Awesome app. i do keep running into an issue with the plot route command. I use a rift VR. and i can only get the command to work correctly if i am in an outpost and not a full station. so like if i can dock outside.. any station where i am inside a station the command doesn't pause long enough to go to next Ui panel and select the system entry box. so example
outpost:
acknowledges the command: plot route to and even plot rout to X
map opens
ui goes to next pannel
system entry feild is active and system name is typed in
searched
ui pane to plot
exited out of map
in station:
command accepted
galaxy map opens
ui pane to plot course
map closes.
any help would be great. i can also tell you the command does not work in open space either.. just when i am on an outpost (the stations where you land outside/on top)
Awesome app. i do keep running into an issue with the plot route command. I use a rift VR. and i can only get the command to work correctly if i am in an outpost and not a full station. so like if i can dock outside.. any station where i am inside a station the command doesn't pause long enough to go to next Ui panel and select the system entry box. so example
outpost:
acknowledges the command: plot route to and even plot rout to X
map opens
ui goes to next pannel
system entry feild is active and system name is typed in
searched
ui pane to plot
exited out of map
in station:
command accepted
galaxy map opens
ui pane to plot course
map closes.
any help would be great. i can also tell you the command does not work in open space either.. just when i am on an outpost (the stations where you land outside/on top)