WinterRanger97

I'm not going to mock you. I'm going to THANK YOU, for coming back and telling everybody what the exact problem was. Not everybody does that, and instead will come back and say "NVM, fixed it" and that's the last you see of them. So, I appreciate you coming back and letting everybody know what the problem was, and I'm sure people in the future, with the same problem, will be thankful too. *The only thing I will warn against, is running Vortex as Admin and ignoring the warning I locked myself out of Vortex' files until I took ownership of the folders it accesses. Yeah, that's a fair point. Running anything in Admin mode is dangerous if you don't understand it. It'd be nice if certain Steam games weren't so thoroughly broken as to require Steam running in Admin mode in the first place, but that's neither here nor there.

Consider this topic closed. I've figured out the issue. When I changed the Steam.exe program to no longer run as admin, I forgot the SteamOverlayUI.exe. Changed that, and the overlay now works. So, in case anyone else has this issue, make sure Steam, the Overlay, AND Vortex are all running with the same elevation. Either run them all as admin (ignoring Vortex's warning), or run them all as standard. You may now all publicly mock me for my stupid mistake. Thanks to those who tried to help.

It's all good. Seems that one of my special powers is causing weird and obscure bugs to occur in even the most well tested software.

Except the Steam Overlay DOES work with Fallout 4. I can boot Fallout 4 from Steam and be able to play the game and access the Overlay with zero issues. It is only, and I can't stress this enough, ONLY when I launch through Vortex that the overlay does not work. Furthermore, I tested if the Steam beta might be the issue, since I'm opted into it. Changing to the stable release of Steam had no effect. Thank you for the links, and trying to help, but this seems to be a Vortex exclusive issue.

I'm going to go ahead and bump this topic. The issue hasn't gone away, nor have I been able to fix it, even after re-installing Vortex. If anyone has any more advice, I'd appreciate it.

I turned CFA off when I reinstalled Win 10. That setting has been nothing but problems for me in the past.

I was more thinking of doing a re-install of Vortex, and seeing if something got fudged during the install process. Copied your settings to a T, still no dice. Furthermore, I just did my weekly reboot last night. Didn't fix anything. On a hunch, I went looking and couldn't find any permissions issues either. No weirdly marked "Read Only" files or firewall issues.

Can't believe I didn't think to try that. Still no luck, I'm afraid, but that pretty much proves that this is purely a Vortex issue. Though, I cannot, for the life of me, think what if might be. I've checked pretty much every setting and window I could and have found NOTHING to indicate what the problem is. I'm at the point where I might just uninstall Vortex and see if that fixes the issue.

I've read that, but have had zero issues with the overlay affecting ANY of the Beth games I've played. Plus, I'm fine with occasional issues if it means being able to access the features the Overlay has (chat, achievements, time, etc.). Not a huge fan of alt-tabbing all the time. Thanks for the advice, though.

I have an nVidia GTX 1070, so I doubt it's something exclusive to Nvidia/AMD. Oh well, like I said, it's not a huge problem. Just means I won't have the overlay when playing. Hopefully, one of the devs or someone who has had this problem will pop in and be able to help more. Thanks for making the effort, in any case.

Steam was set to run as Admin due to another game I have (Steam had to run as admin in order to avoid the game crashing). Changed back to non-Admin mode. Still no overlay.

GPU acceleration is currently on. Turned it off to test if that was the issue, but no dice.

Hello all. I just recently returned to the modding scene after an extended absence and replaced NMM with Vortex. I've got everything set up and working, with only one minor issue. I'm currently running a modded Fallout 4 game with about 41 mods, ranging from texture fixes to weapons. I've got Vortex set up to launch F4SE in the dashboard (pointing to the f4se_loader.exe in my Fallout 4 folder), and it's set as the primary when launching the game. When launched, Script Extender loads (version number visible in settings menu in-game), and mods work. Steam even says that I'm in-game. However, it does NOT load the Steam Overlay. This seems to be a Vortex issue, as launching directly from the .exe works fine, as does launching from the Steam Library. I also did the old trick of replacing the Fallout4Launcher.exe with a renamed SE launcher. This also worked when launched from the both the Library and .exe directly, but not from Vortex. I'm running on Windows 10, Version 10.0.18362 Build 18362. Vortex is version 1.1.15. This is seriously a minor issue, but it's been bugging me for over a week now. Any help is greatly appreciated. Thanks.

I hope today finds you all well, because it certainly hasn't been for me. When I went to class this morning, the Geck was being its usual, barely functioning self. Nothing new there. What is new is that, now that I'm home, I cannot, for the life of me, get the damn thing to work. It now crashes loading FalloutNV.esm at 41% and always, always, on cell LAND " (22,11). It instantly goes to "Not Responding" and, unlike when its working, never comes back. Just crashes. That's it, that's all I got to work with here. Nothing has changed, as far as I can tell, since this morning. The only thing that has changed was a new definition file for Ad Aware. ANY help is appreciated at this point. I'll do what I can to help the process along. Edit: The problem has magically gone away, though I'm sure it'll be back. Apologies for wasting all your valuable time.

I know that you posted this back in May, sorry it took so long to respond. College and stuff. Anyways, this will only require Lonesome Road and Honest Hearts. Unfortunately, while I may be able to remove these requirements at some point after the initial release, they both contain models I need. We'll see. I hate to see people not able to play my mods because of DLC requirements, but sometimes they are necessary things. Sorry.