dalamud err: could not get swapchain address about dalamud

[ff-meli]

Thanks! This helps narrow things down a bit, at least.

Test builds are going to be on hold a bit because of the patch, which I assume will derail dalamud in general for a day or two.

I'll make another after that, though it will probably just be adding logging to absolutely everything in the path that crashes, since it won't be nice and give us actual crash info (at least I know whereabout it is now though!)

[Aida-Enna]

Are you sure you're using the latest version of the game? Silly question, I know. Just gotta cover all the bases 😃

[MaxineMutini]

i should be, cuz the default launcher boots it with no issues

[Aida-Enna]

Can you post the error it gives you when you launch as admin? You can just post it here.

[MaxineMutini]

[MaxineMutini]

[Aida-Enna]

Try this https://github.com/goaaats/FFXIVQuickLauncher/wiki/FAQ#q-im-getting-a-msvcp140dll-was-not-found-or-vcruntime140dll-was-not-found-issue-help

[MaxineMutini]

on it

[MaxineMutini]

there are no longer any errors in either log file, but it still crashes

[Aida-Enna]

To be clear, when running both as admin and not, the game crashes at the square enix logo with no popup error or anything in the logs?

[MaxineMutini]

correct

[MaxineMutini]

just tried again as default user and got this error in dalamud.txt

[FTL] Unhandled exception on AppDomain
System.NullReferenceException: Object reference not set to an instance of an object.
   at ImGuiScene.RawDX11Scene.Dispose(Boolean disposing) in C:\Users\jonas\Documents\repos\Dalamud\lib\ImGuiScene\ImGuiScene\RawDX11Scene.cs:line 262
   at ImGuiScene.RawDX11Scene.Finalize() in C:\Users\jonas\Documents\repos\Dalamud\lib\ImGuiScene\ImGuiScene\RawDX11Scene.cs:line 281

[MaxineMutini]

fiddled around with settings and discovered that disabling ingame feature fixes the issue at the cost of the obvious

[ff-meli]

A few questions:

• Are you running the dx11 version of the game? The dx9 one won't work.
• Do you have dxgi.dll, dxgi.fx or d3d11.dll in your game folder? (the same folder that has ffxiv_dx11.exe). If so, could you delete them and/or uninstall whatever programs added them, and try again?
• Are you running any other things that change game appearance (like reshade/gshade) or add other overlays onto the game? Or any driver "tuning" tools (rivatuner, nvidia inspector, etc)?

If none of those seem promising, could you try this?

• Delete the dalamud.txt logfile entirely (from %APPDATA%\XIVLauncher\addon\Hooks)
• Run the launcher (NOT as admin), ensure in-game features IS enabled, launch the game.
• Assuming that crashes, post the new dalamud.txt logfile here.

Thanks!

[MaxineMutini]

dalamud.txt
no overlays or tuners that i can think of, i even turned off the windows game tuner thing with no luck. the files you mentioned dont exist. deleted the txt file, launched dx11 as normal user, and crashed. dalamud log is attached as requested

[ff-meli]

Thanks for trying all that.

The only other thing I could think of that is somewhat easy to test is to make sure your graphics drivers are up to date, but I would be surprised if that mattered.

That error is not something I would expect to see on windows, and it's actually more of a warning - things should usually still work anyway, just potentially with some artifacts if you were also using gshade or similar.

I'm not too sure what else I can have you try without a build that has more logging enabled or similar, but it's not easy to get those out to individual people for testing.

Could you find your C:\Windows\System32\dxgi.dll file and upload it here (in a zip etc is fine if it doesn't let you directly)? I can try testing with that locally to see if there's something different about it, but there really shouldn't be...

[MaxineMutini]

dxgi.zip

[MaxineMutini]

im kinda at a loss as well, sorry

[ff-meli]

It's ok, this stuff is always a bit weird. Your dll is identical to mine, so at least that isn't the problem!

I'll add a bunch of logging and see if we can't get you a build to test with to hopefully make it a bit more clear what exactly is breaking. I'm not sure when exactly that might be though.

[ff-meli]

OK - if you are not comfortable doing this for a test, that's perfectly all right, but we'll have to wait for goat to make a test build available in some fashion. If you don't mind a one-off build that I created for testing, try this:

• Download a test build of the in-game features from my repo here
• Go to %APPDATA%\XivLauncher\addon\
• Delete the entire Hooks folder. (This is very easy to replace with the real version later)
• Unzip that archive directly into the "addon" folder. It should create a replacement Hooks folder with everything necessary inside. (Make sure you don't end up with Hooks\Hooks)
• Run XivLauncher.
• Enable in-game features again.
• Launch the game.
• I assume it will crash again, since basically all this does is add some logging. Even if it doesn't, you don't need to go in game beyond the title screen.
• Upload the new dalamud.txt here.

Sorry for the headache! I can't really debug this one easily since I can't cause the problem to happen, so I'm hoping this will have some more info.

[MaxineMutini]

i have no idea what changed, but its working. im gonna relaunch with default hooks to see if thats it

[MaxineMutini]

default hooks crashed the game

[MaxineMutini]

theres no log file for the test build, and /xlhelp doesnt work, so im assuming it didnt even boot

[ff-meli]

Can you check the output log in %APPDATA%\XivLauncher and see if it has any messages about failing to load? There's no reason I can think of that it wouldn't load automatically if the normal one does.

[mattavist]

I’m seeing the exact behavior that MaxineMutini describes, down to in-game features not working with the debug hooks.

The output log does not contain and messages about loading failures.

Happy to help debug or provide other information here.

[ff-meli]

Can you look inside the unzipped Hooks folder and see if any or all of .exe files are set as blocked? (right click, properties, see if there is a message about downloaded things being blocked down near the bottom, along with an 'unblock' option)

I'm not sure why it would just fail to load, especially with no error, when I can dl and unzip that build and it just works... There are also only very minor changes in that test build, and nothing that is involved with how it is loaded.

[mattavist]

Yes that was the problem, had to check "Unblock" for all applications and dll files in Hooks. FFXIV crashed after loading, dalamud log attached.

dalamud.txt

[ff-meli]

Thanks, that should help with one problem, but maybe not with the crashes...

I made another build here that has some different logging and a fix for part of the signature error (maybe). Could you give that one a try when you get a chance? Same process as before, and you'll probably have to unblock things again.

Thanks!

[mattavist]

Another crash, another log!

dalamud.txt

[ff-meli]

Sorry for the delay on this! Client patches and such are always a bit of a headache.

If you're still able to test, I have a new version here (removed, see next comment)

This should still crash, but it logs just about everything possible, so it should hopefully pinpoint what the problem is, and then I can start trying to figure out why.

Steps to test are the same as before -

• Go to %APPDATA%\XivLauncher\addon\
• Delete the entire Hooks folder
• Unzip the test archive you downloaded above, directly into the "addon" folder. It should create a replacement Hooks folder with everything necessary inside. (Make sure you don't end up with Hooks\Hooks)
• Go through all the .exe files in the new Hooks folder and unblock them
• Run XivLauncher, make sure in-game features are enabled, launch the game
• Probably crash
• Upload the %APPDATA%\XivLauncher\addon\Hooks\dalamud.txt file here.

Thanks!

[ff-meli]

I won't be keeping the test builds up to date, since it's a bit of a chore to do.

If anyone is still having this issue and willing to test, comment here and I can see about making a new one.

[daemitus]

Please re-open a new issue if this issue persists.