All of the bugs that I am trying to get more attention to have been in the game for over a year now.
First, the Thruster bug that has been in Odyssey that reduces thruster power by 50% when rotational correction is on. This has existed since The Odyssey Alpha. If you think your docking computer is running into things more often, it is because it is, because it defaults rotational correction to on and tries to use thrusters to their max, but even it is limited to half power. So many people are having trouble thinking they are not as good at the game as others. It was the PvP, AX combat and Racer communities that noticed it first, because they are pushing their ships to 10/10th's and to the ragged edge all the time, and loss of ship performance hurts. Others might think their ship is more slippery. If a racing game limited people to partial throttle for acceleration, I would hope it would get fixed quickly.
Second, the Pulse Wave scanner, it does not light up crackable rocks in the middle to close levels of detail (mostly anything less then 10km out), causing about 90% of core rocks to not show up. This one has existed since update 6. There has been more reports of it getting worse in a more recent update, as it used to work in a narrow cone in front of you, but even that is now gone. Newer players think that they are playing wrong, when the issue is the tool to find them is broken. Even the Third Party Databases have shown a general lessening of core rocks being sold, because if you cant find them, you cant sell them. New players follow guides, but all those guides were written when the scanner worked properly, so they miss out on so many core rocks because they are not lit up. This is a core gameplay loop added in 3.3 (2018) that has been effectively removed from the game for a lot of people.
As a VR player, the fact that the ships and SRVs shadows sometimes just entirely vanish in normal space, leaving only the chair casting a shadow. When flying a ship, it causes the ship not to cast a shadow on itself, which creates a strobing effect when flying over bodies. When in glide and approaching a planet, it almost needs a health and safety warning for the flashing as the shadows appear and disappear, making it light up the interior of the ship multiple times a second. Sometimes only the ship body kit will vanish, or individual parts of the SRV as you cross an invisible line on the ground. I have had to stop doing certain things because it has given me headaches, for example, taking a courier though canyons in VR with the entire interior strobing because the self shadows stop working every few seconds.
Also for VR, the issue where the entirety of rocks, flora, anything on the ground vanishes and then reloads back into view as you fly over the ground. Rocks and planets will do that fade out effect and then fade back in.
For the last two bugs above, I wrote bug reports, assisted by a render programmer that wrote code for Elite: Dangerous to use terminology to make it easier for the render team to know exactly what to look for and correct. The reports were merged with other reports that had nothing to do with what I had made them for, so to finish this off, a report not about Elite:
So Fifth, and last, I have tried to report a major bug with the bug reporting website before as well. If you make a report, and someone merges it with another report (even if has nothing to do with what your bug was about, see above) your attachment to said bug is removed. Meaning, if Person A and Person B write the same bug report, Person B's gets merged with the first one, Person A can still search their reports, using my reports, or contributed, but Person B's can not search theirs to find it, they have to manually go though all reports to attempt to find it again, which is worse if it is merged with something unrelated.
The part that make this so frustrating with some of these, is that when we make reports, upon a game update, any bugs before that point are all marked as expired, even when they still exist with no way for us to flag them as still active. The thruster bug was one of the largest and most voted on bugs, and we effective got a reply from a developer of "it does not happen on my machine" when players have it very well documented with tests and video. The shadow bug years ago that was caused giant shadowed patches on planet surfaces happened because the developer version and player client versions handled a NaN (not aa number) error differently as well, so please take a look at some of these.
For example, this was one of the bugs I personally was given a "not on my machine" type reply and it closed. This one has been a bug since the landable crescents were added to the game with the Horizons update in 2015. I have written this bug up so many times I have lost count. It would be nice to get at least the first two, and the fifth one in this post (Thruster, Pulsewave, bug report site) fixed, because they effect the greatest number of users.
First, the Thruster bug that has been in Odyssey that reduces thruster power by 50% when rotational correction is on. This has existed since The Odyssey Alpha. If you think your docking computer is running into things more often, it is because it is, because it defaults rotational correction to on and tries to use thrusters to their max, but even it is limited to half power. So many people are having trouble thinking they are not as good at the game as others. It was the PvP, AX combat and Racer communities that noticed it first, because they are pushing their ships to 10/10th's and to the ragged edge all the time, and loss of ship performance hurts. Others might think their ship is more slippery. If a racing game limited people to partial throttle for acceleration, I would hope it would get fixed quickly.
Second, the Pulse Wave scanner, it does not light up crackable rocks in the middle to close levels of detail (mostly anything less then 10km out), causing about 90% of core rocks to not show up. This one has existed since update 6. There has been more reports of it getting worse in a more recent update, as it used to work in a narrow cone in front of you, but even that is now gone. Newer players think that they are playing wrong, when the issue is the tool to find them is broken. Even the Third Party Databases have shown a general lessening of core rocks being sold, because if you cant find them, you cant sell them. New players follow guides, but all those guides were written when the scanner worked properly, so they miss out on so many core rocks because they are not lit up. This is a core gameplay loop added in 3.3 (2018) that has been effectively removed from the game for a lot of people.
As a VR player, the fact that the ships and SRVs shadows sometimes just entirely vanish in normal space, leaving only the chair casting a shadow. When flying a ship, it causes the ship not to cast a shadow on itself, which creates a strobing effect when flying over bodies. When in glide and approaching a planet, it almost needs a health and safety warning for the flashing as the shadows appear and disappear, making it light up the interior of the ship multiple times a second. Sometimes only the ship body kit will vanish, or individual parts of the SRV as you cross an invisible line on the ground. I have had to stop doing certain things because it has given me headaches, for example, taking a courier though canyons in VR with the entire interior strobing because the self shadows stop working every few seconds.
Also for VR, the issue where the entirety of rocks, flora, anything on the ground vanishes and then reloads back into view as you fly over the ground. Rocks and planets will do that fade out effect and then fade back in.
For the last two bugs above, I wrote bug reports, assisted by a render programmer that wrote code for Elite: Dangerous to use terminology to make it easier for the render team to know exactly what to look for and correct. The reports were merged with other reports that had nothing to do with what I had made them for, so to finish this off, a report not about Elite:
So Fifth, and last, I have tried to report a major bug with the bug reporting website before as well. If you make a report, and someone merges it with another report (even if has nothing to do with what your bug was about, see above) your attachment to said bug is removed. Meaning, if Person A and Person B write the same bug report, Person B's gets merged with the first one, Person A can still search their reports, using my reports, or contributed, but Person B's can not search theirs to find it, they have to manually go though all reports to attempt to find it again, which is worse if it is merged with something unrelated.
The part that make this so frustrating with some of these, is that when we make reports, upon a game update, any bugs before that point are all marked as expired, even when they still exist with no way for us to flag them as still active. The thruster bug was one of the largest and most voted on bugs, and we effective got a reply from a developer of "it does not happen on my machine" when players have it very well documented with tests and video. The shadow bug years ago that was caused giant shadowed patches on planet surfaces happened because the developer version and player client versions handled a NaN (not aa number) error differently as well, so please take a look at some of these.
For example, this was one of the bugs I personally was given a "not on my machine" type reply and it closed. This one has been a bug since the landable crescents were added to the game with the Horizons update in 2015. I have written this bug up so many times I have lost count. It would be nice to get at least the first two, and the fifth one in this post (Thruster, Pulsewave, bug report site) fixed, because they effect the greatest number of users.
