Patch Notes Update Server Update Incoming - 19.06.2015

[Del-Dredd]

I think he means the majority of issues that are currently in the game were identified during the 1.3 beta and should have been fixed before it was released, this 'test it for a week then sling it out' approach to updates is ridiculous. I would much rather wait for big updates like 1.3 to be tested properly than be left with the largely broken game we've had for the last two weeks.

That is what I would like as well, although it has been same since Premium Beta, test - bugs reported - release anyway and then have big issues (or should that be bug issues) in some cases major fupars.

 

[TruffleSnout]

I think he means the majority of issues that are currently in the game were identified during the 1.3 beta

Some of them were, but the repair/integrity costs? While they may have been there in beta, they were not identified as issues. Because all that stuff is based on a % of ship/module base cost, and during beta all ship and module base costs are dropped to below-dirt-cheap so everyone can afford to purchase them for the purposes of testing. There was no way for the beta testers to realize that repair costs were out of line.

 

[bitstorm]

Thank you Michael,
Is there any chance that there may be a change to the RES spawn rates? Currently it is very hit and miss, sometimes I can have a continuous flow of wanted ships other times I am sitting twiddling my thumbs for extended periods of time. The later doesn't make for much fun at all.

I think that was caused by the server network issues.

Servers were taking a long time to respond, as a result spawns into an instances were happening very very slowly. =(

I expect spawn rates this will be fine after today's patch.

 

[CMDR xX_Phaethon_Xx]

Which system?
What is your commander name?
What time?

Thanks

Michael

Michael, the poster is referring to their detailed-surface-double-scan-o-matic scanning stars and subsidiaries twice within every system they have unexplored stars and subsidiaries to scan.

 

[TomoRosso]

That is what I would like as well, although it has been same since Premium Beta, test - bugs reported - release anyway and then have big issues (or should that be bug issues) in some cases major fupars.

IIRC there was a delay to the 1.3 beta and Michael said it was necessary to sort out some issues and they didn't want to give us a game that was broken (large dollop of paraphrase but you get the idea), but despite the delay that's exactly what we got.

 

[bogdan.pascu]

Will we receive any news about fixing the rank progression missions? By this time I think I have done about 15 to 20 missions that should have granted me the Count rank long ago

 

[lovely lovely]

Hello Commanders!

For clarity:

Repair costs *for individual modules* will be higher.

Overall *total* repair costs (hull, plus ship integrity, plus modules) will on average be lower.

I understood

 

[CMDRKNac]

I was hoping there would be a fix to the galaxy/system map data inconsistencies. My dreams are shattered

 

[Boson Higgs]

Which system?
What is your commander name?
What time?

Thanks

Michael

There are three separate double-scan problems:

- surface scanning: it scans,reports success in text, but not in the scanner, KEEPS ON SCANNING, reports success
- discovery scanning: you ping the system, it reports nothing (except the one you get for being close); you do it again: it finds 25 bodies
- discovery scanning: you ping the system, it reports finding 25 bodies, but nothing appears on your scanner or navigation window; you scan again: they appear

All three happen ... basically all the time. As in, 1 in 5 systems I visit will have at least one of these 3 issues.

Edit: the first happened 4:23 BST, Boson Higgs, scanning HYPOE FLYI VI-T C6-326 1

If you want an example of the other two... well, any system I've visited in the last 2 days where I haven't (according to the system) discovered all of the bodies ;p

 

[Genar-Hofoen]

Which system?
What is your commander name?
What time?

Thanks

Michael

Michael, it's basically everywhere and at all times. It seems to be a fundamental comms problem between game client and your server(s) - whatever servers are involved in giving the client the exploration info it needs to display info after using the Space Horn, or during/after a detailed scan.

Regards

 

[Michael Brookes]

There are three separate double-scan problems:

- surface scanning: it scans,reports success in text, but not in the scanner, KEEPS ON SCANNING, reports success
- discovery scanning: you ping the system, it reports nothing (except the one you get for being close); you do it again: it finds 25 bodies
- discovery scanning: you ping the system, it reports finding 25 bodies, but nothing appears on your scanner or navigation window; you scan again: they appear

All three happen ... basically all the time. As in, 1 in 5 systems I visit will have at least one of these 3 issues.

Edit: the first happened 4:23 BST, Boson Higgs, scanning HYPOE FLYI VI-T C6-326 1

Thanks - it was details we were after so we can investigate a specific case.

Michael

 

[CMDR Ediya]

Thank a lot to finally give us some data about repair. Maybe some will not agree the value, but we'll know if cost are intended or just randomly bugged.
Let see if combat career could be viable with high end ships, or if like ur moderator Aleksej stated we are all "unskill" if we don't do cargo.

 

[Traveler]

It happens now and then. To lots of CMDRs in lots of systems. I suspect that it is to do with server load. The worst example I had was having to scan 7 times before it actually completed the scan. There are also similar issues with blowing your horn. You frequently get an incorrect scan, even with the Advanced scanner. Blowing the horn again usually works, if you leave it long enough. Again, I suspect server load. I sometimes get,say, just a star and two asteroid belts shown in the system scan, with a gap between the belts that obviously has planets in it - very like the view you get with an incomplete scan from just a basic scanner. I also get it where you blow the horn and are told there are lots of objects (say, 54), but the system map only shows a couple of stars, or similar. Blow the horn again, and it reports the 54 again.

Bottom line is that it looks like server load problems, with the client apparently not knowing that it has only received partial information: not only do you need to worry about the server loads, but you should probably put in more robust comms wih the server, so the client knows when it has only got partial information, and asks again.

TL; DR : scans are inconsistent, do not always work, and often report wrong information.

There are three separate double-scan problems:

- surface scanning: it scans,reports success in text, but not in the scanner, KEEPS ON SCANNING, reports success
- discovery scanning: you ping the system, it reports nothing (except the one you get for being close); you do it again: it finds 25 bodies
- discovery scanning: you ping the system, it reports finding 25 bodies, but nothing appears on your scanner or navigation window; you scan again: they appear

All three happen ... basically all the time. As in, 1 in 5 systems I visit will have at least one of these 3 issues.

Edit: the first happened 4:23 BST, Boson Higgs, scanning HYPOE FLYI VI-T C6-326 1

I can confirm all of this.
Name: Cmdr Barnaba
Time/frequency: on regular basis

 

[Arksun]

Lots of people quick to attack Frontier for not getting everything right in Beta, yet little praise for the fact that they've worked real hard and fast to roll out updates to fix issues since 1.3.0 was launched. They could have just left us in the lurch for ages but they didn't, they DO actually listen. And the ultimate testing will always be by everyone.

Though speaking of listening, something still needs to be done about turrets, which when using beam lasers are utterly useless at ranges greater than 1km (they persistently fire around the outer edges of the targeted ship causing little or no damage) I'm hoping that too will be addressed in a future update

 

[EAGLE 5]

Off the wall but I posted this bug in the beta 1.3 forum back then but any idea if the HUD resetting to lower brightness and orbit line on every time I launch the game bug will get a fix?

 

[Vikinger]

Which system?
What is your commander name?
What time?

Thanks

Michael

About 4th scanning attempts result that I have to scan it twice. Can be individual planets or an entire, initial system scan. ( Cant write the name of all systems this happened in )
CMDR Vulcor
Date 2015-06-18 -- 19. Time GMT 23:00-03:00

 

[Lima]

Thanks for this. Now kindly put those numbers in read-only so they don't randomly change in the next patch

 

[Distance]

Cargo limit is still present, please fix the profession breaking patch as soon as possible.

Thank you for the integrity update.

This!

Thanks for the repair update I might venture out to do some trading.

Please don't forget to add a "recharge shields" button in stations so I don't have to sit for 15 mins in a station waiting for my conda with 8 boosters to recharge shields.

 

[TomoRosso]

Lots of people quick to attack Frontier for not getting everything right in Beta

Then what's the point in having them. Just bosh out updates and hope for the best?

 

[Dan Banner]

That happened to me yesterday, was kinda weird (high int. RES). Also, when at a different RES ealier, it was all going ok and then all of a sudden over the space of a minute or so, all other ships just vanished except for a couple of miners.

Ian.

Was it something you said? LOL