You know what, you are absolutely right. It's just been so long since I've done any coding, I have forgotten virtually everything I knew. Was just hoping to NOT eff things up too bad. LOL
- Status
You know what, you are absolutely right. It's just been so long since I've done any coding, I have forgotten virtually everything I knew. Was just hoping to NOT eff things up too bad. LOL
Well, if you just delete a thing here and there, you can't eff it up too hard, you can 'reset to default' every script and start anew.
Edit: have you already looked into this one:
https://forums.frontier.co.uk/showthread.php/311614-EDDI-Scripts-and-EDDI-enabled-VA-Commands-Thread
?
Lotsa cool examples and suggestions'n'things.
If you got special requests on how to do something, post it in there, all nice and helpful people.
Last edited:
Well, if you just delete a thing here and there, you can't eff it up too hard, you can 'reset to default' every script and start anew.
Edit: have you already looked into this one:
https://forums.frontier.co.uk/showthread.php/311614-EDDI-Scripts-and-EDDI-enabled-VA-Commands-Thread
?
Lotsa cool examples and suggestions'n'things.
If you got special requests on how to do something, post it in there, all nice and helpful people.
Wow, that is some great stuff in there! Thanks for that!! I've already used quite a few things from it. Should make it sound a lot better!
Definately will. Just be careful to not import scripts using an outdated format. API changed without warnings between some updates. But as i said, ye could always reset a script.
When you already heavily modified one to your liking and want to apply some other changes, just copy/pasta the old into a textfile before. Just saying.
Definately will. Just be careful to not import scripts using an outdated format. API changed without warnings between some updates. But as i said, ye could always reset a script.
When you already heavily modified one to your liking and want to apply some other changes, just copy/pasta the old into a textfile before. Just saying.
Yup we try very hard indeed not to do anything that will break your custom scripts, but we are only human and sometimes we eff up. If you want to backup your EDDI settings including your scripts, the directory is %APPDATA%\EDDI. If you're a techie sort, you might like to put that under version control.
Hmm, well, this is the image of the default personality. You can see that they are all grayed out under enabled so I can't do anything to them. https://imgur.com/9y82SJr
On this one, you see my test profile. I've deselected the Body Scanned part, but I can't deselect the Body Report. In fact, none of the top three are able to be unchecked. https://imgur.com/ItlsFVo It's really weird. And I can try to delete the Body Report, but it comes back when you reload EDDI.
I have deleted the Body report line from the script and will see how that works. Thanks.
EDIT: Looks like deleting that line did the trick. Thanks again. It was just becoming a bit annoying to hear that every single time. If it only did it on a configurable basis, that might be nice. Like I don't need to hear all the vulcanism and geyser reports. Just something short and sweet. I know that can't be done, so I'm good with not hearing any of it.
If instead you'd prefer EDDI to tell you about volcanism and geysers only occasionally, you can do that too. The example below modifies the same code so that it only shares volcanism and geyser info with you about a third of the time (added code is BOLD RED):
Code:
[SIZE=3][COLOR=#ff0000][B]{Occasionally(3,"[/B]
[/COLOR][/SIZE] {if reportbody.volcanism:
This planet shows signs of volcanism, with
{if reportbody.volcanism.type = 'Geysers':
{if reportbody.volcanism.amount = 'Major':
high numbers of
|elif reportbody.volcanism.amount = 'Minor':
low numbers of
}
active {reportbody.volcanism.composition} geysers
|else:
{if reportbody.volcanism.amount = 'Major':
high levels of
|elif reportbody.volcanism.amount = 'Minor':
low levels of
}
active {reportbody.volcanism.composition} magma flows
}.
}
[SIZE=3][COLOR=#ff0000][B]")}[/B]
[/COLOR][/SIZE]Regarding only being able to delete some scripts: only scripts that are directly triggered by a journal event can be deselected / disabled. 'Body scanned' is a journal event while 'Body report' is not... it's normally triggered through the code {F('Body report')} in the 'Body scanned' script.
Last edited:
Greetings,
I use EDDI with VoiceAttack and have a Question about Mission Plot Route. In 1/20 EDDI make an Mission Auto Route in Galaxy Map (Its open the Galaxy Map and set the Destination automaticly) but i dont understand how to Config that (Enable, Disable, Change how often and how to activate with Voice.
Here are all relevant Datas:
Thats the Event when i Undock (i added "L" for Auto Landing gear up after Start)
And thats the Voice Command but it never Works (Its says something about the 2 Systems but no Route)
So what i need Help is:
- How to Enable/Disable Autoroute?
- How to make that the Voice Command Works?
- How i make that its always Autoroute automaticly or only when i say as a Command?
Thanks for help and Input
Fly Save o7
I use EDDI with VoiceAttack and have a Question about Mission Plot Route. In 1/20 EDDI make an Mission Auto Route in Galaxy Map (Its open the Galaxy Map and set the Destination automaticly) but i dont understand how to Config that (Enable, Disable, Change how often and how to activate with Voice.
Here are all relevant Datas:
Thats the Event when i Undock (i added "L" for Auto Landing gear up after Start)
And thats the Voice Command but it never Works (Its says something about the 2 Systems but no Route)
So what i need Help is:
- How to Enable/Disable Autoroute?
- How to make that the Voice Command Works?
- How i make that its always Autoroute automaticly or only when i say as a Command?
Thanks for help and Input
Fly Save o7
EDDI 2.4 release candidate 1 is now available.
2.4-rc1 is available via https://github.com/EDCD/EDDI/releases/tag/Release/2.4.0-rc1 or the auto-update mechanism, if you have enabled beta access.
We think you will like this build very much. If you have any problems, please report them ASAP as we will be going ahead to release otherwise.
I would like to thank Hoodathunk and T'Kael for doing a huge amount of work in a very short time.
Enjoy.
2.4-rc1 is available via https://github.com/EDCD/EDDI/releases/tag/Release/2.4.0-rc1 or the auto-update mechanism, if you have enabled beta access.
We think you will like this build very much. If you have any problems, please report them ASAP as we will be going ahead to release otherwise.
- Exporting engineered module data to Coriolis and EDShipyard is back! (At the time of writing, EDShipyard is accepting the data but Coriolis needs just a little more time to implement it).
- Reporting of loadout changes is dramatically improved compared to 2.3.
- EDDI can once again track how many limpets you have (and there was much rejoicing).
- EDDI can now respond to many more events, see the full changelog for more details.
- EDDI can now tell you what's in a ship's fighter bays and vehicle hangars and how many SLF rebuilds you have left.
- If you scan without a DSS, the 'Body Report' script no longer falsely claims that all bodies are unsuitable for landing.
- Many things that were borked have been unborked: see the full change log.
I would like to thank Hoodathunk and T'Kael for doing a huge amount of work in a very short time.
Enjoy.
Last edited:
In line with VB’s announcement, I would like to draw our Trader’s attention that changes to the API, breaking market & outfit reporting to EDDN, has been repaired. As an added bonus, shipyard reporting (ships available for purchase) to EDDN is now functional.
Enjoy!
Enjoy!
Good news. Thanks to the three of you (and Darkcycle and JGM) for this great tool.
I would encourage everyone to try the release candidate 2.4-rc1.
We are looking to go final on it in a day or so, unless we get a show-stopping bug report.
When we go final, 2.4 will become a mandatory update i.e. we shall be killing off 2.3.x.
We are looking to go final on it in a day or so, unless we get a show-stopping bug report.
When we go final, 2.4 will become a mandatory update i.e. we shall be killing off 2.3.x.
WOOT!!! This is gr8! u guys rock! thanks so much for making eddi even more incredible
Hi, been using EDDI alongside the A.S.T.R.A. voicepack for a while now (great application BTW) and noticed a problem, the EDDI voice is a LOT quieter than A.S.T.R.A. I have set the EDDI volume to max in the app, but it's still too quiet. Is there anyway to balance the volume of the two?
Last edited:
Hi,
in my case, in VA in the settings menu/audio tab, as I adjust Audio output type to integrated components, then VA sounds/voices are the loudest. If I set it to Windows Media Components, sounds are much more subdued.
If your EDDI volume is still the weakest, adjust the volume on your speakers so, that EDDI is loud enough, and decrease volume of the rest of the apps in Windows Volume Mixer. Windows should remember these volume settings in the future (in most cases).
I think, this is because EDDI is using only the center speaker for speech in mono (I have a 5.1 system), VA uses stereo for speech, so it is filling the room more, than EDDI.
I hope, this helps with the adjustments! If you have further question, I've played around a lot with the audio things, maybe I can help
Best regards!
As far as I know the API is up. You may need to re-enter your credentials after the update however.
Could be, surely was the case sometimes before.
Could you shed a bit of light in what makes the connection to want it to re-authenticate?
If i'm not completely wrong, after some EDMC updates, in the past, i had to do this, too, but it seemed to stop long ago.
Just curious bc it seems to be on just some occasions...
:S
It isn't anything that we're doing at our end. Maybe it's Thargoids.
Ouch, I didn't know that. I'm on a 7.1 setup even. I'm using the Soundblaster MB3 software, so I can expand sound sources to surround, but still.
- Status