Imports Expedition, but won't plot

[Akquar]

Hi, amazing idea for a very annoying VR issue, thanks :) I get a voice confirmation of the expedition import, gives the correct stats of hops an planets. "Get Next System" returns the correct name, but "Find Next System" does not open the map or plot it. I am using custom control binding file for my X52 HOTAS and the Ripley Galactic KICS 4 voice pack for VoiceAttack. My suspicion is a mismatch key binding, but I can not figure it out. Any advice would be greatly appreciated, I have spend a whole Saturday on this, but am now at a loss.

[alterNERDtive]

Did you follow the setup instructions?

Are you using a non-US keyboard layout?

[hallah60]

Hi Akquar - I agree this sounded a great fix for exploration in VR, ATBH even without VR this would be a great help However I had same issue, using X-55, but also think its a key binding thing, or rather the speed of sending the keys. If i open notepad i can see the keys being sent but in Elite either nothing happens or map opens but no text entered I have looked at the json file and changed some of the values Currently tried "GalaxyMapOpenDelay": "5000", "GalaxyMapUINavigateDelay": "500", "KeyDownDuration": 100

And this seems to work - however have no idea what these do so please can someone advise.

Thanks H.

[Stickymaddness]

@hallah60 As you suspected, it's usually to do with the speed that the keys are sent at. Elite runs at different performance levels on different PCs, which is why it's configurable. You were on the right track with the settings you changed,

GalaxyMapOpenDelay is how long Sextant should wait (in milliseconds) after opening the galaxy map, before hitting the next key to fill in the system name. A setting of 5000 means Sextant will wait 5 seconds.

GalaxyMapUINavigateDelay is how long Sextant should wait (in milliseconds) between keypresses when navigating the galaxy map. For example:

• Next UI Panel shortcut key
• Wait 500ms
• UI Select shortcut key
• Wait 500ms

KeyDownDuration is how long (again, in milliseconds) Sextant should "press" keys down when sending commands.

The key thing to note is that if Sextant sends the commands too quickly, for example pressing the Next UI Panel key before the galaxy map has opened, Elite will ignore those keypresses completely. A higher GalaxyMapOpenDelay value solves this by making Sextant wait longer before sending the next keypress.

What values to use are completely dependant on your system and its performace. As a starting point you can try time how long it takes Elite to open the galaxy map on average, and add a second or two extra to that time, and set that as your GalaxyMapOpenDelay. Once everything is working, you can always lower the timings until it feels natural.

I hope this helps, and clarifys how the settings work.

[hallah60]

Hi Stickymadness,

Thanks for clarifying, and thanks for an amazing app, just off to test fly. Is it possible to use HCS Voice Packs or dont they support Text to Speech ?

H.