Latest krpano version: 1. Javascript must be activated for this page! Examples Version 1. Animated Hotspots xml: anihotspots.

Author:Gagis Zuzilkree
Language:English (Spanish)
Published (Last):2 May 2009
PDF File Size:6.95 Mb
ePub File Size:9.55 Mb
Price:Free* [*Free Regsitration Required]

Latest krpano version: 1. Javascript must be activated for this page! These files can be written or edited with any usual texteditor, but when writing the xml code, it is important that the xml-syntax-rules will be respected! These basic rules are the same for all xml files and not specific to krpano. For more information about the basic xml syntax, please have a look here:. This documentation is about the krpano xml structure, about all krpano xml elements, attributes and values and their mapping to their dynamic krpano variable names.

The documentation is split into normal and 'advanced' parts. This was done for better readability and more clearness. All other elements must be placed inside this element. All xml elements and attributes in the krpano xml are optionally and can be defined a several times and in any order. The xml itself is just a transport-format - that means it will be only used to transport the data for the krpano viewer. That means after parsing there is internally no xml anymore. Special krpano XML elements and attributes Some xml elements and attributes are handled in a special way in krpano.

This special handling happens already during the xml loading and parsing. The name of the Array is the name of the xml element itself. When no Array with that name already exists, it will be automatically created.

This means there can be several declarations of a xml element, but each element would need to have its own unique name for identification. Important notes about the name attribute: Each name needs to begin with an alphabetic character! That means using a number as name is not allowed! When a name still begins with a numeric character, then the name will be interpreted as array index. This is okay for dynamic index-based access inside actions but not for defining the elements!

All names will get converted automatically to lower case to allow direct case insensitive access! When a relative path will be used as url value, then the path will be automatically adjusted to be relative to the xml file in which the url attribute was defined. That means relative paths in a xml will be always relative to the xml itself.

This can be any krpano variable, but it need be defined before the xml or scene will be loaded, e. Beside of using file-paths, it's also possible to use Data-URLs as url value. Base and Plain-encoding are supported. Syntax: The value of the devices attribute can be one or more of the available devices. Note - for checking for the devices settings dynamically in actions code, use the device object and the if or calc actions.

Normally the variable-type is not relevant because inside the actions type conversions will be done automatically when required, but sometimes it can be still helpful to be able to define the exact type of a variable.

And that's possible by adding a dot. Note - This is for static xml code - for defining variables with types dynamically at runtime the def and set actions can be used. Available types: bool A boolean value, true or false.

Syntax: Everything before the first dot belongs to the name of the attribute itself and everything after the first dot belongs to the device check. All the devices as in the devices attribute can be used for the device checks. A no- prefix before a devices setting can be used to check if the given devices setting is NOT set like the! Important to know: The order of xml-attributes is random and can differ each time!

Therefore never redefine attributes again other devices settings that would override previous definitions.! This could be done in the html file during embedding by using the initvars setting or in the xml before doing a loadpano call.

Every other xml element that has a name attribute can also have a style attribute. This will be done before the attributes that are defined at xml element itself will be applied.

Several styles can be loaded at once by combining the style names by characters. For dynamically getting the attributes from a style at runtime, these actions can be used: assignstyle elementname, styles layer[name]. All further xml elements need to be defined within this element. Advanced notes - when the xml gets parsed and resolved into the data structures the leading 'krpano' tag will be stripped away.

This is mainly only an information for orientation, but it should be still defined to allow handling potential compatibility-related version changes. When set to a valid color number in hex format e. When enabled variables will no longer 'automatically' resolve to their value inside expressions. This avoids accidentally mix-ups between variables and strings. Note - When using the Branding Free License the default value will be false.

The location on the keyboard - always the top-left most key below the ESC-key independent of the keyboard-language or keyboard-mapping :.

This preview image should should be small in filesize and image dimensions to allow fast loading! Note - For best rendering quality and performance the usage of cubestrip images will be recommended! High quality preview images smoothed along all edges and all directions can be easily created by using the krpano tools.

Possible settings: empty, not set, the default - when not set, the type of the preview image will be detected automatically by its image-size and side-aspect e. Attribute name Full variable name Type Default value url preview. This can be a spherical, cylindrical or a cubestrip 1x6, 6x1, 3x2 or 2x3 image. Attribute name Full variable name Type Default value striporder preview. Cubestrip One 'image-strip' with the six cube-faces images. Supported arrangements: 1x6, 6x1, 2x3, 3x2.

The order of the cube-faces can be defined by the striporder setting. Supports: Single-Resolution. Partial panos are possible by using custom hfov , vfov and voffset settings.

Cylinder A cylindrical panorama image. With any field-of-view coverage from 1. Fisheye An image or video shoot with fisheye lens. Cube - Multi-Resolution Short Syntax. Cube with Stereo-Images. Default With custom order. Cubestrip with custom order.

Sphere Cylinder Flat-Image. Normal Stereo-Images Video-Input. Fisheye Image with Stereo-Images. Fisheye Image with Video-Input. Depending on the image type and the related settings, the url of the image should contain several placeholders to allow addressing the right image file. For stereo-rendering with one-image, for VR-viewing, for 3D-transitions or even for walking around in 3D-space. The depthmap image need to be in spherical x projection. The pano image itself can use a different projection, like cubical.

The interpretation of the gray-value to the distance can be controlled by the scale and offset settings. By default one unit in the 3D-model represents one centimeter in krpano. This is especially important for the VR-usage so that everything looks in the right scale. The Depthmap support is available for cubical panos single- and multi-resolution and for spherical panos single-resolution only.

Supported 3D-object file types: STL. When the server setup doesn't allow. Attribute name Full variable name Type Default value enabled depthmap. Can be changed also anytime dynamically at runtime. Attribute name Full variable name Type Default value rendermode depthmap. That's the fastest way to load the depthmap. But as disadvantage it is not as accurate as when using the 3D-model directly, and it's not possible to view the obscured parts of the 3D-geometry.

With very detailed 3D-models and the default subdiv setting the loading and rendering of the 3D-model can be slower compared to using "depthmap".

When not set, the default setting depends on the display. This setting can not be changed at runtime as it controls how the depthmap gets 'loaded'. Attribute name Full variable name Type Default value background depthmap. Available settings: "none" default Render only the depthmap pano itself.

Attribute name Full variable name Type Default value scale depthmap. Invert the depth: for depthmap images that use black for near and white for far a negative scale value should be used to invert the depth.

Attribute name Full variable name Type Default value offset depthmap. The value to use depends how the depthmap image was created and mapped. Typical values are in the range around 0.


KRPano Tutorial: How to Create a Panorama or Virtual Tour with krpano

Types of panoramas Hotspots What is a hotspot? How to delete logos? Adding plugins in your tour Combobox Options. In current version of MakeVT supported spherical and cylindrical panoramas. A spherical pano must have aspect ratio If a pano has another aspect ratio, then it will be uploaded as a cylindrical one.


Advanced Tutorial: How to make a virtual tour with MakeVT

Skip user information. Remember me? You are not logged in. Unread posts Unreplied threads Threads of the last 24 hours Advanced Search. Skip user information szmorriss Beginner.

Related Articles