You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common usecase for the WebRenderer is to have a webpage available as a Stride Texture somewhere in a 3D Scene.
Transformation (Rotation, Scaling, Position) might change over time. (Think of a cover flow e.g)
It has been a pain since ever in beta to tranform the mouse/touch tranforms according to the object (and camera) transforms and keep the WebRenderer in a working status. Especially when dealing with multiple resolutions and window sizes.
whats needed: A simple best practice to make sure the touch/mouse nodes are always working on a WebRenderer (no matter how its transformed). This might be something like a custom context.
Any ideas here?
The text was updated successfully, but these errors were encountered:
Idea is to create a help patch showing this. But in order to create that help patch we first need to cook up some sort of input injection nodes for Skia and Stride. This is independent of CEF. Will report back here once we have something useful.
A common usecase for the WebRenderer is to have a webpage available as a Stride Texture somewhere in a 3D Scene.
Transformation (Rotation, Scaling, Position) might change over time. (Think of a cover flow e.g)
It has been a pain since ever in beta to tranform the mouse/touch tranforms according to the object (and camera) transforms and keep the WebRenderer in a working status. Especially when dealing with multiple resolutions and window sizes.
whats needed: A simple best practice to make sure the touch/mouse nodes are always working on a WebRenderer (no matter how its transformed). This might be something like a custom context.
Any ideas here?
The text was updated successfully, but these errors were encountered: