vizmat.makeIdent()

[david]

Hi,

I have a weird error with vizmat.makeIdent(). It is strange in the sense that it does not happen all the time. I could not reproduce it in a simple script, but I had it several times before. I did not write the error message down, but the line incriminated was highlighted in yellow and the message was displayed in the interactive window. Anyone had this before?

David

[farshizzo]

Hi,

Do you remember what the error message was? Also, would you get this error message even when you didn't edit that line?

[david]

Hi, it did it again, although it does not seem to prevent the script from running. Here is the error message:


Traceback (most recent call last):
File "<string>", line 1, in ?
File "settingUpRooms.py", line 42, in ?
positions[i].makeIdent()
File "C:\Program Files\Vizard\vizmat.py", line 181, in makeIdent
transform.makeIdent(self.id)
SystemError: error return without exception set

The portion of the script containing the line was :
positions = []
positions.append(vizmat.Transform())
for i in range(0,11):
positions.append(vizmat.Transform())
positions[i].makeIdent()

If I remove the line incriminated, then I get the same kind of error message when I try to modify the transform objects (set them to rotations for instance)
The strange thing is that if I run that portion on its own, I do not get an error


David

[farshizzo]

Hi,

Thanks for the information. I believe the problem has do with the fact that there was a limit to how many transform objects you could have. We recently changed this so that there can be an unlimited number of transform objects. So the next release, 2.11, should hopefully take care of this.

[david]

However, before releasing v 2.11, you may want to try and run simpleworld.py in vizard 1.098 and 2.10. On my computer the former works fine and the latter crashes everything (I have to unplug my machine, but this may have nothing to do with vizard). On other computers, the results look similar but are not exactly the same (position is not the same). Why is that?
And for some more complex VRML files that I have, vizard 2.10 displays them in a way that is so different that I can not even see them. Using the mouse I could retrieve on or two objects but the whole scene was mostly messed up.

David

[duda]

Attached are left eye images of the identical script run viz.go(viz.STEREO | viz.HMD) under versions 1.097 and 2.10.

Any thoughts as to why the distortion occurs?

[farshizzo]

Hi,

This is a problem that has already been fixed in 2.11. In the meantime you can issue the following command to fix the FOV:

viz.fov(40,2.6)

Sorry for the inconvenience

[farshizzo]

Hi david,

Would you mind posting the VRML files that are not loading correctly so that I could take a look at them. If you don't want to post them on the forum you could also email them to me at lashkari@worldviz.com. Thanks.

[david]

Hi Farshizzo,

After testing dummy scripts, the vrml files that were not loading properly seem not to be the problem. It could be the rotations within the bigger script that are not interpreted the same way in vizard 1 and 2 and tend to put things everywhere. More testing is required.

Thanks for the answer though.

David