Hi,
First of all, thanks for Bonvision. Great tool!
I am wondering whether there is any reason not to move the eye position instead of the textures when using Bonvision for VR. In your VR corridor example, the "z pos" variable is used to translate all the textures, but I have the same result can be (apparently) achieved by moving the Eye, leading to a much simpler and cleaner workflow*.
I am about to code a VR experiment and I would like to know if there is any pitfall associated with moving the eye versus the textures (e.g. latencies, bugs, etc.). For now, I don't see any difference.
In case it matters, I am using a PythonTransform to control the eye based on "z pos"
import clr
clr.AddReference("OpenTK")
from OpenTK import Vector3
@returns(Vector3)
def process(value):
return Vector3(0,0,-100-value)
Best,
Romain
Hi,
First of all, thanks for Bonvision. Great tool!
I am wondering whether there is any reason not to move the eye position instead of the textures when using Bonvision for VR. In your VR corridor example, the "z pos" variable is used to translate all the textures, but I have the same result can be (apparently) achieved by moving the Eye, leading to a much simpler and cleaner workflow*.
I am about to code a VR experiment and I would like to know if there is any pitfall associated with moving the eye versus the textures (e.g. latencies, bugs, etc.). For now, I don't see any difference.
In case it matters, I am using a PythonTransform to control the eye based on "z pos"
import clr
clr.AddReference("OpenTK")
from OpenTK import Vector3
@returns(Vector3)
def process(value):
return Vector3(0,0,-100-value)
Best,
Romain