Game unplayable both OPEN and SOLO, Frontier please fix your game!
- Thread starter VR SenseiMatty
- Start date
That's pretty cool. Instead of doing nothing while waiting for FDEV to fix the game, we apparantly found a workaround for the issue by fiddling around with our computers. And we can even support FDEV by telling them what's causing the issue. I'd say that's one point for troubleshooting and zero points for being snarky whenever someone suggests to take a closer look at the computer.
What did you say, I can't hear you over all the snark! Funny thing is, if I HAD blocked you (some days I'm tempted), we who remain still would have solved this problem without youThat's pretty cool. Instead of doing nothing while waiting for FDEV to fix the game, we apparantly found a workaround for the issue by fiddling around with our computers. And we can even support FDEV by telling them what's causing the issue. I'd say that's one point for troubleshooting and zero points for being snarky whenever someone suggests to take a closer look at the computer.
IWhat did you say, I can't hear you over all the snark! Funny thing is, if I HAD blocked you (some days I'm tempted), we who remain still would have solved this problem without you
See, this is why I don't block you - humor covers a multitude of sinIprobablymost definetely would've suggested the same solution if I wasn't occupied with arguing against you!
Wait, you're German, where's this humor coming from?
Only when we agree (which surprisingly actually happens on occasion).
Me too. And even when I am wrong, it is the world's fault for not giving me better clues.
HIS router is dusty!
Deleted member 182079
D
Have IVP6 off (only just realised it under networking options in the game... d'oh), still encountering zig zags. Doesn't seem to be the problem (router has sufficient dust levels so can't be that either).
Turning off IPv6 might not completely fix the rubber banding, but it fixed the server caused freezes in all Menus. I can live with some rubberbanding, but the menu freezes (and sometimes disconnects) were killing the fun for me.
If you turn off IPv6 in the games network options, you might not be able to turn it back on in the options (which might be a seperate bug). In my case, I had to change it to on in the settings file (AppConfigLocal.xml) for tests.
Playing with IPv4 only might cause some additional latency towards/from players with IPv6 only connections, hence FDev should fix the IPv6 server transactions quickly.
If you turn off IPv6 in the games network options, you might not be able to turn it back on in the options (which might be a seperate bug). In my case, I had to change it to on in the settings file (AppConfigLocal.xml) for tests.
Playing with IPv4 only might cause some additional latency towards/from players with IPv6 only connections, hence FDev should fix the IPv6 server transactions quickly.
Last edited:
I turned off everything in my Wi-Fi adapter except the IPv4. Unfortunately I can't confirm it helps. Yes, first two runs between Teveri and Diso was without rubber banding and zig-zagging but later it happened again. And I aslo saw something new at the station: Invisible Cutter! That was other commander. I was able to see only the fire and trails from his engines, but no ship!
Something is messy here.
edit
But I think FDEVs made some changes since few days, because rubber banding for me looks smaller that before. Or maybe it's because traffic is smaller at this time of day.
Something is messy here.
edit
But I think FDEVs made some changes since few days, because rubber banding for me looks smaller that before. Or maybe it's because traffic is smaller at this time of day.
Last edited:
Deleted member 182079
D
With ipv4 only, the rubber banding was as bad as with 6. Ships would glitch through the station it was terrible (and holding your breath when traversing through the mail slot yourself in case another jumpy ship may get in your way). I find it very difficult to play like this, not only is it nasty on the eye it's affecting gameplay.
Did a test run in Solo (at the CG) and everything smooth, no issues at all.
Did a test run in Solo (at the CG) and everything smooth, no issues at all.
DeletedUser191218
D
As an update to this topic:
With a lot of research and testing, I was able to get IPv6 working again to a satisfactory level in Elite. The (final) trick was, to enable IPv6-Pinging in all firewalls for the PC running E. You might give it a try, though the exact way to set this up is probably different in every router.
After the changes, the startup procedure with enabled IPv6 is on par with IPv4 only. Also, I did not notice any timeout hangs in the menus.
With a lot of research and testing, I was able to get IPv6 working again to a satisfactory level in Elite. The (final) trick was, to enable IPv6-Pinging in all firewalls for the PC running E
. You might give it a try, though the exact way to set this up is probably different in every router.After the changes, the startup procedure with enabled IPv6 is on par with IPv4 only. Also, I did not notice any timeout hangs in the menus.
![[PS4] Filthymick420](https://forums-cdn.zaonce.net/data/avatars/m/201/201444.jpg?1555738739){kind=avatar}
Ipv6? Is that a vape mod? Ive had an ipv3 and ipv4. Those were vape mods, so yea
Last edited: