Ameribear Posted July 24, 2012 Share Posted July 24, 2012 When I try launching SKSE it instead pulled up the main menu for Skyrim (as if I had hit 'play' from my steam list). I opted to update to the 1.7 Beta after this and update my SKSE to the newest beta version to see if this might fix my issue, but it is still occurring. Regardless of whether I launch SKSE from NMM or manually from the skyrim folder in the steamapps it still brings up the regular Skyrim menu, making it impossible to actually utilize SKSE. Any advice? Thanks! Link to comment Share on other sites More sharing options...
kevkiev Posted July 24, 2012 Share Posted July 24, 2012 (edited) Does it do this even on repeat startups? I swear that, back when I played FO3, launching FOSE saved me from looking at the main menu (yeah as though I had started from steam) and would go immediately to the game. But somewhere during my FONV days (NVSE) and after I moved to Skyrim, the script extender would on first try go to the regular old menu. Which would detect and set my graphics settings, sometimes, would even cause my gameplay settings and skyrim ini to go back to default values. It was a PITA since I'd sometimes forget to re-disable auto and quick save which I do religously. However, on subsequent launches through NVSE and (now) SKSE, it would go right to the game (but still with the settings/ini changes unless I fixed 'em first). It's like my PC always has to make that first connection to steam. I realize SKSE always has to connect through steam but, yeah, it used to just spare me the grief of going through that initial menu. So I think you are still using SKSE, even though it doesn't look like it. Never could figure out a fix. But what I do now as a workaround is to start up steam (not the game) so I go to my library or the store or whatever I have as my default steam start page, then just shut it down right away. Then I launch SKSE and it takes me right to the game. As do all subsequent startups until I shut down my PC. No longer have to worry about settings or ini changes. edit: now that I think about it, I wonder if there's a steam setting that makes your PC connect to it immediatlely on starting. Duh... I betcha there is and I betcha that by selecting it the issue will be solved. edit: okay, that wasn't the fix. Turns out I do have that box checked to start steam when I start my PC. Edited July 25, 2012 by kevkiev Link to comment Share on other sites More sharing options...
Ameribear Posted July 25, 2012 Author Share Posted July 25, 2012 You can lock this thread. I was able to resolve the issue by restarting my computer - It's ALWAYS the simplest things that end up being the solution! Link to comment Share on other sites More sharing options...
Recommended Posts