I've recently moved to LV 2025 Q3 and am experiencing some really awkward behaviour.
It seems like this version of LabVIEW is not doing a great job of isolating different contexts of code within the IDE, perhaps specifically for VIMs.
I have a class which contains a vim which allows me to input both child classes (uses only parent methods within) and adapt to a secondary datatype at the input. This has been working fine for years in other LV versions. But int his version, if I have a VI containing an object which uses this vim on both "My Computer" context AND on an FPGA context, the VI is broken. If I remove the dependency from one or other of the contexts, the VI is no longer broken.
This is new for this version of LabVIEW. I have also other observations that the compile cache is having again more of an impact on the code than it should, there somewhere seems to be some utilisation of compiled cache information AHEAD of the actual VI on disk which leads to all kinds of chaos.
If I can, I'll try to get a mock up and running.
