Divinity: Original Sin 2

Divinity: Original Sin 2

View Stats:
Boink Sep 1, 2018 @ 2:12pm
[Bug] Quitting DE = hard lock, required manual power reboot
As title, not very impressed as this damages hardware. Selected quit game from reload screen, game hung, couldn't even access task manager - entire OS frozen.

I deleted the original folders because I don't want x2 copies of the same game. Apparently this causes the game to hard-lock on quit?

Any solutions? So far the free DE has been one long headache and annoyance.
Last edited by Boink; Sep 1, 2018 @ 2:14pm
Originally posted by tomsolo:
Try this: Disable Support tool in regedit (larian/Dos2/SupportTool -> set no to all) - after this launcher maybe will be not working until to revert.

Start Dos2 with -> SteamApps\common\Divinity Original Sin 2\DefEd\bin\EoCApp.exe
< >
Showing 1-15 of 23 comments
Adeptus Sep 1, 2018 @ 2:35pm 
You need both versions installed. I know it sucks but there is no workaround right now.

And no i dont have any crashes.
Boink Sep 1, 2018 @ 2:51pm 
I just confirmed this for a 2nd time - quitting from the main menu 100% gives a hard lock. Which is just frakking insanely dumb.

Originally posted by Fane *DivinityPLS:
You need both versions installed. I know it sucks but there is no workaround right now.

And no i dont have any crashes.

I installed both: someone in a thread on this board stated that you could delete the original version + data directory and still run DE without a problem.

They lied and could lead people to damaging their computers.

Apparently the moderator randomly deleted that thread - it was a complaint about the 70 gigs size. Good job moderators, deleting feedback / complaints about the DE launch, really useful of you!

To sum up: the game loads fine, runs fine, saves fine... but hard-locks on quitting. This is frankly cruddy coding and/or should have been tested (because, you know, who is *not* going to attempt to remove the duplicate, esp. if they've already done a few play-throughs).

So: do NOT manually delete folders.

Since Classic is already deleted and DE is breaking stuff, time to uninstall. What a shower.



Edit: since I never tested DE without deleting classic, for all I know the hard-lock on quit could be a bug within DE rather than related to manually deleting files. Whatever, hard-lock and forcing hard reboot is a total no-no, no matter if other content is manually removed. DE should do the check at the start, not on quit.

>Uninstalled. Unimpressed.
Last edited by Boink; Sep 2, 2018 @ 2:15am
Boink Sep 2, 2018 @ 2:15am 
Bump for visibility.

This is not cool Larian, not cool.

Why this was a bad idea:

1) No opt-in for DE: was instant d/l, game refused to load without Steam update. Thanks for removing my personal preferences there.

2) 8+ gigs, unpacked ~22gig, duplicated files all over the place: some of us have data caps / bandwidth issues or size issues (SSDs). Making this all not optional = massive annoyance / irksome

3) No option to remove DE or Classic if user did not want them. Thanks for making sure I cannot enjoy the game I actually paid for...

4) See above option: nuking from orbit an OS = instant uninstall, don't care. If you're running x2 copies, and forcing an install: you make DAMN SURE they can run as stand-alone products.

Kickstarter backer from the original, not that this matters, but I've supported Larian for a while now.


All in all: console hardware companies are making you bad people Larian. Not cool.
Last edited by Boink; Sep 2, 2018 @ 2:27am
eRe4s3r Sep 4, 2018 @ 10:07am 
Can't you just ALT + F4 ? ;P
TLDR: He made a dumb choice and now wants to complain about it and have everyone feel sorry for him. Also, complaining about a free extension of a game because he can't manage his file space. (Try deleting some porn)
Boink Sep 4, 2018 @ 11:08am 
Originally posted by The Maroon Typhoon:
TLDR: He made a dumb choice and now wants to complain about it and have everyone feel sorry for him. Also, complaining about a free extension of a game because he can't manage his file space. (Try deleting some porn)


No, Eric is incorrect here. Or is that Mike?

The folder structure should have had no issues with simply removing Classic & Data, as long as you didn't chose 'Classic' from the launcher.

However, the launcher / Steam are doing some kinky things behind the scenes. He could look up on the official Larian forums people having issues with Steam cloud saves interfering with DE, but he's here to troll, not learn.


On a serious adult note: warning people that they can OS lock their computers, requiring a hard power-down / reboot isn't "complaining" or "wanting people to feel sorry".

It can, under rare instances, permanently damage hardware. Esp. with SSDs (older models).


So, hush: let the adults talk, Eric, and go bother someone else on Reddit or something.


It would have been taken seriously if you hadn't ended the topic of attempting to place the blame on the game itself as for the reason of your cpu crash instead of your decision to delete game files. But what do I know? I'm just a peasant.
Boink Sep 4, 2018 @ 11:19am 
Originally posted by The Maroon Typhoon:
It would have been taken seriously if you hadn't ended the topic of attempting to place the blame on the game itself as for the reason of your cpu crash instead of your decision to delete game files. But what do I know? I'm just a peasant.


Sigh.

We'll make this simple for you.

Classic & Data folder *are not used by the DE .exe*. However, there is a (hidden) check from the launcher it would seem, but not on launch. Thus you **can** safely delete the Data folder but NOT the Classic folder itself, since the launcher apparently requires a file in there to refer to.

If you cannot see the difference between:

a) A CTD / program refusing to load and a hard-lock due to DE itself running fine without those folders, but the launcher requiring them on quitting the application and randomly deleting files from an active directory (which is what you've very immaturely and without much finesse or nuance attempted to imply was what was happening, which is childish / stupid in the extreme), well then: stay in school.

b) You're not very good at this insult / trolling business. I quite clearly stated:

