DInsight

The above method of creating x64 apps works for any version of Visual Studio and any version of .NET with one exception: .NET v4.0 or 4.5 on Visual Studio 2012. We are still investigating this problem. .NET 4.0 works OK on Visual Studio 2010
Pls keep in touch
Nick

Visual Studio 2008 or later can create 64 bit applications, but it is a 32 bit application itself. This has to be kept in mind when creating a 64 bit application which uses KernelCAD. To create a Windows Forms 64 bit application start with either Any CPU or x86 configuration. - With this configurati...

Memory leaks are pretty common because the management is fiddly. They are often caused by the application and also by ourselves too (guilty) You were first to report specifically about meshes. More recently somebody mentioned strange behaviour in meshes too but inconsistently. It can be something di...

Sorry atrev
This will be addressed eventually. There really something urgent came up and we are busy with many things. You need a subscription to keep it on top of priorities. http://www.dynoinsight.com/phpBB3/viewt ... p?f=3&t=18
I assume you are using v4.3?
Nick

Ibi, We have fixed the empty window problem and an issue with explorer in today’s update 3741: http://www.dynoinsight.com/ProDown.htm (b) In the current version 4.3 the model Explorer only works when the application targets .NET 2.0. See the next post on this thread if you decide to target a differe...

Hi Ibi There are two issues: 1. In form editor 64 bit component should work like that. It does not show the 3d model in form editor, instead it shows a warning that it will be OK at runtime. It is caused by the fact that the Visual Studio itself is a 32 bit application (64 bit does not exist yet). S...

Ibi, 1. Each section has user data allocated for use by the application only. It is a 32 bit integer. It can be set/read via IUSerData queried form the relevant ISection: http://www.dynoinsight.com/Help/Interface/UserData/IUserData.aspx 2. There is also a string which is used only as a layer name to...

Hi atrev What language are you using? In .NET a quick suggestion is to avoid keeping references to any interfaces when they are no longer needed. One way is to set something like myIMesh = null; in C# It is also possible that we have missed some scenario with reference counting, so there is a memory...

Hi Guolian Unfortunately it is not implemented. We have been thinking about it, but there always was and still is something more important. You are the first to ask for that. When somebody is willing to contribute to this feature we would be happy to implement. Otherwise we assume nobody really want...

Hi Tony Positioning, modelling, etc is not a problem. Such a large number of holes may be an issue, if you do it straightforward with Boolean Operations. I think after 50 holes or so it will get sluggish with any software. Simply because Boolean Operations are quite complicated For large number of h...