[Dark Souls 2] Cannot launch game with GeDoSaTo enabled

[awksie]

So, it worked with the last version posted to the blog (release 10? 'poltergeist' I think), which I had configured to run the game in 3840x2160@60 on my 1920x1080@120 monitor; I ran the auto-updater today and now it doesn't work.

When I try to launch the game, the window comes up as normal, pure white, and normally, after a couple of seconds, the game would start to load, but now, nothing happens. I tried this a few times, alt+f4-ing the game (which gives me the Windows 8 "not responding" dialog) each time, and after the third or fourth time, I disabled GeDoSaTo and opened the game (which launched in 1920x1080 windowed, as it was unable to find the configured 3840x resolution), then tried enabling GeDoSaTo, at which point the game crashed -- and took Steam with it!

Steam wouldn't even launch, after that; I had to completely exit GeDoSaTo to launch Steam. I'm not sure what happened, but it was bad; as soon as I launched Steam, the Steam error reporter would come up for a split second and then that would crash out too. Is GeDoSaTo trying to hook into Steam for some reason?

After I got Steam running again, I loaded GeDoSaTo again, and then I set loglevel to "9", and tried to start the game, and let it sit for "a while". I don't know how long, but it wasn't ages; I alt-tabbed to IRC and chatted for no more than 2-3 minutes. (According to the image below, it was indeed 2 minutes.) Finally I closed the game and checked the logs folder only to find this:

It's so big I can't even open it. So I tried again, and this time closed the game very fast -- it still generated a 30Mbyte log file, which you can retrieve here: http://www.mediafire.com/view/8wwmzrkzmhs3nty/DarkSoulsII_Sun_Aug_17_02-03-09_2014.log

Sooo, I'm kinda stuck. I did try disabling borderless window, which made no difference.

Game runs fine without GeDoSaTo.

[PeterTh]

I can't access that log file (I get an "access denied" message). Can you upload it somewhere else/make it accessible?

For now, I can just say that DS2 works perfectly here, it''s the one thing I always test before I push a new build.

A few things for you to try:

• completely delete any old GeDoSaTo installation
• check the contents of the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs" and "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs" registry paths
• disable UAC

Let me know if any of these change the behaviour.

[PeterTh]

The Steam issue at least may be fixed by https://github.com/PeterTh/GeDoSaToTool/commit/af33ee78a96f8ed5e2bf83f3323158eff4f96138.

[awksie]

Really, you can't get the file? Here's a different link: http://www.mediafire.com/download/8wwmzrkzmhs3nty/DarkSoulsII_Sun_Aug_17_02-03-09_2014.log

The link Mediafire gave me originally was a 'view' link rather than a 'download' link. Sorry about that! I've never uploaded a plaintext file there before.

I'll try the new version.

[PeterTh]

Ok, that log file is totally insane. I don't even have any idea what might be going on there, but I'll try to look into it.

[awksie]

Well, no change in behavior with the current version.

The only oddities in my setup are that I disable the Steam in-game overlay, and that I'm using multiple displays with two different GPUs, my Geforce and my Intel HD. I tried enabling the Steam in-game (I have it disabled normally), to no avail.

I disabled the Intel HD and lo and behold the game launches in fullscreen mode! However, oddly, it initalizes Direct3D three times (I assume, as I get the Downsampling: message 3 times.) Everything works; I went in-game and messed around a minute, and I can even change resolutions in the video menu without a crash.

HOWEVER, forceBorderlessFullscreen -- which I require to use the strobing mode of my display -- doesn't work, even with my second display disabled. The log ends up with a bunch of these: EnumDisplaySettingsExA .\DISPLAY1 -- 264575 -> Fake

Well, 264575 of them before I Alt+F4, obviously -- and that's doing it as soon as Windows will let me. I should have zipped up the previous file, here's a <500K download with two log files -- the first one is a working launch and exit of the game, and the second one is an attempt to launch in Borderless mode. http://www.mediafire.com/download/76fr5zio1mt057f/awksie&#39;s_das2_logs.7z

Thanks again for all your help, Durante! I'd absolutely make a donation if I hadn't just lost my job! D:

[PeterTh]

Ok, this might have something to do with your refresh rate. Have you tried it at 60?

[awksie]

Tested: 120hz desktop / presentHz 60 / forceBorderlessFullscreen false = working 120hz desktop / presentHz 60 / forceBorderlessFullscreen true = crash 120hz desktop / presentHz 120 / forceBorderlessFullscreen false = working (with strobe!) 120hz desktop / presentHz 120 / forceBorderlessFullscreen true = crash 60hz desktop / presentHz 60 / forceBorderlessFullscreen false = working 60hz desktop / presentHz 60 / forceBorderlessFullscreen true = crash 60hz desktop / presentHz 120 / forceBorderlessFullscreen false = working (with strobe) 60hz desktop / presentHz 120 / forceBorderlessFullscreen true = crash

And just for farts & funnies, I enabled my second GPU again, which still makes everything crash all the time. Hope that helps.

edit: just tried new build 0.12.1236 and no change. ( ;∀;)

[PeterTh]

Can you try again with the latest version?

[awksie]

I ran the updater, which didn't seem to change anything? Not sure if I already had the latest version or not.

Anyway, no changes. Let me check the logs and see if there's anything notable.

edit: No, same as before... these are the last few lines of the log, which I probably don't need to post since they're the same every time, but anyway:

CreateVertexBuffer: length 96, usage: 00000000, fvf: 00000000, pool: 1 --> 00312100 GetAdapterModeCount Adapter 0 | D3DFMT_A1R5G5B5 ------ -> 0 (reporting 0) GetAdapterModeCount Adapter 0 | D3DFMT_A2R10G10B10 ------ EnumDisplaySettingsExA .\DISPLAY1 -- 0 -> Fake (on and on and on and on and on for pages) EnumDisplaySettingsExA .\DISPLAY1 -- 183455 -> Fake

[PeterTh]

Just to make sure, which version is reported? SHould be build 1237

[awksie]

Aha, it's 1236. Let me try running the updater manually again.

[PeterTh]

You shouldn't have to, it should detect that it's not up to date :/

[awksie]

Yay! It works! Even with second GPU and my other two monitors enabled! Hehe. (*'▽')

Have some tea! ^^) _旦~~

I think it didn't automatically detect because I wasn't re-launching GeDoSaTo every time; I hadn't re-launched it since I clicked the update button in the app to update to 1236.

On a (maybe?) related note, the option to choose which graphics adapter to run the game on would be neat, if that's possible. I don't know if the game is hard-coded to use adapter 0 or what.

[PeterTh]

That's easy, make a new issue for it so that I don't forget, I'll stop here for today.