Comprehensive Thread for DK2 Bugs

[Woofington]

The idea is simple, we gather every bug that exists for Elite Dangerous under one thread so the developers can quickly see what is not working or what needs fixing. This is a thread specifically for bugs or pressing issues but not suggestions that are personal preference (unless this preference would be ubiquitously supported for all rift users).

Items in this list will be color coded:

Bug/Issue present in game - The issue or bug is known by players but not known or acknowledged by devs.
Bug/Issue acknowledged by devs - The issue or bug has been acknowledged by the development team and a fix is underway or present in a dev build.
Bug/Issue Fixed - The issue or bug has been fixed and is in a released version of the game.
Will not fix Bug/Issue - The issue/bug has been acknowledged by the dev team however for whatever reason, it will not be fixed.

I will be trying my best to keep this thread updated.

Force Low Persistence On - For myself and others, elite dangerous can sometimes force low persistence off even though it had been previously turned on.
Comms Panel no longer focusable - While all major panels (left panel, right panel) can be accessed simply by looking at them, the communications panel has lost this ability in the latest updates. To access when using the rift you must use the UI focus button or button specifically mapped for the comms panel which should be unnecessary with the head tracking the rift provides.
Cache the name of the last searched system in galaxy map's search bar - Typing is problematic and frustrating with the rift, so having to retype things is equally frustrating. The navigation search bar in the galaxy map should remember and keep whatever you last searched for in it for quick re-search.
Outside of ship does not have paintjob - When using the rift's positional tracking to peak at the outside of your ship, your ship has no paintjob/decals.
X52 issues in rift only - https://forums.frontier.co.uk/showthread.php?t=72591&p=1209041&viewfull=1#post1209041
Text too hard to read - With the current size of most text and the color of the font, many HUD elements are difficult for users to read, even with positional tracking allowing lean in.
Direct Mode handled improperly - Several users are reporting that direct mode seems to introduce several performance issues. Something is fishy with direct mode it would seem.
Galaxy map inconsistency/difficult to use - The galaxy map just seems unbearable to use, almost impossible even. It seems that getting a system to consistently have a pop up with the destination, route, system info, trade info etc is incredibly difficult. And when it does pop up it seems to disappear without reason. It is nearly impossible to consistently use the galaxy map. This does not seem to affect HOTAS galaxy map controls which apparently function very well. It seems to only affect mouse/keyboard controlling.
Planetary rings generate different rock positions per - When approaching a Planet with rings, when you get close enough to "see" the rocks but still in super-cruse or really far from the disk in normal space, the left and right eye are getting a different randomly generated series of rocks, so it appears as if you have a bunch of simi transparent rocks as you approach. This is kinda disorienting, as you can not tell distance if each eye is seeing something different.
Please feel free to post issues/bugs.
X52 issues - Apparently the hat can stop working. Repro is inconsistent but apparently sometimes the hats to control the left and right panels and the starport services stop working. Seems to only affect rift users.

 

[cherbert]

Please feel free to post issues/bugs.

Still can't see applied skin outside of ship windows.

 

[Woofington]

Still can't see applied skin outside of ship windows.

THis isn't a bug related specifically to the oculus rift though is it? It sounds like a generalized bug for all players unless I am missing something.

 

[cherbert]

THis isn't a bug related specifically to the oculus rift though is it? It sounds like a generalized bug for all players unless I am missing something.

I don't think normal players can see the outside of their ship like a Rift user can. So yes.. its a Rift bug.

 

[CylonSurfer]

I don't think normal players can see the outside of their ship like a Rift user can. So yes.. its a Rift bug.

Yup - Agreed.

 

[dementia]

For me the top 2 problems are...

1. The stutter when moving your head. Most noticeable when inside the stations etc. It should be silky smooth like the Oculus desk demo. Not sure if this a problem ED or the Oculus driver or both. I have had hints from other forum posts that it is the Oculus driver but it needs clarification. If it is then is anyone from FD banging the Oculus people over the head with this? ED will be a real showcase title for the Oculus if they can get this working well.
2. The UI panels (left and right mostly) are too far away on some ships which makes the text very difficult to read. A slider in the config allowing them to be brought closer to your head would be a great solution.

 

[grodenglaive]

Can you see the paintjob on other cmdrs' ships? I've not noticed.

 

[Woofington]

For me the top 2 problems are...

