Posted by: noobzor - Saturday, December 6, 2008 10:38:13 AM

Whenever I am editing scripts in worldbuilder, it takes forever to make the changes. It always says program is not responding, and then it evntually pops back to life with everything working again. any ideas why this is happening? by the way, this was not a problem with vanilla gens WB. I have 3 gb of ram and a quad core processor, so this should not be a problem, but it is. This always happens, but when I am scripting AI it takes forever to copy a single script, much less a whole group of them.

Posted by: yodaman888 - Saturday, December 6, 2008 11:06:12 AM
The only answer I have is that is after all crappy beta software

Posted by: Annihilationzh - Saturday, December 6, 2008 11:16:40 AM
My computer switches between very slow (takes several minutes to open the script window) and very fast (everything works instantly). So I only script when it's running at a decent speed. Not sure what slows it down, but I think it must be a lot of pointless checks or verification of something that my computer doesn't process all the time.

Posted by: noobzor - Saturday, December 6, 2008 11:21:05 AM
this is really only a problem when scripting, but when scripting it takes so long that by the time anything gets done I am hating it. So basically, I am stuck with mind-numbingly slow scripting? great.

Posted by: Drummin - Saturday, December 6, 2008 12:02:39 PM
I working with a very old PC and don't have this problem. I would think it's something to do with WB not made for a Quad processor. Is there any way to set how and application is run on your PC? Maybe someone with specs like yours can shed some light.

Posted by: CommieDog - Saturday, December 6, 2008 3:35:53 PM
Make sure that you have "Auto verify" turned off--that option is a massive resource hog that does, in my experience, absolutely nothing.

Posted by: Drummin - Saturday, December 6, 2008 4:02:15 PM
AH! I should have remembered that CommieDog. That could very well be the problem. That Auto-Verify just continually looks for errors in your scripting. I always have Auto-Verify off but will sometimes click Verify when I'm going to take a break as it also can takes a long time to complete a scan this way it can look things over while I'm gone.

Posted by: noobzor - Sunday, December 7, 2008 4:37:10 AM
thanks- a [i]dramatic[/i] change: it instantly does things now, even with the large skirmish scripts file. My question is why EA had that automatically checked in the first place.