It seems the problem is not caused by Sensics plug-in or the xSight HMD. In my code, I commented the Sensics lines and directly used the viz.go(viz.FULLSCREEN) method. I found whenever the image output to the normal LED monitor, the texture looks fine. However, when the image go through the Matrox TripleHead2Go splitter, the texture becomes weird. It seems that the problem is probably caused by the incompatibility between the Matrox and the Vizard (because previously when I used Virtools with the Matrox, there was no such a problem). If it is the case, what can I do now?
Last edited by Zhi; 04-26-2011 at 07:15 AM.
|