Larian Studios Forums Divinity - Original Sin Divinity - Original Sin - Enhanced Edition Cannot Play Coop online multiplayer on Xbox one

The submission process involves testing the patch, which requires a full playthrough of the game, which takes at least a week.

The patch has not failed submission, nor would I expect it to, given that Sony approved it and released the PS4 patch last Thursday. If there are any delays, or it does fail, there will be an update about that.

Hopefully Microsoft will release the update this week. If they don't, I'll see if I can find out what is going on with it. AFAIK they are just slower than Sony, since there were no significant differences between patch creation and testing at Larian, and I assume Focus would have started the submission process at the same time.

Microsoft does not play the entire game all the way through. They take an endgame save from the developer and are mostly worried about the Technical Certification requirements for the game. Either way, you said it was in submission on the 6th and it is now the 28th; that is a bit more than one week. I'm not trying to be antagonistic, I really just want to be able to play what I paid for.

are we there yet?

I feel like we wont see a patch until early 2017 at this rate.

Yeah, this is very frustrating. What I don't understand is your refusal to give a steam key for the game to those of us who paid you $60 and have nothing to show for it. We bought the game specifically to play the online coop together, and really overpaid for this game relative to other RPG's on the market for access to that feature alone (i.e. if I wanted to play alone I would have gotten The Witcher 3, a much more impressive single-player game that warrants a $60 price tag).

So why not at least give a steam key so we can get our money's worth on a different platform? Isn't that a lot better than us wanting a refund because you didn't deliver the product we purchased? Is is costly for you to give a steam key or something? More costly than losing customers long term and getting bad press and bad word of mouth?

Raze you need to find out if the patch was ever submitted for Xbox One. Please get us some information.

From the end user's point of view, there seems to be a worrisome lack of communication between all parties involved. It is like Larian and Focus aren't talking and ultimately Microsoft is blamed. In the end, your xbox one customers still have a broken product.

I will point out that other developers and publishers, your competitors, don't seem to run into such severe delays and lack of info like this.

Also of concern, why would there be assumptions about Focus' operations? If I were in your position, I would choose to contact them, verify status, and know for certain. (...and update the community with hard fact instead of assumptions.) Remember: technically, they work for you. Perhaps in the future Larian should consider handling their own ports instead of outsourcing?

Finally, I want to agree with Dr.Vengeance. We aren't going out of our way to be confrontational, we are just frustrated with a problem that shouldn't exist in the first place that is just dragging on for an unusual amount of time. The core of that problem is that it appears that you don't know any more than we do, yet you represent Larian. The vague responses we keep getting are only fuelling the fire. We need acknowledgement (obviously the problem isn't as hypothetical as you suggested earlier) and factual responses that contain actual substance we can depend on in order to rebuild our trust. I know your job is tough, Raze, and requires an immense amount of patience; thank you for that. But imagine yourself on our side of the fence, money paid for a product we can't properly enjoy.

For that particular 'assumption' I am not directly involved with Focus or the console patch submission process, so I can not say for certain that both started exactly the same time. It is possible some testing could have been a little slower or people off sick, which could add up to days difference, but I can't reasonably see there being a significant difference, especially since the last ETA I got made no mention of that possibility. Verifying that assumption seems pointless, IMO.
I will certainly check on the status of the update, though.

What 'vague' responses are you referring to? The fixes for a problem that wasn't reproduced enough for the programmers to be 100% sure it would solve every case? The contingency plans that require cooperation from other parties, so are not entirely up to Larian? The release ETA, which is inherently inaccurate, subject to delays and at this point determined by another company?
In the long term, making definitive statements about uncertain things causes more problems than being vague. If I could make definitive statements, I would certainly do so, as that would be much easier and faster.

I've played games a lot longer than I've worked for Larian. Being on, or having access to, the developer 'side of the fence' doesn't actually remove people from the gamer 'side' (not automatically, anyway).

Well, Raze, you have a bright future as a politician. Talk constantly, say nothing, cover your ass. For example, your statement from 11 days ago: "If things go smoothly, the patch should be released this month, possibly even this week" led everybody to believe that something was quite possibly coming soon - certainly by the end of the month, maybe quicker. Today is January 31st. I'm going to ASSUME the patch will not be approved on a Sunday, but hey, you covered your ass by saying "if things go smoothly". Obviously, things didn't go smoothly. Do you have any info on what didn't go smoothly? Have you been given a new ETA? Do you feel the urge to use the term "double plus ungood" in your next response?

'If things go smoothly' means 'if things go smoothly'. Should I have made a definite statement about when Microsoft would do something that is entirely up to them at this point? Obviously not, and you would have criticized that, was well (and most likely not giving an update at all).

You are ignoring the fact that the 'possibly even this week' was entirely accurate for the PS4 patch, with Sony releasing it the next day.

