1.2 + DK2 = unplayable

[Pennyblack]

I resided myself to the fact that Elite - Dangerous, would increase the recommended specs as it advanced in development.
With the expansions and overall development, I'll wager we'll all be upgrading this year for sure.

 

[azl]

I am also seeing a major reduction in performance. It was so bad supercruising through Lave that I was convinced there was something wrong with my Rift setup. There were a large number (over a dozen) of nearby contacts. I will note that earlier in the night I was supercruising around with no performance issues.

I then entered a USS and everything went back to normal (perfect) performance. Of course that was probably because all of the local contacts were no longer visible.

I'm not sure if 1.2 is simply more demanding on the hardware, or if it is a bug that is popping up at certain times.

I'm on a 970 and my settings are pretty high but no supersampling. I had always gotten a bit of judder in the station, and I'm not sure if that has changed any.

 

[Beavis Tingleball]

me no juddery. game like most fun this time.

 

[Soliluna]

Saari. FYI, unparking my cpu cores completely eliminated all in-game cpu judder for me (i.e. planets loading in in SC, and game loading up next area during hyper jumps).


Ahh.. i thought I was going crazy. planets in their "white dot" stage before the planet actually loads DO look more like fuzzy balls now. I was pretty tired last night, so I just brushed it off. But yeah.. they look slightly different.

Agreed, certainly noticed the fuzziness, thought I was tired and it was me.

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

I resided myself to the fact that Elite - Dangerous, would increase the recommended specs as it advanced in development.
With the expansions and overall development, I'll wager we'll all be upgrading this year for sure.

I will be upgrading only if CV1 or Vive provides a significant reduction in SDE. Otherwise 970 sli is fine, as are the graphics settings right now.

I imagine planetary landings will need separate settings and I hope FD allow us to have separate settings for those instances (they will obviously be instanced).

 

[Beavis Tingleball]

So it seems that you guys that have noticed no change - better are running newer video cards... maybe its just time for these 670s to go away. Its just odd that back with 1.1 i only got judder when i first loaded the game, and when flying past big planets. Now in 1.2 its everywhere all the time...

When does the titan X hit the shelves?

my 2 670pe's are still rippin' bum. I think there may have been an improvement in performance but it deffinitly didnt suffer.

 

[Helios]

Hi,

Same problem here. What's more: My framerate is no longer affected by anything at all! When I sit in a space station with details at maximum my framerate rythmically changes between slightly below 40 (most of the time) and almost 60 (very regular spikes). It gives the exact same values when I sit with minimum details and supersampling at x0.5 and Oculus Rift detail slider at minimum looking at empty space. In both cases I get EXACTLY the same framerate.

And yes: It has a rythm! The time interval between the repeating "high spikes to almost 60" is always exactly the same.

I submitted a ticket describing this phenomenom with a dxdiag report attached and a video of a frame counter (shown on the display of my G15 keyboard and filmed with my cellphone ^^) showing the perfect rythm. Hopefully the devs will be able to sort this out soon.

Oh, I have a AMG FX6300 and a GTX 970 and of course my framerate was perfectly fine before 1.2.

EDIT: Strangely enough direct mode seems to be unaffected by the framerate problem. I get solid 75 FPS as soon as I switch from extended to direct mode. However in Elite Dangerous running in direct mode low persistence doesn't seem to work. :/

 

[Darth Sidious]

perhaps useful if you guys posted your driver as well
im currently wondering if i should update or not to update

 

[Helios]

perhaps useful if you guys posted your driver as well
im currently wondering if i should update or not to update

I'm using 347.52 ... so in case you are on an earlier driver version and do not have any problems: It could possibly be an issue where the newest ED version and the newest driver version don't work together. In that case not upgrading might be a good idea.

 

[Darth Sidious]

I'm using 347.52 ... so in case you are on an earlier driver version and do not have any problems: It could possibly be an issue where the newest ED version and the newest driver version don't work together. In that case not upgrading might be a good idea.

im currently on 344.48
ill report back after the install (of elite)

edit: im sorry to report 344.48 also has some juddering, not much its still playable but enough to be annoying

 

[Caspar]

Hi,

