News Status on a few reported issues in 3.1

https://m.youtube.com/watch?v=KseNRVIXwWs


I know I'm still gonna come off as salty but that video says it all. I posted earlier but I now see there are many others that feel the same as me. Just like the above guy said, I'm fed up with this what seems like ignoring basically game breaking bugs approach. What's worse is there are still alot of people defending frontier. I've literally had people come into my cutter bug report thread and tell me it's not game breaking and I should use another ship and stop complaining because the cutter is garbage.

That's not the point. I should not have to change the ship and not be able to use the ship I want because of a glitch that they ignore to fix. To me it's gamebreaking. Having to reset the game every 20 or 30 minutes when not doing things like bounty hunting or exploring to me is game breaking. Me and about 10 others that own cutters have been blowing up frontiers bug section on PS4 since OCTOBER/NOVEMBER and all we get is " we are aware of the problem".


How about fixing the thing then? Even if it's a complex bug we are going on 9 months now. Almost a year of a practically game breaking bug with one of the best endgame ships in the game on PS4. This is absurd. When are we gonna get a fix to this absurd audio glitch??

Oh don't worry I'm just waiting for one of the usual shill brigade to pop along and ask me why I need another 10.5LY jump range on an exploration Anaconda. Not because I'll be dignifying whichever emptyhead asks the question by providing a response, just because it will give me something to laugh at tomorrow morning whilst I'm shoving bacon butties into my face and getting ready for the football.

One of the worst things about a certain cohort among the player base for this game is their failure to grasp the concept that just because they can work around or ignore a problem, or simply don't care about it because it doesn't affect the way they play the game, that is not any kind of reason for things not being fixed, nor is it a justification for a lackadaisical approach to quality assurance. It just means they're either lucky to not be affected, or happy to accept mediocrity, or fine with constantly compromising their experience,all of which is fine by me - I'd never dream of having the audacity to tell someone else what they should or shouldn't find acceptable. It's just unfortunate that the cohort in question rarely extend the same courtesy to others.

There's also usually at least one person who will point out that this is 'only a computer game', as if you've somehow mistaken it for an important human rights issue rather than a leisure product. I always find that an interesting approach because it's implying that the thing all of FDev's staff spend their professional lives on (and earn a living from) is basically a worthless frippery, which always seems quite a strange way to go about mounting a defence. 'Hey leave them alone, what they're doing doesn't have any real value anyway!'

Like I said, I've just had a bellyfull of this now. I'd actually be far happier with less content in every single update if it meant there would be sufficient QA/test time to make sure it worked and didn't break pre-existing stuff that was already working but no longer is.

I mean I know the developers aren't terrible human beings, hell they aren't even terrible game developers - I've played games that were made by genuinely terrible developers and I know the difference. There's no way that they actually want to release updates that cause random aspects of the game to crap the bed over and over again and I'm sure they find the fact it keeps happening to be just as frustrating as you and I do. That does beg the question though; since it's something that nobody wants, why does it keep happening over and over and over again?

It's not caused by acts of God outside of anybody's control. It's caused by errors (which we all make from time to time, I fully accept that) and failures in the systems that are supposed to be in place to catch those errors, which is less acceptable to be honest. I don't know what the answer is, more QA and testing resource or more effective project management to ensure that the existing QA/test resource has time to do its job would seem to be the obvious one though.

There is an answer though because although very few games (in fact probably none at all these days) are released bug-free, there are plenty of examples of games that are released without seemingly involving a lottery as to which aspects will become irredeemably broken for an indeterminate period of time.
 
Last edited:
So they added a 'mission depot' and then 'balanced/tweaked' it but never actually said what it is or how it functions. Can anyone enlighten me? Is it a way of partially completing collect missions for solo pilots?
 
Probably some people noticed about the Passenger/Mission generating system? Nobody noticed that the system is Broken?

If a few people play at the night after the servers weekly maintance will remember that a few hours after the server restart we got a time-window that the mission system get all messed up - Please tell me if someone notice that too - So, now in 3.1 we are permanently (or at the last 3 days) at this state: Missions Disconsidering BGS - Generating missions to far away systems instead of systems nearby.
the only "safe" systems are those that have only 1-2 beacons (Or stations) in range (1-30LY) the another ones will generate alot of crap missions to alot of systems.

