#Xplane 11 vr windows#

This sets the pitch orientation (rotating about the X-axis) of the userвЂ™s view in degrees. 0 degrees is facing forward in the aircraft, 90 would look toward the right wing, 180 degrees would be looking back at the tail etc. This sets the rotation orientation (rotating about the Y-axis) of the userвЂ™s view in degrees. A standing hotspot places the userвЂ™s feet at the XYZ location. This sets the location of the user to the location X, Y, Z in meters, relative to the default CG of the aircraft X is right, Y is up, Z is aft.В A sitting hotspot places the userвЂ™s head at the XYZ location. When the teleport beam lands inside this box, if the user ends the teleport, this hotspot will be used to position the user.

This adds an axis-aligned bounding box (in aircraft coordinates, that is +X = right, +Y = up, +Z = aft) in meters around the CG of the aircraft. Each hotspot must be вЂњendedвЂќ before anything else in the file occurs, and before the file ends. This defines the end of a given teleport hotspot. The name property is useful for debugging purposes. A sitting hotspot places the userвЂ™s head at the XYZ location. The legal types of hotspots are вЂSITTINGвЂ™ and вЂSTANDINGвЂ™. All hotspot properties must be specified after this directive and before the matched END_TELEPORT_HOTSPOT directive. This begins the definition of a new teleport hotspot. This is not the same as the English units used in Plane-Maker. Note: All units are in Aircraft Coordinates вЂ“ meters with the origin at the aircraft CG and the positive Z axis pointing aft.

Exactly one Psi, Theta, and Phi orientation respectively.

Exactly one Axis-Aligned-Bounding-Box (AABB).

You must use a matched pair of BEGIN_TELEPORT_HOTSPOT and END_TELEPORT_HOTSPOT. They are commonly used on the pilot and co-pilot seats so that users can quickly position themselves accurately in the seats.Д®ach hotspot block defines a single hotspot on or around the aircraft.

Hotspots are predefined locations that are used to precisely orient the VR user when selected.

#Xplane 11 vr windows#

The _vrconfig.txt file is a text file вЂ“ Unix or Windows line endings are legal, blank lines are allowed after the header, and the character set should be UTF-8.ДЇollowed by the directives listed below. This file must exist in the same directory as the ACF file. For example, to make a VR config for Cessna_172SP.acf, the file needs to be called Cessna_172SP_vrconfig.txt. The VR Configuration name needs to match the prefix of the ACF file, with _vrconfig.txt appended to the end. Aircraft that do not have a VR Configuration will still load and still work, even with VR enabled, however, there will be no hotspots to make it easy for the user to get back into the pilot seat, and there will be no customization allowing the VR controllers to be used to their fullest potential. While VR Configurations are not required, they are strongly encouraged. VR Configurations are aircraft-specific which means each ACF requires its own configuration file. The _vrconfig.txt file is a text-based configuration file that customizes VR interactions for your aircraft.