Same problem here. What's more: My framerate is no longer affected by anything at all! When I sit in a space station with details at maximum my framerate rythmically changes between slightly below 40 (most of the time) and almost 60 (very regular spikes). It gives the exact same values when I sit with minimum details and supersampling at x0.5 and Oculus Rift detail slider at minimum looking at empty space. In both cases I get EXACTLY the same framerate.

And yes: It has a rythm! The time interval between the repeating "high spikes to almost 60" is always exactly the same.

I submitted a ticket describing this phenomenom with a dxdiag report attached and a video of a frame counter (shown on the display of my G15 keyboard and filmed with my cellphone ^^) showing the perfect rythm. Hopefully the devs will be able to sort this out soon.

Oh, I have a AMG FX6300 and a GTX 970 and of course my framerate was perfectly fine before 1.2.

EDIT: Strangely enough direct mode seems to be unaffected by the framerate problem. I get solid 75 FPS as soon as I switch from extended to direct mode. However in Elite Dangerous running in direct mode low persistence doesn't seem to work. :/

Hmm Direct Mode only seems to offer me 60Hz when in ED. What voodoo did you do?

 

[Soda Popinski]

Might be helpful to post what driver you're using / using SweetFX along with if you're having trouble or not.

I haven't updated to the latest NVidia drivers yet. I'm 2 behind. Should I?

 

[Soliluna]

I am using 347.52. I recommend it.

 

[Helios]

Hmm Direct Mode only seems to offer me 60Hz when in ED. What voodoo did you do?

