Hi Vasko,
I don't recall the definitive list of problems that may be caused by running multiple sessions, but some that spring to mind are:
- Settings or resource corruption due to overlapped reading/writing of files. Simultaneous startups or shutdowns are particularly dangerous, especially during plugin loading.
- CPU/memory exhaustion, as the multithreading and large map sizes in L3DT Pro can saturate all cores on the computer and run very high memory loads. Running two such instances is probably not disastrous, but is still ill advised.
- The possibility of two instances working on the same map file(s). Since L3DT Pro pages map data to disk, it is likely that two instances of L3DT working on the same files will overwrite one another's data when working in the background, with unpleasant results.
For these reasons, the more recent versions of L3DT stop multiple sessions from running (or at least, they're supposed to).
Would you mind describing the use case where you find it useful to run multiple instances of L3DT at the same time? I'm genuinely curious.
Best regards,
Aaron.