Peter
Forum Administrator

www.reallusion.com

Thank you very much for addressing this. For one I have to say that I personally as a customer don't see any reason why you make this tool locked source. I don't see the secret with it. It is totally understandable that nobody can catch up with the mess the Unity Pipelines are. If you'd make it open source, we could address the problems at least ourselves in a timely manner.

What's really bothering - after you fought through setting up the materials and the open mouth - is the shoulders. They are just wrong and sticking out in Unity. It's the first what people say is just plain wrong and make the character look ugly when you show them an imported character.

                                    

Unity Virtual Reality Developer

Despite all the "we are not dropping support" it smells a lot like preparing us about dropping support for Unity.

Epic dropped the big ball with their Meta Human software and there is nothing comparable for Unity, you have the chance to take on some market shares here by making the only proper Character Creator for Unity with whatever tools and custom shaders required.
But here we'll get an outside company/individual support which is definitely not on-par with the scale and scope of your tools.

Also, reading about shader graph is quite frustrating. 
HDRP is clearly a niche solution at the moment
URP is far from being ready
I'm pretty 75% of actual Unity dev are sticking to Built-In render pipeline, if you drop the support on that, it's a huge blow.

Making the Auto setup open source is a good thing though, I hope some skilled programmer will take on that. I already created a tool for myself to clean up the textures folders (renaming/organizing) but that could be built-in a more advanced AutoSetup tool with customization upfront.

My biggest frustration at the moment is clearly not having proper Eyes and Hairs shaders. I never found any shader to re-create the nice eye-occlusion. And as for the hairs well I've been through around 12 hair shaders from the Store and from the community (git-hub etc.) and it's almost like each hair type needs a different shader.

What you need is  someone to create Hair and Eyes shaders for Unity that have similar functionalities as the Reallusion ones.
This needs to be compatible with the built-in render pipeline as well as URP/HDRP if you want to cover all bases. Many asset store creators are providing support across all three render pipeline, I hope you'll do the same.

That's a great point about shader graph only being URP/HDRP compatible. 100% agree that many devs (myself included) are sticking to built-in for a number of projects. *Please take this onboard and feedback to the relevant people @Peter

                                    

Unity Virtual Reality Developer

I have been waiting for this! Any ETA's I purchased too many Reallusion product's and I am a little disappointed with how you deal with unity.

Some of the reported problems impacting Unity look like they're not necessarily in the Auto Setup Tool part (import hooks when bringing into Unity) but with the mesh/materials/blendshapes setup that comes out of the InstaLOD bake and export.

Will you still be looking to update and correct issues relating to that, or does this new effort / direction aim to include some of that process too?

Yes, please do not forget the support for the built-in render pipeline, because most of us are using it right now. And we really would love to have hair shaders that look at least ok. And better support for Unity-ready LOD export would be great, too. Thank you!

Can i ask what is the built-in render pipeline that you mention? Thank you

https://docs.unity3d.com/Manual/render-pipelines.html
Traditionally Unity only had a single way of rendering to the screen but they then introduced the Universal Render Pipeline (URP) and the High Definition Render Pipeline (HDRP) each of which have characteristics aimed at targeting different platforms. HDRP is for high end desktops and approximates light in a more realistic way. URP is intended for low end hardware such as mobile. You can also script your own render pipeline if you so wish (and have the expertise. Very few people do this). The render pipelines have been in a constant state of flux since they were originally released as betas and many would argue that neither URP nor HDRP are quite ready for production (despite Unity's assurances) Because of this, or because we have long-term projects which we don't want to port, many of us stick with the so-called 'Built-In' render pipeline, meaning not using URP or HDRP, because of their limitations, buggyness, etc.

                                    

Unity Virtual Reality Developer