You guys also found the LH 3447 unplayable at the moment ?

[Lirezh]

In OPEN mode I get framerates of around 50 FPS, even at lowest settings and 1080p on my SLI 980GTX with lowest oculus quality (everything blurry) and lowest sight range. It makes no difference, stays unplayable.

GPU is 80% idle, CPU is 73% idle and framerate creates heavy judder permanently.

When I switch to SOLO it works fine, framerate hops to 75% at ultra quality and 1440p.
Note, I have seen only 3 or 4 player ships. There must be a lot more as it's a 10% discount but I have none in my radar or sightrange.


That's a big w t f for me.


I attached SOLO and OPEN PLAY in same spot, you can see GPU usage drop sby nearly 50% same as framerate does (what the heck ??)

 

[Rambowjo]

Turn off SLI when playing with the Oculus Rift. SLI doesn't properly support VR atm.

 

[Lirezh]

It's not an SLI issue, SLI works quite good for me and many others.
I have a constant high framerate at 1440p, execpt for this single system when in OPEN mode.

 

[ghcannon]

It's very probably just a bug where the game throws a billion exceptions/asserts that stall your redraw loop
Or because of also some exception that has telemetry set on it, it's busy writing down dumps to file, or packing and sending through them through wire ..

Make a ticket about it.
Doesn't look like a rendering issue if both your cpu and gpu are idling.

Edit : see if your framerate drops without the rift.

 

[Lorien31]

Im near that system and do have the exact same issues.

 

[Dozer.k.a.o.]

It's a server side game, due to the 10% discount in this system problably it's being overpopulated and that affects to the frame rate

 

[STRONTIUM DOG]

"in all the systems, in all the worlds you had to shift into mine..........."
*
(sorry I couldn't resist R.I.P Humphrey DeForest Bogart )

 

[Xntryk]

I am getting more judder in lhs 3447 too. it's not unplayable, but it is unpleasant. other systems are fine.

 

[Lirezh]

I just have a very similar problem in an mostly empty system!

In Asteroid belts I found that in OPEN PLAY my framerate drops to 50, no matter the graphic settings (even lowest settings make not 1 fps difference, also ultra makes no difference btw).
It takes a few seconds up to a few minutes and my framerate is dead, 50 fps with medium to low utilized CPU and GPU.
I stay at the position, log out and in again with solo mode and the framerate is perfectly stable.
NO other players are in the area, no one on radar. I am quite sure I was alone within 15 kilometers.

It's reporoduceable and stopped me from being able to play open, which ruins the fun right now as asteroid belts became the only area where enough NPCs show up to justify bounty hunting.

I suppose same problems will appear at other locations.
It is some sort of delay within the game engine that is not relevant to GPU or CPU, it just waits for some data/network traffic and stops rendering.
That's a problem for normal players and a HUGE "NO GO" for virtual reality, rendering must be as independend from network traffic or IO as possible to make sure we don't puke all over the keyboard.

I created a ticket, this time as "unable to play". As it's the first bug that really stops me from playing.
Solo mode is just too boring.

 

[Popopinsel]

I've opened a ticket for the bad performance in SC in LHS 3447 over a month ago and have not yet gotten any response. For me it's completely unplayable there, FPS are down to <10. Does FD even read/work on tickets anymore? If our customers had to wait this long for a response they'd already terminated the support contract!