Thus spake "dcholtx": > -Problem still exists in 3.0.16, but only if you use a special > application launcher. In my case the stack is set to 1 GB, and the > module is 60 MB, counting extensions.
Can you clarify for me what's taking unusually long? Is it that VASSAL itself is taking a long time to load, or that a particular module is taking a long time to load, or something else? -- J.
