Home › Forums › General Questions › Regarding CSS 3D Renderer feature in New Verge
- This topic has 6 replies, 3 voices, and was last updated 2 months ago by
visualizer.
-
AuthorPosts
-
2025-06-25 at 5:35 pm #82566
visualizer
CustomerHi
After reading the update list of New Verge I came across the integration of CSS3D render.
I am still wondering if any specific example / sample can be made to understand the difference between CSS3D integration & HTML mixer sample.
Secondly is it possible for integrating the camera feed as video onto any plane in published scenes? similar like Youtube?2025-06-26 at 6:02 am #82576Alexander Kovelenov
StaffHi,
The former HTML mixer used custom JavaScript code, while the new one uses similar logic, but integrated in the engine core and puzzles. The difference is mostly about usability (though we made several important improvements which were missing in the original demo).
Regarding what’s possible with this new feature. Just everything! Pages, videos, custom video feeds, chats, you can even integrate an existing Verge3D app into the plane rendered in the other app. The idea is simple. If you something accessible with public URL, just insert the URL into the “create object” puzzle. If you want to make custom UI, place it in the separate HTML and provide the name of it into the same URL input.
2025-06-26 at 2:38 pm #82592Thomas Fabini
CustomerHi Alexander,
would it be conceivable feeding the CSS 3D Renderer dynamically generated html content (e.g. with puzzles / scripting) instead of an url / filename?
For now, all (VR) UI elements have to be build and rendered as canvas elements. Simple ones with puzzles, more complex ones with scripting. Alltough this approach is not that limited it’s a huge effort. If the CSS 3D Renderer would prove able to provide rendering of dynamically generated content it could be a game changer.Btw. thank you very much for the Precise Referencing in Dynamic Scenes in 4.10 pre2.
That’s a wall I’ve hit before for which I currently use a scripted solution, same as for name filtering. These might be obsolete with the release of 4.10.2025-06-27 at 5:42 am #82607Alexander Kovelenov
StaffHi,
With JavaScript it’s possible to feed any HTML element to the CSS 3D Renderer, however we intentionally made the “create object” / “plane with html” puzzle simpler by restricting its input only with page URL. However, it does not mean the developer can’t create a custom UI inside the separate page and provide this page to the puzzle.
As for VR, unfortunately this feature won’t work, since the rendering is provided by the browser itself, just like for any other HTML elements. For VR it’s still required to design custom UI in the modelling suite.
Regarding object referencing, indeed that’s was our idea to eliminate complex hacks and make cloned/dynamically loaded objects easily available!
-
This reply was modified 2 months ago by
Alexander Kovelenov.
2025-06-27 at 6:51 am #82609Thomas Fabini
CustomerThanks for the clarification Alexander, I almost hoped this would be the Holy Grail of VR UI creation.
2025-06-27 at 7:10 am #82615Alexander Kovelenov
Staff2025-06-27 at 9:24 am #82628visualizer
CustomerYes Alexander,
Even I was wondering if this works in VR as well. -
This reply was modified 2 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.