mtc44mag Posted October 31, 2018 Share Posted October 31, 2018 Hello all, I am having a most peculiar error with Vortex and F4SE. Basically, I have all my mods installed, enabled, sorted, all my load conflicts resolved through the load order settings. Everything run's perfectly once the game "loads". The issue I have is launching F4SE through Vortex.. When I do, the game starts to load and then freezes with the loading icon in the lower right corner. If however, I take care of all my settings and mods. Close Vortex and then launch via the desktop shortcut I created to the f4seloader.exe file the game boots up and runs with no problems at all. All my mods are there, everything is working as intended, no problems. If I open vortex and launch from the menu it freezes every time. Not the end of the world since I can use Vortex to ready everything then just load the game from the shortcut but seems like it might be worth mentioning. I didn't really see anything in the known bugs or search topics that described this issue. I am attaching an image of the settings for the shortcut in the game. "yes F:\ is correct, that SSD is for Steam™ games only" Link to comment Share on other sites More sharing options...
HadToRegister Posted October 31, 2018 Share Posted October 31, 2018 Have you tried right clicking on the f4se_loader.exe, setting it to "run as Administrator", then running like you always do from Vortex? Link to comment Share on other sites More sharing options...
mtc44mag Posted October 31, 2018 Author Share Posted October 31, 2018 Have you tried right clicking on the f4se_loader.exe, setting it to "run as Administrator", then running like you always do from Vortex?Unfortunately, yes. I already have that exe flagged for run as admin because I found with FO3 I couldn't get script extender to function at all without it. As such, I have just always run them with admin rights. FO3/NV/4 and Skyrim. I had wondered if ENB had anything to do with it so I completely removed it and it did the same thing so that also wasn't an issue. It's just so strange, all the tools work fine "editor and bodyslide" kick off with no problem. The only thing I haven't tried is running vortex as admin. Not sure if any issues would come from that. Link to comment Share on other sites More sharing options...
HadToRegister Posted October 31, 2018 Share Posted October 31, 2018 Have you tried right clicking on the f4se_loader.exe, setting it to "run as Administrator", then running like you always do from Vortex?Unfortunately, yes. I already have that exe flagged for run as admin because I found with FO3 I couldn't get script extender to function at all without it. As such, I have just always run them with admin rights. FO3/NV/4 and Skyrim. I had wondered if ENB had anything to do with it so I completely removed it and it did the same thing so that also wasn't an issue. It's just so strange, all the tools work fine "editor and bodyslide" kick off with no problem. The only thing I haven't tried is running vortex as admin. Not sure if any issues would come from that. No, don't run Vortex as an Admin, it will mess you up.The only thing I can think of is "Permissions" from that particular folder, because Microsoft is protective of it, and when you run it directly, it works OK, but maybe it needs to be 'elevated" or something when run from vortex.Thing is, except for the install path, it's set up identical to mine, although I have my Mod Staging Folder on Drive D along with my Steam install. Link to comment Share on other sites More sharing options...
rmm200 Posted October 31, 2018 Share Posted October 31, 2018 Your "Start in" line ends in double backslashes. I would at least remove one of them.And starting a non-root directory path with "Program Files (x86)" is bound to confuse some program somewhere... Link to comment Share on other sites More sharing options...
mtc44mag Posted October 31, 2018 Author Share Posted October 31, 2018 Ok, update.. The double backslash was a typo I completely missed so thank you for that!! I also took Vortex off of admin and left F4SE_loader.exe with admin rights and sure enough, booting through Vortex the game started with no issues. So it would seem that the admin rights for vortex was the issue. I wasn't sure if it was the double slash or the admin so I put it back with admin rights and the freeze up occurred again. Then when I disabled admin for Vortex it worked fine. So it definitely was able to be isolated to that causing the issue. Though I am not sure why the double slash didn't cause issues in its own right... Windows is just strange animal I suppose. Your "Start in" line ends in double backslashes. I would at least remove one of them.And starting a non-root directory path with "Program Files (x86)" is bound to confuse some program somewhere...When I installed Steam I used the custom install options and simply changed the drive letter to "F:" leaving the path already completed. This way it allowed Steam to create the appropriate registry key's using this path. I did the same for my E: drive with the origin client. As long as the entire path is in the registry key Windows is too stupid to care what drive the program files folders are actually on. Once Linux is able to rule the world and all these kinds of games work on it I can use the file management and disk pooling that Rhel or Fedora (29 is out btw) offer, and the issues of storage separation will be easily managed. Link to comment Share on other sites More sharing options...
HadToRegister Posted October 31, 2018 Share Posted October 31, 2018 Your "Start in" line ends in double backslashes. I would at least remove one of them.And starting a non-root directory path with "Program Files (x86)" is bound to confuse some program somewhere... Vortex adds that automatically, all my loaders have it. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted October 31, 2018 Share Posted October 31, 2018 This "admin rights" issue has me puzzled. I run Vortex and all script extender loaders without admin rights, and I have no problems. However, in some cases reported here and elsewhere the loaders don't work unless run as administrator. Why is that? In case it's important to know, my PC has one account only - Local Account, Administrator. My apologies for being somewhat off topic. Link to comment Share on other sites More sharing options...
mtc44mag Posted October 31, 2018 Author Share Posted October 31, 2018 This "admin rights" issue has me puzzled. I run Vortex and all script extender loaders without admin rights, and I have no problems. However, in some cases reported here and elsewhere the loaders don't work unless run as administrator. Why is that? In case it's important to know, my PC has one account only - Local Account, Administrator. My apologies for being somewhat off topic. It may also very well depend on what version of Windows you are using. Win 7 handles admin rights differently from 8/8.1. Win 10 is a whole different beast all together. That being said, I am rather concerned that you are using a single account on your computer that is an admin.. (Friends don't let friends run ROOT)The amount of risk you expose yourself to by just having a single user account that is an admin is unimaginable. When you set up a computer you should have an admin account with a password and then from that account create your "User" account as a standard user. This creates a sandbox of sort, if you will. If you get a virus or some form of malware on your standard account you will not easily be able to have system files or registry changes done. Even if you have a hijacker, provided you are using proper backup strategy, you can just logon to the admin account and delete the entire profile. Once you remove the profile and files associated you can re-create the profile and then load from your backup and with the exception of the time it takes to do this, you're not out anything. No worries, about the topic change however.. Its not really that far off since you mentioned that you have no issues running without admin rights, though I suspect this is do largely in part to the fact you're running as root already so elevating your privileges would kind of be pointless. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted October 31, 2018 Share Posted October 31, 2018 @mtc44mag: Thank you for your response and the information provided. I was completely unaware of the risks associated with running a single account as an administrator. I do not have a Microsoft account. Does that make any difference? Also, I am using Win 10 Pro x64 v. 1803. Finally, should we move all this to a new thread? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.