Visual Components 5.0 is out. This means that we will continue updating 5.0 eCat and 4.10 eCat is frozen.

New version introduced new features such as python 3 API, new motion controller and colliders. These affect the eCatalog too. We are updating existing models’ scripts to python 3. This is long process but there are already some components that use the new API. Updated components work the same way as they used to. Whenever large updates are done there a possibility for regression bugs but in case you come up with one please contact our support (support@visualcomponents.com).

New motion controller is introduced as beta version for now. In eCat you can enable extra source called “Motion Controller (Beta)” where there are some 6 axis robots, peripherals and demo layouts that use the new controller. These allow you to test the new controller. Extra source is used because not all features still support the new controller. For example PM transport controller and OLP features still do not work with the new controller. Wider support for the new controller will come later in upcoming releases. For now we want to keep models using old and new controllers separate to minimize compatibility issues. The following video shows how you can enable motion controller source on your eCat.

Collider feature is useful for example in OLP where they make collision detection faster. In eCat under typeLayouts OLPthere are many example layouts where you see colliders being used like in the following picture.

One thing to note when moving to 5.0 platform is that vcmx format has changed quite a bit and you cannot use 5.0 models in older versions. This is generally the case with major VC releases but even more so in 5.0. When you collaborate with other make sure you are using the same platform. Old models will work in 5.0 and if you migrate layouts to new platform please check the following post about migration:

-k

hello,.When opening the software, there is an error message. Is it because of a bug? The operating system is Windows 10 .0:00:00 | Error | NetInvoke exception.
System.NullReferenceException: Object reference not set to an instance of an object. | (4)
| at VisualComponents.UX.Shared.AddUxItemCommand.Execute(PropertyCollection args)
| at VisualComponents.UX.Shared.CommandRegistry.ExecuteAction(String key, PropertyCollection args)
| at VisualComponents.Revolution.NetProxyWrapper.NetInvokeInternal(Int32 type, Void* param1, Void* param2, Void* param3)
| at VisualComponents.Revolution.NetProxyWrapper.NetInvokeHandler(Int32 type, Void* param1, Void* param2, Void* param3)

For bugs and error messages, please contact the support of VC or a partner that has sold the license, so log files and detailed system information can be shared confidentially. This thread is a public announcement of 5.0 eCatalog updates, so this might not be the best channel for troubleshooting.
However, based on the error message, you could try removing any third-party addons installed to the VC version.