Originally posted by Boink:
To sum up: the game loads fine, runs fine, saves fine... but hard-locks on quitting. This is frankly cruddy coding and/or should have been tested (because, you know, who is *not* going to attempt to remove the duplicate, esp. if they've already done a few play-throughs).

I 100% stand by this statement. DE itself isn't causing the hard-lock, and this issue really does not need to exist. It shouldn't have made it past initial QA / design phase.


~

Now go away Eric. Not impressed by the Corporate cover being deployed either (that's not @ you, that's @ the console business people who are running cover / wrote clauses in contracts etc).
Last edited by Boink; Sep 4, 2018 @ 11:24am
I understand how it works, I don't agree with Larian it was the best decision but seeing how I had no say I don't tell them how to do their job.

"Edit: since I never tested DE without deleting classic, for all I know the hard-lock on quit could be a bug within DE rather than related to manually deleting files. Whatever, hard-lock and forcing hard reboot is a total no-no, no matter if other content is manually removed. DE should do the check at the start, not on quit. "

I can neither confirm nor deny I am under any obligations of such a clause or that such a clause exists.
Boink Sep 4, 2018 @ 11:28am 
Originally posted by The Maroon Typhoon:
I understand how it works, I don't agree with Larian it was the best decision but seeing how I had no say I don't tell them how to do their job.

"Edit: since I never tested DE without deleting classic, for all I know the hard-lock on quit could be a bug within DE rather than related to manually deleting files. Whatever, hard-lock and forcing hard reboot is a total no-no, no matter if other content is manually removed. DE should do the check at the start, not on quit. "

I can neither confirm nor deny I am under any obligations of such a clause or that such a clause exists.


If you want to play adults, there's quite clearly been a Corporate handshake / over-sight deal been done with the console platforms to force this entire DE 'upgrade' into a single package and to prevent splitting the content easily. Aka, what I did.

But that's a bit in depth for a Steam forum. But SONY / MS are really not your friends, even as consumers.
-RG- Baxton Sep 4, 2018 @ 11:32am 
Originally posted by The Maroon Typhoon:
TLDR: He made a dumb choice and now wants to complain about it and have everyone feel sorry for him. Also, complaining about a free extension of a game because he can't manage his file space. (Try deleting some porn)

Why is there always one of these guys? Ho ho delete porn, that's hilarious. Why stop there? Why not just make the games have ten versions totaling 1TB? What are you poor?

I have no idea why you would even post in this thread. Stop wasting your life jumping in and out of threads crying about people's opinions on a discussion forum. You do realize that's where you are at right? Not a board for positive praise, but a discussion forum for different opinions. You don't get post count or twitter points here. If you don't like a thread and have nothing more to put in than your lame opinion nobody asked for, go away.

I have plenty of space for this game but I'm empathetic to other people and this is a very serious issue. The OP paid money and the game changed in a way he didn't approve of. Larian didn't take into consideration several factors that affect a multitude of people(who are obviously not you holy one). You don't like the OP or his thread, deal with it. You seem to enjoy defending ...Larian? Why? Go play the game. They aren't going to rush in and give you a pat on the back. Nobody cares about you.
kcnik Sep 4, 2018 @ 12:54pm 
Originally posted by Boink:
Originally posted by Boink:
To sum up: the game loads fine, runs fine, saves fine... but hard-locks on quitting. This is frankly cruddy coding and/or should have been tested (because, you know, who is *not* going to attempt to remove the duplicate, esp. if they've already done a few play-throughs).

I 100% stand by this statement. DE itself isn't causing the hard-lock, and this issue really does not need to exist. It shouldn't have made it past initial QA / design phase.

Just tried it out, deleted both the classic folder and the Data folder, and everything works as intended. The game runs just like before, and quitting doesnt hard lock my system.
Martha Pepper Sep 4, 2018 @ 1:04pm 
Originally posted by kcnik:
Originally posted by Boink:

I 100% stand by this statement. DE itself isn't causing the hard-lock, and this issue really does not need to exist. It shouldn't have made it past initial QA / design phase.

Just tried it out, deleted both the classic folder and the Data folder, and everything works as intended. The game runs just like before, and quitting doesnt hard lock my system.
I was curious about this too and just tried it out. Deleted the classic and data folders, messed around in-game for a bit, saved the game, quit, and all is working correctly. Quitting didn't hard-lock my system either.
Boink Sep 4, 2018 @ 1:20pm 
Originally posted by Martha Pepper:
Originally posted by kcnik:

Just tried it out, deleted both the classic folder and the Data folder, and everything works as intended. The game runs just like before, and quitting doesnt hard lock my system.
I was curious about this too and just tried it out. Deleted the classic and data folders, messed around in-game for a bit, saved the game, quit, and all is working correctly. Quitting didn't hard-lock my system either.


Well then, what a mystery. I tested this out twice, both times hard-locked on quitting. Out of ~50+ other games installed, system hasn't had a hard lock for 2+ years.

Conditionals:

1) I had prior classic saves in the Steam cloud, some of which were hardcore (i.e. deleted on party death = true). My last save games from classic were all hardcore, i.e. the autosave = hardcore. There have been reports of Steam cloud causing x-errors from the classic on the main Larian forums.

2) I didn't save manually - only the autosave, since I just ran the starting ship to see if it was running fine. I was able to 'continue' on the 2nd load (i.e. used the autosave from entering the now 2nd level of the bridge).

3) Did a pass over the system with usual diagnostics - it's fine, drivers are all uptodate, hardware / memory is perfect. It more than meets the requirements to run D:OS2 on ultra and all heat temps are under 80oC. [Note to Steam teenagers: I'm using software that directly measures the heat sensors and reports if any are faulty. This is not a hardware issue, go back to Reddit]. Likewise, the SSD holding the game had a free ~100+ gigs, so it's not a temp file / space situation.

4) I was running the system in ultra (autodetected), which again has been reported to cause crashes / freezes on the main forums: are you running ultra graphical settings? (esp. shadows?)

