View Single Post
  #4  
Old 07-10-2009, 08:01 AM
Joran Joran is offline
Member
 
Join Date: Jun 2006
Posts: 38
Send a message via Yahoo to Joran
Lightbulb

Hello,

I have made a sample script that shows the problem (And I think I may have found a bug).

Code:
import viz

viz.go()

boxbig = viz.add('box.wrl', scale=(2000, 1, 2000))
boxsmall = boxbig.copy()
boxsmall.setScale(100, 1, 100)
boxsmall.setPosition(0, 0.001, 0)
boxsmall.color(viz.GREEN)

viz.MainView.setEuler(0, 87, 0)
viz.MainView.setPosition(0, 3000, 0)
boxsmall.addAction(vizact.spin(0, 1, 0, 20))

#texquad = viz.addTexQuad(viz.ORTHO)
#texquad.setScale(100, 100)
texquad = viz.addTexQuad(viz.SCREEN)

vizact.onkeydown(' ', texquad.visible, viz.TOGGLE)
It looks like when I add something to viz.SCREEN (or viz.ORTHO) that this will be used when calculating the clipping planes. In the example script when you run it, you should see a small green square that z-fights with the red square. When you press the spacebar, all is fine again, since this removes the texture quad from viz.ORTHO or viz.SCREEN.

What do you think? Have I found something? I am still using Vizard 3.12.0004 and not 3.14.0004.

And it looks like that the automatic computing of the clipping planes is on by default.

Greetings, Joran.
Reply With Quote