The default personality just gives the headline, although if I remember correctly the entire article is there in the 'content' variable so you could alter the script to use that in place of 'title'. It's on my list of things to tidy up, but will take a bit of work because you probably don't want to hear the status reports and the like.
1- no, test is ok
2- disable "distort voice on ship damage" did the trickNo boom now
Well, it seems v2.0.5 won't remain running very long if I have the Netlog monitor or ESDM responder active. With those active, it crashes the moment it tries to announce leaving Supercruise at the final destination, or immediately after entering frame-shift, when attempting to announce details of the next jump point. There's nothing in the logs that seems out of sorts, it just... crashes and burns.
Yes, I have pointed the Netlog monitor to the game's storage location point (the Obtain button worked just fine), and I have created and entered the API key and Commander name for EDSM. Simply having those active seems to be what is ruining EDDI's day.
Well, it seems v2.0.5 won't remain running very long if I have the Netlog monitor or ESDM responder active. With those active, it crashes the moment it tries to announce leaving Supercruise at the final destination, or immediately after entering frame-shift, when attempting to announce details of the next jump point. There's nothing in the logs that seems out of sorts, it just... crashes and burns.
Yes, I have pointed the Netlog monitor to the game's storage location point (the Obtain button worked just fine), and I have created and entered the API key and Commander name for EDSM. Simply having those active seems to be what is ruining EDDI's day.
Just in time for the weekend comes version 2.0.6 of EDDI. Lots of stability changes, namely:
- Update ship information when undocking
- Retain ship information between relogs
- Attempt to avoid crashes when configuration files have been corrupted
- Avoid potential crash when network request times out
- Added keepalive harness to monitor threads to catch errors and restart when appropriate
- Strip SSML tags if SSML speech fails, then try again
- Add material IDs for previously-known materials
- Attempt to avoid bad voices that could crash EDDI
- Fall back to standard speech if SSML isn't working
- Add configuration option to avoid SSML altogether
- Updated troubleshooting guide
- Updated VoiceAttack system variables
Download from the usual place, and any issues please let me know.
The commodity check is dependent on two things. First, you need to have data on the local station so will need to have configured the "Companion App" tab in EDDI.exe. Second, it will only talk about commodities if your ship is designated to either the "Multi-purpose" or "trading" roles, otherwise it assumes that you aren't interested in this information and so doesn't provide it. You can set the role in the "Shipyard" tab in EDDI.exe.
Hopefully one of these two will fix your issue. If not then please let me know.
Hiya! I'm not at home at the moment, but I can tell you it would crash when entering frame shift, when a few times it had been able to give me the complete rundown on the system I was jumping to, then just started crashing at that point for some reason.Also...what is your OS, and what voice are you using?
A number of voices are not supportable in EDDI due to their lack of phonetic speech or the fact that some langauges are 64-bit only and EDDI runs in 32-bit mode.
eddi 2.0.5 and 2.0.6 keeps crashing, jumping to a systema and/or exiting supercruise :| any hint? w10x64
I'm having an issue with Voice Attack. I installed EDDI into the APPS directory, started EDDI, configured it. It works great by itself. Shut EDDI down, start VA, make sure Enable Plugins is on, and make a profile called EDDI 2, then import the file. Restart VA, nothing. Restart computer nothing... It says Plugins Enabled, but it never gives a message about EDDI starting the way it did with the older version when we loaded in the start bit each time.
I should perhaps note that my VA isn't installed in the default, it is on the E drive, but otherwise it's the same.
Had the exact same problem this evening, and like you tried all the obvious, checked logs, used the ctrl+alt+shift+e shortcut in the voice attack window and the plugin would not load or respond.
However I did install the beta version straight over the top of the current version and plugin loaded straight away, profiles were all still intact, and seems to be working fine for me now.