1. The stutter when moving your head. Most noticeable when inside the stations etc. It should be silky smooth like the Oculus desk demo. Not sure if this a problem ED or the Oculus driver or both. I have had hints from other forum posts that it is the Oculus driver but it needs clarification. If it is then is anyone from FD banging the Oculus people over the head with this? ED will be a real showcase title for the Oculus if they can get this working well.
2. The UI panels (left and right mostly) are too far away on some ships which makes the text very difficult to read. A slider in the config allowing them to be brought closer to your head would be a great solution.

1) This is not a bug. This is not an issue. This is performance, and judder is related directly to your ability to render the game at a consistent 75 fps. While I'm sure there is still some optimization that needs to be the most likely limiting factor is your own PC and how high your graphical settings are. This game is so much more demanding and taxing on a system that it should never be used in comparison to the oculus rift desk demo, it would be like comparing a go-cart to a Lamborghini. I will not add this to the list.

2) Again this is a personal preference, and might not be feasible. Furthermore with positional tracking you should be able to lean in, even a slight lean in makes most text legible. If this turns out to be more common of a problem I will add it to the list but for right now I don't see it as something I hear a lot of complaining about. Furthermore we have to consider that sometime down the road the end game is for this to work with CV1 which will have a higher resolution which will mean better legibility even at far distances.

Can you see the paintjob on other cmdrs' ships? I've not noticed.

Yes.

 

[Trebor Daehdoow]

I don't think normal players can see the outside of their ship like a Rift user can. So yes.. its a Rift bug.

The bug is that you can put your head through the skin of the ship. When you try to do this, you should hear a loud "thunk" followed by profuse space-profanity.

 

[saviornt]

During the initial game loading spinning ship, the positional tracking is reversed. If you lean into the ship, the game zooms out instead of in.

 

[Shorty]

I have a very strange issue since gamma 2.0. I am using a Saitek x52 and I can't select menu items in left and right panel or starport services with the hat anymore. Well sometime it works but most of the time it doesn't. Same applies for switching energy. Reselect x52 profile in options doesn't do anyting.
This issue only appears when using the rift.
Anyone else experiencing this?

 

[dementia]

1) This is not a bug. This is not an issue. This is performance, and judder is related directly to your ability to render the game at a consistent 75 fps. While I'm sure there is still some optimization that needs to be the most likely limiting factor is your own PC and how high your graphical settings are. This game is so much more demanding and taxing on a system that it should never be used in comparison to the oculus rift desk demo, it would be like comparing a go-cart to a Lamborghini. I will not add this to the list.

I think you'll find that it is a problem that everyone has even those with top end hardware. My own hardware isn't too shabby either. If you read the countless post on this issue you will see there is a lot more to this than simply a PC performance issue. The same stuttering was also on the PCs FD used at the premier with the Oculus and don't tell me they would be using under performing PCs for that! The problem seems to be related to the Oculus not running at 75Hz but instead locking to 60Hz of your main monitor even in direct mode.

2) Again this is a personal preference, and might not be feasible. Furthermore with positional tracking you should be able to lean in, even a slight lean in makes most text legible. If this turns out to be more common of a problem I will add it to the list but for right now I don't see it as something I hear a lot of complaining about. Furthermore we have to consider that sometime down the road the end game is for this to work with CV1 which will have a higher resolution which will mean better legibility even at far distances.

"if it turns out to be a common problem"??? Are you serious? There have been countless posts on the forum related to this. No one saying it is a bug per say as it is more a limitation of the DK2 hardware but the ability to move the UI panels closer to your head would be universally appreciated by all Oculus users I think. Yes it gets better depending on the ship (Eagle of instance since the cockpit is narrower and so the UI panels are closer) and yes you can move your head closer to them but you shouldn't have to practically fall out of your seat just to read the text properly.

 

[[VR] Mad Mike]

in direct mode I cant go above 60hz if my monitor is attached..... essentially for me direct is unusable (thankfully extended rocks )


re the textures not being drawn on your ship bonnet or behind you.... whilst it is an issue, I think it is a deliberate choice to improve performance, ETS2 is the same, lean out of your truck and it has no body panels on it!.

 

[KING5TON]

Galaxy and system maps are still a stuggle to use in VR. Not sure what the solution is for it but I find myself fighting the galaxy map more than using it effectively.

- - - - - Additional Content Posted / Auto Merge - - - - -

in direct mode I cant go above 60hz if my monitor is attached..... essentially for me direct is unusable (thankfully extended rocks )

I know how to fix this if you're on a Nvidia card

Download this http://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU

Setup for your main monitor a 1080p 75hz resolution.
Do not set your monitor to that resolution, just set it up so that it is an option to select it but don't select it.