No, I don't have any updates; today is Sunday. As I said Wednesday, I will check tomorrow.

If you haven't read 1984, I would recommend it. If you have, I think you may have missed the point of newspeak.

I have read 1984, and have not missed the point. The point of the dumbing down of the language was specifically to eliminate descriptive, accurate terminology in favor of lowest common denominator terms that came to lose nearly all meaning. Thus "bad" was determined to be unnecessary, when "ungood" would do. "Very bad" or "horrible" were too descriptive, when "double ungood" would do. In the end, words lost nearly all meaning and any degree of accuracy. I'll leave it to you to piece together why I made these references to your statements about the upcoming patch and its' likely release window.

The point of newspeak was controlling thought, not eliminating accuracy. Removing differences in meaning between words by eliminating synonyms and replacing negative words by prefexing a positive word with 'un' was intended simplify language to control thought, and failing that, leave people unable to articulate any dissent.

How exactly am I suppose to give an accurate release time for a decision being made by another company, in a process inherently subject to delays, which Larian is not directly involved in?

I gave the time frame when the patch was expected to be released, when Larian was reasonably confident it should be released soon. Sony released the patch the next day. Somehow you expect that not only should I have known Microsoft would take longer, but I should have know exactly how much longer. If Microsoft had that information themselves at the time, or even a more accurate ETA, they did not provided it to Larian.

I've been watching this thread for a while because I'm having the same annoying issue on XB1, my brother and I would love to play coop. But I want to make this post now because the unrealistic attitude of some people here is even more annoying to me. Please stop raging at Raze, as he said the ball is in Microsoft's park right now and he's not a spokesperson for them.

Larian's actions and communications regarding the patching process has so far been above average in my experience. I'm hoping that Microsoft takes its time to properly test the patch in a production-like test environment. Also, while I hope this patch fixes the issue ASAP, be prepared for a possible longer wait in case the fix does not work. There are no guarantees at this point, only hopeful estimates.

Hey everyone one should give it a try again me and my wife were just able to log on coop on separate consoles and I'm super happy!!!!

In the end, I regret having an opinion at all because it got me nowhere and this thread has devolved into something other than the original issue. The 1984/Newspeak banter is case in point. The argument isn't even about the Xbox One lack of ability to play co-op anymore. If anyone is upset with Raze, it is that type of combative commentary that is inviting the backlash. His speed of communication however is to be commended. (Even if the responses aren't what we want to hear as end-users.)

I've tried to keep my posts as diplomatic as I can under the frustration of buying two copies for my wife and I, the finger pointing and the antagonism from both sides. But you are right, the way this whole issue is unfolding makes it tough to stomach.



I encourage you to expand your library of games from any variety of publishers/developers to enhance your experience.



I would expect this responsibility is probably up to Focus. Unfortunately a "production-like test environment" in this case would need large control group of test-players to catch issues that would remain otherwise invisible until it hits the wild. I think this is why such a glaring issue as broken co-op (xbox1) exists in the first place. Probably not enough testing, or means of testing for the Xbox One platform. I too hope this is resolved.



This is my primary fear, and core of my frustrations. If the very first (yet to be released) patch has caused this much confusion and volatility, both game-related and community, the future looks abysmal.

FuzzForce:

My wife and I tried again and failed. Same "Connection Failed" message. Seeing as I have seen no patch downloaded, this doesn't surprise me.

To bring this back to troubleshooting; Is it safe to assume you and your wife are on the same network? (Two consoles, one house, both using the same internet connection?)

Edit: To elaborate, as others have said previously in this thread, the issue appears to be when players initiate an LAN-to-LAN connection. WAN-to-LAN doesn't seem to have a problem. Seems like the game demands a network address translation when it needs none for LAN-to-LAN. This may explain why some users experience the problem, and not others. Some routers may allow for a loopback, while others may not.

So here what's I'm doing me and my wife play in the same room I'm connected to lan she uses Wi-Fi. We do a hard restart on the console and I log into the game first and she does not load the game.. she stays at the home menu and I send here the invite to play. It has works this way 2 days in a row so it can't just be a fluke right.

Hrm, we have both been in-game when we sent invites to each other. I will try your method of having one player out of the game when they receive the invite.

Otherwise our set up is the same. My xb1 is wired, while hers is wireless over 802.11n.

I'll post back with results when I can go try it out

No good, the issue persists and the workaround doesn't work for me.

I tried the method listed above twice. Once with my account logged in the game first and her account on the home menu after a cold-boot of both XB1's, and then again with her in game first with me on the home menu after a second cold-boot.

I was hoping this would work as it would give the devs a more precise method of locating the problem. Guess we'll see what happens whenever the patch is released.

I'm sorry to hear that. I thought I found a way to get around it.