adski
Dave Brown
Jon Chuchla posted this on diyc yesterday:
A Google search reveals similar problems in other programs - MS seem to have botched memory management and/or garbage collection in .NET 4.6
In practice, the issue is worse with more complicated displays and sequences, so it may not occur in simpler set ups.
Dave
We've gotten several reports within the past few weeks regarding Vixen 3 performance on windows 10. The problems are manifesting in the actual output chain as well as extremely slow exports with the export function.
While our initial testing on windows 10 was very positive, it appears that something has changed between the prerelease test versions of win 10 we were using and the version that is currently available. So we are temporarily removing windows 10 from the supported OS list until we get it sorted out.
The problems seem to be something within the .net 4.6 framework. Vixen 3.2 targets the 4.5.2 .net framework. However windows 10 ships with 4.6 and it appears that 4.5.2 cannot be installed on win 10. Unfortunately there's some changes in 4.6 that breaks our debugging tools so we're struggling to determine the root cause of the problem. So for the time being, we recommend against windows 10 for vixen 3.2.
A Google search reveals similar problems in other programs - MS seem to have botched memory management and/or garbage collection in .NET 4.6
In practice, the issue is worse with more complicated displays and sequences, so it may not occur in simpler set ups.
Dave