Upstream
/
dynmap
mirror of https://github.com/webbukkit/dynmap.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Page: Defining custom perspectives
Pages
. AWS S3 Storage Addons Advanced Map Configuration Base Plugin Settings Boosting areas on Dynmap BoxRenderer Class Chunk Status Colors Chunk Version Colors Color Schemes Commands Common Features for Texture and Model Definition Files Component Configuration Configuration.txt Configuring Maps and Worlds using dmap Credits Custom Block Definitions Defining a Block using a Custom Block Renderer Defining a Block using a Volumetric Model Defining a Cuboid Block Defining a Simple Block Defining cuboid models Defining custom lightings Defining custom perspectives Defining custom shaders Defining volumetric models Dmarker Dynmap API Dynmap On Xenon Hosting Service, courtesy of mavbear Dynmap With IIS Using URL Rewrite and applicationrequestrouting thanks to kekec852 Dynmap with Apache httpd on Arch Linux Dynmap with IIS Dynmap with Nginx server on Centos Dynmap with Nginx Dynmap with apache2 on Debian Dynmap with lighttpd on Arch Linux Earthmc maps Example configurations and demo website Exporting World Data in Wavefront OBJ Format External Webserver Basics External Webserver on Linux External Webserver on Windows External Webserver on hosting providers FAQ Features FenceWallBlockRenderer Class File System Storage Forwarding Dynmap port through cloudflare Full list of predefined perspectives HD Map Configuration Home How to compile Dynmap Incompatible mods Installation Setup of Dynmap on Linux Installation Internal Webserver with Caddy as a Reverse Proxy (Linux) Internal Webserver Lighttpd and SQLite on a Raspberry Pi 4 with DietPi Model Definition Files MySQL MariaDB Storage Nginx as a Reverse Proxy OCI; Oracle Cloud Instance; Quick how to enable DynMap PaneRenderer Class Permissions PostgreSQL Storage RedstoneWireRenderer Class Resources SQLite Storage Setting up Dynamic Map with apache2 under Debian Setting up Dynmap through hosting services Setting up the Dynamic Map plugin under Windows Setting up without the Internal Web Server SkullRenderer Class Special texture file types StairBlockRenderer Class Storage Setup Support for Minecraft Servers other than CraftBukkit Support for MinecraftForge based mods Support for Tekkit Texture Definition Files Textures of Dynmap Use dynmap via Pterodactyl Using Markers Using custom block renderers Web Setup Web UI Parameters Web ui login support and permissions World and template settings [Tutorial] Setting up a standalone web server with MySQL SQLite limiting render area
4 Defining custom perspectives
mikeprimm edited this page 2011-09-30 18:45:24 -07:00

If the standard, predefined perspectives are not suitable for a user's needs, custom perspectives can be defined. With custom perspectives, a user is free to utilize the full flexibility and capabilities of the rendering engine.

Custom perspective definitions can be made by modifying the standard perspective definitions, found in perspectives.txt, or by adding new or updated definitions to the custom-perspectives.txt file (the preferred method).

At present, only one class of perspective is supported: the IsoHDPerspective class. This class defines an isometric viewpoint, with full control of the direction of view, angle of view, and scale of view. The definition of a perspective is structured as follows:

perspectives:
  - class: org.dynmap.hdmap.IsoHDPerspective
    name: my_custom_perspective
    azimuth: 124
    inclination: 55
    scale: 16

The required parameters for the isometric perspectives include the following:

  • name : the unique name for the perspective. If a custom perspective has the same name as an existing standard perspective, it will replace it.

  • azimuth : the angle, in degrees clockwise from north, of the viewpoint for the map : 0 = north, 90 = east, 180 = south, 270 = west. Any angle value is allowed.

  • inclination : the angle, in degrees below horizontal, of the viewpoint for the map: 90 = top view, 0 = horizontal (not allowed). Permitted values are any value from 20 to 90 degrees.

  • scale : the scale or resolution used for rendering the scene, in pixels per block edge. Values from 1 to 64 are supported, although 64 would correspond to a HUGE map - 16 yields a very high quality map (corresponding to hires in the standard perspectives), 8 yields a good quality map (corresponding to medres), and 4 yields a good quality map (corresponding to lowres) if a shader other than a texture pack shader is used (cave, biome, colorschemes).

In addition to these core required parameters, additional optional parameters are supported to modify the processing of the perspective:

  • maximumheight : if set, this sets a maximum height value (Y coordinate, in the Minecraft map) of blocks to be rendered. If it is set below 127, all blocks above this height will be invisible - logically slicing the top off of the world as a selected height. This can be used to show underground views.

  • minimumheight : if set, this set a minimum height value (Y coordinate, in the Minecraft map) of the blocks to be rendered. If it is set above 0, all blocks below this height will be invisible - logically slicing the bottom off of the world at a selected height. This can be used to show underground views.

  • fence-to-block-join : if set, this overrides the fence-to-block-join setting in configuration.txt. If true, fences will be rendered to join other blocks (as is the case in 1.9 and later); if false, fences only join with other fences.

Contents

Setup

Advanced Configuration

Mod Support

Developers