Game unplayable both OPEN and SOLO, Frontier please fix your game!

But they don't show in the videos?
Yes. On this videos I've show only rubber banding, but I have also other captures with rubber banding and zig-zagging NPC's ships and very long jumps. Sometimes jump between systems are so long that animation of witch space looks like going to an end. There is no stars, nebulas and clusters. I can't tell exactly but 30-40 seconds maybe?
 
Dint bit no nivver mind
Not FD problem for me,more like kb crumbs and restless mind syndrome.

Fact is i can't play open & solo at the same time.
Deduction is I'm not trying.
Conclusion: Collision avoidance protocols work well for me.
Ymmv.
 
Last edited:
Yes. On this videos I've show only rubber banding, but I have also other captures with rubber banding and zig-zagging NPC's ships and very long jumps. Sometimes jump between systems are so long that animation of witch space looks like going to an end. There is no stars, nebulas and clusters. I can't tell exactly but 30-40 seconds maybe?
Interesting, if everyone who has rubber banding also has stuttering the issues could indeed be related.
 
I don't think you need to post videos. I am just pointing out that rubber banding and freezes are most likely separate issues and require separate bug reports.
It's possible indeed. Anyway it's always helpful to see the videos. Someone could notice something more than I did.

By the way, this is my hardware config:

CPU: Intel i7 7700K (not overclocked)
GPU: Zotac GTX 1080 - 8GB
RAM: G.Skill 16GB (2x8GB - 2133 Mhz)
HHD: Samsung SSD 850 EVO, 250 Go
Motherbard: Gigabyte GA-H270 Gaming 3
 
On those suspecting their own systems: I doubt that. I also noticed since last weekend, that the game gets more choppy when i play for a longer time. Completely restarting the game fixed it for me. (Late edit to clarify: returning to the main menu, then back to the game did not fix it. I had to completely restart the game to get back to good FPS. )

So i guess the game currently, since the last big patch, has some memory leak or something like that. Anyway, while i can't say without a doubt what the problem is, the mere fact that several people now at the same time report that they experience problems very much points towards the game. Our hardware isn't all breaking down at the same time. But we all got the new patches.
 
Last edited:
It's possible indeed. Anyway it's always helpful to see the videos. Someone could notice something more than I did.

By the way, this is my hardware config:

CPU: Intel i7 7700K (not overclocked)
GPU: Zotac GTX 1080 - 8GB
RAM: G.Skill 16GB (2x8GB - 2133 Mhz)
HHD: Samsung SSD 850 EVO, 250 Go
Motherbard: Gigabyte GA-H270 Gaming 3
Your machine is a fair bit quicker than mine, but I'm not seeing any glitches. Before the last patch play occasionally stopped for a few seconds then continued from where it left off without jumping the gap, but I've had none of that since. Usually, I have just a browser and email client running concurrently, nothing more.
 
Interesting, if everyone who has rubber banding also has stuttering the issues could indeed be related.
You say this as if you are not having rubber banding. Everyone I instance with (who replies) confirms the rubber-banding is happening. Just go the the CG station when there's a couple of players are there, you'll see it. It also happens on PS4, disproving the grand conspiracy that thousands of ED players had their RAM go bad the day of the September update.
 
You say this as if you are not having rubber banding. Everyone I instance with (who replies) confirms the rubber-banding is happening. Just go the the CG station when there's a couple of players are there, you'll see it. It also happens on PS4, disproving the grand conspiracy that thousands of ED players had their RAM go bad the day of the September update.
So it's not the same issue, otherwise everyone would have stuttering and freezing.
 
You say this as if you are not having rubber banding. Everyone I instance with (who replies) confirms the rubber-banding is happening. Just go the the CG station when there's a couple of players are there, you'll see it. It also happens on PS4, disproving the grand conspiracy that thousands of ED players had their RAM go bad the day of the September update.

During wing CZ's two nights ago the only rubberbanding was the one with a connection even dodgier than mine, he logged out and back in and it was fine after that. I used to get it a lot before improvements to my connection now I only ever get it if bandwidth drops.

You may be griefing everyone you instance with by inflicting dreadful rubberbanding on them :D(y).
 
During wing CZ's two nights ago the only rubberbanding was the one with a connection even dodgier than mine, he logged out and back in and it was fine after that. I used to get it a lot before improvements to my connection now I only ever get it if bandwidth drops.

You may be griefing everyone you instance with by inflicting dreadful rubberbanding on them :D(y).
Maybe Ducky McDuckface needs to dust off his wooden router?
There have been several network related changes in the latest update. I'd say it's not unlikely that some issues affect a large part of the player base.

PS
I still don't understand how that's related to stuttering and freezing though.
 
Played 4 hours in Open yesterday, with multiple CMDRs around, in VR and while the game may have been a little slower than usual, I had no problems. Softlocks or freezes whatsoever didn't occur for me at all since the latest patch. Could be everyone had fast connections, rubberbanding for me usually occurs when one of the guys has a slow one.

O7,
🙃
 
Played 4 hours in Open yesterday, with multiple CMDRs around, in VR and while the game may have been a little slower than usual, I had no problems. Softlocks or freezes whatsoever didn't occur for me at all since the latest patch. Could be everyone had fast connections, rubberbanding for me usually occurs when one of the guys has a slow one.

O7,
🙃
One way to find out is to have a rubber-band CMDR join a silky smooth CMDR in the same instance and see what comes from it. Science!!

iu
 
I still don't understand how that's related to stuttering and freezing though.
I'm get stuttering in Solo, so I don't think it is, except perhaps if something in the net code that also triggers due to server data moving around. My whiplash effect (new since update) is fairly deterministic, as it often happens in the same basic places - shortly after exiting hyperspace, approaching a station to dock, etc.

That said, I do not consider the game unplayable. Jarring, yes, downright annoying during a busy CG, very much so (I'd fly in Solo if I was taking the CG seriously), but I'm not getting regular freezing or lockups.
 
Another data point - I don't see rubber-banding when instancing with a large group of players out in the middle of nowhere, like the epic PvP battles I've joined around the CG. Therefore I conclude that the rubber-banding is caused by sharing NPC telemetry between players in areas like a station.

Personally, I think most NPC traffic should be "diverted" during a CG, like how roads are closed to make way for VIPs and military convoys. I've seen more than enough CMDR traffic at the CG station. NCPs are not needed, except perhaps a couple of police ships outside. Surely this would clean up instancing!
 
Speaking of science, I notice that the white knights haired heroes never have any bugs, ever, so I consider their findings a statistical anomaly that can be ignored :p
 
I'm get stuttering in Solo, so I don't think it is, except perhaps if something in the net code that also triggers due to server data moving around. My whiplash effect (new since update) is fairly deterministic, as it often happens in the same basic places - shortly after exiting hyperspace, approaching a station to dock, etc.

That said, I do not consider the game unplayable. Jarring, yes, downright annoying during a busy CG, very much so (I'd fly in Solo if I was taking the CG seriously), but I'm not getting regular freezing or lockups.

That's exactly when I used to get it, also when NPC wings joined CZ's. In my case it was definitely bandwidth as if you run with CTRL+B enabled you can see it spike.
 
Back
Top Bottom