So far this is the Filter set I applied to ProcMon:DD Stanislaw wrote:Thanks, will try that.
-Process Name Is fs9.exe Include
-Operation Is QueryOpen Include
-Result Is name not found Include
ProcMon starts searching the "missing" files and list them rapidly. After about 3 or 5 min, pop up the Count occurences/path window from the main menu to count the loop number of each Not found file. If the number is low like 5 to 10, that's fine (some times FS9 misses them in early round). But if FS9.exe attempted to search the same file more than 600 loops, there is a chance that whether the file is missing or misplaced. That means, your memory is currently leaking. If missing, you can just try to launch Windows search accross the entire HDD. And if found elsewhere (likely in World\scenery\Texture), copy paste it where FS9 asks it. In case Windows couldn't find the name, create a fake one with Notebook and name it as FS9 expected, then place the fake file where it should be. Usually missing files could be bmp, agn or fx.
Despite this trick, the best solution is by far to have the developer providing with stable scenery structure and clean algorithm.
Finally, before testing scenery stability, it is suggested to shut down all AI traffic because they may cause interfenrence. Yes, missing AI texture may contribute to a memory leak as well.
Hope this helps.