Save Response<\/h4>\n
Adjusts responses Content-Disposition<\/em> header to cause the browser to download rather than view the response file. Useful for triggering save dialogs for images. To configure add the following to your RealityServer configuration:<\/p>\n You can then trigger the functionality by appending the named url argument to the query string of your url. For example:<\/p>\n This will cause the browser to pop up a dialog asking the user where to save the file or trigger the browsers download behavior rather than viewing the result. Note that the handling of this header differs between browsers.<\/p>\n Allows you to output images in the mental images .zt depth format. Useful to use with compositing applications that support this format when you need to write out depth data. The .zt format is binary but quite trivial if you wish to write your own tools to read it or use a tool that can read raw bytes from an image file. From the mental ray manual:<\/p>\n All mental ray native file formats, like ct or st, are following a simple layout. They contain a header followed by the image data, where header consists of a magic number byte identifying the format (8 in the case of the ZT depth format), a null byte, width and height as unsigned shorts, as well as a version number as unsigned short ; and image data are simply uncompressed values written pixel by pixel (with increasing horizontal x coordinate) and line by line (with increasing vertical y coordinate), beginning in the lower left corner (x = y = 0). The pixel data consists of one 32-bit component value. All shorts, integers, and floats are big-endian (most significant byte first).<\/em><\/p>\n<\/div><\/div> A state handler plugin that automatically uses a specified scope for a request and if the scope does not exist it creates it. This can be useful in removing the constant use of use_scope<\/em> and create_scope<\/em> commands. You can simply set a HTTP header and if present it will generate the scopes. Configure as follows:<\/p>\n RealityServer will then look for the header rs-scope<\/em> and if found will use it to set the current scope for commands or create it if it doesn’t exist. To use this you will naturally need to be using a client that allows you to control the headers of your request (most clients should allow this).<\/p>\n False color tonemapper which outputs a heatmap style image using a specific colour gradient based on minimum and maximum values specified. Requires mif_min<\/em> and mif_max<\/em> attributes (Float32) to be set on the camera and the cameras mip_tonemapper<\/em> attribute to be set to falsecolor_tonemapper<\/em>.<\/p>\n Please note, in order for the false color tonemapper to work correctly you must<\/strong> disable the Iray Firefly Filter by setting the iray_firefly_filter<\/em> attribute on your scenes options to false<\/em>. If this is not done the values provided to the tonemapper by Iray will be incorrect. Currently no legend or scale it output so you will need to add your own.<\/p>\n<\/div><\/div> False Colour Heatmap Rendering<\/p>\n<\/div>\n<\/div><\/div><\/div>\n This is a set of commands you can access from the RealityServer JSON-RPC API. For detailed documentation please refer to your command descriptions at http:\/\/127.0.0.1:8080\/?doc<\/a>\u00a0replacing the IP with your hostname or IP if running on a different server. The commands each install their own documentation there. Here is a brief description of what each command\u00a0does.<\/p>\n You can now enable optional HTTPS support for RealityServer. In the past to encrypt traffic from RealityServer it was necessary to place it behind a reverse proxy server such as HAProxy<\/a>. For more complex deployments this might still be the best option but now when you need encryption in less complex scenarios you can enable it directly in RealityServer. This may also be useful when you want to enable encrypted server-to-server communication when you have a separate server communicating with RealityServer rather than a browser. You will need a valid SSL certificate and private key to configure HTTPS support. You can either generate a self-signed certificate or provide one from a certificate authority. We recommend Let’s Encrypt<\/a> for obtaining free, valid SSL certificates quickly but you can of course use any popular provider.<\/p>\n<\/div><\/div> Server-side JavaScript commands are a great way to quickly add new commands\u00a0to RealityServer without the need to write C++ plugins. This feature has existed for a long time but recently we have been using it more heavily internally at migenius for our projects and noticed a few areas that needed improvements. In this update of RealityServer we have made two main updates.<\/p>\n\r\n<user save_response>\r\nurl_argument save_image\r\n<\/user>\r\n<\/pre>\n
\r\nhttp:\/\/127.0.0.1:8080\/?json_rpc_request=[..json_commands..]&save_image=image.jpg\r\n<\/pre>\n
ZT Depth Image Support<\/h4>\n
![](\"\/\/www.migenius.com\/migenius\/wp-content\/uploads\/2016\/06\/rs44-depth-1.jpg\")
<\/p>\n<\/div><\/div><\/div>\nAuto Scope<\/h4>\n
\r\n<url .*>\r\nstate auto_scope\r\n<\/url>\r\n\r\n<user auto_scope>\r\nheader rs-scope\r\n<\/user>\r\n<\/pre>\n
False Color Tonemapper<\/h4>\n
![\"False](\"\/\/www.migenius.com\/migenius\/wp-content\/uploads\/2016\/06\/rs44-falsecolor.jpg\")
<\/p>\nExtra Core Commands<\/h4>\n
\n
<\/h3>\n
HTTPS Support<\/h3>\n
![\"rs44-encryption\"](\"\/\/www.migenius.com\/migenius\/wp-content\/uploads\/2016\/06\/rs44-encryption.png\")
<\/p>\n<\/div><\/div><\/div>\nServer-side JavaScript Command Enhancements<\/h3>\n
Configurable JavaScript Runtime Memory<\/h4>\n