Also, Why we are dropping to far from stations now? i think the drop have increased 1KM or more ><
 
USS threat levels aren't displaying properly.
Distress call threat 5: stranded ship and a rescue craft. No pirates even after they both leave.
Distress call threat 5: Pirate cobra and Asp
Pirate activity threat (7?): Gunship and debris field.

I once had a USS with a g pirate capital ship. Once, and that was over a year ago and nothing in this game has ever stacked up to that experience since. Make some epic moments for us!
 
I'm so glad I saw the message about them still being borked before I went charging off to unlock them tomorrow. I want them primarily to maximise range on two of my long range exploration ships so having them unable to be used with either neutron star boosts or jumponium makes then effectively useless to me. Again. I know this stuff isn't done deliberately but honestly, I'm lost for words. They were supposed to be in the game with 3.0, we've had that update, four or five minor patches to it and now another full point release and they still aren't working right - seriously guys this is frakking shambolic stuff now. Please for the love of God prioritise getting the bloody things working properly once and for all.

Yeah yeah I'm crabby because it's hot but Christ almighty, I'm so sick of this frakking farce.

Edit : I came back to this post because I was considering toning it down a bit. Then I thought about it again and I'm actually adding another couple of paragraphs on a similar theme. I'm absolutely at breaking point with this crap now, this might seem a minor issue but it's the straw that broke the camel's back for me. This is the only game I've ever played where I actively dread updates because instead of looking forward to new stuff, I'm just wondering what parts of the game I'll need to forget about for weeks/months/years (if anyone thinks years is an exaggeration by the way, just remember how long it took to get beige planets fixed) because they've been broken.

I mean how the frak can FSD boosters get past QA without a bug that stops them working with either jumponium or neutron boosts being spotted? In what parallel universe is that not one of the very first things that would be tested when introducing a piece of gear that affects jump range? You know, 'oh hey maybe we'd better check that it doesn't have any conflicts with this other thing that affects jump range, you know because they're both things that affect jump range...' I could understand it if it was some esoteric combination of factors that caused it like flying an Asp Scout on a Wednesday whilst having exactly 12,872.583 credits in your account and three open missions but yeah, it's not that. Not even close.

On top of that, this is stuff that has already been removed from the game once because it was broken! I'd have though that perhaps, just perhaps in view of that somebody might have bothered to check them properly this time.

You know what? Frak it. I'm wasting my time even getting mad about it because if anybody actually gave a crap it wouldn't be happening to begin with. Terribly sorry if I've hurt anybody's feels with a bit of very honest feedback but I'm afraid you've earned it and I'm screwed if I'm dressing it up in diplomatic language. If I screwed something up this many times at work I'd be getting reamed out for it big style.

Thank you for writing the post I wanted to write! It's really a shame having to fear the bugs of each upgrade instead of anticipating the new things added.
I don't know, maybe they are overworked, maybe some are incompetent or underpaid. Every upgrade seems rushed.
I think we love the game more than they do.
Repped
 

Flossy

Volunteer Moderator
Thanks Frontier for your good work

:)
Yes, thank you! This is a brilliant game and I truly appreciate the hard work that goes into it. Making everything work as it should must be a real challenge sometimes especially with so many different computer systems being used by thousands of players. :)
 
Interested if FD have explained what the 'destination' lockout on some S&R missions means. Why they introduced it.
Perused the thread but not found any comment.
Not obvious (to me) what the restriction is; and since it is S&R from the station I am in cannot be a permit issue etc.

Testing.... we don't need no stinking testing.
What could possibly go wrong.

On the other hand, if this is (we are) the beta testing then Thursday might not be the optimal day to release it.
 
Probably some people noticed about the Passenger/Mission generating system? Nobody noticed that the system is Broken?

If a few people play at the night after the servers weekly maintance will remember that a few hours after the server restart we got a time-window that the mission system get all messed up - Please tell me if someone notice that too - So, now in 3.1 we are permanently (or at the last 3 days) at this state: Missions Disconsidering BGS - Generating missions to far away systems instead of systems nearby.
the only "safe" systems are those that have only 1-2 beacons (Or stations) in range (1-30LY) the another ones will generate alot of crap missions to alot of systems.

Also, Why we are dropping to far from stations now? i think the drop have increased 1KM or more ><

I have no knowledge of passengers.

The only difference I have seen in station drops is because the stations I have been visiting lately are further from the object they orbit and that always has allowed the safe drop message to appear sooner the drop completes in the same range it usually does so no change there for me.
 
Thank you for writing the post I wanted to write! It's really a shame having to fear the bugs of each upgrade instead of anticipating the new things added.
I don't know, maybe they are overworked, maybe some are incompetent or underpaid. Every upgrade seems rushed.
I think we love the game more than they do.
Repped

It's ultimately QA/testing thsat's the issue with things like the one I highlighted and honestly, I don't believe it's incompetence at all. I just don't think it's given sufficient priority, resources, time (or all three) within the workflow.

Yes, thank you! This is a brilliant game and I truly appreciate the hard work that goes into it. Making everything work as it should must be a real challenge sometimes especially with so many different computer systems being used by thousands of players. :)

Of course it is. That's exactly why testing is so important. Like I said, being literally bug-free at release is an unrealistic expectation with software as complex as E D is and there will always be odd, unanticipated issues that are dependent on players' individual hardware, or unusual combinations of gameplay elements.

Checking that a module actually delivers its basic functionality, after it has already been removed from the game once months ago because it didn't deliver its basic functionality is not one of those scenarios though. It's more an 'Oh my God how has my foot ended up in my mouth again?!?' kind of deal.
 
Last edited:
I see S&R wing missions available (both below and above my cargo capacity) and also some not available because of 'destination' (both high and low payout).


The bug is just this: if you don't have the cargo capacity to hold the amount of cargo needed, you cannot accept the mission. This makes sense in single player source and return.. but makes no sense for wing missions when multiple players can contribute to it.

I've put in a bug report here.
 
The bug is just this: if you don't have the cargo capacity to hold the amount of cargo needed, you cannot accept the mission. This makes sense in single player source and return.. but makes no sense for wing missions when multiple players can contribute to it.

I've put in a bug report here.

Yes this seems correct.
I think I confused cargo delivery above cargo carrying capacity with S&R. Should be easy to fix :)
 
As I understand it, that is not a bug. Getting a Power Plant down to 0% just reduces its output, or the ships total power capacity (however you want to see it), down to 50%.

You can avoid getting your ship "shut down" by keeping thrusters as priority 1 and the rest of your modules between priority 2 and 5 (in your module tab, right hand side).

I think it IS a bug, i have seen ships with 0 PP with all wepons and shields working. its not npc power priorities, tho im shire this is a thing, its ubiquitous across all ships and loadouts that the power plant being at 0 does nothing.

On a side note.. when my power plant malfuntions.. wich it does constantly once its under 90% my ship looses power to 30% and i stop dead in the ''water'' this NEVER happens to npcs.

I have also seen a new bug where npcs shields regen is reset upon reciveing any damage, its handy some times but its not what i want.
 
Hello Commanders,

With the deployment of the 3.1 update yesterday, we have received reports on a few issues and wanted to update you on the steps being made to correct them. For anything that hasn’t been listed here, please report it in our Bug Report section so they can be investigated by our QA team.

Missions

  • Collect Wing Missions: We received reports that it is not possible to hand in Collect Wing Missions. The team believe that this is an issue with the mission template and we are working on a server-side fix that will be deployed as soon as possible.
  • Mission Depot: You may have noticed we have added a mission depot for all Collect mission types. There are a few improvements and balance tweaks we want to make to this feature before it works exactly as intended. As this is a server-side template update, it should be deployed as soon as possible. It’s worth mentioning that these balance tweaks will be ongoing, and this kind of depot structure is something we’d like to bring to future mission types and templates.
  • Missing Missions: Missions that were taken on (and still active) during 3.0 have been removed with the arrival of 3.1. In future, we will endeavour to communicate this with more advanced notice.

    However, the team are working on returning the following missions types:
Returned Mission Templates
  • Long Distance Courier
  • Long Distance Delivery
  • Long Distance Passenger (Bulk, VIP, Sight Seeing)
  • Long Distance Smuggle
  • Passenger (Bulk, VIP, Sight-Seeing)
  • Ram Tah Missions
For other mission templates, affected Commanders will receive a credit refund and an inbox message outlining the amount (based on average earnings, plus a bonus, for each mission type.)
These issues are server-side fixes so will not require an update and will be deployed as soon as possible.​

Crashing at certain Installations

As detailed here, we have identified that the following installations are causing players to crash:

  • Military Installation LFT 926
  • Security Installation Izanagi
  • Military Installation Gridge
  • Security Installation Mandhrithar
  • Military Installation Coeus
  • Military Installation Los
  • Military Installation Randgnid
  • Colonia Bastion Colonia
  • Skulmoor Keep HIP 33368
  • The Golkonda Polevnic
  • The Sentinel Pleiades Sector IR-W d1-55
As a temporary measure, we have removed these installations as we work on a fix. We’ll keep you updated in this thread.

Guardian FSD Booster

The Guardian FSD Booster is not functioning as intended in specific situations. If commanders attempt to use either the FSD Injector Synthesis or Neutron Star FSD boost, the Guardian module will fail and display ‘Jump Exceeds Drive Fuel Use Limit’ info message.

We’re aiming to deploy a client-side hotfix in the near-future to address the Bodysite Crash and Guardian FSD Booster. We’ll keep you updated in this thread, also.

In the meantime, thank you all for your diligence in reporting these issues, and your patience as we work to get them fixed.

UPDATE:

Engineer Stats Not Updating

As of 3.40PM we have resolved an issue where certain player's stats were not updating in relation to reputation with the Engineers.
Although you won't see any change as a result of this fix until early next week, you can rest assured that you are still making progress and your transactions will be counted over the weekend, and since launch. They will display correctly at some point early next week.

UPDATE AND FIXES:

Hi all. The team have been hard at work at introducing some fixes to some of the issues above.

· Collect Wing Missions – can now be handed in.
· Mission Depot – now tweaked and balanced. Please keep in mind that further tweaks may be necessary.
· Missing Missions – refunds have now been issued for affected Commanders.
· Returned Mission Templates – missions should now appear on transaction tabs.
· Commander stats – should be now updating, including Engineer unlocks. Stats that should have been accrued between 3.1 release and this fix being applied may take a few days to appear.
· Market effects, including Powerplay effects and discounts are now fixed and working.
· FX’17 flight suit - can now be applied.

Thank you all for your patience while we continue to work on any issues you’re experiencing. Thanks again for all your feedback.

Ed

Posted by Will.

Written by Mr. Ed? :)

[video=youtube;tSsuohepbVk]https://www.youtube.com/watch?v=tSsuohepbVk[/video]
 
Only had a short time to play the update, but noticed one really weird thing: I spotted a listening post in HIP 16743 in the Pleiades that seemed like it wasn't orbiting a body of any kind. It was actually moving while I tried to drop into it from SC - and once I did, the thing moved away from me at about 500 KM/second (no exaggeration). I couldn't keep it targeted. Not sure if it's spinning around the star, or some "new" gravity got a hold of it, but it certainly doesn't seem like proper behavior for a listening post...
 
This is the type of communication with the community that I like to see! Good job, Frontier!

As for the issues, it is the middle of a heat wave by me, so I haven't had the inclination to sit in front of a hot PC to play ED. As such, they haven't bothered me in the least! :D
 
Your reaction is very understandable, and you are not alone in feeling so.

Mengy and Red Anders I would rep you both again if I could. I fully agree with the both of you. The latest bugs show me that Frontier cares more for the Dinosaur sim rather than let the FDEVs work on this game PROPERLY. It stinks to the ceiling of very poor QAQC. Being blunt it shows me QAQC is non exhistant. How in all that is Holy can the FSD booster be released like this.

I just took on a kill a bad guy Mission to LFT 926. Honk and got the Incoming Mission Critical message telling me to fly to a planet. Did so and instead of the USS appearing the perp did and promptly flew away from the planet without interdicting me and so I chased him to the L class star where he dropped too close to follow. So I flew back to Jameson and fitted my FSD interdictor. Did he show again? Nope. Another thing worthy of note was perp was in a wing! Which was not in the mission descriptor.

So I waited for perp or USS and did one show? Er Nope. So something else that is broken; Kill pirate lord.
 
Back
Top Bottom