Error and other feedback

In some cases, when you start the camera-based calibration, this message appears:

“The projection surface could not be identified. If this is intended, push the NEXT button. Otherwise, click on the BACK button and adjust the camera.” 

The reason for this issue is in the misoperation of the camera.

1. Camera image is too dark to detect any projection. Re-adjust the camera. Check here for how to adjust the camera.
2. IDS camera works on 100 Mbits/s. Control of the network adapter, and switches and hubs are 1Gbits/s compatible. Check the cable for the 1Gbit/s compatibility. Note that sometimes broken ports or cables can continue to work, but drop the bandwidth from 1000 to 100 Mbits/s. Read here for how to configure an IDS camera.

This error can happen because a required programming runtime environment is missing on your system. Please download and install the runtime environment provided by Microsoft:

• Download Visual Studio 2008 (64 Bit) runtime – for 64 bit systems.
• Download Visual Studio 2008 (32 Bit) runtime – for 32 bit systems.

After a reboot, this error should be gone and the application should start normally.

If the error still occurs, there could be an issue with the DirectX runtime (see Installing DirectX Runtime).

Our logging file is located in the working directory. This is usually in C:\Users\Public\Documents\VIOSO

To change the logging value, next to an executable, there is a file called SPeASY.ini. There you will find the attribute LogFileLevel in

<VIOSO\SPeASY\DebugOptions\ErrorHandling>

Standard value is 1. Set this up to 3 to have more detailed logging.

1. The split mode may be set incorrectly. Check your settings in the calibrator options.
2. The version of DirectX on the server might not be up-to-date. Update DirectX to the lastest version (read more about this here: Installing DirectX Runtime).

At the startup of an application, an error message like this is shown:

„d3dx9_40.dll“ or „d3dx9_41.dll“ is missing on your computer.
Reinstallation of the application could solve your problem.

An outdated, incomplete, or missing DirectX 9 runtime is the most likely reason for this error.

See here how to install or update DirectX:

Installing DirectX Runtime