Patch Notes Update Elite: Dangerous Update 1.05 Change Log

Status
Thread Closed: Not open for further replies.
Some server sdie fixes are a work in progress ( on the mikunn experiement thread) indicates that a few server side changes this week have been applied, and will probably be applied each business day as they drill down and make necessary changes

Right, but I hope they tell us when it's done, so we can try again the bugged systems.
 
What you need to understand is that user support / CS is a completely different department from development and programming. If a thousand people report the same bug, and you leave those tickets open, it looks like support is sitting on a thousand unworked tickets, even though they can not actually give support to those players. If I were in charge of support, the last thing I'd want is having someone elses problem sit on my desk when I do not have the tools and people to fix the problem myself to begin with.

So closing tickets with "This is a known bug that will be fixed in the future" is perfectly acceptable.

I did not see the response that the OP got from FD. The appropriate answer for a duplicate defect report is to state the active ticket's ID and state that the user should follow that ID for further updates. Not just close the ticket with no further information.
 
Also please sort out the Navigation in Galaxy Map please? You cannot plot anything over 100ly. If you want to plot a course to somewhere why cant you do it? Why do you have to revert to a web browser to plot a long route such as cmdr.club

Keep up the good work though. Looking forward to more content.
 
Added server updates to the original post:

- Fixed some issues that stopped some Commanders logging into the Companion App
- Stopped wars and civil wars in starsystems with only 1 minor faction in that state
- Added ship discount to Founders World
- Various reliability and performance improvements

Michael

Wow awesome... :) will be nice to not be fighting one sided civil wars :D
 
Hi everyone,

update 1.05 is incoming. The servers will be closed at 11am GMT to apply the update and will be down for up to 30 minutes. Here is the change log for this update:

- Fixed crash when launching limpets
- Fixed some system meta data mismatches between client and server
- Memory use improvements and fixes on server
- Fix assert when someone manages to select 'declare bankruptcy' button before UI receives proper data from the game
- Optimise mission template list selection
- When switching servers do not disconnect during the transfer
- Added telemetry for when a player dies to help identify cause of death when players explode near stations
- Added further telemetry to trace failed resource loading
- Fix large quantity missions using "light cargo" text
- Fix salavage coms lines
- Correct reputation on abandon branch of pirate missions
- Fix incorrect destination for massacre branch money collection
- Fix salvage mission branching
- Change order of mission contracts in massacre missions
- Change data that is displayed to players in massacre missions

Server Updates:

- Fixed some issues that stopped some Commanders logging into the Companion App
- Stopped wars and civil wars in star systems with only 1 minor faction in that state
- Added ship discount to Founders World
- Various reliability and performance improvements

Thanks!

Michael

Hi Michael. There's a comms bug (haven't downloaded the new patch yet) whereby when you click to message a player, it automatically tries voice connect and you cannot disable it via the cancel voice chat button.
 
I did not see the response that the OP got from FD.
Here is the response from FD relating to my ticket:
Thank you for raising this issue with us. We are currently looking into this problem and we have a bug in our database.
I will resolve the ticket for now. If you have any other problems, please let us know!
 
There seem to be a lot of whiners here that don't understand development.

Do you really think that every single person in the dev team is working on the same bug/issue until it is squashed in some sort of objective priority list? No, there are going to be different people working on different things, and certain fixes/updates are going to be available before others. Some (seemingly minor) bugs may need input from various people, some may require changes to different (seemingly un-linked) game systems/mechanics which may need a lot more development and testing time.

Give the guys a break. If there are updates to some bugs that can be easily deployed via a minor update then why would they hold back just because they have other bugs still unresolved?
 

Michael Brookes

Game Director
Does this address the 2 issues u mentioned earlier in the week surrounding influence factors over solar systems. The one with a faction expanding to a nearby system and anotehr surrounding some of the influence and meta data not taking effect ? or is that being held for a later date

We're still working on fixes for these two issues.

Michael
 
Also please sort out the Navigation in Galaxy Map please? You cannot plot anything over 100ly. If you want to plot a course to somewhere why cant you do it? Why do you have to revert to a web browser to plot a long route such as cmdr.club

Keep up the good work though. Looking forward to more content.

Yes you can. Done it loads of times. You just have to wait a little for it to become available while the nav computer does the calculations. Only takes about 10-20 seconds maybe, maybe less. never timed it.
 
Thanks for the regularity of minor bug fixes. I am sure you're working hard on not only stamping out yet more bugs, but also providing more content and features. I much prefer this schedule of frequent drips and drops of patches, than waiting for ages until a 'mega-patch' is ready. Besides, in my experience, big patches usually require a hot-fix or two pretty soon after release.

Keep up the good work making a great game even better :)
 
That's interesting, I thought it was already working. I went there the other day to see what price they were charging for a Python, and their price was around 51M - about 10% less than the wiki average price of 56M. If the discount was broken then, I wonder if that would make their Python 46M (10% off the 51M they had earlier). Maybe the wrong discount was only on some of the ships. Will be keen to find out.

Could you give some clarification, Michael? Thanks.
Yea, I would like to know more about this too. I was playing 1.03 over the holidays and saw all the ships were discounted at the Founder's World (Shinrata Dezra). I didn't try to buy any though. Perhaps the advertised price wasn't what they were actually charging when you came to buy them and the bug has now been fixed? It would be nice to know what's happening here.
 
And does that include refunding those of us the discount, who ended up paying full price instead of the discounted price M.B., or do we just have to lump it.

Probably "lump it" since FD have said in the past that players were not intended to get a discount and that the bug was in the displayed prices indicating that players would.

Here's a FD pick the right answer list:

2. We are aware of the landing pad issue but other issues are more important.
Answer is probably "two" (or babelfisch's "six"!) since even if the numbers disappear, our direction indicator still works fine, making it pretty easy to line up our ship with the correct pad.
 
I did not see the response that the OP got from FD. The appropriate answer for a duplicate defect report is to state the active ticket's ID and state that the user should follow that ID for further updates. Not just close the ticket with no further information.

I dont know where you got that from, but it is just wrong. Never used the ticket system here, but normaly tickets between support and you are private, there is no open ticket pool where every visitor could follow your ticket. If your ticket is a bug report it should get closed, regardless if you are the first to report. Bug reports are not 2-way tickets. You report it, they note it and you are done with it. You can now wait for the next patch and hope its fixed there. There is now reason to leave it open as it will not change anything.
The only case where a ticket should stay open is when you have an individual issue, for example a failed server transaction, where either the support or you needs further information. That is not the case with bug reports.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom