Plugin updates for Unity 2018.3, multiple HDA inputs, custom pipelines/shaders

   3276   3   1
User Avatar
Member
571 posts
Joined: May 2017
Offline
There have been a number of updates to the Unity plugin in the last couple of days. I'd thought it would be good to point them out in case you have been waiting for these, and to get feedback. These should all be in the latest daily builds.

Unity 2018.3 Support
The plugin should be compatible with Unity 2018.3b. This includes updates to support the changes in prefabs and terrain in Unity 2018.3. Specifically, updated Unity API calls for prefab creation and modification, as well as creating the new terrain layers for heightfields.

Fixed baking issues for meshes, and creating proper nested prefabs when using instance inputs that are prefabs.

Updated UI for Unity 2018.3 editor changes.

Custom Default Shaders
This was intended to support the new Scriptable Render Pipelines. Since the APIs to create and manage materials and shaders for these are not yet finalized or even available in some cases, the workaround for the plugin was to allow to set the default shaders used when creating the materials. In the Plugin Settings window, you can now change the default shaders under the Geometry section. For example, to use the default LWRP shader, change Default Standard Shader to Lightweight Render Pipeline/Lit.

Multiple input HDAs
Added support for specifying multiple input HDAs for object merge path parameter. Previously only one HDA was allowed. HDA inputs also now expose and support the Keep World Transform and Packed Primitive options that regular mesh inputs had.

Other fixes and changes
Added support for outputting convex colliders.

Fixed editing rotated curve's points, and mouse jumping while editing.

Fixed Plugin Settings window trying to update after being closed or disabled on scene refresh.

Fixed bug where loading preset with inputs objects that weren't root objects in scene failed.

Fixed painting and editing nodes failing on uploading attributes.


Changelog here: https://www.sidefx.com/changelog/?journal=17.0&categories=25&body=&version=&build_0=&build_1=&show_versions=on&show_compatibility=on&items_per_page= [www.sidefx.com]
Edited by seelan - Dec. 14, 2018 16:44:11
User Avatar
Member
5 posts
Joined: Nov. 2015
Offline
Hi Seelan,
Is the last Houdini 16.5 update supporting Unity 2018.3.0f2 ?

I am currently using 16.5.663. It worked until 2018.3.0f1 (with a few instabilities but still usable), but with 2018.3.0f2 (shipped today) I can't use the Unity Asset/Mesh input anymore.

Edit: Solved. I just saw the last entry in the 16.5 log : https://www.sidefx.com/changelog/?journal=16.5&categories=25&body=&version=&build_0=&build_1=&show_versions=on&show_compatibility=on&items_per_page= [www.sidefx.com]
Edited by Valentin BESSON - Dec. 13, 2018 16:33:41
User Avatar
Member
28 posts
Joined: March 2015
Offline
Hi,

It's cool to be able to define custom default shaders, but is there a way to define a custom default shader for Terrains to use in LWRP or HDRP?

And talking about terrains, when do you plan to support the new Unity terrain (Terrain instanced rendering checkbox)?

Thanks a lot!

Alex

Attachments:
2019-04-30 16_51_45-.png (11.2 KB)

User Avatar
Member
571 posts
Joined: May 2017
Offline
chekboom
Hi,

It's cool to be able to define custom default shaders, but is there a way to define a custom default shader for Terrains to use in LWRP or HDRP?

And talking about terrains, when do you plan to support the new Unity terrain (Terrain instanced rendering checkbox)?

Thanks a lot!

Alex

Hi Alex,
Both of your requests are great, and I've added RFEs for them. I'll update this thread when they are in.
  • Quick Links