Its not just any forum its the dedicated forum of the thing in question, so people who both like it and find it works should probably be expected to be encountered on a regular basis.
Game unplayable both OPEN and SOLO, Frontier please fix your game!
- Thread starter VR SenseiMatty
- Start date
Its not just any forum its the dedicated forum of the thing in question, so people who both like it and find it works should probably be expected to be encountered on a regular basis.
Of course, I'd bet most bugs don't affect everybody.
@Sensei,
just a thought, do you have a buddy around that could come along with his computer to your place? Hook up, see whether Elite runs without the described issues. In the - in my opinon - unlikely event that everything runs smoothly on his, well, you can concentrate on your local HW & Connection. If this goes as I would assume, same problems occurring, it is useful information for FD Support, is it not?
As others said, so many parameters are involved, diagnosing is best performed by exclusion strategie. I know, pain in the butt, but I remember when I did music on keyboards, many keyboards, only an Atari hooked inbetween for sequencing, many external modules, drums etc. all in a network, and all of the sudden something refused to work, the only chance to eliminate errors was to take all units out of the network, reboot, and add one after the other to begin eliminating possible faulty hardware etc. and take it from there.
I think same applies here, I would start eliminating the possibility of error on your side first, then up date this information to FD.
Hope you get it sorted soon.
just a thought, do you have a buddy around that could come along with his computer to your place? Hook up, see whether Elite runs without the described issues. In the - in my opinon - unlikely event that everything runs smoothly on his, well, you can concentrate on your local HW & Connection. If this goes as I would assume, same problems occurring, it is useful information for FD Support, is it not?
As others said, so many parameters are involved, diagnosing is best performed by exclusion strategie. I know, pain in the butt, but I remember when I did music on keyboards, many keyboards, only an Atari hooked inbetween for sequencing, many external modules, drums etc. all in a network, and all of the sudden something refused to work, the only chance to eliminate errors was to take all units out of the network, reboot, and add one after the other to begin eliminating possible faulty hardware etc. and take it from there.
I think same applies here, I would start eliminating the possibility of error on your side first, then up date this information to FD.
Hope you get it sorted soon.
Has FD made suggestions on how to verify if this indeed is a bug? It'd make sense for them to do so if they believe this isn't their doing.
Yup I have a ticket open and they are supporting me with the troubleshooting!
Hi Sensei
I have a very similar spec to you so, same gpu, memory, lower spec I7. I got some time to play last night for the first time since you posted; in solo based on your experience I was expecting trouble (I play in VR). I had zero problems, its the same experience as its been for a long time, like I mean years.
What I do see are two big differences and they have to do with the internet connection. I am located in the UK and my broad band connection is fibre and substantially quicker than yours and it brought back some bad memories of the small print in broadband contracts that I first discovered when ED first came out and it crossed my mind the same thing might be afflicting you. Basically my broad band connection had been fine for every game until I played ED then suddenly I had misery with similar symptoms as you are experiencing and I started looking into why ED might be different to other games.
Elite uses a peer to peer network topology which means download and upload speed are both critical. Most people focus on download speed as that is usually what most of us do, download. My very crafty internet provider sells based on download speed, but when you look in the small print their upload speed is a tenth of the download speed and at peak periods they reserved the right to throttle the upstream. I ended up having to upgrade to their best package and that resolved my problems (my kids were even happier).
Regards
KIlvenny
I have a very similar spec to you so, same gpu, memory, lower spec I7. I got some time to play last night for the first time since you posted; in solo based on your experience I was expecting trouble (I play in VR). I had zero problems, its the same experience as its been for a long time, like I mean years.
What I do see are two big differences and they have to do with the internet connection. I am located in the UK and my broad band connection is fibre and substantially quicker than yours and it brought back some bad memories of the small print in broadband contracts that I first discovered when ED first came out and it crossed my mind the same thing might be afflicting you. Basically my broad band connection had been fine for every game until I played ED then suddenly I had misery with similar symptoms as you are experiencing and I started looking into why ED might be different to other games.
Elite uses a peer to peer network topology which means download and upload speed are both critical. Most people focus on download speed as that is usually what most of us do, download. My very crafty internet provider sells based on download speed, but when you look in the small print their upload speed is a tenth of the download speed and at peak periods they reserved the right to throttle the upstream. I ended up having to upgrade to their best package and that resolved my problems (my kids were even happier).
Regards
KIlvenny
It can still be the game's fault even if the problem only occurs on specific configurations. It's the job of FDEV, Windows and hardware / software manufacturers to ensure that the game runs well on all supported systems. It's possible that some bug in the game results in issues on specific configurations. It's also possible that the game in combination with certain Nvidia drivers cause the issues. And it's possible that the game in combination with a specific Windows update causes the issues.
It's very unlikely that the 100 people who report rubber banding all have faulty RAM though...
others have stated the ram. i would also suggest it may be the cpu. memory management is built into the cpu.
i had thought my ram was bad. every test said it was good.
after a lot of messing and switching between amd and intel MBs.
both setups woulds run except constant random BSODs on intel. replaced the cpu by intel and all my issues went.
cpu's memory management had failed
test your ram on another board if possible.
This issue might be related to the IPv6 mode!
I noticed, that the initial server connection upon start took longer than before the September update and was always a IPv6-IP. After disabling IPv6 in the settings, the initial server connection was snappy as before the update.
I will check, whether this also removes the extreme rubber banding with other players present and the extreme lags in using the station menus...
Edit: Of Course, it might also be related to how my ISP is handling IPv6, though this did not change in the last months as far as I am aware.
I noticed, that the initial server connection upon start took longer than before the September update and was always a IPv6-IP. After disabling IPv6 in the settings, the initial server connection was snappy as before the update.
I will check, whether this also removes the extreme rubber banding with other players present and the extreme lags in using the station menus...
Edit: Of Course, it might also be related to how my ISP is handling IPv6, though this did not change in the last months as far as I am aware.
Update to the above:
With IPv6 disabled, rubber banding is significantly reduced. More important: The menu freezes seem to be gone, at least for the station menu. Refueling so far worked instantly every time and the commodity market opened normal with displaying all commodities after 1 or 2 seconds.
With IPv6 disabled, rubber banding is significantly reduced. More important: The menu freezes seem to be gone, at least for the station menu. Refueling so far worked instantly every time and the commodity market opened normal with displaying all commodities after 1 or 2 seconds.
Updating the video driver did nothing for me. I wasn't expecting it to solve rubber-banding or network-related stutter, but I was hoping it might fix the FOV-pop and solo-stutter I occasionally get.
Ahhh, thanks for reminding me! I normally turn off EVERYTHING except IPv4 on a network connection when I get a new computer (I don't need any of this other rubbish), but I hadn't done this yet on my new laptop. Regardless of whether this fixes things or not, I still like to do it. I'll check later to see how it goes.
What I don't understand is Sensei sees zig-zag NPCs in solo, and I would swear this is an issue of sharing NPC data with other CMDRs (something that only happens when sharing an instance).
Speaking of, as I said earlier, I do not have rubber-banding away from the station. I noticed the other day when in a PvP battle in deep space, even when security NPC showed up, everything remained silky smooth. What is unique about stations that causes this phenomenon?
Ahhh, thanks for reminding me! I normally turn off EVERYTHING except IPv4 on a network connection when I get a new computer (I don't need any of this other rubbish), but I hadn't done this yet on my new laptop. Regardless of whether this fixes things or not, I still like to do it. I'll check later to see how it goes.
What I don't understand is Sensei sees zig-zag NPCs in solo, and I would swear this is an issue of sharing NPC data with other CMDRs (something that only happens when sharing an instance).
Speaking of, as I said earlier, I do not have rubber-banding away from the station. I noticed the other day when in a PvP battle in deep space, even when security NPC showed up, everything remained silky smooth. What is unique about stations that causes this phenomenon?
Yesterday I played the game normally without big issues (except rubber banding, some loading time exiting supercruise at busy starports and a couple of rebuys 
).
I did change nothing in my config. Support suggested me to make a clean boot and the game was working fine but it also worked fine later when I did a normal boot.
).I did change nothing in my config. Support suggested me to make a clean boot and the game was working fine but it also worked fine later when I did a normal boot.
Hm, stations are basically very high polygon counts in an instance and hence a lot of collision checks on top of the rendering load. I noticed, that being in/close to stations increase the CPU load (higher fan RPMs).
Did some further tests with IPv6:
As soon as I enable IPv6, the game shows several seconds of a logging in message. Once in the main menu, it shows several seconds "getting server adress" and needs further seconds to establish a connection to the server. If this happens in game as well, it might explain the limpet/station menu freezes upon accessing the transaction servers (without the messages of course).
With IPv6 disabled in either "AppConfigLocal.xml" or the router itself, the logging in, getting address and server connection takes at most 1 second for each step. The station menus are very snappy. As I am doing the community goal right now, I did not check limpet behavior, yet
=>Going to leav IPv6 disabled for the time being.
I hope it's just coincidence and your issue will come back, otherwise a certain Duck will need to eat some hats.Yesterday I played the game normally without big issues (except rubber banding, some loading time exiting supercruise at busy starports and a couple of rebuys
I did change nothing in my config. Support suggested me to make a clean boot and the game was working fine but it also worked fine later when I did a normal boot.
I'm only eating a hat if that specific obnoxious troubleshooter (or you) fixes rubber-banding for everyone. Has that happened yet?
As I wrote earlier, I'm not having problems to the serious extent Sensei is, and I suspect even if the seriousness of his problem is solved, the bigger problem hundreds of us (your number, not mine) are seeing will still be there.
That said, if eating a hat will bring back my buttery smooth non-studdering non POV-popping pre-update experience, well then pass the ketchup!
Deleted member 182079
D
Similar experience (sans rebuysYesterday I played the game normally without big issues (except rubber banding, some loading time exiting supercruise at busy starports and a couple of rebuys
I did change nothing in my config. Support suggested me to make a clean boot and the game was working fine but it also worked fine later when I did a normal boot.
) and we shared the same instance a few times too o7The rubber banding is AWFUL though. At some stage I exited through the mail slot in my Cutter, while another Cutter zig zagged and jerked along at the same time. Not sure how we managed not to get stuck. I've never seen it this bad and it's very consistent i.e. it happens almost always now especially if another player is around. Really hope they fix this soonish.
IIRC almost everyone agreed that rubber banding is probably caused by Frontier, while stuttering, freezing and lock ups could be related to the local machine. Your reply to that was always sarcasm, irony and snark, suggesting that every issue must be caused by Frontier and we shouldn't even imply that people could try to look for other solutions while waiting for an update.
Still love you though!