5) Did you use the launcher to load DE, or direct via the .exe? I used the launcher both times (and it makes a weird little window). i.e. Does the launcher re-load on quitting the game, or does it just dump you to Steam / OS?



So.

Originally posted by kcnik:
Just tried it out, deleted both the classic folder and the Data folder, and everything works as intended. The game runs just like before, and quitting doesnt hard lock my system.

What do you mean "runs like before"?

My system hard-locked on the 1st run of DE, then the 2nd. It had no errors running Classic (prior to this update).


TL;DR

If you're going to reply "it's your hardware!111!11" - it isn't.
Last edited by Boink; Sep 4, 2018 @ 1:37pm
Martha Pepper Sep 4, 2018 @ 2:22pm 
Originally posted by Boink:
Originally posted by Martha Pepper:
I was curious about this too and just tried it out. Deleted the classic and data folders, messed around in-game for a bit, saved the game, quit, and all is working correctly. Quitting didn't hard-lock my system either.


Well then, what a mystery. I tested this out twice, both times hard-locked on quitting. Out of ~50+ other games installed, system hasn't had a hard lock for 2+ years.

Conditionals:

1) I had prior classic saves in the Steam cloud, some of which were hardcore (i.e. deleted on party death = true). My last save games from classic were all hardcore, i.e. the autosave = hardcore. There have been reports of Steam cloud causing x-errors from the classic on the main Larian forums.

2) I didn't save manually - only the autosave, since I just ran the starting ship to see if it was running fine. I was able to 'continue' on the 2nd load (i.e. used the autosave from entering the now 2nd level of the bridge).

3) Did a pass over the system with usual diagnostics - it's fine, drivers are all uptodate, hardware / memory is perfect. It more than meets the requirements to run D:OS2 on ultra and all heat temps are under 80oC. [Note to Steam teenagers: I'm using software that directly measures the heat sensors and reports if any are faulty. This is not a hardware issue, go back to Reddit]. Likewise, the SSD holding the game had a free ~100+ gigs, so it's not a temp file / space situation.

4) I was running the system in ultra (autodetected), which again has been reported to cause crashes / freezes on the main forums: are you running ultra graphical settings? (esp. shadows?)

5) Did you use the launcher to load DE, or direct via the .exe? I used the launcher both times (and it makes a weird little window). i.e. Does the launcher re-load on quitting the game, or does it just dump you to Steam / OS?



So.

Originally posted by kcnik:
Just tried it out, deleted both the classic folder and the Data folder, and everything works as intended. The game runs just like before, and quitting doesnt hard lock my system.

What do you mean "runs like before"?

My system hard-locked on the 1st run of DE, then the 2nd. It had no errors running Classic (prior to this update).


TL;DR

If you're going to reply "it's your hardware!111!11" - it isn't.
Just had a few more tries at this, I let it autosave (in Hollow Marshes) and it seemed fine on exit and subsequent load of the autosave upon reloading the game.

I don't use Steam cloud at all. It is disabled for all games.

Yeah, everything whacked up on ultra settings at 1080p limited to 60fps in options.

I tried both using the launcher and running it from EoCApp.exe (which is my preference as it actually starts the game up much faster, there's a weird delay of about 15 seconds or so when running it from Steam launcher). Both act as expected when quit from the game i.e. running from the launcher just plops me back at the desktop with my Steam window as it was before running the game, quitting from .exe just dumps me back at the desktop as it was before running the game.

Using these specs (laptop):

I7 7700HQ
16gb
1tb ssd (Steam is installed on this, and Win 10 is on separate 256tb ssd)
GTX 1060 6gb

Not sure what to say really :(

EDIT: Forgot to mention, all drivers are up to date too, except for I've stayed on nvidia 398.36. No performance gain on later versions for me as of yet, and these are perfectly stable.
Last edited by Martha Pepper; Sep 4, 2018 @ 2:31pm
< >
Showing 1-15 of 23 comments
Per page: 1530 50

Date Posted: Sep 1, 2018 @ 2:12pm
Posts: 23