2.0.12 hasn't been officially released, so if you pulled down EDDI.exe it will be 2.0.11.
- Status
2.0.12 hasn't been officially released, so if you pulled down EDDI.exe it will be 2.0.11.
No, it's my fault. I pushed the release but haven't had time to update the server with the new links etc. Tomorrow, with any luck.
Do you have a detailed surface scanner on board? The game doesn't put information in the journal without it.
And yes, the API is often out of date, especially with the more real-time informs such as damage and ammo counts.
Nowhere to put Cottle templates but feel free to share them here.
JDM,
Can the Galnet moitor do more than just read you the headlines? This is a request, not a question, even though I phrased it in the form of a question, it's still not a question. Got it?
Can you add features to actually read the articles?
Can the Galnet moitor do more than just read you the headlines? This is a request, not a question, even though I phrased it in the form of a question, it's still not a question. Got it?
Can you add features to actually read the articles?
Ok here is my "Commander progress" script. It happens when you have the orange spinning ship. Just replace the default with this.
Update from the Pilot's Union.
It reads:
Dear Commander,
We are very glad to have you back in service... It's been a while, and many things have happened whilst you were away..
More than ever before maintaining peace and protecting our peoples requires us to be out there, in the black, patroling vigil-lently.... We must be always ready to Smash those that seek to do us harm..
In these, most difficult, and, pressing times I wish you good luck. and... Fly-safe Commander.
Update from the Pilot's Union.
It reads:
Dear Commander,
We are very glad to have you back in service... It's been a while, and many things have happened whilst you were away..
More than ever before maintaining peace and protecting our peoples requires us to be out there, in the black, patroling vigil-lently.... We must be always ready to Smash those that seek to do us harm..
In these, most difficult, and, pressing times I wish you good luck. and... Fly-safe Commander.
Here's my "Bounty awarded" script.
{Pause(3000)}
{OneOf(
"You destroyed a ship of the {(event.faction)} fleet.",
"You just killed some {(event.faction)} scumbag.",
"You broke his space ship.",
"Those {(event.faction)} scum will have to float their way home.",
"Apology accepted you {(event.faction)} scum.",
"Frying tonight.. {(event.faction)} ships.",
"Those {(event.faction)} ships explode very nicely.",
"The {(event.faction)} pilot just ejected.",
"You certainly punched his ticket.",
"That guy should have been more respectful.",
"We got 'em, yeah!. We got 'em.",
"That pilot won't be getting his bounty vouchers any time soon.",
"{(event.faction)}.. Don't send anymore of your ships after me.",
"{(event.faction)}.. One of your pilots is missing.",
"{(event.faction)}.. There were no survivors from that ship.",
"{(event.faction)}.. I hope your escape pods malfunction. "
)}
{Pause(1500)}
{if len(event.rewards) = 1:
{OneOf("Bounty voucher","Voucher","Bounty")} of {Humanise(event.reward)} credits received from {P(event.rewards[0].faction)}
|elif len(event.rewards) > 1:
{len(event.rewards)} {OneOf("Bounty vouchers","Vouchers","Bounties")} received for a total of {Humanise(event.reward)} credits
}
{if event.shared:
to share between yourself and your wing-mates
}.
{Pause(1500)}
{F("Damage check")}
{Pause(3000)}
{OneOf(
"You destroyed a ship of the {(event.faction)} fleet.",
"You just killed some {(event.faction)} scumbag.",
"You broke his space ship.",
"Those {(event.faction)} scum will have to float their way home.",
"Apology accepted you {(event.faction)} scum.",
"Frying tonight.. {(event.faction)} ships.",
"Those {(event.faction)} ships explode very nicely.",
"The {(event.faction)} pilot just ejected.",
"You certainly punched his ticket.",
"That guy should have been more respectful.",
"We got 'em, yeah!. We got 'em.",
"That pilot won't be getting his bounty vouchers any time soon.",
"{(event.faction)}.. Don't send anymore of your ships after me.",
"{(event.faction)}.. One of your pilots is missing.",
"{(event.faction)}.. There were no survivors from that ship.",
"{(event.faction)}.. I hope your escape pods malfunction. "
)}
{Pause(1500)}
{if len(event.rewards) = 1:
{OneOf("Bounty voucher","Voucher","Bounty")} of {Humanise(event.reward)} credits received from {P(event.rewards[0].faction)}
|elif len(event.rewards) > 1:
{len(event.rewards)} {OneOf("Bounty vouchers","Vouchers","Bounties")} received for a total of {Humanise(event.reward)} credits
}
{if event.shared:
to share between yourself and your wing-mates
}.
{Pause(1500)}
{F("Damage check")}
This is on the list to do. The current version as below can be used, but it reads everything and a lot of the articles are dumps of information. For the final version I'll filter them out so that you only hear the content of the more interesting articles.
Code:
{if len(event.items) = 1:
A new Galnet article has been published, entitled {event.items[0].title}.
It reads {event.items[0].content}.
|elif len(event.items) > 1:
{len(event.items)} new Galnet articles have been published.
{set item to 0}
{while item < len(event.items):
{if item = 0:
The first is entitled {event.items[item].title}, and reads {event.items[item].content}
|elif item = 1:
The second is entitled {event.items[item].title}, and reads {event.items[item].content}
|elif item = len(event.items) - 1:
The last is entitled {event.items[item].title}, and reads {event.items[item].content}
|else:
The next is entitled {event.items[item].title}, and reads {event.items[item].content}
}
{set item to item + 1}
}.
}Please could you hit the 'Send EDDI logs to developers' button on the main EDDI tab to send me a log so that I can see what the crash reported? Thank you.
Is it possible to change the moment EDDI checks for new articles ?
I use EDDI with VA. I first start VA and than ED but as soon as VA starts it tells me there are new articles even before ED started.
Would it be possible to combine the Galnet check with the "Commander continued" event so that I'm aboard my ship when I hear about the new Galnet articles.
Or maybe even a seperate VA-command so that I can pick the moment Galnet is checked myself (when on a long SC journey for example)
There have been a fair few changes internally between 2.0.11 and what will be 2.0.13, so I'm requesting beta testers for this release. If you are interested then please download http://www.mcdee.net/elite/EDDI-beta.exe. Note that the it will report itself as version 2.0.12.
The biggest internal changes have been around the speech subsystem, where there have been on-going reports of crashes that I haven't been able to track down. I've put a lot more defensive code in place as well as a new exception reporting system, so even if it does still crash I should be able to track down root cause. It also provides various enhancements that people have asked for but caused more code disruption than I would normally have liked in a minor release. All of this leads me to be a little wary, hence the beta status of this for the moment. Once I have some feedback on how it's going I'll re-evaluate promoting this to being an official release.
If you do want to give this a test, please drop a note here to say you're testing it, and another when you either see a crash or you play for a significant chunk of time (several active hours) without a crash. This will allow me to gauge how well the code is holding up. Also, if you do have a crash please use the 'Send EDDI logs to developers' button on EDDI's UI to send over your logs for investigation. Thank you.
The full changelog is as follows:
The biggest internal changes have been around the speech subsystem, where there have been on-going reports of crashes that I haven't been able to track down. I've put a lot more defensive code in place as well as a new exception reporting system, so even if it does still crash I should be able to track down root cause. It also provides various enhancements that people have asked for but caused more code disruption than I would normally have liked in a minor release. All of this leads me to be a little wary, hence the beta status of this for the moment. Once I have some feedback on how it's going I'll re-evaluate promoting this to being an official release.
If you do want to give this a test, please drop a note here to say you're testing it, and another when you either see a crash or you play for a significant chunk of time (several active hours) without a crash. This will allow me to gauge how well the code is holding up. Also, if you do have a crash please use the 'Send EDDI logs to developers' button on EDDI's UI to send over your logs for investigation. Thank you.
The full changelog is as follows:
- Fix issue where engineer rank journal message without rank would cause a crash
- Allow non-string sample events for testing scripts
- Add sample galnet news event for testing
- Do not throw spurious errors when shutting down
- Avoid bug in journal where superpower promotions are logged as combat promotions
- Update shield resistances with booster stats when exporting ship
- Add body information to speech responder
- Add system main star stellar class and age to VoiceAttack variables
- Fix commander progress "trade" rating
- Disable "distort voice on damage" effect until we can find a better distortion process
- Add separate exception logging system
- Fix incorrect name for Type-7 when exporting to Coriolis
- Send raw ship JSON directly to Coriolis for import rather than use local processing
- Update 'Jumping' script: add warning if jumping to known white dwarf or neutron star
- Update 'Body scanned' script: fix typo where 'higher' was written 'higer'
I'll have a think about how to conditionally trigger the check.
Will do, the beta notes look like it could help in that case, so i will participate.
Another thing that irritated me: sometimes the pauses in the scripts seem to be ignored.
Like, when docking, it confirms directly on touchdown, no matter what i set the pause to.
Sometimes restarting EDDI fixes this. Will investigate further this evening.
This is an incredible piece of work you've done here!
Hats off to you.
Still trying to figure out the syntax for the following:
On commander continue, it says e.g. 'welcome back your grace' when in empire space.
I tried to put that function in a OneOf, with a fixed text like 'welcome back, general', but got script errors.
Changing the function to a second, fixed text worked. So can't both modes used together?
Not on PC atm, eventually i'll post the syntax later for better understandment.
edit: uploaded log after the standalone crash on exit, using the beta.
Last edited:
I'm testing the Beta now. Didn't have crashes before but I'm using VA and only use Eddi-standalone to edit scripts so maybe that's why I didn't have crashes in release and, so far, in Beta. I'll try it without VA later today.
What I did try out is the warning if jumping to a known white dwarf or neutron star. I filter the map to only show them and the first one I jumped too (LAWD 27) didn't give the warning but the second one (BPM 890) did. The first is stellar class DQ and the second is DA so I looked at the script but I saw you only check for the first letter so that couldn't be it. Then I looked them up in both EDDP and EDDB and there I found the problem.
The stellar class of LAWD 27 isn't available in both. While typing this I think you're already aware of this because it says "..if jumping to known white dwarf..".
While checking this out I also used the system main star stellar class variable in VA but it seems that isn't updated when the stellar class of the star you're jumping to is unknown.
During the jump I had VA call out the name and the class of the star and the name was updated while jumping but for the stellar class it gave the class of the last star with a known class (so it said LAWD 27, starclass T). Would it be possible to change the value EDDI gives for the system main star stellar class variable to "unknown" when the stellar class isn't known. That way it would be possible to include it in the warning like "warning: the next star could be dangerous because I can't get the stellar class" or something like that.
Is it possible to write a variable to a .txt file?
I have an idea for streaming that I would like to try out one my internet connection has been upgrade and I'd love to have the variables written to a .txt file that OBS or other streaming software and pick up and display.
I got a feeling I could adjust the Jumping, Jumped, etc to do this but I have no idea how to write a .txt with the variablesin EDDI {event.system}... etc
I can work how to do it in VA but I would like to have it EDDI 2.
I know its probably something simple to write a .txt file but I have no idea
Cheers for the hard work jgm and everyone else.
I have an idea for streaming that I would like to try out one my internet connection has been upgrade and I'd love to have the variables written to a .txt file that OBS or other streaming software and pick up and display.
I got a feeling I could adjust the Jumping, Jumped, etc to do this but I have no idea how to write a .txt with the variablesin EDDI {event.system}... etc
I can work how to do it in VA but I would like to have it EDDI 2.
I know its probably something simple to write a .txt file but I have no idea
Cheers for the hard work jgm and everyone else.
Elite doesn't provide the star's class anywhere in the journal unless it is unknown and then scanned with a detailed surface scanner, so if it isn't in EDDB then EDDI can't report on it.
If you find such a star you can add it's information directly to EDDB by clicking the 'Fix it on ROSS' link at the bottom of the relevant EDDB page.
EDDI should unset the stellar class if it isn't known; I'll take a look at this and fix it.
- Status