This is an error from an overloaded GPU. Read here how to resolve:
https://helpdesk.vioso.com/knowledgebase/dealing-with-tdr-error-message/
This is an error from an overloaded GPU. Read here how to resolve:
https://helpdesk.vioso.com/knowledgebase/dealing-with-tdr-error-message/
This issue often happens because of extrapolation errors when using “Curved screen/Dome” scanning method. The maps generated after each scan are bad, which (unfortunately) cause the blending calculation to crash. To resolve, you need to redo the scans and make sure, that the generated maps are valid. Follow these instructions after each scan carefully:
Once all projectors are handled this way, having a proper projector map, the blending calculation won’t crash.
There are different reasons of such behaviour so we will go through all of them starting from very obvious.
A. Check if the camera cap is still on
Yes, yes it happens so often, so its definetely worth to check one more time.
B. Check the camera adjustments
Both mechanical and software: it can be that black screen is simply way too dark image that camera streams to you. Make sure the iris of the lens is not totally closed. In driver settings (buttons Format and Options) reduce fps and increase exposure times until you will see the image.
C. Directshow Filter problems
When everything else is checked, the reason of black image stream can be the DirectShow failure. This can be double check using following steps:
C. Other hints
Here are some hints which can help you to solve this problem. Any of this single steps can help. Please check if the camera starts to work, after each step, so you wont need to perform further steps.
If the IDS camera looses its basic settings, e.g. color format, timings, etc., there might be an issue with the DirectShow driver that is utilized to handle the camera. Some hints that might fix this issue:
C:\Windows\System32\regsvr32.exe uEyeCapture.ax
bInitCameraParamFromCalib="1"
bInitCameraModeFromCalib="1"
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.
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:
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.
At the startup of an application, an error message like this is shown:
„d3dx9_40.dll“ or „d3dx9_43.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. You basically just need to (re)install it as an administrator.
See here how to install or update DirectX: