summaryrefslogtreecommitdiff
path: root/modules/mobile_vr/doc_classes/MobileVRInterface.xml
blob: 359d654433dce09d4c55ae70431ee94f8d3a9499 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
<?xml version="1.0" encoding="UTF-8" ?>
<class name="MobileVRInterface" inherits="ARVRInterface" category="Core" version="3.1">
	<brief_description>
		Generic mobile VR implementation
	</brief_description>
	<description>
		This is a generic mobile VR implementation where you need to provide details about the phone and HMD used. It does not rely on any existing framework. This is the most basic interface we have. For the best effect you do need a mobile phone with a gyroscope and accelerometer.
		Note that even though there is no positional tracking the camera will assume the headset is at a height of 1.85 meters.
	</description>
	<tutorials>
	</tutorials>
	<demos>
	</demos>
	<methods>
	</methods>
	<members>
		<member name="display_to_lens" type="float" setter="set_display_to_lens" getter="get_display_to_lens">
			The distance between the display and the lenses inside of the device in centimeters.
		</member>
		<member name="display_width" type="float" setter="set_display_width" getter="get_display_width">
			The width of the display in centimeters.
		</member>
		<member name="iod" type="float" setter="set_iod" getter="get_iod">
			The interocular distance, also known as the interpupillary distance. The distance between the pupils of the left and right eye.
		</member>
		<member name="k1" type="float" setter="set_k1" getter="get_k1">
			The k1 lens factor is one of the two constants that define the strength of the lens used and directly influences the lens distortion effect.
		</member>
		<member name="k2" type="float" setter="set_k2" getter="get_k2">
			The k2 lens factor, see k1.
		</member>
		<member name="oversample" type="float" setter="set_oversample" getter="get_oversample">
			The oversample setting. Because of the lens distortion we have to render our buffers at a higher resolution then the screen can natively handle. A value between 1.5 and 2.0 often provides good results but at the cost of performance.
		</member>
	</members>
	<constants>
	</constants>
</class>