I had that problem as well at first. It seems the buggy Elite Dangerous direct to rift support is limited to the refresh rate of the primary monitor. (In my case selecting a very low resolution that my "60 Hz monitor" could take at 75 Hz and setting it to that 75 Hz allowed me to select 75 Hz in the ED graphics options. (Yea, this is quite different from other Rift direct mode applications where in direct mode the refresh rate of the normal monitor doesn't matter. In ED it apparently does ... unfortunately.)

However I do still get some kind of ghosting even at 75 Hz - I don't remember that from pre-1.2 times. (I however always used the now unusable-for-me extended mode in ED.) It's not as bad as it was at 60 Hz, and also still much better than the 40 to 60 FPS in extended mode, but IMHO it is still a significant stepp down from the 1.1 experience.

 

[thafred]

Could you guys check your gpu utilization while at different locations? I noticed that my gpu usage has gone down in 1.2 as the judder increased. RES sites where 99% smooth before in 1.1 (mostly high settings) and now I can only play on low with the card never going above 60% utilization, no matter what setting I choose, even ultra setting only gives me 65% gpu usage!! When I up the supersamplig usage goes up and hits 99% at DSR 2x but it allways judders.

I never recorded gpu usage before but I noticed that all my temps are universally lower in 1.2 so something must be broken?!

Can you guys with no judder report how much your gpus are taxed at RES and in Hangar?
Thanks!

Forgot: gtx 980 stock on i7 920@4ghz. Newest nvidia drivers. All the nvcp tweaks (got me judder free in 1.1) and I use sweetFX cpt America settings.

 

[Caspar]

I had that problem as well at first. It seems the buggy Elite Dangerous direct to rift support is limited to the refresh rate of the primary monitor. (In my case selecting a very low resolution that my "60 Hz monitor" could take at 75 Hz and setting it to that 75 Hz allowed me to select 75 Hz in the ED graphics options. (Yea, this is quite different from other Rift direct mode applications where in direct mode the refresh rate of the normal monitor doesn't matter. In ED it apparently does ... unfortunately.)

However I do still get some kind of ghosting even at 75 Hz - I don't remember that from pre-1.2 times. (I however always used the now unusable-for-me extended mode in ED.) It's not as bad as it was at 60 Hz, and also still much better than the 40 to 60 FPS in extended mode, but IMHO it is still a significant stepp down from the 1.1 experience.

Many thanks. I'll investigate.

It's funny - I only just set up my DK2 hours before the 1.2 patch so don't have a huge frame of reference but on my R9 280 I had everthing running smooth. Immediately after the 1.2 update I hit significant judder issues a) in stations when in that hanger or in the pad (but not once released) b) round Suns scooping c) in super cruise within a local system (not the normal near planet issues).

What seemed odd about these issues was that they were not consistent. As in I could encounter the same environment types at different times and get judder one moment and no judder the next. All this with the settings dialled right down (in fact, it doesn't feel like the settings make much diference to this issue at all).

I was prepared to accept that the R9 280 wasn't up to the job but seeing the posts from other people with better cards experiencing the problem makes me wonder if somethin else is amiss. Probably wishful thinking though on my part.

Must check whether the GPU spikes (or not) as thafred suggested.

 

[Caspar]

Here's my CPU / GPU usage from a session earlier today.

I'd say that I had judder during the periods where the GPU was between 70 and 90%. I'm guessing that these things don't go at top whack and then start dropping out at 100% - but that performance degrades when pushed in to the final third? Now I have a DK2 - I'm suddenly interested in how these things work!

If I should expect good performance until I hit 100% - then perhaps something else is going on.

 

[Helios]

Today I played a bit in direct mode (since extended doesn't work for me right now, as I described above) and I also noticed serious 'micro freezes' and stuttering in supercruise - especially when approaching planets. (Occasional very slight stuttering might have happened with 1.1, too, but that was something that consistently got better with almost every bigger patch since beta for me. This was the first time it got worse.)

 

[Katkon]

I too am seeing a minor performance hit in the form of judder/stuttering. More concerning: I feel dizzy and nauseous after playing 15 minutes. That's never happened before. Very odd.

 

[anTs]

Honestly, I'm surprised people aren't more vocal about how frustrating this is. I've got a buddy with a lower specced rig who has a judder free experience. On his recommendation, I bought a rift and ED. It's an incredible gaming experience but wow is it frustrating to drop $400 on entertainment that you spent 50% of your time trying to troubleshoot and the other 50% experiencing partially midst constant reminders of performance issues.

I'm running a 3930k OC'd to 4GHz with SLI 780s 16GB RAM, I've unparked CPUs I've tried all versions of drivers, I've tried every combination of Nvidia CP settings, I've tried running the game on low, in SLI, out of SLI, you name it I've tried it and it does nothing. It is seemingly random but I get an absolutely frustrating like-clockwork tick in stations, out of stations, in supercruise, in belts with a lot of contacts, with a few contacts. Nothing works. Frontier support really had no help for me when I submitted a ticket. I was suggested to try a different powersupply.

It feels like Oculus is ignoring that people bought their product for this game (it's a "dev kit" but come on, they've sold over 100k units and are owned by Facebook) and Frontier is not providing any kind of communication or leadership around the issue and appears to not be paying attention to it, or at least not devoting a meaningful amount of resources. I really have no idea as I'm not a project manager over there so please don't take this the wrong way, but I'm simply a customer who is just not seeing the effort if it's happening.

I would personally feel a bit better if someone from Frontier stepped forward, provided a thorough technical explanation around what the situation is and why it hasn't been resolved yet (the fact that you have to use extended mode to play seems to indicate some stopper on their end from properly supporting direct Rift play) or at least admitted here's what we know, and here's what we don't know. It doesn't seem like anyone is paying attention to this, or working on it. If Frontier can show it's actually put effort towards resolving this, I think the community could direct pressure towards Oculus to fix their (insert problem) and help solve this faster.

Don't mean to express a poor attitude here, but I'm just a bit confused by how this is being handled. After a long day at work I want to fly through space and not mess with drivers. I will literally buy all of the paint jobs and emblems and DLCs you can pump out! Just fix, or show progress on fixing, this game-breaking issue.

Anyone else feel the same way? I'm a bit new to this forum so excuse me if I'm way off, and just point me in the appropriate direction please!

 

[Caspar]

Ants, I think the thing is, it's not sold quoting Oculus support. It's an experimental 'nice to have'. The fact that news of this has spread like wildfire in the gaming press and encouraged people to buy the DK2 doesn't oblige them to commit more development reaources to it. I feel your frustration. I have seen how amazing this experience can be and it really is a game changer, yet unlike the experience I had when I set it up in the training missions, playing live in 1.2 I've encountered all the judder you've seen regardless of the detail settings. Unless there is some revelation, I'm prepared to accept that rendering this game twice is just flattening my rig and VR needs a top end card as a minimum (currently running an R9 280).

What rig is your friend running who doesn't have issues? If you say that it's lower spec - how low?

All that said, it would be good to hear an update from the guys at FD about any development plans and any optimisation work that they have planned. Purely from a selfish point of view so I can decide whether it's worth persevering with current hardware.