[quote=hellbiter88][quote=SafiraPanther]I use the Steam engine, and it works just fine when I launch the classic DOS2 Editor, but when I attempt to launch the one for the DefEd, it straight up won't load. [/quote]
We do have the same issue, it seems. I can run the Classic DOS2 editor, as well. The Def Ed editor will not even start up.
So at least it's not just me lol. [/quote]
It's not just you. I was literally using it this morning fine, then it stopped working over lunch. I registered for these forums to post that I've been trying to fix it for several hours now and nothing has worked. I've tried:
1) Rebooting Windows 7.
2) Uninstalling and reinstalling the tool.
3) Uninstalling and reinstalling both tool and game (in process, stupid slow Steam download).
4) Checking/repairing kernel.dll (the specific fault module).
5) Checking Windows Event Logs.
According to the event logs, the Application Error says:
Faulting application name: DivinityEngine2.exe, version: 3.6.29.9522, time stamp: 0x5ba0cad2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23915, time stamp: 0x59b94f2a
Exception code: 0xe0434352
Fault offset: 0x000000000001a06d
Faulting process id: 0x8c0
Faulting application start time: 0x01d44fa8d8a4e24a
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\The Divinity Engine 2\DefEd\DivinityEngine2.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 17fe96dc-bb9c-11e8-829d-408d5cbffba8
According to the event logs, the .NET runtime error says:
Application: DivinityEngine2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
at <Module>.main(System.String[])
Usually when something works fine at first, then stops working on the same boot of Windows, something glitched on that boot, but I've done everything including a hard power reset to fix that sort of issue, and none of the file integrity tools I've used indicate anything on my system is corrupt. It'd be nice to get this fixed, to say the least - this is now the second time in three days I've reinstalled everything (including the game) because of some kind of program error.
