Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
) validating game files
) changing controller settings in "Big Picture"
) restared the game to see if it was a reocurring bug
) tryed to update controller drivers (the were the newest ones)
so your in game chat works ?! cause mine is ♥♥♥♥♥♥♥ gone and it pisses me off
If this is what you're doing and it's not working, I'd let Larian know. This game seems to work fine for some people and be buggy to the point of unplayability for others.
The trigger is supposed to, however, it doesn't. What we find is that the left trigger, dedicated to the party panel, works with the right trigger. The left trigger does nothing at all, ergo we can only access the party panel. Seeing as we're playing Lone Wolves, we don't get a lot of use out of that function. This also prevents us from leveling up, which is kind of a huge deal breaker, lol.
Some research into the matter tells of Xbox One drivers combined with Windows 10 updates messed up the Z-axis controls, despite the fact that we're using a 360 and a ps4 controller (we even tried two ps4 controllers).
We don't know exactly how steam handles controller drivers, especially for ps4 since they're a bit off the map on PC, but we assume it makes use of installed xbox controller drivers and that's what carries the fault over to the ps4 controller.
We're gonna try using a 360 emulator, to see if that does the trick and unmesses (censored btw) the control scheme. We'll keep you updated.
I personally have not had a problem with the game before this and really like it and the story (what I've seen of the story) so far, but it is getting to a point where we are playing it more to show that we can, than to enjoy it...
It just felt like either a driver or a patch messed something up on the controllers, as all the other buttons works as intended but not the triggers, but after troubleshooting for close to 6 hours of total time (yes we also do other things) we still actually don't know what the issue is, but it looks like the triggers are working as one trigger.
Our understanding from doing a bit of research says that the 360 has a trigger layout which goes from 0-100 where the normal value is 50 and using either trigger will make it swing either way. That is, they block each other, so to speak. However, the Xbox One controller is supposed to have two different axis/values here, what with the z-axis and z-axis-rotation (?). However, That does not match up to the triggers in Divinity Original Sin 2 seeming to still cancel each other out. Surely there must be some firmware/driver collision with the game, but since the 360 controller and Windows 10 are both up to date and using the 360 should be supported acccording to other forum posts by Larian*, it's impossible for us to tell where the errors happens.
1) Closed DS4 tool (made sure it is completely closed)
2) Set up the controller in Steam settings as a desktop PS4 controller, made sure that it was connected through steam (change the default light to something else so you know steam is connected by the light)
3) Set up the controller in DOS2 steam settings.
4) In game forced the game to see the controller as a PS4 controller.
That fixed it. Not sure if this would help an XBox 360 controller but you could try (4).
Now if only something could be done about the long loading times sigh.