Start a new topic
Answered

Verification Script Graphics Not Loading

When attempting to run the Verification scripts that load graphics (e.g. Vortex Studio Samples 2018b/Verification/test_Vehicle_Verification_LAV1_speed.py) the following warning occurs - 

WARN - VxPluginManager - Error Plugin file could not be loaded : The specified procedure could not be found.

 on file C:/CM Labs/Vortex Studio 2018b/plugins/Camera.vxp.

WARN - VxExtensionFactory: Unable to create Display.3D Display {a411f362-b6e0-4d65-8245-26341f891a0b}, 'Camera'.vxp does not contain the extension.


We have used the Display.3D Display extension elsewhere with no issues, and the extension does correctly list itself as belonging to Camera.vxp - 

Vxp name: Camera

Category: Display

Feature: 3D Display

UUID: A411F362-B6E0-4D65-8245-26341F891A0B


We can initialize the display extension normally. It seems to only be an issue when running off the vxatp files. Our own adaptation of vehicle verification has the same issue. When the display fails to load, the verification still proceeds normally and reports the expected behavior, but we would like to preserve the visual feedback for manual review.


This issue I believe is new to upgrading to 2018b, and the graphics worked as expected in 2018a.


Best Answer

Hi Seth,

We are aware of this problem. It is a conflict between our embedded python and QT (managing our 3D display) when comes the time to load certain python modules. In this case, it is matplotlib.py import.

The workaround for the moment is to modify the python script and import matplotlib later in the script (at line #68 in LAV1_speed.py in your case).

This bug is fixed in the next release. Sorry for the inconvenience.



1 Comment

Answer

Hi Seth,

We are aware of this problem. It is a conflict between our embedded python and QT (managing our 3D display) when comes the time to load certain python modules. In this case, it is matplotlib.py import.

The workaround for the moment is to modify the python script and import matplotlib later in the script (at line #68 in LAV1_speed.py in your case).

This bug is fixed in the next release. Sorry for the inconvenience.




2 people like this
Login to post a comment