{"id":2000,"date":"2018-01-16T05:35:28","date_gmt":"2018-01-16T05:35:28","guid":{"rendered":"https:\/\/www.migenius.com\/?p=2000"},"modified":"2018-01-16T05:35:28","modified_gmt":"2018-01-16T05:35:28","slug":"whats-new-in-realityserver-5-1-update-173","status":"publish","type":"post","link":"https:\/\/www.migenius.com\/articles\/whats-new-in-realityserver-5-1-update-173","title":{"rendered":"What\u2019s New in RealityServer 5.1 Update 173"},"content":{"rendered":"

We recently released RealityServer 5.1 build 2017.173. This is mainly an incremental and bug fix release but adds some cool features some customers have been waiting for, including multiple UV sets, materials and holes for the generate_mesh<\/em> command, updated AssImp plugin, a new Smart Batch command and render loop improvements.<\/p>\n

<\/p>\n

Mesh Generator Improvements<\/h3>\n

The generate_mesh<\/em> command is extremely useful when you want to programmatically create geometry in your application. For example when creating walls for a floor plan which someone has designed in your software. However what if you want to have each wall use a different material, with different texture coordinates and have holes in the wall mesh for the windows. Previously you would need to generate separate meshes for this and manually create the holes within the polygons.<\/p>\n

With this update you can now have multiple UV coordinates for your meshes, simply by providing an array of coordinates instead of a single set. You can also add a material index to each polygon which allows the same mesh to have polygons with different materials. This can be much more efficient than defining separate meshes.<\/p>\n<\/div><\/div>

 <\/p>\n

\"Example<\/p>\n

Example with Multiple Holes, Materials and UVs<\/p>\n<\/div>\n<\/div><\/div><\/div>\n

Finally polygons can also now define holes which are automatically cut from the polygon and are tessellated for you. This is great when you need to make room for a window or cut a hole in the ceiling for a light fitting for example. You can find a simple example set of commands using the new features here<\/a>. This will create the same image as shown above and shows all of the new features.<\/p>\n

Smart Batch<\/h3>\n

Quite often when building a RealityServer application you want to execute a bunch of commands in sequence but you need to use the results of one command as input to another later in the sequence. Previously you only had two choices for this, either do multiple round trips to the server or write a server-side V8 command to encapsulate the operation. This release adds a third option, the new smart_batch<\/em> command. With Smart Batch you can do things like this:<\/p>\n

\r\n{"jsonrpc": "2.0", "method": "smart_batch", "params": {\r\n    "environment" : {\r\n      "scene_file": "scenes\/meyemII.mi",\r\n      "resolution" : { "x" : 384, "y": 384},\r\n      "iterations" : 50\r\n    },\r\n    "commands" : [\r\n      {\r\n        "name" : "create_uuid",\r\n        "id" : "uuid"\r\n      },\r\n      {\r\n        "name" : "import_scene",\r\n        "params" : {\r\n          "filename" : "${scene_file}",\r\n          "scene_name" : "${uuid}"\r\n        },\r\n        "id" : "scene"\r\n      },\r\n      {\r\n        "name" : "instance_get_item",\r\n        "params" : {\r\n          "instance_name" : "${scene.camera_instance}"\r\n        },\r\n        "id" : "camera"\r\n      },\r\n      {\r\n        "name" : "camera_set_resolution",\r\n        "params" : {\r\n          "camera_name" : "${camera}",\r\n          "resolution" : "${resolution}"\r\n        }\r\n      },\r\n      {\r\n        "name" : "element_set_attribute",\r\n        "params" : {\r\n          "element_name" : "${scene.options}",\r\n          "attribute_name" : "progressive_rendering_max_samples",\r\n          "attribute_value" : "${iterations}",\r\n          "attribute_type" : "Sint32",\r\n          "create" : true\r\n        }\r\n      }\r\n    ]\r\n}, "id": 1}\r\n<\/pre>\n
If you have ever used a templating language in JavaScript such as Handlebars or Underscore you will get the idea. You have a starting environment where you can specify variables for use in replacements later on, but the real magic happens when you add an id<\/em> to the sub-commands. This causes their results to get added to the environment so you can access them in future commands. The final environment is also returned by the command at the end.<\/p>\n
You’ll notice you can also use dot notation<\/em> to access members of the variables during replacement. It’s also clever enough to work out when you want to replace your string with a full object or other type. One powerful use case for this new command is creating templated snippits in your application code which you can easily just change the environment on and resend. We have already been using this command heavily on our own applications.<\/p>\n
While you could use the multiple round trips or V8 command options, there are many use cases where a Smart Batch would be preferable. If you need branching, loops and other advanced functionality then you will still need to do a V8 command but for many things a Smart Batch will do the job better. One final thing to note, you should not use smart_batch<\/em> with commands that return binaries such as the render<\/em> commands. For more details, refer to the RealityServer Features<\/em> section under Getting Started<\/em> in the RealityServer Document Center.<\/p>\n
AssImp 4.1.0<\/h3>\n
The fantastic AssImp<\/a> project recently released their 4.1.0<\/a> update. We have incorporated this into our importer\/exporter plugin so we inherit the new features such as 3MF export and glTF 2 support for import and export. There are also plenty of bug fixes in the new release, check out the projects release notes<\/a> for more details.<\/p>\n
Render Loop Improvements<\/h3>\n
The default<\/em> and simple<\/em> render loop handlers now allow you to change the renderer between Iray Photoreal and Iray Interactive on the fly, without restarting the render loop. All you have to do is set the renderer<\/em> parameter with\u00a0render_loop_set_parameter<\/em> just like any other parameter. A new update_scene<\/em> parameter has also been added so you can inform the render loop if you change the camera instance or options used in a scene, previously these were not picked up and caused issues.<\/p>\n
Iray Version Bump<\/h3>\n
Upgraded to Iray 2017.1.2, build 296300.3713 which contains mainly bug fixes, including a fix for a performance regression for certain simple scenes with uniform lighting. Checkout the neurayrelnotes.pdf file in your RealityServer installation for more details.<\/p>\n
Introspection of Structures and Enums<\/h3>\n
The internal API of RealityServer has built in and user definable Structures and Enums (defined with IStructure_decl and IEnum_decl). We have now added a new command type_get_declaration<\/em> to allow introspection of these types. This is helpful when building user interfaces that might need to understand how these types are defined. For example the built in Approx<\/em> structure attribute used to define tessellation.<\/p>\n
Aways Read the Release Notes!<\/h3>\n
There are several other fixes both in RealityServer and Iray so always read the full release notes and Iray release notes.<\/p>\n","protected":false},"excerpt":{"rendered":"
We recently released RealityServer 5.1 build 2017.173. This is mainly an incremental and bug fix release but adds some cool features some customers have been waiting for, including multiple UV sets, materials and holes for the generate_mesh command, updated AssImp plugin, a new Smart Batch command and render loop improvements.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"spay_email":"","jetpack_publicize_message":"See what\u2019s New in RealityServer 5.1 Update 173.","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true},"categories":[15],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/posts\/2000"}],"collection":[{"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/comments?post=2000"}],"version-history":[{"count":12,"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/posts\/2000\/revisions"}],"predecessor-version":[{"id":2016,"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/posts\/2000\/revisions\/2016"}],"wp:attachment":[{"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/media?parent=2000"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/categories?post=2000"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.migenius.com\/wp-json\/wp\/v2\/tags?post=2000"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}