I posted an updated report on this issue last night in the old forum which seems to be lost…so reposting here…
To recap…The issue that I am having started about 4 weeks ago. SimLink crashes which results in a severe pulsed stutter every 1-2 seconds or so. It happens suddenly and is unrelated to scenery loading or AI traffic density etc. For example, in a recent occurrence my FPS remained at the locked 30 with CPU loading at about 35% during the stuttering. I had not experienced anything like this prior to 4 weeks ago. Since then it occurs about once in every 2-3 flights. There have been no changes in my setup during this time other than possible Windows updates. I am flying P3Dv4.5 with the latest SimLink version. Windows Firewall is turned off.
I have found that the problem is fixable by simply re-executing the SimLink exe…the stuttering immediately stops and all is back to normal. That would seem simple enough to do in most cases but is somewhat problematic for me since I fly a full-scale cockpit. That means I have to climb out of the pilot’s seat to get to where the server station is outside of the cockpit. Since I fly mostly on VATSIM leaving the cockpit can be problematic in certain instances (and in fact has been on 2 occasions).
In the old thread it was suggested to reinstall SimLink even though it showed as the latest version. So I uninstalled, downloaded the most current SimLink, and reinstalled but that did not fix the problem…the same exact issue remains.
An additional observation for whatever it may be worth…Most of the time I fly online with VATSIM using vPilot as the ATC interface. What I have noticed is that in the several minutes before SimLink crashes vPilot will start doing fits of disconnecting and auto-reconnecting. So that has become a warning sign for me. VPilot never actually crashes though, only SimLink. Is there some relationship between vPilot/VATSIM and SimLink involved? I have read in another thread that there is evidence of a SimLink memory leak. Perhaps that is what is causing all that. I will be sure to check for a memory leak in the future.
Is there anything else I can investigate on this?