RideTheCatfish Posted March 21, 2010 Share Posted March 21, 2010 Whenever I work on a mod in GECK and decide to close out, it takes about three or four minutes for the program to close out. I know it doesn't sound like much of a problem, but it gets to be a pain in the ass when I'm testing mods in the game itself. I'm not sure how to diagnose this problem, but some help would be nice. Link to comment Share on other sites More sharing options...
Daynox Posted March 21, 2010 Share Posted March 21, 2010 I got the same problem...2-4 minutes before it closes completly... Link to comment Share on other sites More sharing options...
amcclell Posted March 21, 2010 Share Posted March 21, 2010 Whenever I work on a mod in GECK and decide to close out, it takes about three or four minutes for the program to close out. I know it doesn't sound like much of a problem, but it gets to be a pain in the ass when I'm testing mods in the game itself. I'm not sure how to diagnose this problem, but some help would be nice. Mine does the same thing. I believe it's unloading the esp files from memory. The solution is that you don't actually have to close GECK to test files in game. Just save the changes, minimize GECK, and load up the game as normal. Link to comment Share on other sites More sharing options...
Cipscis Posted March 22, 2010 Share Posted March 22, 2010 The GECK always takes a long time to close, which I believe is mainly due to the fact that it uses this time to back up your work. If you want to close the GECK quickly, then you can use the control panel to "End Process", or use this method:Open the script windowCreate a new script but leave the source blankAttempt to save the blank scriptWhen prompted, select "No", then "Yes"The GECK should close quickly and cleanly, although it won't create any backupsCipscis Link to comment Share on other sites More sharing options...
blue_fox Posted March 22, 2010 Share Posted March 22, 2010 I believe it's (just like said above) that the esp files are unloading. Because it takes a few minutes to load up so it would make sense that it would take a few minutes to unload. I just do something else while I wait. It's about all you can do to safely close the program. :P Link to comment Share on other sites More sharing options...
Cipscis Posted March 22, 2010 Share Posted March 22, 2010 I believe it's (just like said above) that the esp files are unloading.Due to the fact that the GECK can be closed quickly either via the task menu or via the method I mentioned in my post above, and the fact that the GECK can take a long time to close without Fallout3.esm loaded, I strongly believe this is not the case. Besides, allocating memory and populating it with information read from files doesn't take nearly as long as deallocating said memory. Cipscis Link to comment Share on other sites More sharing options...
angelwraith Posted March 22, 2010 Share Posted March 22, 2010 HAHA i guess i just dont care enough.. my backups are on nexus.. int he form of previous versions sooo i could care less what geck is trying to do.. i just hit the close "x" about 5-10 times and windows is like "soo i guess you want to close that" and does so accordingly.. :) never had a problem due to this.. unloading esp's or not geck is buggy as hell and i decided a long tome ago to not worry about it.. no problems yet. cipscis's plan is the best.. force a error in geck and say you dont wanna continue.. BOOM=OFF! Link to comment Share on other sites More sharing options...
csgators Posted March 22, 2010 Share Posted March 22, 2010 ...or just use the task manager, killing the process is the cleanest way. Link to comment Share on other sites More sharing options...
angelwraith Posted March 22, 2010 Share Posted March 22, 2010 ...or just use the task manager, killing the process is the cleanest way. fact... or opinion? where are you getting the info to support this claim? Sorry i'm just trying to understand the logic behind the claim that allowing g.e.c.k. to close itself is somehow "less clean" than using task manager to force it. i tried to find some info to support your claim but came up with nothing.. can you link it please?? if this is true somehow that would be nice info to avoid issues (although technically your method and mine are the same.. mine is just lazier.. repeatedly hitting the close "x" forces an end process window, and continuing to click the x confirms the end process. same as selecting the process through task manager, just this way there is no need to find the process, saves you 1/8th of a second haha) Link to comment Share on other sites More sharing options...
csgators Posted March 22, 2010 Share Posted March 22, 2010 fact... or opinion? where are you getting the info to support this claim? I think you misunderstood my post, I should have quoted the post above me but I meant as opposed to forcing the GECK to crash in some form. Obviously waiting for the program to close as intended is the best way. Sorry for not being more clear. Link to comment Share on other sites More sharing options...
Recommended Posts