Go back in E: D on direct and you will now be able to select 1080p 75hz.
It seems like E: D in direct only allows you to select the resolution and refresh rate that is allowed on your main monitor, if there is an option for 1080p 75hz for your monitor (even though you don't actually use it) then you can select it for the rift in game.

You may get the issue where your fps gets capped to 37.5fps (half of 75fps) though, I did the last time I tried this. Will give it another try this weekend since the build has been updated numerous times since I last tried


UPDATE: I hear the 37.5fps issue is related to triple buffering being left on and it should be turned off. Will have a tinker this weekend and report back.

 

[Woofington]

During the initial game loading spinning ship, the positional tracking is reversed. If you lean into the ship, the game zooms out instead of in.

This was actually done on purpose by the devs, it is in an old changelog, but the idea is it will zoom away from you so you can't clip through the model.

I have a very strange issue since gamma 2.0. I am using a Saitek x52 and I can't select menu items in left and right panel or starport services with the hat anymore. Well sometime it works but most of the time it doesn't. Same applies for switching energy. Reselect x52 profile in options doesn't do anyting.
This issue only appears when using the rift.
Anyone else experiencing this?

Added to OP.

in direct mode I cant go above 60hz if my monitor is attached..... essentially for me direct is unusable (thankfully extended rocks )


re the textures not being drawn on your ship bonnet or behind you.... whilst it is an issue, I think it is a deliberate choice to improve performance, ETS2 is the same, lean out of your truck and it has no body panels on it!.

Again this is an issue with RIFT's direct mode, I do believe, and not ED. We need a fix to the ouclus software/drivers. Unless you can get 75Hz in other games using direct mode and this issue is related solely to E: D.

 

[[VR] Mad Mike]

Its elite I have no issue with direct in other apps and I have tried a lot.

 

[Viajero]

I am suddenly seeing black smearing after applying 2.03 (dk2 and 0.4.4)... anyone else?

 

[Trebor Daehdoow]

2) Again this is a personal preference, and might not be feasible. Furthermore with positional tracking you should be able to lean in, even a slight lean in makes most text legible. If this turns out to be more common of a problem I will add it to the list but for right now I don't see it as something I hear a lot of complaining about. Furthermore we have to consider that sometime down the road the end game is for this to work with CV1 which will have a higher resolution which will mean better legibility even at far distances.

I fear I must strenously disagree with you here. The amount of lean I currently have to do to get readable text is on the order of 6-8 inches, and it is uncomfortable. A zoom option that magnifies the pilot's lean by moving the headsup elements closer to her (as opposed to zooming the entire scene) would be extremely helpful, and should be fairly easy to implement since the panels are already being repositioned for different cockpits; its just a matter of making that repositioning a little more dynamic.

Even if the CV1 ends up having higher resolution screen, "you dance with the boy wut brung you". The current reality is DK2, and improvements to the UI that enhance the DK2 will benefit the CV1.

Even something as simple as being able to bind one of the HOTAS scroll wheels to mean "adjust zoom of the headsup element that is most central in my FOV" would be helpful, not to mention it would provide enhanced support for devices that only support 3-axis positioning.

 

[cherbert]

1) This is not a bug. This is not an issue. This is performance, and judder is related directly to your ability to render the game at a consistent 75 fps. While I'm sure there is still some optimization that needs to be the most likely limiting factor is your own PC and how high your graphical settings are. This game is so much more demanding and taxing on a system that it should never be used in comparison to the oculus rift desk demo, it would be like comparing a go-cart to a Lamborghini. I will not add this to the list.

2) Again this is a personal preference, and might not be feasible. Furthermore with positional tracking you should be able to lean in, even a slight lean in makes most text legible. If this turns out to be more common of a problem I will add it to the list but for right now I don't see it as something I hear a lot of complaining about. Furthermore we have to consider that sometime down the road the end game is for this to work with CV1 which will have a higher resolution which will mean better legibility even at far distances.

I also disagree with these points. Both clearly still need to be logged. I think you should stop trying to vet every suggestion based on your personal preference. Unless a dev has specifically addressed an issue then it needs logging until they do so. I have little time to have to participate in a debate over something every time an issue is put forward.

 

[Woofington]

I have logged the text readability and the direct mode issues into the opening post. I will not log the judder inside stations issue because it is not an issue related to the rift, all users experience perforamnce loss inside stations, its just more pronounced for rift users because once you drop below 75 fps you introduce judder. This is an overall optimization/performance issue that isn't unique to VR. If you are experiencing this upgrade your pc or turn your settings down until a performance patch hits.