I'll take a look at this. To be clear, you only have one fuel tank, the internal one?
I'll take a look at this. To be clear, you only have one fuel tank, the internal one?
0.9 Released
0.9
New OcellusPlugin.dll released
New VoiceAttack Profile
New configuration items added. Say "configure plugin" to configure them
New Functionality:
- EDDN updates will happen in the backround if the netlog indicates the ship is docked
- Get current Star system and coordinates from the netlog where possible
- Optionally make announcement on plugin startup
- Check for plugin updates in the background
- Speed up "distance from here" commands by avoiding querying Frontier API if we can get the system from netlog
- Change all profile Text-To-Speech to a single commands so that it is easier to change voices for the entire profile
- Move all keybinding error reporting in the profile to a single command "error - keybinding" to make custimization easier
- Added "text to speech" profile command
- Make eddb indexes download weekly instead of daily
Plugin Bugs Fixed:
- Fixed Reinforced Alloy in Coriolis/EDshipyard
- Now works with non Custom control bindings
Profile Bugs Fixed:
- Fix grammatical problems in plot route to ship commands
Known Issues:
- Some keys on non-US keyboards/languages are not mapped properly. Message me if you can be a tester for this.
- Not all PowerPlay weapons will show up in Coriolis/EDShipyard exports. Email me your companion.json file if you have this issue.
0.9
New OcellusPlugin.dll released
New VoiceAttack Profile
New configuration items added. Say "configure plugin" to configure them
New Functionality:
- EDDN updates will happen in the backround if the netlog indicates the ship is docked
- Get current Star system and coordinates from the netlog where possible
- Optionally make announcement on plugin startup
- Check for plugin updates in the background
- Speed up "distance from here" commands by avoiding querying Frontier API if we can get the system from netlog
- Change all profile Text-To-Speech to a single commands so that it is easier to change voices for the entire profile
- Move all keybinding error reporting in the profile to a single command "error - keybinding" to make custimization easier
- Added "text to speech" profile command
- Make eddb indexes download weekly instead of daily
Plugin Bugs Fixed:
- Fixed Reinforced Alloy in Coriolis/EDshipyard
- Now works with non Custom control bindings
Profile Bugs Fixed:
- Fix grammatical problems in plot route to ship commands
Known Issues:
- Some keys on non-US keyboards/languages are not mapped properly. Message me if you can be a tester for this.
- Not all PowerPlay weapons will show up in Coriolis/EDShipyard exports. Email me your companion.json file if you have this issue.
Is this possibly due to the next/previous tab keybinding conflict that @nomadyow talks about in his FAQ?
@nomadyow,
I'd mentioned in a previous post that the "Plot Route to" functions seemed a bit funky in that it does not actually plot the route after it acknowledges the system, opens the galaxy map, and enters the dictated system into the text box... it only 'selects' the target system and then drops out.
I checked the 'executeplotroute' command code and it exectues one 'ui-right' and one 'ui-select' command, which only selects the system. Shouldn't it be two 'ui-right's and one 'ui-select' to lay in the plot?
While I'm at it, I would like to reiterate my request to make available more of the API data.
The ability to monitor a verbose netlog to get real time environment data such as normal space vs supercruise would also be extremely useful.
Bottom line, I would like a one-stop-shop type of plugin, negating the need to also run EDDI.
Thanks for your continued efforts!
I'd mentioned in a previous post that the "Plot Route to" functions seemed a bit funky in that it does not actually plot the route after it acknowledges the system, opens the galaxy map, and enters the dictated system into the text box... it only 'selects' the target system and then drops out.
I checked the 'executeplotroute' command code and it exectues one 'ui-right' and one 'ui-select' command, which only selects the system. Shouldn't it be two 'ui-right's and one 'ui-select' to lay in the plot?
While I'm at it, I would like to reiterate my request to make available more of the API data.
The ability to monitor a verbose netlog to get real time environment data such as normal space vs supercruise would also be extremely useful.
Bottom line, I would like a one-stop-shop type of plugin, negating the need to also run EDDI.
Thanks for your continued efforts!
Edit:
Disregard the 'problem' mentioned my last post...
Learning opportunity here... NO galaxy map keybindings may conflict with any UI keybindings... left, right, next, previous, in particular
Disregard the 'problem' mentioned my last post...
Learning opportunity here... NO galaxy map keybindings may conflict with any UI keybindings... left, right, next, previous, in particular
Last edited:
Ok will do
EDIT , testing at desktop with commands , that work , like " where am I' ect
Well it did crash ,. badly , had to get the backup dat file ... BUT , I think it was another plugin , I remember someone saying there was a memory leak possibly with , AER, https://github.com/SingularTier/AerSpeech/releases never had any issues, with AER until this crash ( or the one I thought was EDDI ), and it was an out of memory error, so Ive disable it
AER is good works well but it's old and not update ,and since disabling AER , and using the same Ocellus commands that brought the crash on , VA has been stable...
The reason I thought it was EDDI , was the API calling , AER works differently , no API
Will test further in game , now desktop testing is stable
UPDATE , in game , the Plot Route , did not work , keys setup as per instruction.. would open map and move slightly , on the map page , but never highlight , where you input system name ,if its supposed too do this... Sometime it would open the starport commodities tab
The Route Plotting is all I tested as that's all I would use. When saying Plot route to "Witchhaul , VA never understood me, Or 'sol" and a few others.
The command Plot route too 'Hauler' was understood , but as I have two , Ocellus would ask, which one , this is way too fast , Ocellus was jumping between the two choices, not giving me time too respond. Nor was it loud enough too hear ( unless I turn master volume up ) given , what was been asked said. I did manged too choose a Hauler , but the Mapping of the route did not happening
Ocellus was stable no crashes or other issues . I have not looked inside the VAP too see what I could change on the timing , or if I can increase volume when sentence I need to hear happen...yet
Last edited:
If you're able to get the galaxy map to open with 'Plot Route To', then I would check the command log to see if there are any errors about unbound keys. If you can't get any systems to work at all, then it might be due to the same bug I had (which Nomad will be fixing at some point in the future). You're only option is to wait in that case.
Hi,
Probably a good time to provide a status update.
1) Star System recognition engine. IncKursion was a great help. I have an interim solution to get the recognition engine working for non US. I'm working through the "right" way to fix this so that it will use the Windows speech engine appropriate for your language.
2) Keyboards. I understand what needs to be done there - that is the #2 task to get working. I will be sending our a request on this thread for keyboard testers soon.
These are the two main blocker features before I consider Ocellus "release" worthy, and then it will be on to new feature content. Other smaller issues will get patches as they are discovered.
Nomad
Probably a good time to provide a status update.
1) Star System recognition engine. IncKursion was a great help. I have an interim solution to get the recognition engine working for non US. I'm working through the "right" way to fix this so that it will use the Windows speech engine appropriate for your language.
2) Keyboards. I understand what needs to be done there - that is the #2 task to get working. I will be sending our a request on this thread for keyboard testers soon.
These are the two main blocker features before I consider Ocellus "release" worthy, and then it will be on to new feature content. Other smaller issues will get patches as they are discovered.
Nomad
@IncKursion
I have a Suggestion .. Can you separate the Profiles , FULL VERSION and just the ROUTE PLOTTING Version
Reason is most players who have VOICE ATTACK already have Profiles VAPS ,VOICE PACKAGES , that do all the normal commands
Your ROUTE PLOTTING is something players really can use given VR , it is whats missing
I do suggest that EDDI and your Profile don't double up
Full VERSION , is everything , no need to run EDDI (can if you want )
ROUTE PLOTTING can run EDDI
I have a Suggestion .. Can you separate the Profiles , FULL VERSION and just the ROUTE PLOTTING Version
Reason is most players who have VOICE ATTACK already have Profiles VAPS ,VOICE PACKAGES , that do all the normal commands
Your ROUTE PLOTTING is something players really can use given VR , it is whats missing
I do suggest that EDDI and your Profile don't double up
Full VERSION , is everything , no need to run EDDI (can if you want )
ROUTE PLOTTING can run EDDI
Last edited:
Yes, "Plot Route To" would be very handy in VR. This is the feature I look forward to most to get working. These are the button presses I use to plot a route in VR:
1. Enter galaxy map
2. "Next Panel Tab" then "UI Panel Select" to navigate to the search menu
3. key in the system that was dictated. Then "UI Panel Select" to commit the search
4. "UI Panel Right" then "UI Panel Select" to select "plot route"
Also, I captured the output of what was coming out of "Plot Route To" and it seems like there is very little delay between key presses, may try adding some?
Edit: Just to be more clear, I have the same issue as sutex while in VR, galaxy map opens, jumps around a bit, but nothing selects and sometimes the galaxy map closes, opening commodity window.
Edit edit: Just found my issue. I had a colliding button in the galaxy map UI control settings. Works now!
1. Enter galaxy map
2. "Next Panel Tab" then "UI Panel Select" to navigate to the search menu
3. key in the system that was dictated. Then "UI Panel Select" to commit the search
4. "UI Panel Right" then "UI Panel Select" to select "plot route"
Also, I captured the output of what was coming out of "Plot Route To" and it seems like there is very little delay between key presses, may try adding some?
Edit: Just to be more clear, I have the same issue as sutex while in VR, galaxy map opens, jumps around a bit, but nothing selects and sometimes the galaxy map closes, opening commodity window.
Edit edit: Just found my issue. I had a colliding button in the galaxy map UI control settings. Works now!
Last edited:
It would be very useful if I could say "Plot Route to" inside the galaxy map with the plugin understanding that I am already in the galaxy map. Pressing "Open Galaxy Map" while it is open closes it. If the plugin does not understand that, a hacky way to get the same functionality is to hit "UI Back" before opening the galaxy map at the beginning of the sequence so that the already open galaxy map would close. Hitting UI back with no UI open does nothing, so it should be safe to press in any case. Maybe press it a bunch of times to clear out all the open UIs. 
IMO, there are two areas in which Ocellus adds value... Voice assisted route plotting, as you rightly mention, and automated keybind mapping.
I think there would be a difficulty in separating the route plotting from the automated keybinding. Regardless of concocting a selective mixture of personal, EDDI, VoicePack, or Ocellus voice commands, you will either have to modify all non-Occellus commands to utilize the Ocellus keybind commands or you will have a measure of 'command bloat' from having both Ocellus kebind definitions and your own. Neither is particularly attractive, but ultimately a matter of personal choice and a lot of work.
That said, I opted for modifying/re-writing my non-Ocellus commands to use Ocellus keybind commands and being very mindful of keeping the 'bloat' down to make it manageable.
Last edited:
0.95 Released
Version 0.95 released
New OcellusPlugin.dll released. Download it HERE
New configuration items added. Say "configure plugin" to configure them
New Functionality:
- Added Error Text-To-Speech notifications
- Added star system recognition engine engine readiness notifications. An option text-to-speech or wave file (default action) is played when the recognition engine is loaded.
- Reduced memory consumption of plugin by 40%
Plugin Bugs Fixed:
- Fixed broken background loading of recognition engine. Plugin loads much quicker now. - Star map speech engine should now initialize properly for non English users
Profile Bugs Fixed:
Known Issues:
- Some keys on non-US keyboards/languages are not mapped properly. Message me if you can be a tester for this.
- Not all PowerPlay weapons will show up in Coriolis/EDShipyard exports. Email me your companion.json file if you have this issue.
Version 0.95 released
New OcellusPlugin.dll released. Download it HERE
New configuration items added. Say "configure plugin" to configure them
New Functionality:
- Added Error Text-To-Speech notifications
- Added star system recognition engine engine readiness notifications. An option text-to-speech or wave file (default action) is played when the recognition engine is loaded.
- Reduced memory consumption of plugin by 40%
Plugin Bugs Fixed:
- Fixed broken background loading of recognition engine. Plugin loads much quicker now. - Star map speech engine should now initialize properly for non English users
Profile Bugs Fixed:
Known Issues:
- Some keys on non-US keyboards/languages are not mapped properly. Message me if you can be a tester for this.
- Not all PowerPlay weapons will show up in Coriolis/EDShipyard exports. Email me your companion.json file if you have this issue.
Hi there, started using your pack today, and while it looks like it could be very good, I'm having a few issues. I can get it configured fine (verified and authenticated), and it understands what I am asking, but the route plotting doesn't really do much other than open the galaxy map, move the cursor a little then close the map, certainly didn't do what was in the demo vid. Also having problems with the frontier API apparently - "Where am I?" and the various other commands don't work, with the where am I one resulting in an error
Code:
22:34:57 - Error: Cannot reach the Frontier server. Consider saying "Configure Plugin" to solve the problem.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.
Last edited: