I have on more than a few occasions seen [] in solo mode. Actually logged out to check.
Clarity sought on - uh - "mode mixing?"
- Thread starter rOmiLaYu
- Start date
I have on more than a few occasions seen [] in solo mode. Actually logged out to check.
Two things:
1) I didn't realize that "SYSTEM" chat was across all modes. That's very interesting...it also explains a lot. I was tabbing through LOCAL, SYSTEM, and SQUADRON at the initial DW2 jumpout point and man that SYSTEM chat was moving! If it's all three modes, that explains it.
2) The explanation above regarding "flags" makes a little sense to me about the actual "how" this could happen.
Thanks, all!
1) I didn't realize that "SYSTEM" chat was across all modes. That's very interesting...it also explains a lot. I was tabbing through LOCAL, SYSTEM, and SQUADRON at the initial DW2 jumpout point and man that SYSTEM chat was moving! If it's all three modes, that explains it.
2) The explanation above regarding "flags" makes a little sense to me about the actual "how" this could happen.
Thanks, all!
Last edited:
It's quite possible because the modes are just another matchmaking rule - there are no 'Open' servers or 'PG' servers, there are only instances started up by the first player in a location and then players are added to that instance or a new one created based on the matchmaking rules.
If the process managing the matchmaking got overloaded then it's feasible that it started mismatching players in the same instances.
If the process managing the matchmaking got overloaded then it's feasible that it started mismatching players in the same instances.
So, you're saying..
If I select 'open' then the MMS selects the best available 'open' instance or, creates a new one? Likewise, PG etc/Solo just create a new instance?
Kinda makes sense too
No, I'm saying that instances only get created by the first player in a location.
The mode they used to log in defines a matchmaking parameter for that instance.
A second player jumps to or logs in to the same location, and the matchmaking process kicks in.
* Different mode - new instance; same mode - join
* On a block list - new instance; not on a list - join
* etc.
If all the checks say 'join' then the second player joins the first in their instance, otherwise a new one gets created.
Then there are the priority parameters if there are already multiple instances that are equally valid to join:
* Same Wing
* Same Squadron
* Friend List
* latency
* etc.
Once all players leave an instance, after a short period of time, it shuts down.
Last edited:
I'm no programmer, but that makes perfect sense....and if the servers are getting hammered by 10,000 people all at the same time, it's clear how that process could have broken down and people were in a "mode" they didn't select.
Well it is called a game "mode" afterall, not an entirely different PvE server, so when server is under a lot of stress and things get weird, stuff like this could happen, and has happened before. I wouldn't get mad about it, even though it could be made look bad.
besieger, how is there a FSD interdictor on your exploration vessel? I thought it was all about scanning some anemone trees and spacemushrooms, and taking some nice pictures, visiting tourist beacons and driving around circles in SRV's close to Shapley. There even was a forum thread about it.
besieger, how is there a FSD interdictor on your exploration vessel? I thought it was all about scanning some anemone trees and spacemushrooms, and taking some nice pictures, visiting tourist beacons and driving around circles in SRV's close to Shapley. There even was a forum thread about it.
The other thing that people don't realize is that there are no instance servers - the first player in a location is hosting the instance on their machine.
FD's servers are just processing the matchmaking rules, processing transactions, and sharing info like the system seeds, BGS states, station prices, etc.
This is actually where FD could step in to improve the multiplayer experience without changing the network model too much.
Hosting can switch to another player if the first one leaves or if that player is causing the instance to lag.
That switching mechanism could be used in instances with a large number of players to switch hosting to a dedicated FD machine with better capabilities than your average PC.
but the server(s) seem to have a limited number of "slots" for instances,
so if to many player end up on the SAME cloud server, the matchmaking forfeits even the highest priority flag for game modes