Elite: Dangerous - Bug discussion
- Thread starter Kerrash
- Start date
- Status
Same here. In SC screen freezes sound continues. Before it happens frame rate drops.
Had a quick read back and couldn't see this one mentioned.
Since 1.06, I often see a problem with the message you receive from an NPC when they want to offer an alternative to a mission.
The error looks a little like:-
"Please meet me at s##badestinstionname," rather than actually having the system name showing.
Almost as if a variable had been placed within quotes in the code.
Since 1.06, I often see a problem with the message you receive from an NPC when they want to offer an alternative to a mission.
The error looks a little like:-
"Please meet me at s##badestinstionname," rather than actually having the system name showing.
Almost as if a variable had been placed within quotes in the code.
Last edited:
Easily reproduced exploration bug -
May have already been discovered
1. Scan system with directional scanner to gain partial listing of celestals. surface scanning found objects
2. travel 20 LY and sell data
3. fit advanced discovery scanner
4. re scan the same system to discover additional celestals
5. drink 10 beers and drunk crash type 6 into station interior, with loss of ship
6. all data for system, including previously sold data, has vanished from system data display
I have lost some good system data to this. A bit dissapointed, it's really obvious bug
May have already been discovered
1. Scan system with directional scanner to gain partial listing of celestals. surface scanning found objects
2. travel 20 LY and sell data
3. fit advanced discovery scanner
4. re scan the same system to discover additional celestals
5. drink 10 beers and drunk crash type 6 into station interior, with loss of ship
6. all data for system, including previously sold data, has vanished from system data display
I have lost some good system data to this. A bit dissapointed, it's really obvious bug
I don't pretend to be an Astronomer but Ive' suspected for some time this was faulty; I think you have a good point. Hope someone else chimes in on this...
I updated the client today. For some reason the Lakon 6 I've been using won't make a jump well within it's range claiming insufficient fuel amout (2t) even though the fitting hasn't changed and have 8t aboard. Did someone break something?
Not by me.
Kill warrant scanner erases bounties
I had a very common problem (many people on Reddit and the official forums have that problem) where the game wasn't awarding bounty claims for destroying ships that had a bounty on them.
I made some tests in an Anarchy system, and it turns out that when you scan a ship and its bounty is revealed, if you then scan again but don't complete the scan, the bounty disappears from the left-hand panel and you are not awarded the bounty claim when you destroy the ship.
(This was hard to notice, since due to my firegroups setup, I would tap the scan button by mistake, not being aware that I did so, making it appear like there was no reason at all why the game refused to award bounty claims. I suspect something similar is happening to other players as well.)
TICKET #00000031270
I had a very common problem (many people on Reddit and the official forums have that problem) where the game wasn't awarding bounty claims for destroying ships that had a bounty on them.
I made some tests in an Anarchy system, and it turns out that when you scan a ship and its bounty is revealed, if you then scan again but don't complete the scan, the bounty disappears from the left-hand panel and you are not awarded the bounty claim when you destroy the ship.
(This was hard to notice, since due to my firegroups setup, I would tap the scan button by mistake, not being aware that I did so, making it appear like there was no reason at all why the game refused to award bounty claims. I suspect something similar is happening to other players as well.)
TICKET #00000031270
Last edited:
FOr anyone having rouble with the "vanishing landing lights" bug, you may not be aware that your target indicator (the little blue light in the cross-hairs just to the left of your heat scale) homes in on the correct landing pad. It may help, next time that you are lost within a station...
Still losing bounties after destroying a powerplant on an Anaconda. Most often it works, but ysterday I wasn't awared 184k because of it.
I did keep firing on it when the powerplant went down too, to make sure I kept it "claimed".
I was playing in private group with no other CMDR around, so there was no "kill stealing" involved.
I did keep firing on it when the powerplant went down too, to make sure I kept it "claimed".
I was playing in private group with no other CMDR around, so there was no "kill stealing" involved.
I think others have said this but, noticed last night:
.
I had a pirate kill mission, 4 targets, I found 3 straight off and killed them, mission said 3 killed out of total 4. Next USS was the annoying 'abandon mission' contact, I ignored him found my next pirate which would have made 4, checked my mission details and it said 1 killed out of 4 -! It had reset after meeting the abandon mission guy !! A small inconvenience but sometimes, my wife is on my back or I have to go to work and I have time for 1 mission, so this causes me to fail missions as I dont have time to go look for them all again! Please fix. Thanks
.
Also.....If you are going to bribe someone to Abandon a mission you have to compensate them a lot more than what they would originally get paid, 20K to kill 4 pirates, Oh tell you what, abandon this mission and I will give you 1750CR, yeh right whatever, is this mission change thing just there to screw up your missions? I sometimes wonder whether the same people that created the brilliant fundemental game that elite is, actually created all the rest of it, the missions etc, I bet they subcontracted it out to some amateur software house or it was just an afterthought they knocked up in their lunch breaks!
.
I had a pirate kill mission, 4 targets, I found 3 straight off and killed them, mission said 3 killed out of total 4. Next USS was the annoying 'abandon mission' contact, I ignored him found my next pirate which would have made 4, checked my mission details and it said 1 killed out of 4 -! It had reset after meeting the abandon mission guy !! A small inconvenience but sometimes, my wife is on my back or I have to go to work and I have time for 1 mission, so this causes me to fail missions as I dont have time to go look for them all again! Please fix. Thanks
.
Also.....If you are going to bribe someone to Abandon a mission you have to compensate them a lot more than what they would originally get paid, 20K to kill 4 pirates, Oh tell you what, abandon this mission and I will give you 1750CR, yeh right whatever, is this mission change thing just there to screw up your missions? I sometimes wonder whether the same people that created the brilliant fundemental game that elite is, actually created all the rest of it, the missions etc, I bet they subcontracted it out to some amateur software house or it was just an afterthought they knocked up in their lunch breaks!
Last edited:
Viajero
Volunteer Moderator
Wing mechanics, Peer to Peer still has some bugs:
Not really a surprise, and from my gaming point of view instancing issues seem to be on a downtrend, but I have just reported 3 tickets:
Yesterday Jan 25th a group of 7 players (all Friends) in game (OPEN) we started to test jumping in and out of low energy FSD clouds so to practice helping each other in interdictions etc etc. For the most part it worked really well but we found the following issues in a few occasions:
1) Low Energy wakes bugged / inaccessible with a "cloud not scanned" error message. This should only happen with High Energy ones before scanning, Low Energy ones should not need any scan. We realized that for the most part this issue tends to happen when either a) following an FSD wake of someone leaving SC in a random empty spot or b) interdicting (or being interdicted) by random NPC. It does not happen as often (didnt happen at all) when jumping into FSD wakes after a friend has joined an USS. It would seem as if USS related FSD wakes are more "clear" and less buggy from a peer to peer point of view.
2) Interdicted or interdicting NPC not seen by other players. This happens quite regularly. Only the interdicted or interdicting player manages to see the relevant NPC. Other players joining in later via the FSD wake seem not to see the NPC. Again, this issue seems to happen mostly with random NPC related interdictions, and not as often when multiple friends join an USS.
3) There are still some occasions where players listed as Friends and who have followed all the relevant advice for connectivity (opening exceptions at the Firewall, Antivirus and port forwarding etc). For the most part those resolve themselves by leaving and re entering the instance. But it still is a bit annoying and may give some issues to some teams and new comers.
All in all it is not really like a killer list and it does not happen (at least to us) too often as to kill the experience, but it is definitely still a big issue.
I d love for Sandro et al to give us an update on this...
Not really a surprise, and from my gaming point of view instancing issues seem to be on a downtrend, but I have just reported 3 tickets:
Yesterday Jan 25th a group of 7 players (all Friends) in game (OPEN) we started to test jumping in and out of low energy FSD clouds so to practice helping each other in interdictions etc etc. For the most part it worked really well but we found the following issues in a few occasions:
1) Low Energy wakes bugged / inaccessible with a "cloud not scanned" error message. This should only happen with High Energy ones before scanning, Low Energy ones should not need any scan. We realized that for the most part this issue tends to happen when either a) following an FSD wake of someone leaving SC in a random empty spot or b) interdicting (or being interdicted) by random NPC. It does not happen as often (didnt happen at all) when jumping into FSD wakes after a friend has joined an USS. It would seem as if USS related FSD wakes are more "clear" and less buggy from a peer to peer point of view.
2) Interdicted or interdicting NPC not seen by other players. This happens quite regularly. Only the interdicted or interdicting player manages to see the relevant NPC. Other players joining in later via the FSD wake seem not to see the NPC. Again, this issue seems to happen mostly with random NPC related interdictions, and not as often when multiple friends join an USS.
3) There are still some occasions where players listed as Friends and who have followed all the relevant advice for connectivity (opening exceptions at the Firewall, Antivirus and port forwarding etc). For the most part those resolve themselves by leaving and re entering the instance. But it still is a bit annoying and may give some issues to some teams and new comers.
All in all it is not really like a killer list and it does not happen (at least to us) too often as to kill the experience, but it is definitely still a big issue.
I d love for Sandro et al to give us an update on this...
Last edited:
Unable to launch on first flight.
I got the game last week, and have been doing the tutorials to gain some reasonable level of competence before trying this thing for real. I started the game last week to select my KS starting vessel, and to look at the options re equipment etc. but not to fly it. Between starting the game, and going for my first real flight, the update to version 1.06 happened - this may or may not be relevant to the problem.
However, having completed all the tutorials, including the launch one, when I went to launch my Cobra for the first time, it just wouldn't take off. I was taken out of the hanger, put on the landing pad, told the engines were online, and then - nothing. It was full of fuel but the thrusters just would not work (and yes I had done the preflight control checks).
The cobra was the federal trader version and I had added a docking computer - I gather these seem to have been problematic - and I wonder if this may have been relevant? After restarting and the same thing happening I did a clean save and started again with the KS explorer variant of the cobra instead. So far so good.
I got the game last week, and have been doing the tutorials to gain some reasonable level of competence before trying this thing for real. I started the game last week to select my KS starting vessel, and to look at the options re equipment etc. but not to fly it. Between starting the game, and going for my first real flight, the update to version 1.06 happened - this may or may not be relevant to the problem.
However, having completed all the tutorials, including the launch one, when I went to launch my Cobra for the first time, it just wouldn't take off. I was taken out of the hanger, put on the landing pad, told the engines were online, and then - nothing. It was full of fuel but the thrusters just would not work (and yes I had done the preflight control checks).
The cobra was the federal trader version and I had added a docking computer - I gather these seem to have been problematic - and I wonder if this may have been relevant? After restarting and the same thing happening I did a clean save and started again with the KS explorer variant of the cobra instead. So far so good.
Automated docking computer malfunctioning
Dear Faulcon Delacy,
I recently bought a Cobra MKIII and I noticed that I have the same issue with the automated docking computer as i had in my previous ship, the Adder (built by Zorgon Peterson).
After arriving at Cleve Hub in Eravate (and similar stations) and being granted docking permission, the docking computer takes over (as it should) and proceeds to steer me towards the station.
But at reaching the edge of the station entrance it proceeds to hang up on me. It simply stays in place for the full 9 minutes of docking permission.
I have tried different angle approaches and speeds but the result is always the same.
I currently have version 1.06 of your firmware but i noticed the same problem with the Adder that had Version 1.05 of the firmware.
Please provide me with a updated firmware version to fix this bug.
Regards, CMDR RedDevilGiant
Dear Faulcon Delacy,
I recently bought a Cobra MKIII and I noticed that I have the same issue with the automated docking computer as i had in my previous ship, the Adder (built by Zorgon Peterson).
After arriving at Cleve Hub in Eravate (and similar stations) and being granted docking permission, the docking computer takes over (as it should) and proceeds to steer me towards the station.
But at reaching the edge of the station entrance it proceeds to hang up on me. It simply stays in place for the full 9 minutes of docking permission.
I have tried different angle approaches and speeds but the result is always the same.
I currently have version 1.06 of your firmware but i noticed the same problem with the Adder that had Version 1.05 of the firmware.
Please provide me with a updated firmware version to fix this bug.
Regards, CMDR RedDevilGiant
- Status