I am experimenting with the viability of displaying a perspective screen on a web browser through a google home TV Chromecast.
Currently the home TV is connected to a wireless AP that is attached to a local network. Everything is working fine but the more you load the screen up with assets/graphics the more it lags and becomes unusable. If you dont intend to change the screen with a remote it works fine.
When you try to move around the screen with the hand held remote it lags like hell. Tried it on a few different browsers within the Chromecast same thing.
I would of thought the home TV would be able to manage a perspective screen?
Any thoughts or recommendations for people who had tried this before?
Like with most things, adding more and more will result in reduced performance. A 60Hp car will have more trouble going up a steep hill than a 200Hp car.
Without knowing the specs of your TV it is difficult to say, but each of those assets/graphics requires memory and processing power to load it in. It is likely that the TV's specs are just struggling with what you're trying to throw at it. TVs typically don't have particularly powerful hardware.
Does it lag on your PC/laptop? Have you optimised any bindings/script transforms etc? Can the view be changed to use fewer assets?
Its just a 23inch PC screen ($20) with a Google Chromecast Home TV ($30 - Plugs into a TVs HDMI port) Did a bit more investigating and it appears the stock animations from the components in perspective destroy any performance, i assume all animations really. I set the animation speed to 0 on my pumps/fans and the screen operates lag free. This was a viability experiment to see if i could just drop a screen and a Chromecast (A $60 solution) anywhere in the plant in range of a wireless AP to display a perspective screen of any size.
It does not lag on my development PC in the browser. I guess Chromecast & their built in web browsers don't like perspective animations all that much.
It still achieves its purpose without any animations.