Patch Notes Update April Update - Patch Notes

Don't know where to place this, so this thread seems as good as any:

With the new Cruise Control, ASC, once you have selected your target destination, do you HAVE to go to the navigation menu, scroll through the whole galaxy to find the target, and then engage ASC?

I've looked for a binding to enable ASC but haven't found one. That would be a nice feature to have. Sort of point, select and enable ASC.
 
Don't know where to place this, so this thread seems as good as any:

With the new Cruise Control, ASC, once you have selected your target destination, do you HAVE to go to the navigation menu, scroll through the whole galaxy to find the target, and then engage ASC?

I've looked for a binding to enable ASC but haven't found one. That would be a nice feature to have. Sort of point, select and enable ASC.
CORRECT.
Yes you seem to do it in the Navigation window. Select the Target Port/station then select the second icon from the left (i think it is) Select it again to turn it off. Which you seem to have to do when Planetside or it keeps trying to get you too orbit.
 
Set the value to 0 for 'EnableEngineTrails' in all quality settings there, if you cannot figure out which quality applies to you.
That reliably switches off just the engine trails and leaves anything else running as before.
No need to tamper with the FX quality option in the game or elsewhere in the Config file.
^^^^ This!
Works much better than total trails disabling in FX section above these.
 
I can confirm that this works! Thanks!!!

The description is a little vague and implicit, so for those in doubt:

Close the game if it is running.

Find the file called "GraphicsConfiguration.xml".

It's typically located somewhere like:

C:\Program Files\Oculus\Software\Software\frontier-developments-plc-elite-dangerous\Products\elite-dangerous-64

Copy the file so you have a backup. (Ctrl-C, Ctrl-V).

Open the file with Notepad (right click, Open with>Notepad).

Search for "trails" (Ctrl-F), it's roughly 3/4 down under FX.

Note: The GraphicsConfiguration.xml file contains information that the games uses, so you will find different values for the Off/Low/Medium/High settings in the games Options menu. The game uses these values for the in-game Options, but the game does NOT change the file when you change the Options. Hope that makes sense. I personally was in doubt.

You will see something like this for each Option in the game menu (Off/Low/Medium/High):

<Item>
<Feature>Trails</Feature>
<QualitySetting>2</QualitySetting>
</Item>

It is the value between the <QualitySetting>2</QualitySetting> that you have to change. It needs to be set to zero like this

<Item>
<Feature>Trails</Feature>
<QualitySetting>0</QualitySetting>
</Item>

After you have changed all four FX Trails values to 0 you must save the file.

This fixes the FPS issue. At least it worked for me.

EDIT: After you save the file, you can play around with the in-game options like you normally would.



I can confirm, this method works perfectly. Much better temp solution than disabling FX.
Thank you and quaintyetpeculiar on reddit.
 
I can confirm, this method works perfectly. Much better temp solution than disabling FX.
Thank you and quaintyetpeculiar on reddit.
Actually, after setting trails to 0, ED runs smoother than ever on my PC. I use VR on a 1060 3GB, which is kind of stretching the GPU a little. The trails might be missed in a dog fight, but I've yet to find out. Otherwise trails stays at 0 :)

I anyone from Fdev is listening. Make a quickfix. That should be pretty easy.
 
129198

What does the "27" mean after "Social"?
I've tried clicking on it and nothing obvious jumps out at me.
 
That was fun, landing at Explorer's Anchorage with 15 FPS. It was like one of those Jib-Jab videos.

Don't say turn off FX, done tried. Done tried vsync too. Yesterday and this morning I got a livable 60, this afternoon some chip inside my rig must be taking a nap. I'll be glad when the fix is in.
 
I've seen people in this thread post, who have similar computers to me or better, yet I'm not getting the massive slow down you're posting above. I haven't tried in VR, yet, just 5760x1080 but I'm still sitting on 60fps (v-sync.) I'll drop 5~10 frames the moment I go through the mail slot, for 2 or 3 seconds, and then it's right back at 60

I'm not sure what to make of that
 
Wow, I have noticed a drop in FPS when in stations on XB1X since the last update. Once out of the station it’s fine. This is on 4K performance setting. Not experiencing the fps drop on PS4 Pro.

Strange, imho I experience an increase of performance overall, and things look a bit crispier too.
I play in 4k quality on a 55" 4k tv.
I used to notice a lot of stuttering and fps drops before the latest update.
 
  • Corrected the cockpit health disparity displayed between module tab and advanced maintenance
Can we get clarification here? Did the integrity of canopy modules change, or were they always displayed incorrectly in the module panel? A lot of folks are reporting that their integrity is now 1/2 of what it was before, but if this is the same as it has always been it may be a big scare over nothing.
 
Still bugged - I'm out in the black and still getting fully scanned planets when they have not been. Doesn't seem to be session based, doesn't seem to be system based. Can't work out a pattern to it ( Yet )
Do you want to say that relog does not help at all now? That's a bad news...
Before the patch I was able to relog and reset that false "mapped" blue overlay. It worked OK then for 1-2 (or even several if you're lucky) next planets.
 
Do you want to say that relog does not help at all now? That's a bad news...
Before the patch I was able to relog and reset that false "mapped" blue overlay. It worked OK then for 1-2 (or even several if you're lucky) next planets.
Yes, I relogged and it didn't help. I came back more than 24 hours later and it didn't help. Same planet bugged as was another in the system but the local gas giant with water life was not.
 
Yes, I relogged and it didn't help. I came back more than 24 hours later and it didn't help. Same planet bugged as was another in the system but the local gas giant with water life was not.
(sarcasm)
Well, they fixed something. Relog is bad, you know. That is nearly cheating.
(/sarcasm)

In the meantime I just ignore the bug. After scanning a lot of planets I can do it even with this bug efficiently. But the bug seems to be a harder one, since they already tried twice to fix it. Now they are near the solution, because all the things they did before did not really change the bug behavior. Now something has changed. LOL :p
 
Yes, I relogged and it didn't help. I came back more than 24 hours later and it didn't help. Same planet bugged as was another in the system but the local gas giant with water life was not.
I see... Then, I'm afraid, FDev fixed it wrong and applied some straight overrides not finding the root cause of this issue. :(

In the meantime I just ignore the bug. After scanning a lot of planets I can do it even with this bug efficiently.
Good for you. I have no problems with blind scan of small planets, but have no skills to scan efficiently some big body with eff target about 20. :)
 
Still bugged - I'm out in the black and still getting fully scanned planets when they have not been. Doesn't seem to be session based, doesn't seem to be system based. Can't work out a pattern to it ( Yet )

I spent several weeks trying to establish a pattern for the “already scanned” planet bug. In the end, nothing seemed to form a reliable set of circumstances, every time I thought I could see a pattern, it got broken a few scans later. Eg. I thought for a while it was connected to scanning two HMCs in a row, and this held up for a few systems, then it didn’t.. Then it seemed to be connected to scanning Water Worlds as the first scan in the system, then I thought it might be scanning an object in an “A” spectra system, etc etc etc... :(

In the end, I gave up and viewed each occurrence as being an opportunity to practice my memory skills for where probes landed ;)

(I started with a ZX81 as well. There was always a certain frisson with wondering if the 16K ram pack was going to fall out and glitch the thing at any point in time :) )
 
Back
Top Bottom