Closed ElliotWood closed 1 year ago
DrewLonMS
commented
1 year ago Hi Elliot!
Thanks for the question. We are always excited to hear what developers would like to see in Azure Remote Rendering. Please add your vote to our feedback page here: https://aka.ms/ARRfeedback.
Can you elaborate on the challenges that web support would solve?
Thanks!
ElliotWood
commented
1 year ago Thanks will do.
The challenges that web support would solve is the ability for customers to view massive 3d assets via the browser, and therefore in a contextual dashboard for the use case.
Consider industries such as Consruction who want to do building inspections, contractor scheduling and other workflow optimizations. The ideal outcome for those customers is a web-based portal where data, charts, web maps, and large 3d models are visualized all together and integrated.
ElliotWood
commented
1 year ago
Hi Team, love the library, well done.
As per title Is WebGL publish from Unity being considered? What are the current blockers or limitations?.
From the QuickStart we have a working version in Unity with WebGL as "Platform" selected
However, it only runs whilst in Unity tool and the Build step is where the errors occur due to the assemblies not currently a compile target"Assets\Scripts\RemoteRendering.cs(4,17): error CS0234: The type or namespace name 'Azure' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)"
If it's not currently on radar, would it be possible to get access under an agreement to these assemblies for a custom port.
Our goal, be able to view the outputs in a browser including interactivity. Ideally, we can look to create a binding or shim for webGL support.
Alternately, we have to put facade Unity WebGL project in front of an emulated Windows build (docker in AKS) and stream a RenderTexture over the network and relay input between the client builds. (Which feels gnarly) i.e. WebGL Build <--->Windows Build <---> ARR
Looking forward to your response.
Kind Regards, Elliot Wood