GECK takes about ages to close out.

[phoneyLogic]

(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)

Nope, the fasted way is:

Ctr+Alt+Del

Alt+T

Enter

:biggrin:

[csgators]

(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)

 

Ok, so misunderstood your post, yes they are the same thing. I simply find it quicker to right click on the windows bar, click task manager (or ctrl+alt+del) and clicking end task, no fuss, no "crash" warning.

[angelwraith]

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.

 

oh well crap then i guess i wasnt clear either.. i didnt mean force a 'crash' i meant force an error if you use the method cipscis was talking about: opening a script and trying to save a blank script the program brings up a warning box and asks if you want to disable the warning.. if you say no it just closes the program.. quick n prettty.. this isnt actually forcing a 'crash'

 

(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)

Nope, the fasted way is:

Ctr+Alt+Del

Alt+T

Enter

:biggrin:

 

i said lazy. i click 1 btn, works for me! (and honestly i still feel its faster for me b/c i don't touch type, gotta find the keys (i know, i know i really need to learn.. and fix my puny 36wpm)) its my preference, anyway, it does the SAME thing.. dont like it? Im sorry, im not exactly forcing you to use it, just sharing my method...

 

:D just redid the typing test with memorized text instead of copy and i got 57wpm

 

thats supposed to be about average on the low side for a 'typing professional' who can touch-type

 

although my copy is still a PUNY 36 and im sure all of you hit 8000000wpm

sorry for the off-topicness.. i got excited.

 

yeah so like im said. im lazy.

[Norinvaux]

Both the GECK and the TESConstructionSet are extremely buggy. The GECK even more so (fallout 3 programming sucks bad). Both programs take a really long time to close. I just use task manager, end process, and BOOM, exited. Also, I think the reason for it taking so long is something besides "unloading .esp files" or "making backups", as (at least on my computer) the GECK and TESConstuctionSet both use no cpu, and very little RAM while closing. I think it's like closing internet explorer, sometimes it just takes a long time. Sadly, there is no theoretical Firefox to replace our slow closing theoretical IE, so, we'll just have to live with it. :P

[Cipscis]

Like I posted before, because the GECK can be closed quickly by causing an error or using the task manager, it seems very unlikely that the delay is caused by "unloading data files", so the most likely culprit is the creation of backups and general bad programming.

 

P.S. Was that really worth reviving a 3 month old thread to say?

 

Cipscis

[phoneyLogic]

In my belives the GECK seems to check the all the references again, so to speak to evaluate the EditorWarnings.txt file. So this seems to take almost as long as loading up the Mod :unsure: