coincoin73

I have not modify the script (I also tried with the latest version 1.0.3). For the moment I manage to avoid the problem. I have developped a soft to launch FSET with my parameters (geo point) and kill the process at the end for launching the next FSET command. By this way I can create a large photo area easily. I 've also developped a little program to create a batch file that allows to cover a large area without the problem of memory of FSET (in high resolution mode). It creates small area of 1' by 1' between the 2 points of the bounding area.

idem = the same behaviour

idem with .net 2 framework, on a fresh XP install. Very surprising.

I try to use it on a virtual machine with a fresh installation (only .net 3.5 framework) and I have the same effect I will try with only the .net 2 framework tomorrow.

I tried on another XP computer without problem.

I use FSET like this in batch mode : FSEarthTiles.exe --north 43 18 00 N --west 005 21 00 E --south 43 17 00 N --east 005 22 00 E --zoom -1 --snap Off --fetch --compile

Hi (Sorry for my english, but I'm french) I have used FSET for a long time. But when I use it as a batch it always craches at the end of the process. Consultez la fin de ce message pour plus de détails sur l'appel du débogagejuste-à-temps (JIT) à la place de cette boîte de dialogue. ************** Texte de l'exception **************System.InvalidOperationException: La collection a été modifiée ; l'opération d'énumération peut ne pas s'exécuter. à System.Collections.ArrayList.ArrayListEnumeratorSimple.MoveNext() à System.Windows.Forms.Application.ExitInternal() à System.Windows.Forms.Application.Exit(CancelEventArgs e) à System.Windows.Forms.Application.Exit() à FSEarthTilesDLL.FSEarthTilesForm.MainThreadTimerEventProcessor(Object myObject, EventArgs myEventArgs) à System.Windows.Forms.Timer.OnTick(EventArgs e) à System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam).... It seems to come from the script CustomizedProcessesScript.cs I first, thougth about a problem with the .net frameword, but after reinstallation, there is no change. The problem is the same with the version 1.0 and 1.0.3. Thanks for your help.