Honestly it's their servers, if they had more dedicated servers around the world instead of having us all ping to the UK which right now for me is registering nearly a 200 ping on a full strength connection that's 40mpbs we would be fine, but they don't want to invest in the physical infrastructure to do this, and it annoys me to no end.
"Physical" Multicrew broken for anyone else?
- Thread starter Aurora Destiny
- Start date
Yeah. It's just a shame. I wish i could say or do more. But given how long things have been. Being apathetic is the least painful option. For better or worse.
This game is primed for some fun coop stuff, but they've genuinely worked against it with these network problems... No mission sharing.
(You should be able to share all missions. Not just wing specific ones.)
Idk. It breaks my heart.
My buddy spent 90 bucks buying a copy for me and for him, we are both highly disappointed right now in Odyssey, and I told him if I had bought it myself, I would have refunded it by now, full stop I would have. I've beta'd, and alpha'd for probably 8 games in the past 10 years, and I feel like I'm playing an Alpha, I don't feel like I'm even playing a beta at the moment.
To say I'm angry at David, the board, and management at Fdev is an understatement. I'm angry as no tomorrow about this, cause well currently I can't work in RL due to a vestibular injury, my games are pretty well the only thing I can do during the lockdown we have in Ontario currently.
Yeah. I have more faith they will fix most of the expansion over time... But not 80% of longstanding bug or coop issues. Despite this, yea.. None of this should have happened regardless.
Viajero
Volunteer Moderator
Not sure if I understood you correctly but I am not FDEV staff, just a volunteer moderator in the forum, a player like you.
Re logs, I do not think nearly enough players send them actually. We mostly complain, create a ticket and leave it at that. The best logs for FDEV to review are those sets where you have all players that tried to instance together, not just the logs of the player creating the ticket, hence my recommendation to send all players logs in the same ticket.
As a mod you are a rep of the company though correct? While you might not be staff you are technically a representative on the forums in an official position.
Fdev has had over 4 years to fix these issues, they've known about the issues with MC since it came out, and they've failed to do anything about it, they abandoned it in development hell for multiple years and now are caring about it? The only reason they are caring about it now is cause of Odyssey, if they truly gave a crap about their customers, they would have been like "Hey send us these logs" all along, instead they blamed players for their connections, they blamed our routers, they blamed our computers and didn't take responsibility as well, Fdev can see the log server side to see what's going on with it, if we are getting time outs and etc.. I know this part cause I've watched the support staff troubleshoot issues with people on social media for example, the other day they came out on twitter and told a guy he was having a lot of timeouts to the server
Source on my claim: Source: https://twitter.com/Frontier_Help/status/1397088786480312323
So it's not that we as players need to do more, Fdev has logs showing this happening. As well us all having to ping to the UK causes peoples connection to not be the greatest, personally I'd love if they had servers in North America but they don't, my ping to the server today was between 180 to 200 consistently and when that happens the game starts to mess up extremely bad. Like I said Fdev probably already knows the solution, they've had since launch day of elite to actually do something about it but never have.
This happens to me playing on a LAN with my two sons. It's NEVER worked reliably - but it's now much worse in Odyssey.
I have submitted many tickets and full logs over the years. It's still the same.
I have submitted many tickets and full logs over the years. It's still the same.
As with most things Odyssey so far Im not sure Im playing the same game as everyone else. Without messing with router settings or any of that, myself on the west coast linked up with a friend on the east coast. We instanced together from the beginning, jumped in my ship (physically, not multi crew) jumped a few systems over and knocked over a settlement together then hit CZs. Everything went smooth except for a CTD during carrier jumping, but that happens to me every time even by myself. So it is possible that things work. just wonder why its not working for so many.
Was it recent? Its entirely possible things have gotten better overtime as the network and patches stabilize things. My friends have given up for a while.. So i cannot test it.
about 14 hrs ago
we played for about 4 hours together and only had the carrier CTD
My attempt was about a week or two ago. Maybe the network has stabilized more.
Mine was earlier this week, but if the mission server is acting up and the pings are still spiking high cause the servers are overloaded it most likely won't work for everyone, it also depends on what time he was doing it at.
Yeah i just got my friend to play recently. she was scared of all the negative reviews that it was so bad and unplayable. But honestly except for a few connection issues I have had almost none of the issues people have reported.
OP asks if it is broken for anyone else, clearly looking for others who have issues
and then you waltz in here just to tell him you have no issues, which doesnt help OP at all.
The original post was 8 days ago, when the servers were melting and before either of the hotfixes or the patch.
I had the supercruise bug in physical multicrew throughout Alpha and in the first few days of release, but the last few times I've tried it it was flawless.
That was the reason for my post. Has the OP tried again since the fixes, patches and general improvements to server stability?
Viajero
Volunteer Moderator
Volunteer mods opinions are theirs and theirs only, not FDEV´s. In fact, when we post an opinion we are not allowed to moderate that thread anymore. But that is by the by, what you actually said was:
Which is still incorrect as I am not part of FDEV.
Re logs, I just wanted to add my 2 cents in that the more useful ones for FDEV tend to be the ones where they can see several players trying to connect together in the same incident.
The peer to peer system used in Elite seems to be inherently less stable and robust in many regards compared to server based, but it has other advantages too. The issues we have in instancing will most likely be with us for a long time irrespective given the almost infinite arrray of individual internet connection set ups out there for players, but the logs can help in minimizing some of those issues. If you can/want to send them those great, if not well
be my guest.
Last edited:
I'm not sure we have successfully completed 1 high wake jump in physical multicrew yet.
Actually, if people werent so sensitive it does. Everyone replying it doesnt work for them helps the OP even less. people confirming that it indeed can work then that means that the FDev system works (at least in some instance) and would cdrive an objective person to look toward thier own system or ISP to solve the issue.
I played 10 hours in multicrew with 3 different teams yesterday, across a variety of activities. Laser mining, missions, conflict zones, etc.
No crashes or disconnects.
The only issue we had in one session was me trying to get into an instance where two people were already teamed up. They really need to sort this, or pop up a message explaining why I am landing at a station (or joining a conflict zone) where I can see team markers moving around, but not the actual team.
No crashes or disconnects.
The only issue we had in one session was me trying to get into an instance where two people were already teamed up. They really need to sort this, or pop up a message explaining why I am landing at a station (or joining a conflict zone) where I can see team markers moving around, but not the actual team.