[VisionScape .Net Core application]

Hi NTri,

I understand where you are going with .NET core. It is a cool idea.

I would not expect this to work out of the box with Visionscape. Visionscape has been in development for the last 20+ years, first starting with COM and Active-X, both of which we recently wrapped for .NET use. I am not a programmer, and would have to talk to the developers, but my guess is there is too much complexity under the hood for this just to work since it is so highly dependent on older Microsoft technology. 

We will however take this as extremely relevant feedback for future development.

Best regards,

Steve King 

 

 

[Compiling Visionscape .NET Programs - Memory Issue]

[Compiling Visionscape .NET Programs - Memory Issue]

When compiling Custom Visionscape .NET Programs, it is required to add the top line to your Post Build event to allow the program to use more memory than normal 32 bit programs do. Typically 32 bit programs are limited to 2GB. This allows programs to go well past that. Required for image size, stack size, etc.

 

[When updating Visionscape I-PAK on a multiple camera system, only one camera is visible after update]

Good answer. For Visionscape in general, always keep a safe copy of your jobs as well as your Custom Perl Scripts. If you ever have to uninstall and reinstall, these directories can be written over.